Hi there. I have been monitoring the list to observe changes in setup
specifically. I have been waiting for things to stabilize since there
seemed to be many sorts of changes occuring in arriving at what it
would look like including splitting CMFSetup etc.
When will these changes in machinery come out on a new CMF release. As
far as third party products, I have been generating Install type files
still will my products. Will these still be able to be used or will
this be completely replaced by the new machinery. What happens to
CMFQuickinstaller as a result? Is that completely dead after these
changes occur? I am wondering what to do with any non standard code
executed on install, like add things like python scripts or folders,
etc. Where will this go without Install? I am assuming the xml will
take care of many standard things, but what about anything out of the
ordinary like what I mentioned?
Sorry if this sounds like worry. It is not. Rather I am wanting to
make sure that I stay current so my own products won't break and I am
keeping in tune with recent developments. Also these changes are
important to me since I am trying to develop a portal by subclassing
CMFSite so there seems to be many things happening that could affect
what I am doing.
Many thanks
David
On Thursday, October 20, 2005, at 12:53 PM, yuppie wrote:
Hi all!
If there are no objections, I'll merge tomorrow the
yuppie-setup_cleanup branch into the trunk. This will break the setup
code of all third-party products that haven't yet switched to
GenericSetup/CMFSetup.
1.) factory_type_information data is replaced by XML files in the
types directory of profiles.
TypesTool.listDefaultTypeInformation was removed, the 'fti' argument
of utils.ContentInit and the 'typeinfo_name' argument of
TypesTool.manage_addTypeInformation are ignored.
2.) manage_addCMFSite is replaced by addConfiguredSite.
3.) PortalGenerator is replaced by setup handlers and a base profile.
4.) enumerateIndexes, enumerateLexicons, enumerateColumns and
_initIndexes of CatalogTool are replaced by a catalog.xml file in
profiles.
5.) Install.py scripts are replaced by extension profiles.
Cheers,
Yuppie
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
