RE: Tree widget upgrade ideas

Alex, 

1) For the tree I would need (what I implemented manually but badly): two
properties of the tree:

a) pointer to DOM-node of the currently (or last) clicked-on node
c) pointer to the respective node in the internal tree representation (data)
of the tree

2) If you could implement a default mouse-over and mouse-down
change-background-colour behaviour as in the menu bar widget.

2) Usually, tree widgets in other GUI sets are embedded in tables, so that
they do not only have one row (the tree), but also additional rows (compare
the select file widget: folder structure, file name, file size, file type
etc).

Christian


> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Michael Flanagan
> Sent: Thursday, January 29, 2004 11:59 PM
> To: netWindows development discussion list
> Subject: [NW-Devel] Tree widget upgrade ideas
> 
> 
> Couple of ideas I've had while playing with this new tree widget:
> 
> 1) Type / image system
> - Ability to specify a default type for all leaf nodes in a specific 
> branch
> - Ability to over-ride the default at the leaf node level
> - Have the branch be intelligent enough to figure out the type of a 
> leaf node when dealing with dynamically loaded branches
> 
> Just to clarify here the purpose of this system is to register 
> different images with different types of nodes so that it will 
> automatically assign the proper image to each type of node.
> 
> 2) Extended expand / collapse feature
> - Ability to fully expand all child branches within a given 
> branch node
> - Ability to fully collapse all child branches within a given branch 
> node
> 
> The idea here is that you can fully expand and collapse all branches 
> which are the children of a given node. My idea is to put an image at 
> the end of line which is the name of the branch. This image would act 
> as a button which would have two states. One would  be a 
> fully expanded 
> state, and the other a fully closed state. This behavior would be 
> optional to the tree widget. If you wanted to use it, you 
> would have to 
> specify it in the widgets constructor.
> 
> That's all I can think of for now.
> 
> Michael
> 
> 
> _______________________________________________
> The netWindows developers list: [email protected] 
> http://netwindows.org/mailman/listinfo/devel_netwindows.org
> 
> 


_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org