>I want to set up a stack that centralizes all my most >useful functions. What's the best way to include these in the standalone >when I'm ready to build it? Is there an easy way to include only the >functions that the stand-alone will need?
Hi Doug, A. You can distribute the library as a separate stack, which allows you to update the library in the future without having to build a new distribution, or B. You can include the library as a substack within the stand-alone, which means the library can't get separated from the rest of the app or be viewed by the user. If it's a general-purpose library of Transcript handlers, I wouldn't worry about optimizing a different library for each application. OTOH, if it's a library of .jpeg images, sounds, or other memory hogs, I would consider creating an optimized library sans unnecessary objects. You may also work the other direction: create a clone of your general library and add to it resources specific to each standalone you create. -- Rob Cozens CCW, Serendipity Software Company http://www.oenolog.com/who.htm "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) _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution