Well I don't know if you are missing it or not. Because you can edit an item inside Netscape doesn't mean you must. Zope allows uploading of documents, I have been using BBedit or Jed to work in DTML, and uploading through netscape, You could also just paste changes into the edit window. I've been using DB storage for many years now (other than but similar to Zope)and I prefer it over a file system. For access control, session awareness, and undo abilities, a db works very nicely. It is also much easier to assign properties, behaviors and other object values to a db object, than a flat file item. An opinion :^) DAve.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Curtis Galloway Sent: Tuesday, December 29, 1998 2:47 PM To: zope@zope.org Subject: [Zope] - Why I don't think Zope will work for me
Zope is very cool. Zope has many useful features. But I believe that storing most of your useful data inside an opaque object database is a fatal flaw.
I learned through painful experience that having your project data in text files in a filesystem is a Good Thing. You can use standard UNIX tools to manipulate these files. You can use EMACS or vi or any other tool to edit them. And most importantly, you can use CVS or RCS or any other similar tool for source control.
I just don't see how you can build a large project with multiple developers using a Netscape browser as your editing tool, unless I'm missing something very obvious about the way Zope works.
--Curtis