Re: [Zope-CMF] Test setup problems with Zope 2.13
Am 28.07.2010, 14:28 Uhr, schrieb Hanno Schlichting : > Well, right. Except in Plone / Archetypes this and variants based on > it are still the only option. Archetypes doesn't know about add views > or any of that "new" IFactory pattern. Hi, thanks for reverting the changes and all the other fine work you're doing. I'm not sure about the scope of these changes but I'm happy to chip in but not sure what you want done with ContentInit. Can't Archetypes be updated to work with this stuff? Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Test setup problems with Zope 2.13
On Wed, Jul 28, 2010 at 1:17 PM, yuppie wrote: > Hanno Schlichting wrote: >> ContentInit > > ContentInit is only used for BBB. It registers oldstyle constructors. Well, right. Except in Plone / Archetypes this and variants based on it are still the only option. Archetypes doesn't know about add views or any of that "new" IFactory pattern. >> I'd love to see someone tackle registerClass and at the same time >> decouple ZMI add menu visibility and the OFS.CopySupport stuff. > > You mean the CopySupport issue I fixed 5 years ago? Or something > different? http://svn.zope.org/?view=rev&rev=40552 > > five:registerClass doesn't require to specify an 'addview'. CopySupport > works for all CMF content types without adding them to the ZMI add menu. > > We just can't use five:registerClass in OFS/OFSP because it doesn't > support oldstyle constructors and legacy methods. Ah, yeah! This was exactly what I meant. I had no idea this was already done. So a belated thank you :) Hanno ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-CMF] CMF Tests: 4 OK
Summary of messages to the cmf-tests list. Period Tue Jul 27 12:00:00 2010 UTC to Wed Jul 28 12:00:00 2010 UTC. There were 4 messages: 4 from CMF Tests. Tests passed OK --- Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux From: CMF Tests Date: Tue Jul 27 21:49:33 EDT 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013337.html Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux From: CMF Tests Date: Tue Jul 27 21:51:33 EDT 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013338.html Subject: OK : CMF-2.2 Zope-2.12 Python-2.6.5 : Linux From: CMF Tests Date: Tue Jul 27 21:53:33 EDT 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013339.html Subject: OK : CMF-trunk Zope-2.12 Python-2.6.5 : Linux From: CMF Tests Date: Tue Jul 27 21:55:33 EDT 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013340.html ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Test setup problems with Zope 2.13
Hi! Hanno Schlichting wrote: > Zope2 has: > > registerClass > registerIcon registerIcon is defined in CMFCore, not in Zope2. > HelpSys (effectively deprecated) > > CMF brings in: > > ToolInit > ContentInit ContentInit is only used for BBB. It registers oldstyle constructors. > I'd love to see someone tackle registerClass and at the same time > decouple ZMI add menu visibility and the OFS.CopySupport stuff. You mean the CopySupport issue I fixed 5 years ago? Or something different? http://svn.zope.org/?view=rev&rev=40552 five:registerClass doesn't require to specify an 'addview'. CopySupport works for all CMF content types without adding them to the ZMI add menu. We just can't use five:registerClass in OFS/OFSP because it doesn't support oldstyle constructors and legacy methods. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Test setup problems with Zope 2.13
Morning.
On Tue, Jul 27, 2010 at 1:09 PM, yuppie wrote:
> The whole registerPackage concept is a can of worms. We need real ZCML
> directives for *all* the stuff currently done in initialization
> functions. And to deprecate the usage of initialize instead of expanding
> that old concept to non-product packages.
Right. I think it's not all that many things left there.
Zope2 has:
registerClass
registerIcon
HelpSys (effectively deprecated)
CMF brings in:
ToolInit
ContentInit
I'd love to see someone tackle registerClass and at the same time
decouple ZMI add menu visibility and the OFS.CopySupport stuff. Well,
in general the CopySupport stuff could use some work and merging with
zope.copy / zope.copypastemove to correctly deal with persistent
parent pointers. But that's another story that also applies to the
ZEXP mechanism.
>> I reverted this now and all tests pass again. Both CMF 2.2 and CMF
>> trunk against Zope 2.13.
>
> I guess some more changes should be reverted. There is at least a
> ZopeTestCase.installPackage('OFS') in the FunctionalLayer of CMFCalendar.
I reverted the corresponding changeset and looked over my other
commits. I think that one was the only other change.
Hanno
___
Zope-CMF maillist - Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
