Am 08.09.2008 um 18:15 schrieb Jean-Baptiste BRIAUD - Novlog: > Good point ! > > I didn't realized that performance issue as I was focused on size. > > And what about a lazy loading or on demand loading of classes ? > So unused but included classes won't be loaded, initialised ... > > I guess the answer is : that's why there is a Python build, so unused > classes are not even included and it is quicker. > > I understand that, but for us (with our generator on top of qooXdoo) > either we have a performace issue at load time (with big distrib > hypothesys) witch is not acceptable or we have a build-time > performance issue when launching the Python build everytime our user > want to see the resulting application (and that could happen very > often, like every 5 min) and it may not be acceptable as well.
What about some type of caching. The user may start the same app-type over and over so it might be cachable. > > > Whatever we do it will be slow to launch the application either way. > > That's why I come back with that lazy loading thing but to be honest I > don't know enough qooXdoo to feel how hard it could be. The major issue is dependency tracking. You could however build separate packages for e.g table, tree, toolbar, form, ... Each module would be sized from 20-100kb and would only contains these classes. All of them share one base module though which is maybe 300kb. All sizes ungzipped. Sebastian > > Maybe it is just a crazy idea ... > > Any other idea to improve that ? > > > On 8 Sep 2008, at 17:51, Sebastian Werner wrote: > >> That definitely should work. You can also try a >> >> cd framework >> ./generate.py build >> >> As far as I have understood this should also create a bundled >> one-package qooxdoo. >> >> Just one thing to keep in mind. While the size (network wise) may not >> hurt you, the load time definitely increase for such a use-case. The >> issue is that every class, used or not, must be parsed and >> initialized >> by the browser. This is the main reason why we build these optimized >> applications most of the time. >> >> Sebastian >> >> >> >> Jean-Baptiste BRIAUD - Novlog schrieb: >>> Might be a really stupid idea ... but how about a fake application >>> that would use (just by referencing for example) all widgets and >>> sort >>> of modules, so the build will produce the "big javascript" I would >>> like ? >>> I think to that rather than other approach to make sure I'll be able >>> to have "my build" with future version. >>> >>> Does it make sense ? >>> >>> >>> On 5 Sep 2008, at 15:11, thron7 wrote: >>> >>>> Derrell Lipman wrote: >>>>> On Fri, Sep 5, 2008 at 8:08 AM, thron7 >>>>> <[EMAIL PROTECTED]> wrote: >>>>> >>>>> >>>>>> (I also had to exclude qx.ui.progressive, due to an >>>>>> incompatibility with >>>>>> qx.ui.table which I deemed more important to have). >>>>>> >>>>> >>>>> But I'll be fixing the problem in Progressive today, so you'll be >>>>> able to >>>>> remove that exclusion too. >>>>> >>>> I guess Jean-Baptiste is on 0.8, not trunk, so he'll has to keep >>>> the >>>> exclusion. >>>> >>>> T. >>>> >>>> >>>> ------------------------------------------------------------------------- >>>> 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 >> >> >> ------------------------------------------------------------------------- >> 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 ------------------------------------------------------------------------- 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
