Re: [Zope] one 'document' in many 'folders'
I just thought a little more about the approach having a pool and some proxy objects that refer to the pool. I think it could be made quite neat when using just the following code for the proxies (DTML documents): <!--#var "RESPONSE.redirect ('/pool/'+id())"--> So you just need to put zope_is_cool inside your pool and add DTML documents with the above code under the same id to your folder structure wherever you like. Just check it out. Two caveats: - You have to use DTML documents, not methods, otherwise id() refers to the folder's id - Make sure that zope_is_cool really exists inside your pool, or you get an infinite redirection! (zope_is_cool is not found in the pool and then sought for along the aquisiton path, which refers to zope_is_cool itself, which redirects to the pool which ...) Maybe this could be even generalized to some kind of "symbolic link" product. Ideas anyone? Stefan
----- Original Message ----- From: Stefan Franke <sfranke@cdc-group.com> To: <wade@okaynetwork.com>; <zope@zope.org> Sent: Monday, March 22, 1999 1:19 PM Subject: Re: [Zope] one 'document' in many 'folders'
I just thought a little more about the approach having a pool and some proxy objects that refer to the pool.
I think it could be made quite neat when using just the following code for the proxies (DTML documents):
<!--#var "RESPONSE.redirect ('/pool/'+id())"-->
An alternate solution could be something like <!--#var "_.getattr(pool, id)"--> for your "link" methods. I think this would take better advantage of acquisition. A document could pick up its headers and footers from the category, instead of the pool. It does seem like someone could create a "symlink" product pretty easily. Kevin
participants (2)
-
Kevin Dangoor -
Stefan Franke