On 01/17/2013 02:37 PM, Dietrich Streifert wrote:
>> A canoncial solution would be to do as Alexander suggested and have the
>> *app.js* as no-cache so any potential change to this file is picked up
>> immediately. This should be a small overhead if you use the Generator
>> features so that app.js only contains the loader logic.
> Thank you for you answer Thomas.
>
> In fact the app.js size is 2.2 MByte and uses the generator but my app
> is a really big one.
> There are a total of 639 classes in the app containing two (really!)
> large forms.
>
> So how do I use the "loader logic"? Do you mean the part loader?
Yes, quite, but there is no need to use any real parts. You can just
split the loader from the application code. In your config.json use
"build-script" : {
"packages" : {
"parts" : {
"boot" : { "include" : [<your normal include list>] },
"separate-loader" : true
}
}
}
This defines a (trivial) one-part app for the build version, with just
the minimal "boot" part, but also splits the loader from the app code.
And there is no need to instrument your code with
qx.io.PartLoader.require calls, as the boot part is loaded anyway. (For
a big app, using actual parts beyond "boot" might be a good idea as well.)
T.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
