> 1. Get rid of the tree lines. No modern UI system uses them > anymore. The usability guy, who did the new qooxdoo theme told us > that they are actually distracting people. The code to handle tree > lines is really bloat and they make it hard to have different row > heights in the tree.
Interesting. Could they be included as a mixin which could be excluded if not used? I'm certain that we would want to retain the option to have them here. > 2. Remove the tree row structure and find a better way to customize > tree items. My first goal in this direction is to make the tree > file and tree folder widgets easier to subclass. May be implement > something similar to the tree row structure API directly in the > tree element API. Have you see http://bugzilla.qooxdoo.org/show_bug.cgi?id=294 - this discussed a few problems I had with the tree API and proposed solutions. There's a thread on the mailing list starting with a message posted by myself on 12 Feb 2007 with subject "API of tree folder" (unfortunately this doesn't appear to be on Nabble etc) which discusses the points raised in the issue. If you don't have it on a machine there I can export the complete text to you (I've got a complete set of mailing list messages going back to Jan 06!) > 3. The tree widget no longer derives from tree folder but acts as a > container for tree items. I guess this is OK. Our code had to work around this structure with a bit of duck typing. It wouldn't take long to rewrite it, but it definitely isn't something that migration could do. Hugh Hugh ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
