My suggestion would be to develop it as a Python Product in Zope 2.8.9
and use automatic product refreshing so you can change code and test it
immediately without having to restart Zope. Zope 2.8 is slowly becoming
old but still the fastest development environment I believe.
I'm also keeping
I have to thank you all for your valuable suggestions.
to aj:
If you have the freedom to choose your Zope version:
- start with Zope 2.10 + CMF 2.1
- put your templates etc. into the filesystem using portal_skins
- use Zope 3 technology together with CMF: Zope 3 schema + formlib
--On 25. März 2007 10:26:42 + Roberto Scelzo [EMAIL PROTECTED]
wrote:
Someone suggested us to use a FS dump product, another one instead
pointed us to zope FS products, but, is there any
article/howto on how to make group development/debugging of middle/large
sized zope apps a nice
On 3/25/07, Roberto Scelzo [EMAIL PROTECTED] wrote:
Hi all,
we are developing a couple of zope apps which now
are becoming pretty complex and, unfortunately,
up to now we're developing TTW since we
haven't yet find
a smart fast way to do our job avoiding the ZMI.
We've searched a lot around
One 'kickstart' way to get started with something that will build out
a Zope environment in a repeatable way on UNIX (Linux/BSD/Mac/
probably Solaris) is available at http://www.plope.com/static/misc/
buildit_example-20070314-1.tgz. It requires buildit at http://
Hello,
Marco's recommendations are very good, I would just add the following:
- each developer works on his own instance, and commits his work in SVN or
CVS, then everything must be regularly delivered in an integration instance
where the latest current versions of all the developers can be
