Hi Derrell, > The distinction is between "make source" and "make build" (assuming you're > using the Makefile system). The former generates a custom.js (or whatever > name you choose to give it) that just brings in all of the individual files by > adding a copious number of <script src="..."> tags. The latter creates a > custom.js file that itself includes all of the necessary classes, avoiding the > need to add any <script> tags to bring in additional files. > > If you're not using the Makefile system, then you'll want to look here: > > http://qooxdoo.org/documentation/user_manual/custom_builds > > Unless that page has been updated, I believe there are some differences > between what was documented and what exists in svn at the current time. You > may need to ask some questions of Sebastian and Fabian, but at least that > should explain what you need to know. > > Whether documented or now, there is an option (as used by the Makefile) to > include only those classes from the framework and your skeleton-derived source > that are actually used. > > This is actually the dafault for "make build". The build contains only the needed JavaScript files. It can be controlled by these Makefile variables:
APPLICATION_COMPLETE_SOURCE // default: true APPLICATION_COMPLETE_BUILD // default: false Best Fabian ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
