Sebastian Werner wrote:
>
>
>
> This basically look like you do not have a configuration for the
> packages support. There seems to be a misunderstanding of the idea of
> what packages can do for you. These are not thought to build library
> like packages which may be used by different apps. The ideal use case
> is to automatically split an application into separate packages which
> are loaded on-demand during the application runtime.
>
> A example would be something like an outlook clone where you initially
> load the email view together with the basic application structure
> (tree, toolbars) and only when the user jumps to the calendar
> automatically load this part afterwards etc.
>
> A configuration here would look like this:
>
> "core" : "my.Application",
> "mail" : "my.email.View",
> "calendar" : "my.calendar.View"
>
>
Actually, what I am trying to accomplish is to build the app so that my code
is delivered to the browser in "source" format and qooxdoo library code is
delivered in "build" format. Doing this has several advantages while
developing
1. Makes debugging so much easier (ex. 800 fewer files in the Firebug script
tab)
2. Makes the app load faster than an all "source" version.
3. shortens the "edit-build-run" cycle since I don't really "build" anything
I thought the "packages" feature could do this for me - but looks like I am
mistaken. Still trying to get comfortable with the new tool chain.
Perhaps the tool chain could include this type of build as a standard job. I
think many developers would appreciate the benefits.
Sebastian Werner wrote:
>
> When you want to built library like packages an include statement with
> explicit "=" classs lists would be more ideal. Not sure if there exist
> documentation around this topic though.
>
That sound like what I need. I looked through the docs but didn't see
anything.
The new "window.qxloader =" scheme is very different from how 0.7.x loaded
the JS files.
I wonder if I could hack the window.qxloader.uris after a "source" build of
my app - like the following - (where qx-0.js is the entire Qooxdoo library)
window.qxloader =
{
parts : {"myapp":[1],"qooxdoo":[0]},
uris : [
["../script/qx-0.js"],
["../script/class/my/ui/View.js",../script/class/my/ui/Control.js",<REST_OF_MY_CLASSES>"]
],
boot : "qooxdoo",
...
}
Do you think that will work?
Thanks
Mike Shillinger
--
View this message in context:
http://www.nabble.com/How-to-use-Packages--feature-in-0.8-Build--tp21939291p21975679.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
