[Zope3-Users] Plone conference 2007
Hi guys, The conference registration closes in just over one month, on October 5th! If you want to come to the conference, now is the time to register http://ploneconference2007.bookdirect.it/ This year we will have a huge conference with a lot of very interesting talks and panels. Here is the complete list of Plone Conference 2007 sessions: http://plone.org/events/conferences/2007-naples/speakers-1/speakers, Moreover we will have important talks from the Plone co-founders Alexander Limi and Alan Runyan who will present their by now traditional State of Plone keynote address in which they summarize the recent past, active present and exciting future of Plone and Thomas Moroz from OSI (http://www.soros.org) who will present Open Source and the Open Society: Using PLONE to build community online, Abstract --- NGOs and non-profits have become important actors in both the development of public policy and in deployment of technology for positive social change. The Open Society Institute (OSI), a private operating and grantmaking foundation, aims to shape public policy to promote democratic governance, human rights, and economic, legal, and social reform. On a local level, OSI implements a range of initiatives to support the rule of law, education, public health, and independent media in over 60 countries. At the same time, OSI works to build alliances across borders and continents on issues such as combating corruption and human rights abuses. Recently, OSI engaged Plone and open source systems for a comprehensive knowledge management system to bolster its operations and support its objectives.. In this keynote, Tom Moroz ties together some of the ideas of Karl Popper that underpin the Open Society Institute and the rationale behind the implementation of their Knowledge and Resource Locator (KARL). He will then explain the rationale that made Plone an appropriate choice showing the links between the mission of the open society institute and the open source software movement. Cheers Vincenzo -- Vincenzo Barone - Web Architect - Project Manager [EMAIL PROTECTED] Abstract Open Solutions [ http://www.abstract.it ] Mobile +39 328 3358110 Tel. 02320624747 Tel./Fax +39 081 0608213 PGP Public Key: http://www.abstract.it/gpg/vincenzo.barone begin:vcard fn:Vincenzo Barone n:Barone;Vincenzo org:Abstract snc adr;dom:Via Maroncelli, 12 - 20154 Milano ;;Via Coroglio, 57 d - 80124 Napoli email;internet:[EMAIL PROTECTED] tel;work:081 0608213 tel;fax:081 0608213 tel;cell:3283358110 x-mozilla-html:FALSE url:http://www.abstract.it version:2.1 end:vcard ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] I need an advice
Hi there, I'm new in zope3 (1 week) but I have been working with Zope2 and Plone for 1 year. Now I have to design and develop a Web App for a small / medium company. The app have to manage the finance of the company, clients, services, stock, providers, prices, sales... the question is: what do you think: should I use Zope3 or Plone3 ? thanks in advance -- Santiago Videla www.revolucionesweb.com.ar Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que [EMAIL PROTECTED] [EMAIL PROTECTED] somos. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] I need an advice
On 9/12/07, Santiago Videla [EMAIL PROTECTED] wrote: the question is: what do you think: should I use Zope3 or Plone3 ? Santiago, take a look at Grok: http://grok.zope.org Grok is Zope 3 with an API which makes the simple tasks simple. And as the complexity of the task increases, the entire Zope 3 API is at hand, without limitations. Cheers, Luciano ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] z3c.formdemo fails upon ./bin/buildout
Hi srs I think there was a mistake in the last version of z3c.form demo. (trunk) After running ./bin/buildout, it fails due to a develop = . z3c.form in buildout.cfg. I think z3c.form was supposed to be pulled from svn with a svn:externals set to z3c.form in the z3c.formdemo directory. Checking out z3c.form inside z3c.formdemo seems to solve the problem. Regards, Fernando ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Moving from z3 tarball to z3 buildout/eggs
I developed my Vice outbound syndication library on z3.3 (originally) using the full tarball of z3.3. I now want to move to a buildout-based, eggified method of developing and testing Vice. I use functional tests (using zope.testbrowser.testing.Browser) in Vice. These functional tests log into the zmi, create some folders and files, syndicate them, read the resulting feed, and verify that it is correct. The problem is that I don't know how much of zope.app these tests depend on. Very few eggs are actually required by imports in Vice. But the library is not much use (and there's not much to test) without a pretty thorough install, I suspect. Should I be attempting to grab all the zope eggs and making a replica of the full install? Or should I be trying to judiciously minimize the eggs that I use for testing? And what is the best way to go about whichever of these paths I should follow? I *really* like the buildout approach. It would just be even nicer if I knew of some way to have buildout replicate the entire Zope app server ecosystem for testing without having to specify the eggs one ... by ... one. Thanks, Derek ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Moving from z3 tarball to z3 buildout/eggs
Derek Richardson wrote: The problem is that I don't know how much of zope.app these tests depend on. Very few eggs are actually required by imports in Vice. But the library is not much use (and there's not much to test) without a pretty thorough install, I suspect. Should I be attempting to grab all the zope eggs and making a replica of the full install? No. Or should I be trying to judiciously minimize the eggs that I use for testing? Yes. And what is the best way to go about whichever of these paths I should follow? I suppose you can do this inductively (start ftesting.zcml from scratch) or deductively (start out with a full-fledged ftesting.zcml and remove things). If you want to do things inductively, there are a few hints I can give you: * If vice depends on the configuration of another package, but always assumed that this package's configuration was being loaded by Zope 3.3's site.zcml, make this dependency *explicit* now in vice's configure.zcml. For example, let's say that vice needs the intid utility and event subscriber registrations to be active, then it should do: include package=zope.app.intid / at the top of vice/configure.zcml. This will probably add more explicit depenencies to vice than you currently have (they should also go into setup.py). Note that you won't have to worry about ZCML being loaded several times. It won't be, zope.configuration makes sure of that. * ftesting.zcml should include package=vice / somewhere, therefore load all of its direct dependencies anyway. Then you should check which dependencies your tests have. You mention folders and other things. So you probably want to include zope.app.zcmlfiles/configure.zcml (which is the old 'zope.app/configure.zcml') because that pretty much loads the basic Zope 3 stuff. * Don't forget to load the meta stuff first. This usually boils down to: include package=zope.security file=meta.zcml / include package=zope.i18n file=meta.zcml / include package=zope.app.zcmlfiles file=meta.zcml / and the security policy's meta.zcml if you want to define roles: include package=zope.app.securitypolicy file=meta.zcml / * You'll need to define a security policy. Usually we take zope.app.securitypolicy for that: include package=zope.app.securitypolicy / securityPolicy component=zope.app.securitypolicy.zopepolicy.ZopeSecurityPolicy / Then you want to define the standard principals that are needed in ftests (anonmyous, the manager, etc.). Look at Zope 3.3's ftesting.zcml for those (incl. the grants). I *really* like the buildout approach. It would just be even nicer if I knew of some way to have buildout replicate the entire Zope app server ecosystem for testing without having to specify the eggs one ... by ... one. I think it's much better to sit down for a moment and *just* load the things you really need in tests. Usually this leads to much better tests. May I just remind of the horrid PloneTestCase which people have simply started using for every tests, which has cause Plone tests to be poorly isolated, quite slow and depend on much too many things at once. The path to a truly eggified system is to think about dependencies and write good tests that only load a minimum load of dependencies. This is not a trivial task. Testing never is. And I don't think there's a silver bullet, either. -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Moving from z3 tarball to z3 buildout/eggs
Philipp von Weitershausen wrote: * If vice depends on the configuration of another package, but always assumed that this package's configuration was being loaded by Zope 3.3's site.zcml, make this dependency *explicit* now in vice's configure.zcml. For example, let's say that vice needs the intid utility and event subscriber registrations to be active, then it should do: include package=zope.app.intid / at the top of vice/configure.zcml. This will probably add more explicit depenencies to vice than you currently have (they should also go into setup.py). Note that you won't have to worry about ZCML being loaded several times. It won't be, zope.configuration makes sure of that. OK, agreed, this is the *right* way. And thank you for the detailed instructions on how to achieve this - they are very clear and I plan to follow them closely. One problem confronts me, though, before I do the boring work of sorting out the dependencies. My package is designed to run in both z2 and z3. So, I could add a bunch of z3-specific dependencies to a z3-configure.zcml that is loaded only if Five is not installed. Not too hard. But, the hard part is: I don't want to add all the z3 eggs to my setup.py, because that's ugly if I'm actually running in z2. My idea is to have a z3-only package that depends on my z3/z2 hybrid package and that simply has a setup.py that includes all the z3 dependencies and a configure.zcml and an ftesting.zcml that does all the z3-specific zcml work. And then I can have a z3-specific buildout that uses the z3-specific package and another buildout for z2 that uses the base package and a third buildout for z2+plone, which includes some additional plone-specific packages. A big pain, but I want my code usuable in all three environments, to the extent that is possible. Opinions? Thanks, Derek ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Moving from z3 tarball to z3 buildout/eggs
Derek Richardson wrote: One problem confronts me, though, before I do the boring work of sorting out the dependencies. My package is designed to run in both z2 and z3. So, I could add a bunch of z3-specific dependencies to a z3-configure.zcml that is loaded only if Five is not installed. Not too hard. But, the hard part is: I don't want to add all the z3 eggs to my setup.py, Yes you do. because that's ugly if I'm actually running in z2. No, Zope 2 is ugly because it doesn't support eggs yet :). Well, actually I *did* change that. I've eggified Zope 2.11 (the trunk) a while ago and it seems to work so far. My idea is to have a z3-only package that depends on my z3/z2 hybrid package and that simply has a setup.py that includes all the z3 dependencies and a configure.zcml and an ftesting.zcml that does all the z3-specific zcml work. And then I can have a z3-specific buildout that uses the z3-specific package and another buildout for z2 that uses the base package and a third buildout for z2+plone, which includes some additional plone-specific packages. A big pain, but I want my code usuable in all three environments, to the extent that is possible. Opinions? If you're going to be basing this on Zope 2.11/3.4, I'd say you're better off with a simpler solution: betting on eggs all the way. I certainly hope that Zope 2.11 will go this way (I will do everything I can to support that) and I see similar wishes in the Plone community as well. Fortunately, eggification is just a means of packaging and pretty orthogonal to the actual code. -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Adapting or monkey patching?
Hello everyone. Since there's no default adapter for OFS.interfaces.IItem, I was wondering the best approach to patch/adapt OFS.SimpleItem.Item raise_standardErrorMessage method so it sends an event upon errors. Currently I have a adapter that subclasses OFS.SimpleItem.Item and re-implements the raise_standardErrorMessage method with my line of code that sends the event. I also have an event subscriber for that event BUT it does not work of course, because there's no adapter been called. Any clues or experiences to share? Regards, Fernando ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
