Hi Gregor, I'm about to do the exactly same thing. Maybe we can work together on this one? I have tried using DTML to solve this but i'm slowly getting to the conclusion that its too much a hussle to get it working. Mayby subclassing the tree-tag removing the stuff that we don't need could be a way to try. but I'm not sure if it's possible to add custom tag from a product? If you have any bright ideas I'm all ears. Best Regards, Johan Carlsson

I need a navigation element for tree-like structures, but with a different rendering (no collapsing/expanding, different font sizes for the various depths etc.). I could try and write that thing from scratch, but given that most of its interface is similar to the TreeDisplay code, I wonder what would be the zopisticated way to reuse the interface and as much code as possible.

Perhaps a similar question is: given that TreeDisplay is a builtin DTML tag, should I try to augment the TreeDisplay code, or is there a reasonable way to build user-defined DTML tags, or is it more reasonable to employ traditional methods (e.g. var-exprs) for this ?

Gregor

_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope

(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )

Denna lista drivs av Torped Marknadskommunikation AB