Matt just gave us some guidelines/ priorities so probably we shouldn't elaborate/detail too much this spec now, matt just wanted some ideasof which direction could we take i think, following the architectural idea of Fl_group inheritance. So I will only comment briefly some of them (because it's damn exciting) :
> it seems like the open/close > icons would still have to be there because one should be able > to click on those to open/close the tree (if it's a 'folder' node) > without the app's widget having to handle that. Sure this would be useful, I tried to be minimum and not to get into too much details now thus more favorizing approach (do we reuse Fl_Group or will we tend to Node containers encapsuling widgets, etc...) > Insert If we can insert now with Fl_Group, this will be also true in the Fl_Tree_Browser, that's the idea. but still it can be interesting to extend these capabilities (insert before,after & replace) > Invisibility I think it would also be inherited from Fl_group, only the draw() part would have to be heavily rewritten but that's fair enough. > Optimization: Avoiding Unnecessary Recalc()s True, other important optimisations with direct impact is how we handle multiple selected items, search them when the load gets heavy. Thanks Greg, Fabien _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
