Either that or having the possibility to choose which substacks to include in the application and which substacks to save as individual stacks would help.
Tore > 6. feb. 2015 kl. 23.11 skrev Mike Bonner <bonnm...@gmail.com>: > > DOH, thats what you said above, though this might be a good time for a > feature request. It would be nice if inclusions were searched for BEFORE > the option to disconnect substacks into seperate stack files, it would make > building splashstack. > > On Fri, Feb 6, 2015 at 2:32 PM, Mike Bonner <bonnm...@gmail.com> wrote: > >> Tore, read this. >> http://lessons.runrev.com/m/datagrid/l/7339-what-do-i-need-to-do-to-deploy-a-standalone-with-a-data-grid >> >> Specifically the part of bulding with a datagrid using a splashstack. The >> easiest way to get functional datagrids that are parts of seperate stack >> files is to incuded a single substack in your main that is named "datagrid >> templates dud" so that the builder will decide to include all the datagrid >> support libraries. More detail available in the link from above. >> >> On Fri, Feb 6, 2015 at 2:27 PM, Tore Nilsen <tore.nil...@me.com> wrote: >> >>> The problem with letting the compiler handle this is that I cannot access >>> the Data Grid Template stack from the main stack if it is not a part of the >>> engine file. The standalone setup dialog is somewhat confusing in the sense >>> that it seems as if it is possible to choose which substack files to >>> include with the engine file and which substack files to branch out in a >>> folder of its own. As far as I have discovered it is all or nothing. I >>> guess I will have to dive into the code of the main stack again and write >>> relative paths to all the stacks I don’t want to be a part of the engine. >>> Luckily there are not very many of them, and they are not called from more >>> than a couple of handlers. >>> >>> Tore N >>> >>> >>>> 6. feb. 2015 kl. 22.17 skrev Bob Sneidar <bobsnei...@iotecdigital.com>: >>>> As mentioned in the past, the easiest way around this is to have a >>> mainstack that calls your actual application stacks. Password protect the >>> app stacks if you like to protect the code. That way the app stacks are not >>> actually a part of the read-only application, they are like support files >>> that can be modified if put in the right place, which the compiler does for >>> you. >>>> >>>> Bob S >>>> >>>> >>>> On Feb 6, 2015, at 12:47 , Tore Nilsen <tore.nil...@me.com<mailto: >>> tore.nil...@me.com>> wrote: >>>> >>>> I am using several Data Grid objects, as tables, in a standalone. When >>> I try to manually enter data into fields in the data grid object it works >>> alright as long as the main stack and the substacks are built as a single >>> file, but not when I try to build the standalone with the substacks as >>> separate files. I guess the reason is that the main stack loses connection >>> with the Data Grid Template stack once this is moved into a separate file. >>> I would however prefer to have the substacks as individual files in order >>> to be able to upgrade them easily, without the need for an upgrade of the >>> application as such. Are there any solutions to this problem that does not >>> require a total rebuild of the application structure. >>>> >>>> Tore N >>>> ____________ >>>> >>>> _______________________________________________ >>>> use-livecode mailing list >>>> use-livecode@lists.runrev.com >>>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >>> >>> _______________________________________________ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >> >> > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode