[Zope-Coders] Re: [CMF-checkins] CVS: CMF/CMFStaging CMF/CMFStaging - Imported sources
Florent Guillaume
fg@nuxeo.com
Wed, 15 May 2002 13:28:23 +0000 (UTC)
Yum yum, I've had a look at that and ZopeVersionControl, looks quite
interesting. And does in a much cleaner way what we do by hand for a
project here...
BTW is it envisionned that in the future CMFCore.PortalContent will
mixin ZopeVersionControl.VersionSupport ?
I have a question about ZopeVersionControl too: how would one go within
this framework to implement traversal to a given revision ? What I mean
by that is, that using a syntax like http://foo.com/bar;version=2.3 or a
cookie or an URL parameter one would get to that object's version. Is it
at all possible ?
Thanks,
Florent
Shane Hathaway <shane@cvs.zope.org> wrote:
> Update of /cvs-repository/CMF/CMFStaging
> In directory cvs.zope.org:/tmp/cvs-serv14536
>
> Log Message:
> Start of the CMFStaging product, using code from a customer project.
>
> Status:
>
> Vendor Tag: ZC
> Release Tags: initial
>
> I CMF/CMFStaging/LockTool.pyc
> I CMF/CMFStaging/StagingTool.pyc
> N CMF/CMFStaging/tool.gif
> I CMF/CMFStaging/VersionsTool.pyc
> I CMF/CMFStaging/__init__.pyc
> N CMF/CMFStaging/LockTool.py
> N CMF/CMFStaging/StagingTool.py
> N CMF/CMFStaging/VersionsTool.py
> N CMF/CMFStaging/__init__.py
> N CMF/CMFStaging/tests/testStaging.py
> N CMF/CMFStaging/tests/__init__.py
>
> No conflicts created by this import
--
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 87 http://nuxeo.com mailto:fg@nuxeo.com