I guess it depends on if the library is for yourself, or others. In the past, I've created an autoinstaller which intalled the requisite stacks into a users main stack. Or, of course you can 'start using' your library as it's own.
Another option, and one which I think could be a good idea is 'suck-up/spit-out' where you unpack the stacks in memory when the library is initilized. This has the advantage of being able to work as a substack of a mainstack. -C _______________________________________________ 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
