Hello all,

So it took me over a year to get back to the extension that I left 
unfinished, and finally play more with the Tree component. It did take 
care of majority of tree-related problems very well.

However, I came across few problems that I would like to share with you. 
Maybe I'm missing something and if not, maybe there's space to 
contribute something.

The major issue is that I have not found a way to instantiate subtrees 
of the big tree that would also be trees (and not lists of 
child/descendant nodes). At least not in case of DB-stored tree. This 
has some serious consequences since for example I have not found (an 
easy) way to use visitator visualizations on a subtree. The method 
fetchSubtree is only an alias for fetchSubtreeDepthFirst, which 
basically returns a collection of tree nodes rather than a fully 
functional tree object (as far as I understand it).

Of course, I can see lots of complications with the model I'm imagining 
(for example, root, level and path calculations). Still extracting 
subtrees seems like a basic thing to have. I'd be grateful for any help 
on this issue.

Thanks,
Piotrek
-- 
Components mailing list
[email protected]
http://lists.ez.no/mailman/listinfo/components

Reply via email to