RE: [Zope] - Why I don't think Zope will work for me
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
What about having an export/import to/from file system? That way, you *could* use the file system for editing, version control etc., except that you would import into zopes DB before publishing it to the web... -- Magnus Lie Hetland www.pvv.org/arcadia <arcadia@pvv.org>
Magnus Lie Hetland wrote:
What about having an export/import to/from file system?
I think that there is a good possibility for this to happen. I definately plan to support import and export in XML. My original idea was to export to a single XML file. I could see extending this in some fashion to export to individial files. Documents would export to files, folders to directories, etc. It will be a little tricky to handle things like folder attributes and objects that aren't completely folderish.
That way, you *could* use the file system for editing, version control etc., except that you would import into zopes DB before publishing it to the web...
Yes. Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (888) 344-4332 Python Powered! Digital Creations http://www.digicool.com http://www.python.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
On Wed, 30 Dec 1998, Magnus Lie Hetland wrote:
What about having an export/import to/from file system? That way, you *could* use the file system for editing, version control etc., except that you would import into zopes DB before publishing it to the web...
Doesn't work to well. You also need a standard mapping to represent the class of objects, the properties, etc. (You would want to be able to change the type of some object in your repository, right?) Andreas -- Win95: n., A huge annoying boot virus that causes random spontaneous system crashes, usually just before saving a massive project. Easily cured by UNIX. See also MS-DOS, IBM-DOS, DR-DOS, Win 3.x, Win98.
participants (4)
-
Andreas Kostyrka -
Dave Goodrich -
Jim Fulton -
Magnus Lie Hetland