Managing default_browser from the ZMI
To all who worked on the 2.6 release, great work! I'm just now starting to process the changelog, and try to understand all the latest stuff. The one thing that kind of caught my eye is that during the first alpha release, there was an entry that stated: - added browser_default hook to ZPublisher. This allows objects to specify the path to the default method that the publisher calls when the object is published. The default for objects not defining browser_default is still 'index_html' for bw compatibility. A ZMI configurable browser_default implementation has been added to ObjectManager. You can configure browser_default for OMs via a new "settings" management tab. which maps to this 2.6 proposal explaining the intentions of default_browser: http://dev.zope.org/Wikis/DevSite/Proposals/ObjectTypeAssociationAndDeathToI... This sounds like a very exciting feature, one that I hope didn't get lost in the shuffle of getting 2.6 out the door. A quick glance at OFS.ObjectManager and ZPublisher doesn't show any sign of this new behavior. Now, I haven't digested the rest of the changelog or the source yet, but the release announcement does list "Addition of a new default view setting ability" as one of the new features. Was this deferred to 2.7 (which is completely understandable)? Is help needed to bring it up to the Wiki proposal level? Inquiring minds would love to know. Still looking to bury index_html, Eron
Did you get anywhere here? I cant find the darn thing either. This should be removed from changes.txt if it aint in. -- Andy McKay www.agmweb.ca ----- Original Message ----- From: "Eron Lloyd" <elloyd@lancaster.lib.pa.us> To: <zope@zope.org> Sent: Saturday, October 19, 2002 8:15 PM Subject: [Zope] Managing default_browser from the ZMI To all who worked on the 2.6 release, great work! I'm just now starting to process the changelog, and try to understand all the latest stuff. The one thing that kind of caught my eye is that during the first alpha release, there was an entry that stated: - added browser_default hook to ZPublisher. This allows objects to specify the path to the default method that the publisher calls when the object is published. The default for objects not defining browser_default is still 'index_html' for bw compatibility. A ZMI configurable browser_default implementation has been added to ObjectManager. You can configure browser_default for OMs via a new "settings" management tab. which maps to this 2.6 proposal explaining the intentions of default_browser: http://dev.zope.org/Wikis/DevSite/Proposals/ObjectTypeAssociationAndDeathToI ndexHtml This sounds like a very exciting feature, one that I hope didn't get lost in the shuffle of getting 2.6 out the door. A quick glance at OFS.ObjectManager and ZPublisher doesn't show any sign of this new behavior. Now, I haven't digested the rest of the changelog or the source yet, but the release announcement does list "Addition of a new default view setting ability" as one of the new features. Was this deferred to 2.7 (which is completely understandable)? Is help needed to bring it up to the Wiki proposal level? Inquiring minds would love to know. Still looking to bury index_html, Eron --- [This E-mail scanned for viruses by Declude Virus] _______________________________________________ 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 )
Found it, there is a bit of code buried that says if you define a __browser_default__ on an object (which is pretty easy to do via a mixin or a monkey patch). This is easy to do if you want to write a custom object or even add this in to the stock UI. However there is no simple ZMI feature as there is meant to be defined in changes.txt. So this bit of the changes.txt is incorrect: "A ZMI configurable browser_default implementation has been added to ObjectManager. You can configure browser_default for OMs via a new "settings" management tab." I would consider this a bug and Ive entered this into the collector (http://collector.zope.org/Zope/643) -- Andy McKay www.agmweb.ca
participants (2)
-
Andy McKay -
Eron Lloyd