Re: [Zope-dev] Overhauling the Zope 2 presentation on zope.org
Lennart Regebro wrote: On Sat, Feb 21, 2009 at 05:14, Martin Aspeli optilude+li...@gmail.com wrote: The new.zope.org initiative died because no-one could write any content. Even then 5-10 pages of content requires for a very basic microsite was too much, and several separate calls for volunteers produced almost no actual content, even if several people showed an interest. Where did you ask for volunteers? I don't remember seeing in on zope-web, but I could have missed it or just forgot. zope-web and this list. My attitude has always been, and is still: Build it and they will come. We don't need content, we need a site. Besides, the current state is, and has for a long time been, almost worse than having no site at all, and definitely worse than having a couple of microsites even if these have almost no content. That was the idea. It wasn't supposed to be big at all. I'm just saying that at the time, no-one seemed to put it high enough on their list of priorities to actually write any content. I really hope that's changed. Another observation: the thing that most people seem to want to make a site about was the ZODB. We nearly had enough content for a ZODB microsite thanks to Christian Theune and a few others. If there is one page, then that's enough. Hence, there should have been a zodb.zope.org by now. :-/ Please go make this happen if you can. It's very important. I can't anymore. 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 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] Overhauling the Zope 2 presentation on zope.org
Andreas Jung wrote: I just checked new.zope.org and I think that your idea appears reasonable. The only thing I dislike about the new.zope.org design is the navigation tree at the bottom of the page. All other parts of the design could be re-used directly - perhaps with some slightly modifications. Er... it's not supposed to be there. It wasn't there last time I looked - it was on the left. Seems to be some problem with the CSS. Two questions: - - how can grant me access to the new.zope.org Plone site in order to look at the stuff and for playing around? Check your mail. I've created you an account and made you Manager. - - are there any legal issues with the design layout in case we want to make modifications? I know that the designer of new.zope.org theme made some trouble when it came to discussion about the briefs and donouts on the new.zope.org frontpage. I don't think he had any problems with changing them, but he wanted to have some oversight if we changed the design or re-used it elsewhere. Speak to Lovely Systems. 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 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] Overhauling the Zope 2 presentation on zope.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 21, 2009, at 08:55 , Andreas Jung wrote: - - are there any legal issues with the design layout in case we want to make modifications? I know that the designer of new.zope.org theme made some trouble when it came to discussion about the briefs and donouts on the new.zope.org frontpage. Yes there are. In essence, do not use the design, period. Here are the reasons I had for voting against continuing new.zope.org: - the design is not free and re-usable - the designer has stopped providing any support for the design, and the person who found and tasked the designer with the design work, Jodok, has given up on the whole issue because he is frustrated as well - the website structure and presentation is too Zope 3-centric. Zope2 is basically hidden away. IMHO this may reflect the original creators' thinking, but doesn't reflect the world out there, which still uses mainly Zope2. - no one has given any thought to migration issues (old URLs will fail, zope.org users with login will complain that there is no login anymore) The ZF board vote was to stop supporting the project on the current path. Everyone still wants to see a new zope.org site, but this particular project wasn't going anywhere anymore. Several project managers came, spent much effort trying to make it work, and left again. It's better to start with a clean slate, and maybe with a smaller set of goals. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkmfyMoACgkQRAx5nvEhZLK5ggCgidiMHbx/uhwvNmXMyXl8t+Ka PRsAnRZu7Lg4zz91OnFGTVszatw9rjt+ =spJH -END PGP SIGNATURE- ___ 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] Overhauling the Zope 2 presentation on zope.org
On Sat, Feb 21, 2009 at 10:14, Martin Aspeli optilude+li...@gmail.com wrote: Please go make this happen if you can. It's very important. I can't anymore. As far as I can see, it's a question of - setting up a server, I would recommend a Plone site with the new Zope theme. - creating a zodb.zope.org DNS record and pointing it at that Zope site. - pasting in the content. - giving zodb people manager access to the plone site. I can not technically do any of that, as I don't have a server to put it on, no access to the Zope.org dns and no content. The rest I can do. :) -- Lennart Regebro: Pythonista, Barista, Notsotrista. 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] SVN: zope2book/trunk/ Lot's of updates over the weekend!
Andreas Jung wrote at 2009-2-16 19:50 +0100: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.02.2009 19:43 Uhr, Dieter Maurer wrote: Andreas Jung wrote at 2009-2-16 19:20 +0100: ... Please come off it. Either become an active contributor and participate in our dictatorship I will never participate in your dictatorship! How childish. I hate dictatorship - consequently I will not participate. -- Dieter ___ 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] [Checkins] SVN: z3c.pagelet/trunk/ Using ``z3c.ptcompat`` instead of deprecated ``z3c.pt.compat``.
Am 21.02.2009 um 11:23 schrieb Michael Howitz: Log message for revision 96885: Using ``z3c.ptcompat`` instead of deprecated ``z3c.pt.compat``. [...] There are still test failures and I don't know how to fix them. Anyone? File /Users/mac/Documents/tmp/z3c.pagelet/src/z3c/pagelet/ README.txt, line 164, in README.txt Failed example: print myView() Expected: Traceback (most recent call last): ... ContentProviderLookupError: pagelet Got: Traceback (most recent call last): ... PTRuntimeError: ['Compilation failed', 'zope.tal.taldefs.TALError: Unrecognized expression type provider. in expression u\'provider:pagelet\', at line 4, column 7'] There are even more errors complaining about 'Unrecognized expression type provider'. 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 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] SVN: zope2book/trunk/ Lot's of updates over the weekend!
Jens Vagelpohl wrote at 2009-2-16 20:43 +0100: ... On Feb 16, 2009, at 19:43 , Dieter Maurer wrote: Andreas Jung wrote at 2009-2-16 19:20 +0100: ... Please come off it. Either become an active contributor and participate in our dictatorship I will never participate in your dictatorship! Only those who participate can influence the direction. As I will make it with ZClasses, I will participate outside your circles. Thus, you may dictate and I fight your dictatorship -- Dieter ___ 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] SVN: zope2book/trunk/ Lot's of updates over the weekend!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21.02.2009 11:27 Uhr, Dieter Maurer wrote: Jens Vagelpohl wrote at 2009-2-16 20:43 +0100: ... On Feb 16, 2009, at 19:43 , Dieter Maurer wrote: Andreas Jung wrote at 2009-2-16 19:20 +0100: ... Please come off it. Either become an active contributor and participate in our dictatorship I will never participate in your dictatorship! Only those who participate can influence the direction. As I will make it with ZClasses, I will participate outside your circles. Thus, you may dictate and I fight your dictatorship Zope is like anarchy - not dictatorship. So you're fighting against non-existing enemies :-) Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmf2P4ACgkQCJIWIbr9KYwpvACdGimY5X3SCdco2XO5ghlXQd9+ lWQAn23/5LTeiHvOldSu2Dbr2vr9MgUR =vAUP -END PGP SIGNATURE- 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] SVN: zope2book/trunk/ Lot's of updates over the weekend!
On Sat, Feb 21, 2009 at 11:27, Dieter Maurer die...@handshake.de wrote: As I will make it with ZClasses, I will participate outside your circles. Thus, you may dictate and I fight your dictatorship With the revolutionary eggification of the masses that is underway the dictatorship has ended. Zope 2.12 is a libertarian meritodemocracy. -- Lennart Regebro: Pythonista, Barista, Notsotrista. 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] SVN: zope2book/trunk/ Lot's of updates over the weekend!
On Sat, Feb 21, 2009 at 11:37, Lennart Regebro rege...@gmail.com wrote: With the revolutionary eggification of the masses that is underway the dictatorship has ended. Zope 2.12 is a libertarian meritodemocracy. Well, at least if you have svn access. :) -- Lennart Regebro: Pythonista, Barista, Notsotrista. 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] Overhauling the Zope 2 presentation on zope.org
Lennart Regebro wrote: On Sat, Feb 21, 2009 at 10:14, Martin Aspeli optilude+li...@gmail.com wrote: Please go make this happen if you can. It's very important. I can't anymore. As far as I can see, it's a question of - setting up a server, I would recommend a Plone site with the new Zope theme. We have this already. - creating a zodb.zope.org DNS record and pointing it at that Zope site. This can get done quickly. We got new.zope.org in a week. - pasting in the content. The problem is having the content. - giving zodb people manager access to the plone site. They've had that for over a year. :-) 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 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] Overhauling the Zope 2 presentation on zope.org
Jens Vagelpohl wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 21, 2009, at 08:55 , Andreas Jung wrote: - - are there any legal issues with the design layout in case we want to make modifications? I know that the designer of new.zope.org theme made some trouble when it came to discussion about the briefs and donouts on the new.zope.org frontpage. Yes there are. In essence, do not use the design, period. Here are the reasons I had for voting against continuing new.zope.org: - the design is not free and re-usable - the designer has stopped providing any support for the design, and the person who found and tasked the designer with the design work, Jodok, has given up on the whole issue because he is frustrated as well - the website structure and presentation is too Zope 3-centric. Zope2 is basically hidden away. IMHO this may reflect the original creators' thinking, but doesn't reflect the world out there, which still uses mainly Zope2. - no one has given any thought to migration issues (old URLs will fail, zope.org users with login will complain that there is no login anymore) The ZF board vote was to stop supporting the project on the current path. Everyone still wants to see a new zope.org site, but this particular project wasn't going anywhere anymore. Several project managers came, spent much effort trying to make it work, and left again. It's better to start with a clean slate, and maybe with a smaller set of goals. I wasn't aware of this vote, but I'm happy to abide by it. I think they are sensible decisions. I also think that the Zope world and the role of Zope 3 and eggs and all that has changed in the last year to the point where some of the original vision (and the role of Grok etc) is not necessarily correct. 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 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] Coding style clarifications
Zvezdan Petkovic wrote at 2009-2-19 13:06 -0500: I can adapt to any style and believe that the fine grain details should not be dogmatically enforced but rather allow for variations in such subjective preferences. +1 -- Dieter ___ 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] Overhauling the Zope 2 presentation on zope.org
On Sat, Feb 21, 2009 at 11:59, Martin Aspeli optilude+li...@gmail.com wrote: We Yes. But not *I*. And you asked if *I* could get it done. :) Perhaps you meant if I could nag people into doing it. I doubt that I could. I'm not good at making people do things for free. :) I think the way your formulated this is indicative of the problems. It's a case of Somebody is not working here. I.e. This should be done or Somebody needs to do X. Well, there isn't anybody called Somebody here, so as long as Somebody needs to do it, it won't get done. :) This is one of the common obstacles of committee work, and it seems zope-web unfortunately got a dose of it. Maybe we are getting out of the slump thanks to Andreas, but if not I again suggest the Zope Foundation appoints a Web Tsar with full access to everything that gets completely free hands to do whatever he wants (after the foundation has taken a backup of everything) and see what happens. :) I'm also lazy, which are the reasons I haven't volunteered for the role of Web Tsar already, as being bad at getting people to work for free would mean I have to do everything myself, and I'm too lazy for that. :) -- Lennart Regebro: Pythonista, Barista, Notsotrista. 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 )
[Zope-dev] Zope Tests: 4 OK, 4 Failed
Summary of messages to the zope-tests list. Period Fri Feb 20 12:00:00 2009 UTC to Sat Feb 21 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures - Subject: FAILED (errors=1) : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Fri Feb 20 20:55:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011157.html Subject: FAILED (errors=1) : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Feb 20 20:57:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011158.html Subject: FAILED (errors=1) : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Fri Feb 20 20:59:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011159.html Subject: FAILED (failures=1, errors=1) : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri Feb 20 21:01:08 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011160.html Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Fri Feb 20 20:47:00 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011153.html Subject: OK : Zope-2.9 Python-2.4.6 : Linux From: Zope Tests Date: Fri Feb 20 20:49:01 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011154.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Fri Feb 20 20:51:06 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011155.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Feb 20 20:53:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011156.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] Overhauling the Zope 2 presentation on zope.org
Lennart Regebro wrote: On Sat, Feb 21, 2009 at 11:59, Martin Aspeli optilude+li...@gmail.com wrote: We Yes. But not *I*. And you asked if *I* could get it done. :) Perhaps you meant if I could nag people into doing it. I doubt that I could. I'm not good at making people do things for free. :) I think the way your formulated this is indicative of the problems. It's a case of Somebody is not working here. I.e. This should be done or Somebody needs to do X. Well, there isn't anybody called Somebody here, so as long as Somebody needs to do it, it won't get done. :) Sure. This wasn't the approach when I was actually trying to get something done. I specifically asked for volunteers for specific tasks. It didn't work at the time. This is one of the common obstacles of committee work, and it seems zope-web unfortunately got a dose of it. Maybe we are getting out of the slump thanks to Andreas, but if not I again suggest the Zope Foundation appoints a Web Tsar with full access to everything that gets completely free hands to do whatever he wants (after the foundation has taken a backup of everything) and see what happens. :) The problem is not giving people decision making power. The problem is getting content. Somebody has to write it. We had carte blanche on what messages to put out there and how to structure things. I'm also lazy, which are the reasons I haven't volunteered for the role of Web Tsar already, as being bad at getting people to work for free would mean I have to do everything myself, and I'm too lazy for that. :) IMHO, the way the Zope community is structured, it's very hard to get people to contribute this kind of thing. I hope things are different now. The work that happened with the Zope book is encouraging, for example. However, most people who care enough about Zope to want the website to be better are too busy or too much into coding. Unlike, say, Rails, there isn't a large community of fanboys who want to contribute and have time on their hands and the right soft skills. 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 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] zope2docs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In preparation for the upcoming Zope 2.12 release we reorganized the Zope 2 documentation: - - all related documentation is now maintained a restructured text document in SVN: svn+ssh://svn.zope.org/repos/main/zope2docs - - The Zope Book, The Zope Developers Guide and some ZODB articles have been converted from STX to ReST - - The Zope 2.12 doc folder has been restified and is included within the zope2docs folder through a svn:external - - The Zope 2 specific documentation including releases notes will be generated in the future using Sphinx from 'zope2docs2' and published on docs.zope.org Thanks to Hanno and Tres for reSTifying the Zope book and the ZDG. 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 PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmgDVAACgkQCJIWIbr9KYyZMQCfShleZE5uqRL2f/UJvXxwkz8X QKoAmQHSNGC/mJMxxznzK79aAPidRc9k =Nw53 -END PGP SIGNATURE- 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] zope2docs
thanks a lot for the effort that has been put into the new zope documentation. I have a litte wish: the colors of the index (light green on whit) is uncomfortable to my eyes and hard to read. maybe this could be changed to a more contrasting combination? robert Andreas Jung schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In preparation for the upcoming Zope 2.12 release we reorganized the Zope 2 documentation: - - all related documentation is now maintained a restructured text document in SVN: svn+ssh://svn.zope.org/repos/main/zope2docs - - The Zope Book, The Zope Developers Guide and some ZODB articles have been converted from STX to ReST - - The Zope 2.12 doc folder has been restified and is included within the zope2docs folder through a svn:external - - The Zope 2 specific documentation including releases notes will be generated in the future using Sphinx from 'zope2docs2' and published on docs.zope.org Thanks to Hanno and Tres for reSTifying the Zope book and the ZDG. 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 PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmgDVAACgkQCJIWIbr9KYyZMQCfShleZE5uqRL2f/UJvXxwkz8X QKoAmQHSNGC/mJMxxznzK79aAPidRc9k =Nw53 -END PGP SIGNATURE- ___ 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 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] z3c.form update issues
Hi all I fixed a z3c.form issue where util.Manager keys and values get append more then one time by calling update more then once on widgets or actions. For doing so, I implemented a UniqueOrderedKeys class for util.Manager._data_keys and a decorator which will prevent to override them. See z3c.form.util.py line: 120 Can you please review if this and let me know it this is compatible with our own z3c.form parts? My motivation to deep into this is to find a better way how we use the update track. I think we should separate the update process into a setup and execute concept. I have the feeling, but could not really tell it right now, that we need to separate execute for prevent calling execute more then once during calling update. Update should get called more then once at least if it comes to calculate button/handler conditions. Because it's possible that an action execute call manipulates something which will change the button condition which we need to recalculate within an action update call. Any hints/ideas about that. Or do you know a good use case for this problem. It also smells to me that the MultiWidget or the ObjectWidgets implementation could be more robust within a better update/execute concept. Regards Roger Ineichen _ END OF MESSAGE ___ 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] Overhauling the Zope 2 presentation on zope.org
On Sat, Feb 21, 2009 at 14:11, Martin Aspeli optilude+li...@gmail.com wrote: IMHO, the way the Zope community is structured, it's very hard to get people to contribute this kind of thing. I hope things are different now. The work that happened with the Zope book is encouraging, for example. However, most people who care enough about Zope to want the website to be better are too busy or too much into coding. Unlike, say, Rails, there isn't a large community of fanboys who want to contribute and have time on their hands and the right soft skills. This is absolutely true. I'll put up Zope.org as a possible discussion item for the OpenSpace, maybe somebody has some bright idea. -- Lennart Regebro: Pythonista, Barista, Notsotrista. 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] zope2docs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 robert rottermann wrote: thanks a lot for the effort that has been put into the new zope documentation. I have a litte wish: the colors of the index (light green on whit) is uncomfortable to my eyes and hard to read. maybe this could be changed to a more contrasting combination? +10 from me. Readability should trump design every time. Andreas Jung schrieb: In preparation for the upcoming Zope 2.12 release we reorganized the Zope 2 documentation: - all related documentation is now maintained a restructured text document in SVN: svn+ssh://svn.zope.org/repos/main/zope2docs - The Zope Book, The Zope Developers Guide and some ZODB articles have been converted from STX to ReST - The Zope 2.12 doc folder has been restified and is included within the zope2docs folder through a svn:external - The Zope 2 specific documentation including releases notes will be generated in the future using Sphinx from 'zope2docs2' and published on docs.zope.org Thanks to Hanno and Tres for reSTifying the Zope book and the ZDG. Baiju did the main work on the ZDG: I just slurped the TTW content into SVN. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJoDkM+gerLs4ltQ4RAnJpAJ0QU3r6CwP08WtWX4iMqw5XhZA2SwCgkb9W S57lPagcGIZslydxGGZcvx0= =GooC -END PGP SIGNATURE- ___ 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] z3c.form update issues
2009/2/21 Roger Ineichen d...@projekt01.ch: Hi all I fixed a z3c.form issue where util.Manager keys and values get append more then one time by calling update more then once on widgets or actions. For doing so, I implemented a UniqueOrderedKeys class for util.Manager._data_keys and a decorator which will prevent to override them. See z3c.form.util.py line: 120 Can you please review if this and let me know it this is compatible with our own z3c.form parts? My motivation to deep into this is to find a better way how we use the update track. I think we should separate the update process into a setup and execute concept. I have the feeling, but could not really tell it right now, that we need to separate execute for prevent calling execute more then once during calling update. Update should get called more then once at least if it comes to calculate button/handler conditions. Because it's possible that an action execute call manipulates something which will change the button condition which we need to recalculate within an action update call. Any hints/ideas about that. Or do you know a good use case for this problem. It also smells to me that the MultiWidget or the ObjectWidgets implementation could be more robust within a better update/execute concept. IIRC, the update and execute phases are already separated for actions (you call actions.update() for setup and actions.execute() for actual execting) and that fact is used in MultiWidget and many custom forms. -- WBR, Dan Korostelev ___ 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] z3c.form update issues
Hi Dan Betreff: Re: [Zope-dev] z3c.form update issues 2009/2/21 Roger Ineichen d...@projekt01.ch: Hi all I fixed a z3c.form issue where util.Manager keys and values get append more then one time by calling update more then once on widgets or actions. For doing so, I implemented a UniqueOrderedKeys class for util.Manager._data_keys and a decorator which will prevent to override them. See z3c.form.util.py line: 120 Can you please review if this and let me know it this is compatible with our own z3c.form parts? My motivation to deep into this is to find a better way how we use the update track. I think we should separate the update process into a setup and execute concept. I have the feeling, but could not really tell it right now, that we need to separate execute for prevent calling execute more then once during calling update. Update should get called more then once at least if it comes to calculate button/handler conditions. Because it's possible that an action execute call manipulates something which will change the button condition which we need to recalculate within an action update call. Any hints/ideas about that. Or do you know a good use case for this problem. It also smells to me that the MultiWidget or the ObjectWidgets implementation could be more robust within a better update/execute concept. IIRC, the update and execute phases are already separated for actions (you call actions.update() for setup and actions.execute() for actual execting) and that fact is used in MultiWidget and many custom forms. Yes, I think we should carefully review this part and probably add action.update after action.execute. Right now, without looking at the code I think we do not update actions after execute. Which could end in bad action handler setup because of skipped action condition handling after execute actions. I'll see later if I take another look at that part. Regards Roger Ineichen _ END OF MESSAGE -- WBR, Dan Korostelev ___ 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] z3c.form update issues
2009/2/21 Roger Ineichen d...@projekt01.ch: we should carefully review this part and probably add action.update after action.execute. Right now, without looking at the code I think we do not update actions after execute. Which could end in bad action handler setup because of skipped action condition handling after execute actions. I'll see later if I take another look at that part. Ah, you mean the update method of the form base classes. Yeah, there's no action update performed after executions currently. But I don't think we should just add another updateActions call after execution as it can be quite expensive. The button actions call their widgets' update methods that performs another thousand of adaptations calls. :) However, the problem is very actual and I personally had it in some of my forms. The most obvious use case is when we use the delete button to delete all entries in the list and then we don't want to show the delete button anymore. One (probably nice) solution that comes in my mind is to make the form somehow aware if it needs to re-update its actions and to provide a way for the action handler to signal about that. Probably, a simple boolean form instance variable will do the trick :) -- WBR, Dan Korostelev ___ 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] z3c.form update issues
2009/2/21 Dan Korostelev nad...@gmail.com: 2009/2/21 Roger Ineichen d...@projekt01.ch: we should carefully review this part and probably add action.update after action.execute. Right now, without looking at the code I think we do not update actions after execute. Which could end in bad action handler setup because of skipped action condition handling after execute actions. ... snip ... One (probably nice) solution that comes in my mind is to make the form somehow aware if it needs to re-update its actions and to provide a way for the action handler to signal about that. Probably, a simple boolean form instance variable will do the trick :) I just checked in a fix like I described above. It seems to work at leasts for tests.:-) Can you please review it? -- WBR, Dan Korostelev ___ 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] z3c.form update issues
Hi Dan Betreff: Re: [Zope-dev] z3c.form update issues 2009/2/21 Dan Korostelev nad...@gmail.com: 2009/2/21 Roger Ineichen d...@projekt01.ch: we should carefully review this part and probably add action.update after action.execute. Right now, without looking at the code I think we do not update actions after execute. Which could end in bad action handler setup because of skipped action condition handling after execute actions. ... snip ... One (probably nice) solution that comes in my mind is to make the form somehow aware if it needs to re-update its actions and to provide a way for the action handler to signal about that. Probably, a simple boolean form instance variable will do the trick :) I just checked in a fix like I described above. It seems to work at leasts for tests.:-) Can you please review it? Yeah great, that's exactly what we need to do. Thanks a lot! Regards Roger Ineichen _ END OF MESSAGE -- WBR, Dan Korostelev ___ 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] z3c.form update issues
On Saturday 21 February 2009, Roger Ineichen wrote: I fixed a z3c.form issue where util.Manager keys and values get append more then one time by calling update more then once on widgets or actions. For doing so, I implemented a UniqueOrderedKeys class for util.Manager._data_keys and a decorator which will prevent to override them. See z3c.form.util.py line: 120 Can you please review if this and let me know it this is compatible with our own z3c.form parts? I would have simply cleared the entire manager upon update() again. Otherwise, how do you handle an item disappearing when update() is called again? My motivation to deep into this is to find a better way how we use the update track. I think we should separate the update process into a setup and execute concept. I have the feeling, but could not really tell it right now, that we need to separate execute for prevent calling execute more then once during calling update. I see what you are saying and I think you are right. However, a formal split may be enough. Could we not just set a flag called wasExecuted? Update should get called more then once at least if it comes to calculate button/handler conditions. Because it's possible that an action execute call manipulates something which will change the button condition which we need to recalculate within an action update call. Absolutely. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ 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] z3c.form update issues
On Saturday 21 February 2009, Dan Korostelev wrote: One (probably nice) solution that comes in my mind is to make the form somehow aware if it needs to re-update its actions and to provide a way for the action handler to signal about that. Probably, a simple boolean form instance variable will do the trick :) I like that idea, since I agree with your argument that updating actions can be expensive. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ 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 )
