Right... You create a build that contains ONLY the library items you're going to use, all in a single JS file. That's the file that then gets downloaded by the end user. It doesn't dynamically build the file for the user at runtime though.
andy -----Original Message----- From: Jim Davis [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 11, 2007 12:59 PM To: CF-Talk Subject: RE: too many js libraries > -----Original Message----- > From: Andy Matthews [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 11, 2007 12:49 PM > To: CF-Talk > Subject: RE: too many js libraries > > He's talking about downloading the code in production to the client > computer. You're talking about a "build" for the developer Jim. No - it's actually both, I'm nearly positive. MooTools lets you say "I only used these tools/methods/functions, create me a customer library that only includes those." This is then the file that gets downloaded by the end user in production. Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 and Flex 2 Build sales & marketing dashboard RIAâs for your business. Upgrade now http://www.adobe.com/products/coldfusion/flex2?sdid=RVJT Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:283492 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
