You know, I've never really gotten this either. Maybe Jim Fulton could explain for us one more time or else point us at a good explanation of -why- acquisition begins at the root and goes down the tree instead of starting at the current level and going up, which I believe is what pretty much everyone expects it to do when they first run across it. -jfarr ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Hi! I'm a signature virus. Copy me into your .sig to join the fun! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ----- Original Message ----- From: Alex Burton <burton@w3cast.com> To: <zope@zope.org> Sent: Tuesday, February 22, 2000 6:47 PM Subject: [Zope] aquisition and refining

Me again (last one for tonight!)

Aquisition is groovy, but is it possible to refine aquired properties instead of redefining them from scratch?

(Creating a standard_html_header in s subfolder and using <dtml-var standard_html_header> does not produce expected result, that is grabbing the upper-level's definition of standard_html_header).

Is there a DTML tag such as <dtml-refine> which, when stated at a given level, would indicate where to insert sublevel redefinition of the DTML method?

Maybe i'm thinking too much of OO inheritance...

Alex

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )