Re: [Zope-dev] RE: Barriers to Zope popularity: Part 2: source control

2001-09-25 Thread Chris Withers
Jay, Dylan wrote: Zope looks nice but I found it has two potential problems. 1. WYSIWYG editing ZPT, WebDAV, etc 2. Source control (by ClearCase) Well, I just used FS-based CMF skins and python Products maintained with CVS to control the 'code'. I don't believe 'data' should ever

Re: [Zope-dev] RE: Barriers to Zope popularity: Part 2: source control

2001-09-25 Thread Kevin Dangoor
- Original Message - From: Jay, Dylan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 24, 2001 11:01 PM Subject: [Zope-dev] RE: Barriers to Zope popularity: Part 2: source control -Original Message- From: Kenichi Sato Sent: Monday, 24 September 2001 5:49

Re: [Zope-dev] RE: Barriers to Zope popularity: Part 2: source control

2001-09-25 Thread Paul Everitt
I'd like to add some misinformation...errmm, comments. :^) On the version control side, you're quite right, we're still behind on it. There _are_ some ways to get there, if you try hard enough. But that's unacceptible. There are two things long term that need to be done: filesystem

Re: [Zope-dev] RE: Barriers to Zope popularity: Part 2: source control

2001-09-25 Thread Chris Withers
2. Source control (by ClearCase) Well, I just used FS-based CMF skins and python Products maintained with CVS to control the 'code'. I don't believe 'data' should ever be put under the kind of source control you're talking about here... The discussion was about over-the-web

[Zope-dev] RE: Barriers to Zope popularity: Part 2: source control

2001-09-24 Thread Jay, Dylan
-Original Message- From: Kenichi Sato Sent: Monday, 24 September 2001 5:49 PM To: djay Subject: Barriers to Zope popularity: Part 2: source control Dear Mr. Jay, Dylan, I am Ken Sato, a manager of software development projects. I'm now taking a look at Zope as a tool to