After reading portal.py, what i understood is that factory_type_information is used in the setup of a CMFSite, by PortalGenerator.setupType, to fill in portal_types tool with the default types. It's a way to customize a basic CMF Site If i want to add y own types, i can define a module sometype.py and add its factory_type_information to portal.factory_type_information otherwise i'll have to add a Factory_type_based_information in portal_types workspace. If i want to use PortalGenerator.setupTypes in my own module to register my type in portal_types, i suppose i'll have to create an instance of PortalGenerator in my module but that i don't need to use PortalGenerator as a base class of my module.
Am i right ? (i'm a newbie so my questions may be simples ones)
I'm still learning a lot about Zope and the CMF myself, but what I found helpful is lots of experimentation and examining Plone's source code. You'll notice their PloneSite subclasses CMFSite. PloneGenerator subclasses CMFDefault.Portal.PortalGenerator. They also have a neat concept of CustomizationPolicy objects. Cheers, // mark -