Thanks, Andreas.
Actually we are looking for very generic answers, even hints, at this
stage.... looking for a starting point, so to say. Something that would help
us commence our study.
Our applications have mostly been small web based application prototypes
which were meant to showcase Zope and our work in specific end-user domains
and addressed small end-user problems. The aesthetics of the applications
were, by and large, secondary. They were not websites and we had commenced
them in 2.x because Zope 3 was not ready at that time. They were commenced
in the period 2001-2004 and maintained through 2006-8. Had we written them
*today*, from scratch, we would have used Grok, probably.

The development and deployment environments were MS Windows versions of the
time. Now we plan to use Linux almost exclusively.

Most of them used DTML rather than ZPTs.
Most used script(python) extensively.
Some used ZODB exclusively, while a few others used RDBMSs alongside.
None of them used ZEO
They used third party Zope products very rarely
One application used SVG extensively.

Two applications were 3 person-years of effort, two others a one person-year
of effort, and others were smaller.

We are planning to rebuild the smaller ones from scratch, using Grok.

The four larger ones we would like to migrate to Zope 2.11 using Python 2.6
(or to Blue Bream, maybe)

We have one application in Zope 3.1 which we would probably extend further
in Zope 3.4 or Blue Bream.

What we have of them are .zexp and .fs files and some installation

The least we want to do is to reinstall the old work in a manner that we
(especially the new programmers with us) would get to see it and take a
decision on each application separately. If there is a way we can install
the applications using the current Zope versions, we would love it.

Thanks and regards
Milind Khadilkar,

On Tue, Feb 22, 2011 at 4:05 PM, Andreas Jung <> wrote:

> Hash: SHA1
> Those are broad questions that can not be answered seriously if you
> don't tell us about the kind of application you have built in the past
> with Zope and what kind of applications you intend to buildout with
> Zope-ish technlogy in the future.
> - -aj
> Milind Khadilkar wrote:
> > Hello everybody,
> >
> > We have used Zope a few years ago... had to stop rather abruptly... and
> > now are attempting to get back into using Zope.
> >
> > Most of the work we have done is in Zope 2.7.x, while some work dates
> > from much earlier versions.
> >
> > Is it right that we would need to install the *exactly* original Zope
> > versions ( or is it *major* original Zope version?) to get our old work
> > up and running?
> >
> > If we want to reuse that work in Zope 2.13 and continue from there, is
> > there a transition path without installing old versions?
> >
> > We also have some work in Zope 3.1. Should we go in for BlueBream now?
> >
> > What should be the Zope2 learning path for new entrants (fresh out of
> > college, with fair Python knowledge)?
> >
> > Advise would be highly appreciated.
> >
> > With Thanks.
> >
> > Milind Khadilkar
> > ZedObject
> >
> > _______________________________________________
> > Zope3-users mailing list
> >
> >
> - --
> ZOPYX Limited           | zopyx group
> Charlottenstr. 37/1     | The full-service network for Zope & Plone
> D-72070 Tübingen        | Produce & Publish
>           |
> - ------------------------------------------------------------------------
> E-Publishing, Python, Zope & Plone development, Consulting
> Version: GnuPG v1.4.11 (Darwin)
> Comment: Using GnuPG with Mozilla -
> W2ETn5Gw9aHODn4LaQ/Gf2lL/RB8lAC/+Wrv56vImy92goXHK8TBjr96RfK+WEMO
> RZJteC3HzoU/eU/rfXlWVWn/iDhn3vvPe9yd/dcZDepx/E6XrucLEP4BiDx9f5UK
> N1UiF06W66pfG4SIwCs5slglwTzr612DHfjvLPyDF+tV/L/2+yCcZYXSNByE+0Jd
> 2F+QbShj+B74DQICZ6ksuHWvU4PA2WFl4FY8tRnYdbSWJqsV9Cncsjl1l0Fp94c4
> VQtOeru91VWy7mH/acZp97k5i8UyfQLRGSOdiavZkxtJ9SOONn3hEqmCbhdfhx/7
> fS8EkUCX7e27rkWV3XCcvDBx/iaSBA5rbpVzmVyeR6CvdxgNq/8OW0Y40Bqk1Xku
> xRZHsOmF08IfVEo6oQfNcl9cwp9ROuNHzbfpeND8gnKoq/Of1F7tsDIvBjFv0VSf
> +b9s5NVVZPDcInuKPUWgB7JJnUWov94=
> =qtAv
Zope3-users mailing list

Reply via email to