Hi,

I'm just getting started with qooxdoo development. I'm exploring if it
can be used for a project I'm working on.
However, I find the whole tooling/scripting/configuration chain around
qooxdoo rather confusing and unstructured. It probably makes sense
once you get the hang of it, but I just want to build UI's, not write
configurations and run scripts generating tons of stuff I have no
clear insight into.

For example, because I need everything to be served by my application
server to avoid cross domain request issues, I had to mess with
config.json which I found rather unclear. Eventually it turned out
that I just need to reconfigure the URI for jobs -> libraries ->
library -> <qooxdoo>Manifest.json, I still have no clear idea what the
purpose of compile-options -> uris is.

But that part's been solved for now - I can serve qooxdoo directly
from my application server, or directly through apache. However, now
it turns out that, in my development/source setup, qooxdoo is loading
over 500 (different) files. An due to the caching parameter,
duplicates are loaded as well. This means it takes over a minute to
"load" my trivial application, which is too long for development.

So, what am I missing here? What does a decent (non-fs based) qooxdoo
development setup look like? Which docs did I forget to read / fail to
find?

Regards

Ivo van der Wijk


-- 
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/

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to