Re: [Zope] New Zope2 releases available
Tres Seaver a écrit : [...] - Zope 2.10.11, http://www.zope.org/Products/Zope/2.10.22 short typo : - Zope 2.10.11, http://www.zope.org/Products/Zope/2.10.11 -- html head /head body bgcolor=#ff text=#00 img alt=Encolpe Degoute lt;encolpe.dego...@quadra-informatique.frgt; src=file:///home/edegoute/Images/mailsignpic2.png/ /body /html ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] z3c.form: GroupForm and ModificationEvents
Am 13.01.2010 um 06:08 schrieb Martin Aspeli: Michael Howitz wrote: Hi, it seems to me that z3c.form.group.GroupForm does not send enough ModificationEvents: only one event for the context of the GroupForm but not for each modified object in the groups. -1 to this being default behaviour. IObjectModifiedEvent is fired from EditForms, not from forms in general. GroupForm has an applyChanges method which send this event. The Group class collects some data for it in its applyChanges method. Normally, an EditForm is used to edit a context. The groups could come from various locations (we use groups to create fieldsets based on schema hints, but they're all logically part of the same content object). I would not expect more than one event sent (in fact, doing this would significantly break code in the wild). The refactoring needn't break the code in the wild by sending only one ModifiedEvent for each different context object being changed. When a group has the same context as the group form, I agree, there should not be two events. In a project of mine I have the following situation: I have a folder with some contained objects. A GroupForm displays the schema fields of the folder and the ones of all contained objects. When I modify one of the fields of a contained object I would expect a ModifiedEvent for this object. (Is this a valid expectation?) But GroupForm sends only one ModifiedEvent for the Folder (context of the form). This is even wrong in my case. At least the ModifiedEvent-Subscriber in zope.dublincore can't handle this and wrongly marks only the folder as modified. Do I have a very special use case which should be handled inside my project? Or should I change GroupForm to send a ModifiedEvent for each modified object? I think you should override the action handler and do this for your project. I don't think it should be the default behaviour. I can do so. But am I the only one who edits more than one object in a GroupForm and might need this feature? Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.form: GroupForm and ModificationEvents
Am 12.01.2010 um 22:22 schrieb Roger: Hi Michael Betreff: [Zope-dev] z3c.form: GroupForm and ModificationEvents [...] Do I have a very special use case which should be handled inside my project? Or should I change GroupForm to send a ModifiedEvent for each modified object? I'm not using group forms so I can't say if it's wrong or right. But I have a question. Does the ISublocation adapter not dispatch the modified event to the containers items? I think ISublocation does not help me here, as the folder is not changed only one item in it. The event wrongly (at least to me) tells the folder as modified. Are you sure that you use the ISublocation adapter which will dispatch events to container items? If this will not help, I think it's not bad to implement such an event notification. Probably in a method or with a marker which allows others to simply disable the additional event notification. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.form: GroupForm and ModificationEvents
Michael Howitz wrote: Am 13.01.2010 um 06:08 schrieb Martin Aspeli: Michael Howitz wrote: Hi, it seems to me that z3c.form.group.GroupForm does not send enough ModificationEvents: only one event for the context of the GroupForm but not for each modified object in the groups. -1 to this being default behaviour. IObjectModifiedEvent is fired from EditForms, not from forms in general. GroupForm has an applyChanges method which send this event. The Group class collects some data for it in its applyChanges method. Sure, but IIRC GroupForm is only really intended as a mixin. In any case, we shouldn't by default send IObjectModifiedEvents from something that isn't an edit form. Not all (group) forms are edit forms. And even for the EditForm scenario, most edit forms edit exactly one context. Your use case is very particular to your application. The refactoring needn't break the code in the wild by sending only one ModifiedEvent for each different context object being changed. When a group has the same context as the group form, I agree, there should not be two events. That would still break code. In a project of mine I have the following situation: I have a folder with some contained objects. A GroupForm displays the schema fields of the folder and the ones of all contained objects. When I modify one of the fields of a contained object I would expect a ModifiedEvent for this object. (Is this a valid expectation?) But GroupForm sends only one ModifiedEvent for the Folder (context of the form). This is even wrong in my case. At least the ModifiedEvent-Subscriber in zope.dublincore can't handle this and wrongly marks only the folder as modified. Do I have a very special use case which should be handled inside my project? Or should I change GroupForm to send a ModifiedEvent for each modified object? I think you should override the action handler and do this for your project. I don't think it should be the default behaviour. I can do so. But am I the only one who edits more than one object in a GroupForm and might need this feature? Perhaps. :) I don't think you can generalise this anyway. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Stepping back as Zope 2 release manager
On Mon, Jan 11, 2010 at 17:19, Andreas Jung li...@zopyx.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I would like to inform you that I intent to retreat from the Zope 2 release manager position soon. I have been serving the Zope community in this position for almost seven years and now it is time to move on Thanks a lot Andreas! I am too busy with other things and I would like to shift my focus on other Zope-related projects Zope3 Release Manager? ;) -- Sebastien Douche sdou...@gmail.com Twitter: http://bit.ly/afkrK (agile, python, open source) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope2 releases available
Tres Seaver a écrit : [...] - Zope 2.10.11, http://www.zope.org/Products/Zope/2.10.22 short typo : - Zope 2.10.11, http://www.zope.org/Products/Zope/2.10.11 -- html head /head body bgcolor=#ff text=#00 img alt=Encolpe Degoute lt;encolpe.dego...@quadra-informatique.frgt; src=file:///home/edegoute/Images/mailsignpic2.png/ /body /html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Tue Jan 12 12:00:00 2010 UTC to Wed Jan 13 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jan 12 20:36:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013371.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Jan 12 20:38:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013372.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 12 20:40:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013373.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 12 20:42:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013374.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 12 20:44:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013375.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Jan 12 20:46:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013376.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Preparing a new release for zope.sendmail
Hello, * 2010-01-13 01:41, Tres Seaver wrote: The 3.7.0 version breaks Zope 2.12, which still expects to be able to import QueueProcessorThread from the old location. I worked around the problem for the moment by pinning 'zope.sendmail3.7.0', but it seems to me that the BBB import should be kept (likely forever). I'm preparing a new release which will keep the BBB import, sorry for breaking zope 2.12 (I did not expect it to import something from zope.sendmail...). Fabio ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope2 releases available
Am 13.01.2010, 04:23 Uhr, schrieb Tres Seaver tsea...@palladion.com: - - Zope 2.12.3, http://pypi.zope.org/pypi/Zope2/2.12.3 Please note that the 2.12 releases are made only on the Python Package Index server, aka PyPI or the Cheeseshop. Thanks Tres, some components require compiling or binary eggs on Windows, ie. zope.container 3.10 for Python 2.6. Is there an easy way of checking for such eggs? 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-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope2 releases available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charlie Clark wrote: Am 13.01.2010, 04:23 Uhr, schrieb Tres Seaver tsea...@palladion.com: - - Zope 2.12.3, http://pypi.zope.org/pypi/Zope2/2.12.3 Please note that the 2.12 releases are made only on the Python Package Index server, aka PyPI or the Cheeseshop. Thanks Tres, some components require compiling or binary eggs on Windows, ie. zope.container 3.10 for Python 2.6. Is there an easy way of checking for such eggs? There is the zope2kgs that I wrote for generating the download index (by accessing PyPI through its XMRPC). It should be easy to extend the package by checking the existence of Windows related packages (you should have to get hold of the files list through XMLRPC and check for something like *win* within the list of package files). Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktN4ygACgkQCJIWIbr9KYzrMACg3fkgmc1HbJ15ux/niblrJmEv HRkAoOn9VhQWQDoQb8zG03PoDeMjjS1w =+/yq -END PGP SIGNATURE- attachment: lists.vcf___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope2 releases available
Am 13.01.2010, 16:13 Uhr, schrieb Andreas Jung li...@zopyx.com: There is the zope2kgs that I wrote for generating the download index (by accessing PyPI through its XMRPC). It should be easy to extend the package by checking the existence of Windows related packages (you should have to get hold of the files list through XMLRPC and check for something like *win* within the list of package files). Hi Andreas, probably overkill for this current project thanks to virtualisation but definitely something that should be worked on. As would, of course, buildots that could do something with the resulting information! 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-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Preparing a new release for zope.sendmail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fabio Tranchitella wrote: Hello, * 2010-01-13 01:41, Tres Seaver wrote: The 3.7.0 version breaks Zope 2.12, which still expects to be able to import QueueProcessorThread from the old location. I worked around the problem for the moment by pinning 'zope.sendmail3.7.0', but it seems to me that the BBB import should be kept (likely forever). I'm preparing a new release which will keep the BBB import, sorry for breaking zope 2.12 (I did not expect it to import something from zope.sendmail...). Great, thanks! Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktON/4ACgkQ+gerLs4ltQ5BkQCghsh+JWxIzmdWqJKZ7L6T1rHi RzwAn2rQD3BSUPppBgZNX5VW/RoJJ/bX =Qc6V -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-CMF] CMF Tests: 4 OK
Summary of messages to the cmf-tests list. Period Tue Jan 12 12:00:00 2010 UTC to Wed Jan 13 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 Jan 12 20:54:40 EST 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-January/012483.html Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux From: CMF Tests Date: Tue Jan 12 20:56:40 EST 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-January/012484.html Subject: OK : CMF-2.2 Zope-2.12 Python-2.6.4 : Linux From: CMF Tests Date: Tue Jan 12 20:58:40 EST 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-January/012485.html Subject: OK : CMF-trunk Zope-trunk Python-2.6.4 : Linux From: CMF Tests Date: Tue Jan 12 21:00:40 EST 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-January/012486.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
