---------- From: Tom Deprez[SMTP:Tom.Deprez@uz.kuleuven.ac.be] Sent: Thursday, April 29, 1999 6:37 AM To: Zope@zope.org Subject: Re: [Zope] examples
Yup, I'm afraid so. For non default combinations (i.e., for wich there is no predefined fmt string), you have to do a call for each element you extract.
Suggestion for next releases? Isn't it possible to incorporate this? A sort of string parser that analyses the fmt parameter?
Other Suggestion : When changing the ID of an object. All documents to which you refer to the old-id have to be edited. What about somewhere an update button, when pressing on it. It iterates through your objects and changes the old-id to the new one.
Sounds like an idea, except how do you deal with acquisition? It is so easy to have the same <!--#var id--> refer to different objects via acquisition, and if you changed the reference <!--#var id--> everywhere, it would break those which refer to a higher level acquisition. This is particularly twisted since you can construct URLs, such as adding the sql dir in as we have recently seen on the list, to effectively change what is meant by an acquired variable. I rather doubt that it would be very possible for some algorithmic code to guess when you meant to refer to this specific object, and when you meant to refer to this pattern of acquisition. After all, what if you are renaming the object so that you can revoke the acquisitive override without losing the functionality of the object? A SAR would break the acquisitive behavior you were trying to cause! Its sounds like a nice idea, but I see too many potential problems due to Acquisition.
Tom.
Just as an aside: PrincipiaTime has been renamed to ZopeTime. Principia was the old name of the management interface, before it was merged with Bobo into Zope.
-- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-6254545 Fax: +31-35-6254555 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------
_______________________________________________ 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 )