Dialogs in library organization
rcozens at pon.net
Wed Feb 4 14:11:54 CST 2004
>However there will be cases in which I (or others) will need to use
>these libraries in building a monolithic standalone application and
>I need to ponder the implications.
There is one issue of which I am aware and for which I have no a
sharing library handlers that manipulate declared local variables.
Ideally, one could place a library stack on a network and have its
resources available to every Revolution standalone running on the
network. This will not work for SDB client standalones, because SDB
handlers in the library stack expect the values in the library's
declared local variables to persist between calls.
To this point I've just shrugged it off with "OK, each SDB client
standalone will have to have its own library stack." However a
solution to this issue would be really slick: imagine updating the
operation of every Revolution standalone on every workstation on the
network by changing a single handler & resource library stack on one
CCW, Serendipity Software Company
"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."
from "The Triple Foole" by John Donne (1572-1631)
More information about the use-livecode