Björnke von Gierke
bvg at mac.com
Thu May 8 08:18:45 EDT 2014
I really would love to hear your reasoning about why start using (library) is not what you want to use (or it's brethren front script and back script).
Alternatively there's of course using 'send' and 'call' (more modern 'dispatch'), instead of relying on the natural order of the message path.
There's also behavior scripts of course, but I think they're more useful for repetitive handlers, not for different calls to a database, but someone who actually likes them should probably talk about wether they're appropriate or not.
If you want to go super crazy you can also do it like I did, and use sockets to have the db run in another program... but that's of course a different topic ;)
On 08 May 2014, at 13:28, Terence Heaford <t.heaford at btinternet.com> wrote:
> I have been reading up on Library Stacks but in this instance I do not feel this is the solution I require.
> I have a Project that needs access to a SQLite database and has many calls into that database from functions and commands which at the moment I have placed in the mainstack script.
> In order to make the script more manageable I would like to have the SQLite scripts modularised and separate from any other scripts in the mainstack which I also may wish to modularise at some point.
> I have placed all these scripts together in the mainstack to allow them to be easily called from all other parts of the project and to have easy access to user properties of the mainstack.
> What is the best way to achieve this type of modularisation within the LiveCode IDE?
> All the best
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
Anyone thinking about going to Zurich in the summer?
Please fill out the form and send me an email:
Use an alternative Dictionary viewer:
Chat with other RunRev developers:
More information about the Use-livecode