<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I just had to port an Intranet to
modern hardware/Linux that has been created in 1996 using plain
zope and has been "programmatically" untouched since 2001.<br>
The Intranet is rather complex and provides a kind of ERP on very
technical data.<br>
The application consist of some 1000 little dtml scripts and is
totaly unmaintainable.<br>
But it runs and runs and runs and is heavily used..<br>
<br>
Unhindered by the fact that the inner working of the Intranet is
unfathomable the transition to an up to date virtualized linux,
actual postgres and such went rather easily.<br>
<br>
Zope might be a zombie, but it is a great and sturdy one ..<br>
<br>
hats of to its creators..<br>
<br>
robert<br>
<br>
<br>
On 17.03.2015 02:37, Jesus Cea wrote:<br>
</div>
<blockquote cite="mid:55078569.5000707@jcea.es" type="cite">
<pre wrap="">On 07/03/15 16:30, Simon Michael wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I've sent you a download link.
I’m somewhat familiar with it, as I managed at least the zope2 wiki (and
wrote Zwiki)
</pre>
</blockquote>
<pre wrap="">
ZWIKI... God...
Is there any possibility of upgrading it to support current Zope2?. I
have currently two zope instances: a current zope and an aging Zope 2.10
just to host ZWIKI :(.
About current topic: I am not a web developer. I host my (heavy)
personal ZOPE webserver and a handful of WSGI handcoded services. But my
Zope webserver is working well and I am happy with it. Every now and
then I have to write new logic and I must decide to "invest" into Zope o
just bite the bullet and jump to Django, Piramid, whatever.
I am keeping Zope because I am using it since 1998 and I know it
inside-out. I can do whatever I want with it and the HUGE learning curve
is already amortized. I just consider other choices because I feel that
Zope 2 is a dead-end, not because I am unhappy with it. But Zope wins
every time so far :)
That said, documentation is really painful. It is very fragmented and it
is not easy to separate "outdated" from "current". Messy. Since current
codebase seems to change really slowly (mature!) I would love to see a
documentation effort. Not holding my breath :-(. Most of the time, when
implementing something new, I don't have any other choice than dive into
the Zope sourcecode. Doable but time-wasting.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Zope maillist - <a class="moz-txt-link-abbreviated" href="mailto:Zope@zope.org">Zope@zope.org</a>
<a class="moz-txt-link-freetext" href="https://mail.zope.org/mailman/listinfo/zope">https://mail.zope.org/mailman/listinfo/zope</a>
** No cross posts or HTML encoding! **
(Related lists -
<a class="moz-txt-link-freetext" href="https://mail.zope.org/mailman/listinfo/zope-announce">https://mail.zope.org/mailman/listinfo/zope-announce</a>
<a class="moz-txt-link-freetext" href="https://mail.zope.org/mailman/listinfo/zope-dev">https://mail.zope.org/mailman/listinfo/zope-dev</a> )
</pre>
</blockquote>
<br>
</body>
</html>