On Wed, Dec 16, 2009 at 04:20, lp1051 <lp1...@gmail.com> wrote: > > > Yes, I was playing with the example in demobrowser and that's why I wanted > to ask for advice. The functionality demonstrated for normal tree was > exactly what I needed for reordering the Folders and Files, but virtual > tree > offered me the table layout.
If you will have a relatively small number of nodes in your tree (fewer than 100 is pretty easy; more than that and you'll have to experiment with performance), then the Tree should do fine for you. Tree does support multiple columns, as demonstrated here: http://demo.qooxdoo.org/devel/demobrowser/index.html#widget~Tree_Columns.html > Btw. I was a little surprised why is it so difficult to add eg. button into > table cell. TreeVirtual provides, as you may have guessed from the name but not really understood what it meant, a "virtual" tree. This means that rows of the tree are rendered as they become visible. When new rows become visible, the rendered portion of the screen is replaced with rendering of the new rows. Although browsers are getting better and better, rendering is still very slow compared to other processing done on widgets, so eliminating any unnecessary rendering is particularly useful to avoid noticeable delays. The rendering is done at a low level, using cell renderer classes which output HTML. There is never an actual qooxdoo widget instantiated for each of the rows or cells, which is advantageous for speed, but means that the nice benefits of qooxdoo widgets are not available within qooxdoo's Table or TreeVirtual (which extends Table). Is there a way to add qx.ui.form.Button() or do I need to use > HTML renderer and copy the html I get from qx.ui.form.Button()? > Even if you add all of the HTML that a Button generates, you won't get the full functionality of a Button widget. Events, for example, have their listeners within the Button and its superclasses code, which will not be available simply from copying the HTML. TreeVirtual is a different beast than Tree. Each has its advantages and disadvantages, so you'll need to choose the one most appropriate for your use. Hope that helps explain things. Cheers, Derrell
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
