Skip to content.

plope

Personal tools
You are here: Home » Members » chrism's Home » A Theory On Collaborative Develpment Using Zope » Zope 3 persistent modules and "ZVS"
 
 

Comment

Above in this comment thread: A Theory On Collaborative Develpment Using Zope » good point.

Zope 3 persistent modules and "ZVS"

Posted by zopepaul at 2004-01-02 02:36 AM
I think there are still benefits to TTW Dev and storing code in the ZODB. As you've mentioned, though, in group development on larger projects, these benefits go with an important list of drawbacks.

If you lined up the benefits and the drawbacks, I think the direction Jim is going with "Zope 3 TTW":http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ThroughTheWebDevelopmentInZope3 (hmm, wonder what STX will do with that link...) addresses a number of the weaknesses while keeping, or improving, some of the benefits. This combines with the "File System Sync":http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/FileSystemSynchronizationProposal proposal.

Though these proposals don't deal directly with bootstrapping a bunch of data, it's a logical extension to these proposals. How do you feel about being able to have your code live, during development, in both CVS/Subversion and the ZODB? Which of the drawbacks would remain?

that'd be great.

I think that'd be great. It's sort of like a super-skins-tool, and it's really nifty. For now, though, I'm gonna stick with trying to put all logic and configuration on the filesystem and only put data in the ZODB, if only because I can't stop and smell the roses for long enough to get cozy with Zope 3 (that stop would be about a year or so for me, as far as I can tell).