On Fri, Sep 18, 2009 at 08:34, Jean-Baptiste BRIAUD -- Novlog <
[email protected]> wrote:
> 4 : use qxbuild : you will just have to include a big js file and you
> are at very few minutes from your previous js tested in the
> playground. You can enjoy qooxdoo power but ok, files are big. At that
> time, it is not important, its not deployed on production, isn't it ?
>
I _think_ there is a misunderstanding here, partly mine, and partly the
folks who are using qxbuild. The playground application produces a large
"library" containing every class available in qooxdoo. That's how it is able
to immediately execute any code typed in. I haven't looked at how that large
library is built, but it seems to me that whatever it is does exactly what
the qxbuild folks have been clamoring for. (The playground application
actually "links" the library with application code that allows entering the
code and producing the resulting page, but that should be pretty easily
detachable.)
This seems a trivial packaging issue. (Nothing is ever as trivial as it
seems, though.) Andreas et al, could this be easily provided as a part of
each release to allow for immediate development with a complete library?
Derrell
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
