Jean-Baptiste,
you can build your libraries yourself :) . Please find attached two files.
One is a custom config file (It is actually pretty similar to what Petr
posted). Drop it into the "framework/" folder of
your qooxdoo SDK and run it like this:
./generate.py -c jean-baptiste.json qxlib-debug (or: qxlib-optimized)
This will create a "build/" subdirectory for the two library variants,
and all resources nearby (for your final applications you'll need the
resources too, for proper functioning). If you look into the config
file, you will find that the two jobs do not differ much. Both resulting
libraries (script/qx-debug*.js and script/qx-optimized*.js) include all
the qooxdoo framework classes apart apparently unnecessary namespaces
like qx.legacy and qx.test (I also had to exclude qx.ui.progressive, due
to an incompatibility with qx.ui.table which I deemed more important to
have). So they contain little over 400 classes.
The other attachment is an index.html. Please drop it into the new
"build/" folder and open it in your browser. It will load the debug
variant by default, and it also shows you how to make use of such a library.
HTH. Let us know how things proceed on your side.
Thomas
Jean-Baptiste BRIAUD - Novlog wrote:
Thanks for all your help, I really apreciate.
I do not need it fast, I'm still playing with qooXdoo as I'm in the
process of choosing a framework.
I really had to evaluate the possibility of using qooXdoo in our
product and thanks to your help, I got my answer : it is possible
because the "Python machinery" is only a matter of packaging for
qooXdoo.
JBB.
On 5 Sep 2008, at 09:55, thron7 wrote:
Jean-Baptiste,
So, is there any hope to find a separate lib file for 0.8 ?
In fact, like most framework, it's always too big, so there are often
several version : a big dev version and an optimized version.
A super optimized version would need to browse the application use of
the lib so the packaged lib only embeded needed (used) elements and
this is probably the purpose of that Python machinery.
Exactly.
Unfortunatly, what is built-time for "classical" usage is runtime
for us.
I won't be able to give details but consider our product as a
generator.
Ok, I get it.
So, I really have to cut that Python build machinery even if this is
the way to get the most optimized packaging of qooXdoo.
Will it be possible to get a qooXdoo lib in dev (not compressed) and
prod (compress, optimized, no debug, ...) flavors ?
I think that's doable. Maybe we can create some custom package for
you.
The problem is, it's vacation time and we don't have enough hands to
help out right now. How fast would you need the package(s)?
Thomas
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win
great prizes
Grand prize is a trip for two to an Open Source event anywhere in
the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
// put this into the framework/ directory and run:
// ./generate.py -c jean-baptist.json [qxlib-debug|qxlib-optimized]
{
"let" :
{
"CACHE" : "../cache",
"BUILD_PATH" : "build"
},
"export" : ["qxlib-debug", "qxlib-optimized"],
"jobs":
{
"common" :
{
"library" :
[
{
"manifest" : "Manifest.json",
"uri" : ".."
}
],
"cache" : { "compile" : "${CACHE}" },
"include": ["qx.*"],
"exclude":
[
"=qx.legacy.*",
"=qx.test.*",
"=qx.ui.progressive.*"
],
"themes" : { "qx.icontheme" : "Tango" }
},
"qxlib-debug" :
{
"extend" : ["common"],
"variants" :
{
"qx.debug" : ["on"],
"qx.aspects" : ["off"]
},
"compile-dist" :
{
"target" : "${BUILD_PATH}",
"file" : "${BUILD_PATH}/script/qx-debug.js",
"uri" : "script/qx-debug.js",
"format" : "on",
//"optimize" : ["basecalls", "variables", "privates", "strings"],
"root" : "${BUILD_PATH}"
},
"copy-resources" :
{
"target" : "${BUILD_PATH}"
}
},
"qxlib-optimized" :
{
"extend" : ["common"],
"variants" :
{
"qx.debug" : ["off"],
"qx.aspects" : ["off"]
},
"compile-dist" :
{
"target" : "${BUILD_PATH}",
"file" : "${BUILD_PATH}/script/qx-optimized.js",
"uri" : "script/qx-optimized.js",
"format" : "on",
"optimize" : ["basecalls", "variables", "privates", "strings"],
"root" : "${BUILD_PATH}"
},
"copy-resources" :
{
"target" : "${BUILD_PATH}"
}
}
}
}
Title: Firt Button Demo
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel