[Zope3-dev] Add flexibility to zope.formlib.form.EditFormBase
Hi, I'm using zope.formlib.form.EditFormBase and want to normalize data before saving it. Saving is done by the applyChanges function which is called from handle_edit_action. The problem is that handle_edit_action is an action, so I can't easily subclass and do a super call to handle_edit_action. If I add my own handle_edit_action I have to copy-paste the code from formlib because applyChanges is a function, not a method on the class. My solution would be to add an applyChanges method to zope.formlib.form.EditFormBase which calls the applyChanges function. Any objections? Yours sincerely, Michael Howitz gocept gmbh co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon: +49 345 12298898 · fax: +49 345 12298891 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] tracking satellite project's trunks
On May 4, 2007, at 6:25 AM, Baiju M wrote: ... We will be using same Zope 3 resources for bug tracking, mailing list and wiki for these satellite project's, is it ? Thanks a very good question. I don't think we need more mailing lists. In fact, I think zope3-dev and zope-dev should be merged. I suspect that these projects will eventually get their own projects in launchpad, but I'm not sure. I'm also not sure about wikis. I don't think we need to do anything about this any time soon. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] tracking satellite project's trunks
Am Freitag, den 04.05.2007, 06:51 -0400 schrieb Jim Fulton: On May 4, 2007, at 6:25 AM, Baiju M wrote: ... We will be using same Zope 3 resources for bug tracking, mailing list and wiki for these satellite project's, is it ? Thanks a very good question. I don't think we need more mailing lists. In fact, I think zope3-dev and zope-dev should be merged. I suspect that these projects will eventually get their own projects in launchpad, but I'm not sure. I'm also not sure about wikis. I don't think we need to do anything about this any time soon. Right. In the last days I felt like in the future we should spend some quality time (maybe face to face at a conference or sprint) to review what happened to the way people work with Zope and how we define it. There were discussions about this popping up over the last 18 months again and again. With the current step to the egg-based release I see us crossing an important border that will require us to think about those philosophical questions again. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] tracking satellite project's trunks
Hi Fred. I like this very much too :-) If you want your product to sing, you can include sing packages, if you want it to dance, you can include dance packages. What's more, is that most python projects are moving to egg distribution, if not there already. Besides eggs, wsgi is allowing many more things to occur on an app level overall. Overall, these developments create some very interesting and exciting potential to mix and match functionality without the constraints of a particular framework. Regards, David Fred Drake wrote: On 5/4/07, Christian Theune [EMAIL PROTECTED] wrote: Right. In the last days I felt like in the future we should spend some quality time (maybe face to face at a conference or sprint) to review what happened to the way people work with Zope and how we define it. I think what's happened is something very simple, inevitable, and reasonable: We've stopped working on Zope 3 and moved to working on our applications. This changes how we think about the place of Zope 3 in our work more than anything else. It's no longer a product itself, but a means to an end. This is what we intended from the beginning, but the shape we predicted for the result was more similar to Zope 2 than has turned out to be useful. The move to separate satellite projects is really a move from using an all-singing, all-dancing framework for all applications to using different sets of libraries for each application based on what's needed for the application. I think this is a good thing. -Fred ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.app.twisted.main and zope multiservice
I am wondering if as part of bootstrapping zope, that a utility could not be set up in the site manager that could hang on the zope multiservice object. Methods available for the utility could allow you access to this after booting zope. Is this reasonable? Many thanks. Regards, David David Pratt wrote: Hi Martijn. Many thanks for your reply. I was not aware of your project so it is quite nice to see. I am hoping to try it out. :-) At zope's startup, a multiservice is started that currently adds the servers setup in the zope.conf. I have created configuration for additional clients and servers to use the existing thread pool and currently adding them to the multiservice using a modified main.py By having access to the multiservice object, you have complete control of each service in the app as well as the ability to incorporate other services to an already running reactor. Interaction within the app using multiple reactors is not safe - so access to this object allows you to add, remove, start or stop services. I also want the configuration to be explicit - so to using zconfig and recipes. Overall, I am integrating apps into buildouts as well. It is useful to be explicit here too since your configuration will otherwise be in a single egg somewhere. This could make it awkward to run multiple servers performing the same task on a machine, which is the pattern I am working with. Regards, David Martijn Pieters wrote: On 5/3/07, David Pratt [EMAIL PROTECTED] wrote: Hi. I'm really wanting to do more with twisted in zope. One thing that would make this much easier is to have a means of getting hold of the twisted multiservice following startup as opposed to using a different main.py (as I have been) to allow the other services to be added, started or stopped at, or any time following startup. I am not sure what you are looking for, but I have no trouble starting additional services after Zope startup. See my Wing IDE integration for Zope3, for example; http://trac.zopatista.com/zopatista/browser/z3wingdbg/trunk/ It starts additional services, such as a single-threaded HTTP debug server on a separate port, either at Zope start or later as the user requests. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/fairwinds%40eastlink.ca ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] tracking satellite project's trunks
Right. Am Freitag, den 04.05.2007, 07:55 -0400 schrieb Fred Drake: I think what's happened is something very simple, inevitable, and reasonable: We've stopped working on Zope 3 and moved to working on our applications. This changes how we think about the place of Zope 3 in our work more than anything else. It's no longer a product itself, but a means to an end. This is what we intended from the beginning, but the shape we predicted for the result was more similar to Zope 2 than has turned out to be useful. The move to separate satellite projects is really a move from using an all-singing, all-dancing framework for all applications to using different sets of libraries for each application based on what's needed for the application. I think this is a good thing. However, something that changes is the identity of the project to various people. I think it gets more challenging to pull on the same rope and in the same direction under those circumstances. On the other hand it actually might get easier as we're pulling smaller ropes. ;) -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1318 Blamelist: ctheune BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1328 Blamelist: ctheune BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: tracking satellite project's trunks
Christian Theune wrote: Same here. I'm feeling like I'm not yet understanding what the trunk will be used like. I'm wondering if we need to maintain a Zope 3 project with any code in it at all (or nearly so). Could Zope 3 just be a buildout with a configuration that creates a Zope 3 application with a bunch of stock components. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: tracking satellite project's trunks
Am Freitag, den 04.05.2007, 12:16 -0400 schrieb Benji York: Christian Theune wrote: Same here. I'm feeling like I'm not yet understanding what the trunk will be used like. I'm wondering if we need to maintain a Zope 3 project with any code in it at all (or nearly so). Could Zope 3 just be a buildout with a configuration that creates a Zope 3 application with a bunch of stock components. Yes it could. However, we don't have enough time to create this kind of buildout. I tried doing that at PyCon and we aren't there yet. It also requires us to deal with upgrading existing instances that are 'old style'. In the future this is likely to happen. Just not for Zope 3.4 Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Experimental alternative/supplement for buildbot
Hi, I've been trying to find a solution to run the individual tests of all top-level projects in the repository. I've set up a cruise control server in our office that monitors the SVN and automatically picks up any top-level project that defines a buildout.cfg in its trunk. You can watch it work here: http://uter.gocept.com:/ It reacts to changes in SVN automatically. New projects will be picked up every 3 hours. This thing is experimental. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Experimental alternative/supplement for buildbot
Gnh. Apart from the shiny UI this thing is unusable for this purpose. It runs a long-running ruby process for each project that it monitors. That would be around 150-200 in our case. My server died two times today when monitoring about 30 processes. That's not gonna work. ;) I'll try figuring out whether buildbot can fit into this picture a little bit better. Christian Am Freitag, den 04.05.2007, 19:16 +0200 schrieb Christian Theune: Hi, I've been trying to find a solution to run the individual tests of all top-level projects in the repository. I've set up a cruise control server in our office that monitors the SVN and automatically picks up any top-level project that defines a buildout.cfg in its trunk. You can watch it work here: http://uter.gocept.com:/ It reacts to changes in SVN automatically. New projects will be picked up every 3 hours. This thing is experimental. Christian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/ct%40gocept.com -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
