On Thu, 21 Jul 2011, thron7 wrote: > On 07/21/2011 07:52 AM, Fritz Zaucker wrote: >> Ok. It might be worth mentioning somewhere in the docu, as the default OS >> tmp dir might be on a RAM disks that usually is not that huge. > > Good point. Please open a bug for it.
Bug 5430 >> I guess this would mean if I don't fiddle with config.json, those parameters >> should be the same. > > Correct. Bear in mind though that even introducing "environment" > settings in the config changes the variant when creating the build version. Ok. >>> But keep in mind that sharing is not only between different apps, but also >>> between different builds of the *same* application. This is another >>> important aspect of sharing. Re-building the same app would be much slower >>> without the cache. >> Isn't this the main (if not only) purpose of the cache? That's why I don't >> want to loose it at reboot (I have almost 3 minutes for a build with clean > > It's certainly the more important aspect for most users. We're not (yet ) > ;in the era where most people work on 3-5 qooxdoo projects at the same > time. We have a few applications out in the wild by now and it is common to fix/improve things in various places. So I'll be happy if the apps can benefit from each other populating the cache. > - We, on the other hand, are constantly re-generating our standard apps > during development (feedreader, playground, demobrowser, ...), and to us > it matters *a lot*. It is probably not the only feature that was > introduced with our own benefit in mind :). Eat your own dog food is always good ... ;-) >> cache and about 6 seconds thereafter; a really big improvement, even if most >> of the development work can be done with the source version). > > Don't be deceived! With an empty cache generating the source version of > an app is not dramatically faster than creating its build version (if > you compare raw source-script/build-script performance). The main > performance hog is not the compile step, where the build code is > compressed, optimized and written to disk, but the code analysis for > dependencies, resource needs, etc., basically: calculation of lists. And > this is done in the source version just as well. Yes, I realize that. What I meant is that most of the time I don't have to re-build at all as I don't add new framework classes. And the source-hybrid option improved that A LOT! Cheers, Fritz -- Oetiker+Partner AG tel: +41 62 775 9903 (direct) Fritz Zaucker +41 62 775 9900 (switch board) Aarweg 15 +41 79 675 0630 (mobile) CH-4600 Olten fax: +41 62 775 9905 Schweiz web: www.oetiker.ch ------------------------------------------------------------------------------ 5 Ways to Improve & Secure Unified Communications Unified Communications promises greater efficiencies for business. UC can improve internal communications as well as offer faster, more efficient ways to interact with customers and streamline customer service. Learn more! http://www.accelacomm.com/jaw/sfnl/114/51426253/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
