Re: [Zope-dev] RFC: product initialization cleanup and improvements

2005-11-02 Thread Dieter Maurer
yuppie wrote at 2005-10-27 14:45 +0200: ... 1.) 'action' key: - I'd like to give empty 'action' values a special meaning: The meta_type is not visible in the add drop down in the ZMI. The five:registerClass directive allows to set empty 'action' values. This would resolve

Re: [Zope-dev] RFC: product initialization cleanup and improvements

2005-11-02 Thread yuppie
Hi Dieter! Dieter Maurer wrote: yuppie wrote at 2005-10-27 14:45 +0200: ... 1.) 'action' key: - I'd like to give empty 'action' values a special meaning: The meta_type is not visible in the add drop down in the ZMI. The five:registerClass directive allows to set empty

Re: [Zope-dev] RFC: product initialization cleanup and improvements

2005-11-02 Thread yuppie
Dieter Maurer wrote: yuppie wrote at 2005-10-27 14:45 +0200: 4.) related cleanup: Application.install_product has some backwards compatibility code for products that have initialization code outside the 'initialize' method of their __init__.py. This is deprecated at

[Zope-dev] RFC: product initialization cleanup and improvements

2005-10-27 Thread yuppie
Hi! Working on the five:registerClass directive for Five 1.2 and Zope 2.9 I had a closer look at the product initialization code. I propose the following modifications for the dicts in Products.meta_types (set by registerClass): 1.) 'action' key: - I'd like to give empty