Well as a said a container approach probably does not make sense fort
his package, so I don't see a way around having two separate packages.
But this is becoming a common problem. See QueryTool etc.
Why not? I think that a container approach would really make sense...
Wolfram already started something in this direction, although some
work is still needed.
QueryTool and/or DataObject are a bit different, since they directly
work on the db, hence to make them container-driven would at least
require multiple inheritance, something PHP4 (AFAIK) can't handle.
On the other hand, I don't see the need for different packages here:
a container-driven class is possible IMO, and I think that a rewrite
would be quite easy. If current PEAR::Tree is going to be moved
to Structure::Tree (or whatever), this would be the perfect time
to consider some changes...
Just my 0.02$
Regards,
Lorenzo