[Zope] RFC. New entity. "Zope Bean".

[Paul T]

Ok. My last comment on productizer.

At the moment I see no problems in implementing the following scenario:

 >1. SomeClass.py
 >( contains the actual functionality )
 >
 >2. ProductDescriptor.XML
 >( contains dependencies, list of product's configurable properties and (maybe) methods )


Productizer generates the SomeClass_Product proxy object, with creation screen, one ( and
only one ) configuration screen and ( optional ) index_html ( including all the dtmls
needed. Everything related to Zope integration is encapsulated in this proxy class.

This is not current Product ( less flexible ) but this is also not a component as well
 has GUI ). This is Zope Bean.

Such beans should be extremely easy to create, comparing to current Product magic. Now I
have to understand how persistency and other things work, but I think that this design can
work. I may implement it occasionaly and then we'l see.

Comments welcome.

Rgds.Paul.