Luke, lp1051 wrote: > Hi T., > > 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. Besides I needed the select boxes and buttons > besides the labels, so I thought altering cellrenderer and celleditor for > table should be simpler than doing something similar for normal tree... So I > didn't know what shall I prefer, what is easier to implement. > > I decided for virtual tree, when I didn't get answer previous week. But I am > not so far yet, so if you think > normal tree would be better, considering the multi columns and specific > content of cells (not just text), I can still update my design. >
I'm neither a tree nor a table expert, but what you write sounds sensible to me. Maybe Derrell can jump in with better advice. > Btw. I was a little surprised why is it so difficult to add eg. button into > table cell. 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()? > I think the base line with table is that you in general cannot use *widgets* in cells. This will only be possible with the new virtual widgets that are in the making. T. ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
