Re: [Zope-dev] SVN: zope.traversing/trunk/ zcml now only depends on zope.component meta, not zope.app.component
On Wed, 2009-04-29 at 00:59 +0200, Marius Gedminas wrote:
On Thu, Apr 23, 2009 at 08:01:36AM +0200, Christian Theune wrote:
On Fri, 2009-04-03 at 01:37 +0300, Marius Gedminas wrote:
Incidentally, I've a long-standing wish to be able to register browser
views in ZCML using the adapter directive.
class MyFineView(BrowserPage):
adapts(IMyContentObject, IBrowserRequest)
template = ViewPageTemplateFile('my_fine_view.pt')
def __call__(self):
# update form or whatever
return self.template()
adapter name=my_fine_view.html factory=.mod.MyFineView /
Maybe something to look for in Zope 4?
How about recording this wish on launchpad?
Sure, go ahead and do it!
Did I miss this thing belonging to April Fool's?
--
Christian Theune · c...@gocept.com
gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1
Zope and Plone consulting and development
signature.asc
Description: This is a digitally signed message part
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 8 OK
Summary of messages to the zope-tests list. Period Tue Apr 28 12:00:00 2009 UTC to Wed Apr 29 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 28 20:51:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011579.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 28 20:53:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011580.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 28 20:55:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011581.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Apr 28 20:57:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011582.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Tue Apr 28 20:59:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011583.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 28 21:01:15 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011584.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Tue Apr 28 21:03:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011585.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Tue Apr 28 21:05:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011586.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: set __parent__ and __name__ in Zope 2.12 OFS
Hanno Schlichting wrote: Chris Withers wrote: I'm also about -sys.maxint on these changes for Zope 2.12 as I'd like to see 2.12 out the door as soon as possible. Then we have a conflict of interest. My main goal for Zope 2.12 is to be based on the Zope Toolkit 1.0 release and loose quite some more stuff. My understanding is that the big drive for Zope 2.12 was to get it egg-based. That is now done, so lets get it out the door. I think Zope 2.13 would be an excellent target for moving to ZTK 1.0. There's no reason Zope 2.13 shouldn't follow as quickly after 2.12 as it is able, but I also see no reason to hold up 2.12 waiting for something which has no defined end point. cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: set __parent__ and __name__ in Zope 2.12 OFS
On 29.04.2009 15:28 Uhr, Chris Withers wrote: Hanno Schlichting wrote: Chris Withers wrote: I'm also about -sys.maxint on these changes for Zope 2.12 as I'd like to see 2.12 out the door as soon as possible. Then we have a conflict of interest. My main goal for Zope 2.12 is to be based on the Zope Toolkit 1.0 release and loose quite some more stuff. My understanding is that the big drive for Zope 2.12 was to get it egg-based. That is now done, so lets get it out the door. I think Zope 2.13 would be an excellent target for moving to ZTK 1.0. There's no reason Zope 2.13 shouldn't follow as quickly after 2.12 as it is able, but I also see no reason to hold up 2.12 waiting for something which has no defined end point. I strongly object inflationary Zope 2 releases. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: set __parent__ and __name__ in Zope 2.12 OFS
On Wed, Apr 29, 2009 at 16:09, Andreas Jung li...@zopyx.com wrote: On 29.04.2009 15:28 Uhr, Chris Withers wrote: Hanno Schlichting wrote: Chris Withers wrote: I'm also about -sys.maxint on these changes for Zope 2.12 as I'd like to see 2.12 out the door as soon as possible. Then we have a conflict of interest. My main goal for Zope 2.12 is to be based on the Zope Toolkit 1.0 release and loose quite some more stuff. My understanding is that the big drive for Zope 2.12 was to get it egg-based. That is now done, so lets get it out the door. I think Zope 2.13 would be an excellent target for moving to ZTK 1.0. There's no reason Zope 2.13 shouldn't follow as quickly after 2.12 as it is able, but I also see no reason to hold up 2.12 waiting for something which has no defined end point. I strongly object inflationary Zope 2 releases. Well, this isn't inflationary, is it? 2.12 is eggified. That deserves a new version number. If we then after that start changing how acquisition work, that also needs a new version number. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: set __parent__ and __name__ in Zope 2.12 OFS
On 29.04.2009 16:51 Uhr, Lennart Regebro wrote: On Wed, Apr 29, 2009 at 16:09, Andreas Jung li...@zopyx.com wrote: On 29.04.2009 15:28 Uhr, Chris Withers wrote: Hanno Schlichting wrote: Chris Withers wrote: I'm also about -sys.maxint on these changes for Zope 2.12 as I'd like to see 2.12 out the door as soon as possible. Then we have a conflict of interest. My main goal for Zope 2.12 is to be based on the Zope Toolkit 1.0 release and loose quite some more stuff. My understanding is that the big drive for Zope 2.12 was to get it egg-based. That is now done, so lets get it out the door. I think Zope 2.13 would be an excellent target for moving to ZTK 1.0. There's no reason Zope 2.13 shouldn't follow as quickly after 2.12 as it is able, but I also see no reason to hold up 2.12 waiting for something which has no defined end point. I strongly object inflationary Zope 2 releases. Well, this isn't inflationary, is it? 2.12 is eggified. That deserves a new version number. If we then after that start changing how acquisition work, that also needs a new version number. We would have to maintain four different major release of Zope: 2.10, 2.11, 2.12 and 2.13. Support for 2.10 can't be dropped since it is the requirement for Plone 3.X. A new major Zope 2.13 can be addressed when there are enough valuable features and changes that satisfy a new release. Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: i...@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
