I have looked at the Partloader but there is a warning on the page telling me not to use it to load framework classes. However this is what I want to do. So for instance, all my apps use a table and I'd like to have that code cached in browser memory.
I've been trying to understand "variants" [1]. The documentation says it does dead code elimination, but I don't understand how to use it to help me. Also maybe I'm doing something wrong, but I put together a small demo application in which I have one class that uses the following framework classes: qx.ui.container.Composite, qx.ui.layout.HBox qx.ui.layout.VBox qx.ui.form.Button qx.ui.form.Textfield qx.ui.tree.Tree qx.data.controller.Tree qx.data.marshal.Json (statically) qx.ui.groupbox.Groupbox The build step creates a 715KB Javascript file. Is this normal? Can this be reduced somehow? Thanks! -deech [1] http://manual.qooxdoo.org/1.5.x/pages/tool/generator_optimizations.html (see the "variants" section) On Tue, Aug 9, 2011 at 3:37 AM, Alexander Steitz <[email protected]> wrote: > Hi, > > On Monday 08 August 2011 20:57:58 aditya siram wrote: >> What is the best way of reducing the size of Qooxdoo apps across >> multiple pages? > You can use so-called "parts" to slice your application and the necessary > framework classes into parts and load them when necessary. > > -> http://manual.qooxdoo.org/1.5.x/pages/development/parts_overview.html > > Take a look at this overview and the detailed pages which are linked to get a > impression what parts can do for you. > >> I have multiple HTML pages with div's each of which has a Qooxdoo >> widget and totals around 700KB - 1MB of Javascript. > Sounds like a good candidate to use parts for me. You can configure your > specific parts in the "config.json" and use the PartLoader API to load them > dynamically. It's all in place and offered by the framework and the toolchain. > >> Because the "build" step generates one large file when I go to another >> page that uses some common widgets the browser loads the JS for those >> widgets all over again. Is there some way to keep a common list of >> compiled classes that any app can use? > Do you need the same widgets on all pages? If not, you can create parts which > contain different widgets and load them accordingly. This way you do not need > to load one big JS file. > You can create a small loader JS file which is capable of loading the > necessary parts on demand. > > Regards, > Alex > > ------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
