Andrew, Why not stick to the main stack/ substacks paradigm? It will be a lot easier in dealing with paths and can still act like a single application. A lot of people will do this even with one stack (i.e. a splash screen stack gets built as the standalone and then all substacks stay as stacks. The benefit here is also that any changes while running the application will 'take' in a seperate substack of a compiled main stack.) Otherwise, every stack will have to find every other stack via file paths....
HTH,s Tom McGrath III Lazy River Software [email protected] iTunes Library Suite - libITS Information and download can be found on this page: http://www.lazyriversoftware.com/RevOne.html On Feb 10, 2010, at 12:06 PM, Andrew Kluthe wrote: > > I haven't built the Main Stack yet but am building LeaseStack to be shown to > my supervisor to show him Rev's capabilities. This is one of Many > modules/stacks that are to be used by the Mainstack when i write it. > > Can I write LeaseStack and add it to MainStack as a sub-stack later? Not a > lot of data is going to be passed from Main to the different Module stacks. > Most of them are going to be near stand-alone (my boss has a dream of > charging differently for versions that include other tasks/modules/stacks). > -- > View this message in context: > http://n4.nabble.com/Noob-Stacks-Questions-tp1476073p1476114.html > Sent from the Revolution - User mailing list archive at Nabble.com. > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
