Hi Fabian, thanks for response. I know that compatibility for IE is important, but many of us are using qooxdoo for admin interfaces or intranet applications where this incompatibility isn't too much problem (we can say, use FF, Opera, Chrome, ...).
Virtual widgets can improve performance, but on the other side they can flicker much more like nonvirtual ones. For example look at tree virtual, in my machine (Turion 1.6GHz) I can scroll, but it's too much slow. BTW: How is your idea to decrease number of DIVs ? Is there comparision how DIVs are using qooxdoo 0.8 application compared to 0.7.3? Cheers - Petr 2009/1/26 Fabian Jakobs <[email protected]>: > Hi Petr, >> This is very interesting topic for me (maybe because I still fell that >> qooxdoo is slow). But I have another idea. Isn't it possible to >> experiment with <canvas> based rendering ? >> >> I think that javascript is fast enough for internet applications so >> most time spent is not in JS but in DOM manipulation and rendering >> pages. If there will be possibility to virtually paint for example >> list box items then qooxdoo application will contain fewer DOM >> elements and browser will render pages faster (and will be faster >> because DOM structure will not be polluted by DIVS for nothing). >> Canvas rendering is ultra fast compared to X thousands of DIVs >> hierarchy. >> > Canvas is interesting but even IE8 will not support it. There are ways > to emulate canvas on IE but this will result in even slower rendering. I > think we have to keep using HTML based rendering for the near future. >> I'm also voting to decrease of needed DIVs in qooxdoo application, but >> I think that this is probably impossible :( >> > I can think of a few situation where we could svae a few DIVs but in > general reducing the umber of DIVs means also a reduction of features. >> So, personally, instead of new features I think that qooxdoo needs >> performance. >> > I see this whole virtual widget topic as a way to increase qooxdoo's > performance. There are plenty of use cases where similar widgets are > arranged in a grid or list, which can benefit from virtual rendering. > Take the messenger application as example. You can use a list to create > the contacts view. This will be fast for few contacts but if the contact > list becomes larger the startup performance suffers. With virtual > rendering only widgets for the visible contacts are needed and startup > time becomes independent of the number of contacts. > > Best Fabian > > -- > Fabian Jakobs > JavaScript Framework Developer > > 1&1 Internet AG > Brauerstraße 48 > 76135 Karlsruhe > > Amtsgericht Montabaur HRB 6484 > > Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas > Gottschlich, Matthias Greve, Robert Hoffmann, Markus Huhn, Oliver Mauss, > Achim Weiss > Aufsichtsratsvorsitzender: Michael Scheeren > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
