On 07/12/2012 10:46 AM, totty wrote: > thanks, that's just perfect ;) > > I would like to know if it's also possible while compiling with > source-hybrid including all the qooxdoo files and not only the one used
Well, that was your original question, wasn't it?! You wanted to include *all* classes, so that also covers the qooxdoo framework library, right?! Daniel's answer already took care of that. > and > not to compile them everytime, just once, as they never change (until I'm > changing the qooxdoo version). In this way compiling would be very very > fast, because only had to compile the user code. For a source* version this doesn't apply, as only uncompiled source files are used. For a build version (or a source-hybrid with optimizations), this is what already happens. If you don't change the compile options, or the environment settings, in your config.json (or run a 'generate.py distclean' which clears the entire compile cache), the framework classes are never re-compiled. T. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
