Re: RFC Nested Set manipulation class

Martin Jansen wrote: [..] > > The source can now be found at > > <http://vie1.webcluster.at/nestedset.php> If the > > package goes into > > pear > > If there is really no chance to merge this with Tree, I'm +1 for > this. Well the main problem will be that having it inside it's own class is the only way for me to be able to maintain the code. NestedSet is used inside projects by 2 developers of my company. So if bugs occur or new features are needed I can easily export the fixed versions from our CVS into PEAR. Would it be a solution to try to create an interface between Tree (which has more features than building NestedSets) and NestedSet? I think that shouldn't be that hard. So Tree and NestedSet could happily grow... Wolfram? BTW: I have no problem at all if this redundancy isn't wanted and if Wolfram wants to add the features inside the existing class. I wanted to make the move from phplib to pear and while I did this I was able to do major rewrites and cleanups of NestedSet (without breaking dependencies with the old structure - like having the node returned as object). So it wasn't a waste of time for me even if the package doesn't make it into PEAR :) > Would be cool to hear some comments from Wolfram concerning the > stuff. Full ACK -- Daniel [datenPUNK] Khan