I don't know much about Zope aside from the research I did a couple of years
ago when I went to PHP.

My understanding was that Zope was a server, serving dynamic pages.
Elements generates static pages (though I've used it to build PHP pages).

Zope has a database as part of the distribution.
Elements uses the file system and standard Python tools to connect to
databases and parse xml.

Zope is a bit like Frontier in that "parts" need to be placed in particular
places in some hierarchy.
Elements places minimal restrictions on everything!

Zope requires a significant amount of set up to derive value from the
process.
Elements facilitates production immediately.
The tutorial describes the set up steps for a first site:
http://www.nthwave.net/elements/tutorial.html

I have nothing against Zope. I hope I have not misrepresented it.

m


Ed Leafe wrote:

> Read on the web at http://community.scriptmeridian.org/16761
> ----------------------------------
>
> On Friday, April 19, 2002, at 04:36 PM, Michael Mell wrote:
>
> > I've learned a lot from Frontier in my years using it, but when I
> > switched, I intended to get Frontier completely out of my system. This
> > meant that I needed a templates & scripts site building tool to replace
> > Frontier for static sites.
> >
> > I first developed the system I call "Elements" in Oct 2000. I've been
> > using it to build my static sites exclusively since then. Elements uses
> > the file system to maintain its data. Scripts are written in Python.
> > Elements has all the tools, speed and stability of Python available to
> > it. Early this year I put a lot of effort into documenting Elements.
>
> I've been looking into Zope, as it seems to offer a lot of this.
> Have you checked out Zope? If so, how does Elements compare? What does
> each do better than the other?
>
> ___/
> /
> __/
> /
> ____/
> Ed Leafe
> http://leafe.com/
> http://foxcentral.net

--
mike[at]nthwave.net
llemekim YahooIM
415.455.8812 voice
419.735.1167 fax

Enclosures

None.  

Replies