You are not logged in Log in Join
You are here: Home » Members » arielpartners » CVS File » swpackage_view
Log in
Name

Password

 
Link icon Forgot your password?
 
Print

CVS File

This is a new release of our CVSFile product. CVSFile enables Zope content to be served out of files residing in CVS sandboxes, and provides access to common CVS functions through the web in the Zope Management Interface.
This new release new features like
  • recursive batch add capability -- add instances whole filesystems at a time. This function can be run multiple times without error-- duplicates are logged and ignored. For example, you could perform the same batch add each week to pick up any new files.
  • tunable batch parameters for example, you can avoid adding CVS control files or system files via a series of easy to use filters
  • page templates all ZMI GUI screens use pages templates instead of DTML.
Why not simply use ZCVSFolder? Because CVSFile stores files in CVS as normal files, rather than as Python "pickles." This makes it easy to use the same content, held in CVS, in both Zope and non-Zope contexts.
CVSFile extends ExternalFile, and therefore inherits all of its functionality. This new release requires ExternalFile version 1.2.0.
This product is compatible with the popular ExternalEditor product.
Release 0.9 is compatible with Python 2.1.3, Zope 2.6.1, and ExternalFile 1.2.0.

Latest Release: 0.9.0
Last Updated: 2003-05-05 04:33:10
Author: ZopeOrgSite
Categories: Content Object, Developer, Examples, External Access
Maturity: Stable

Available Releases

Version Maturity Platform Released
0.9.0 Stable   2003-05-05 04:33:10
  CVSFile-0-9-0.zip (98 K) All
0.8.2 Stable   2002-11-04 12:01:24
  CVSFile-0-8-2.tgz (41 K) All
0.8.1 Stable   2002-08-27 21:00:59
  CVSFile-0-8-1.tgz (41 K) All
0.8 Stable   2002-05-29 02:03:01
  CVSFile-0-8.tgz (55 K) All
0.7 Stable   2002-05-29 01:10:48
  CVSFile-0-7.tgz (46 K) All
Copyright (c) 2011 Zope Foundation. All rights reserved. Legal | Contact
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)