Peter Haworth wrote:
Thanks for the pointer to the stackFiles property. That certainly makes life easier but it still seems to defeat one of the purposes of having a central code library in that there's a copy of the the library in every app I write instead of it being in one central location and accessed from that location by any app.
The idea behind libraries is that you only have to maintain a single code base, which can be re-used anywhere. But each app still needs to have copy, or at least access to a copy. Some apps, like Adobe, store a single copy of their libraries in a central location like Application Data, and all their apps point to and use it. You could do that too if you want, though most of us don't. But there's nothing that says you can't store your library stack in Application Data and "start using" it on startup. A library doesn't have to be in the same place as the app, as long as you know where it is located you can open and use it. You'll have to overwrite it if it changes though, which isn't necessary of you just ship the library along with the standalone.
More commonly, a library is stored inside the standalone as a substack. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
