2011/2/27 thron7 <[email protected]>: > > With trunk of last Friday night there is a new and working 'source-hybrid' > job which you can run on your application. It doesn't match your spec > exactly, though, as the "compiled" files are just a cat of source class > files. But I plan to add compiling those files to their optimized version. > If you are just concerned about the loading time of your source version, > you will find the source-hybrid version a *lot* faster than the classical > source version. >
Hi thomas, thanks for helping me out, again :) Do I need to switch to trunk for this to work or can I just rip some scripts? If not, how stable is trunk at this moment, or when is a new release planned containing these improvements? > The .js files generated by the current source-hybrid job does not sort the > classes by library (that would defeat other constraints), so you won't get > a pure "qx.js" which consists only of all the required framework classes. > I don't know how hard this requirement is for you, but if you insist on > having a pure (and potentially optimized) qx.js, you currently have to > create it in a separate job. The framework's config.json has a (commented > out :) "build" job which you could use as a template. This then generated > qx.js you could use in your application adding it to e.g. the source build > with the "add-script" config directive. But you have also to exclude any > framework classes in such a job, to take advantage of your custom qx.js. > Check the mailing list archives for multiple discussions of this topic. > a pure qx.js isn't a strict requirement, any optimization is welcome. > I'm not sure what you mean with server root setup, but I presume you want > to run this hybrid version through a web server. Well, as far as code is > concerned a source-hybrid version is self-contained, but not as far as > resources are concerned. So to have a running application with all images > etc. you still have to obey the rules for running source versions from a > web server (e.g. as described in [1]). > I'm familiar with [1]. I've also tried to understand [2] but it didn't make much sense. I have some specific demands because I'm trying to somehow package the whole qx application and its dependency in a more-or-less distributable (python) package, from which I want people to be able to easily generate whatever is necessary, possibly both a source and buildversion, both of which can be deployed by my (server) application. >> I find the documentation very hard to comprehend, it seems to assume >> you already know how the system work. > > Which documentation are you referring to? But generally speaking I agree > with you, there is e.g. no tutorial on tweaking the generator config. You > might want to consider opening an enhancement bug for this. > The documentation I've been looking at is http://manual.qooxdoo.org/1.3.x/pages/tool/generator_usage.html and everything it refers to. Regards Ivo [1] http://qooxdoo.org/documentation/general/snippets#running_a_source_version_from_a_web_server [2] http://qooxdoo.org/documentation/general/snippets/setting_a_different_application_root -- Drs. I.R. van der Wijk / m3r Consultancy B.V. Linux/Python/Zope/Plone and Open Source solutions PO-box 51091, 1007 EB Amsterdam, The Netherlands Email: ivo <at> m3r.nl Web: http://m3r.eu/ ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
