Coming from the world of FileMaker where a window can look into virtually anything, am I correct in understanding that with RR a window looks only into a specific stack?
I can't have separate windows for card 1 and card 2 in the same stack?
Didn't see a clear yes/no on this in the docs but my current assumption is the answer is "no".
This isn't a killer issue for me, but, just want to be sure I got it right.
Thanks.
Bill
one window per stack?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Hi Bill,
If you have a need to view two different cards of the same stack in two different windows, you probably have a flaw in your interface design. try changing your design.
For example, cards are not meant for keeping data. You keep data in files, custom properties and other containers. You should not try create say 1000 cards for a database with 1000 records. You might be tempted to do this, because it "looks" like Filemaker does it that way --but Filemaker doesn't!
Instead, create a viewer stack for the data, which retreives the data from a file, custom property, or other container, and displays it. If you want to display two records at the same time, you could clone the viewer and display the second "card" in a clone of the original stack.
When you close the application, you delete all clones and keep the original viewer stack.
Keep in mind that FileMaker has no stacks and substacks and uses completely different approach, incomparable with Revolution, although you can make something in Revolution that is comparable with Filemaker.
Best,
Mark
If you have a need to view two different cards of the same stack in two different windows, you probably have a flaw in your interface design. try changing your design.
For example, cards are not meant for keeping data. You keep data in files, custom properties and other containers. You should not try create say 1000 cards for a database with 1000 records. You might be tempted to do this, because it "looks" like Filemaker does it that way --but Filemaker doesn't!
Instead, create a viewer stack for the data, which retreives the data from a file, custom property, or other container, and displays it. If you want to display two records at the same time, you could clone the viewer and display the second "card" in a clone of the original stack.
When you close the application, you delete all clones and keep the original viewer stack.
Keep in mind that FileMaker has no stacks and substacks and uses completely different approach, incomparable with Revolution, although you can make something in Revolution that is comparable with Filemaker.
Best,
Mark
The biggest LiveCode group on Facebook: https://www.facebook.com/groups/livecode.developers
The book "Programming LiveCode for the Real Beginner"! Get it here! http://tinyurl.com/book-livecode
The book "Programming LiveCode for the Real Beginner"! Get it here! http://tinyurl.com/book-livecode
Thanks, but, I only mentioned FMP with respect to its ability to have multiple windows point to virtually anything. I realize that data will be stored in an external source (except for small chunks of data).
Yes, having two windows which use the same layout (e.g. card) to view two different records from an external data source is one example of what's required here. So, I would clone the layout/card and put it in a different sub-stack and then just have the two diff. stacks open in two diff. windows?
The only problem with this is UI maintenance, both during development and afterwards. Having multiple different iterations of the same layout/card becomes a chore to maintain. I thought this was supposed to be MORE of an object based development environment than FMP?
I'm not exactly sure why from a design standpoint it's necessary to restrict a stack to a single window.
Yes, having two windows which use the same layout (e.g. card) to view two different records from an external data source is one example of what's required here. So, I would clone the layout/card and put it in a different sub-stack and then just have the two diff. stacks open in two diff. windows?
The only problem with this is UI maintenance, both during development and afterwards. Having multiple different iterations of the same layout/card becomes a chore to maintain. I thought this was supposed to be MORE of an object based development environment than FMP?
I'm not exactly sure why from a design standpoint it's necessary to restrict a stack to a single window.
Mark wrote:Hi Bill,
If you have a need to view two different cards of the same stack in two different windows, you probably have a flaw in your interface design. try changing your design.
For example, cards are not meant for keeping data. You keep data in files, custom properties and other containers. You should not try create say 1000 cards for a database with 1000 records. You might be tempted to do this, because it "looks" like Filemaker does it that way --but Filemaker doesn't!
Instead, create a viewer stack for the data, which retreives the data from a file, custom property, or other container, and displays it. If you want to display two records at the same time, you could clone the viewer and display the second "card" in a clone of the original stack.
When you close the application, you delete all clones and keep the original viewer stack.
Keep in mind that FileMaker has no stacks and substacks and uses completely different approach, incomparable with Revolution, although you can make something in Revolution that is comparable with Filemaker.
Best,
Mark
Last edited by billworld on Sat Nov 01, 2008 10:50 pm, edited 1 time in total.
Allow me to follow up saying that I'm fully aware that from a programmatic standpoint it's imperative that cards have a unique existence and thus you can't have two cards with the same name visible concurrently. However, each instance would be in a unique window and differentiation by WindowID can still keep the card instances unique.
But there's likely gobs of legacy code (and thinking) which would prevent this from ever flying.
It's just, to be a truly object independent environment, a single design should be able to be referenced from multiple windows without having to physically copy the design.
But there's likely gobs of legacy code (and thinking) which would prevent this from ever flying.
It's just, to be a truly object independent environment, a single design should be able to be referenced from multiple windows without having to physically copy the design.
billworld wrote:Thanks, but, I only mentioned FMP with respect to its ability to have multiple windows point to virtually anything. I realize that data will be stored in an external source (except for small chunks of data).
Yes, having two windows to which use the same layout (e.g. card) to view two different records from an external data source is one example of what's required here. So, I would clone the layout/card and put it in a different sub-stack and then just have the two diff. stacks open in two diff. windows?
The only problem with this is UI maintenance, both during development and afterwards. Having multiple different iterations of the same layout/card becomes a chore to maintain. I thought this was supposed to be MORE of an object based development environment than FMP?
I'm not exactly sure why from a design standpoint it's necessary to restrict a stack to a single window.
Mark wrote:Hi Bill,
If you have a need to view two different cards of the same stack in two different windows, you probably have a flaw in your interface design. try changing your design.
For example, cards are not meant for keeping data. You keep data in files, custom properties and other containers. You should not try create say 1000 cards for a database with 1000 records. You might be tempted to do this, because it "looks" like Filemaker does it that way --but Filemaker doesn't!
Instead, create a viewer stack for the data, which retreives the data from a file, custom property, or other container, and displays it. If you want to display two records at the same time, you could clone the viewer and display the second "card" in a clone of the original stack.
When you close the application, you delete all clones and keep the original viewer stack.
Keep in mind that FileMaker has no stacks and substacks and uses completely different approach, incomparable with Revolution, although you can make something in Revolution that is comparable with Filemaker.
Best,
Mark