The following is always up for debate.
I only post it so as to get any feedback..
I would love to see more than two people take an interest
in such a complext and major component of the DynAPI.
 
That said.
 
I don't like the name treenode. I honestly don't think htere is ever a case where you will use only one node of a tree.
 
I move to name the new widget DynTree.
The DynTree will actually consist of two objects. Both will be declared in one file for simplicity.
The two objects are:
DynTree
and
DynNode
 
The DynTree will hold all of the the tree manipulation functionality:
-opening and closing branches
-adding and removing nodes, ect.
 
The DynNode will be very simple. It will have content.
This allows the actuall size of a rendered tree to be reduced as a lot of code will only be instanciated once per tree. This should allow a N-numbered tree to be somewhat slimmer and faster than in the previous version.
 
Once I have built an outline of what I intend to code I will post said outline for further discussion.
 
Unless you want to simply give a dinasour like me free-reign? :-)
 
The first version will be a 'light' version using only + and - signs with no images.
As always, there will be a future 'skinable' version.
 
WE can start a discussion about skinning methedology and standards any time now. :-)
 
With so few active developers, we may get a standard hammered out in short-order, no?

Reply via email to