Hi, We all know that Zope needs better docs. To this end we've added a help system, API docs and a tutorial to Zope 2.2. Now the important work of replacing the aging guides is job number one. Michel Pelletier has been diligently working on a Zope book for O'Reilly for a number of months. I convinced him to take me on as a co-author and turn the book into official Zope documentation. O'Reilly is on board and is currently choosing between two different open content licenses. Find out the full scoop on the Zope Docs Wiki. http://www.zope.org/Wikis/Docs/ZopeBook We're excited about the book and think that it will fill an important hole the current official Zope docs. As soon as a content license is chosen we'll make our rough drafts available. -Amos -- Amos Latteier mailto:amos@digicool.com Digital Creations http://www.digicool.com
YAY! Can't wait to see the new docs! Thanks!! -E
In article <613145F79272D211914B0020AFF6401932070D@gandalf.digicool.com> , Amos Latteier <Amos@digicool.com> writes
Hi,
We all know that Zope needs better docs. To this end we've added a help system, API docs and a tutorial to Zope 2.2.
Now the important work of replacing the aging guides is job number one.
Michel Pelletier has been diligently working on a Zope book for O'Reilly for a number of months. I convinced him to take me on as a co-author and turn the book into official Zope documentation. O'Reilly is on board and is currently choosing between two different open content licenses. Find out the full scoop on the Zope Docs Wiki.
http://www.zope.org/Wikis/Docs/ZopeBook
We're excited about the book and think that it will fill an important hole the current official Zope docs.
As soon as a content license is chosen we'll make our rough drafts available.
-Amos
Why not invite authors of popular/important products to contribute their own chapters? Or, is this too radical <g> -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope
Hi, I've setup zope and zwiki to use for internal collaboration. I'm having fun and doing some useful stuff without knowing too much or appearing too stupid. I've decided to do something more adventuresome to learn some more. I'd like to tie in our SourceSafe version control system so I could do reports that list what has been checked in since a date or label. So I have to get input from the user from this and then use SourceSafe com interfaces to gather the data and put it in a nice format. Is this a good project for zope? It would be very useful for checking progress on projects when I'm off-site because using the SourceSafe UI over a modem has horrid performance problems. Along those lines would it be possible to use the Zope tree control to mimic the SourceSafe project tree stuff so the whole thing could be accessible using a modem? Also, is there a backup facility for the zodb? I have built a few pages using zwiki and I'd like to ensure that they would survive a hard disk crash or other nastiness. Thanks. Frank
Hi Frank, It sounds like your SourceSafe tie in could potentially be a fairly complex undertaking. Amos Latteier wrote an example COMObject product that will show you the mechanics of utilizing COM objects from Zope. This might help. And though I know you don't want to VC Zope objects, you might be interested in Steve Spicklemire's CVSMixin product that seems to utilize CVS for version control of several kinds of Zope objects. You may get tips from both of these products. Seach Zope.org for both. To back up the ZODB, just copy the Data.fs file in the var directory. You may safely do this while Zope is running. To restore, reinstall Zope and all the products you're using and copy the Data.fs into the var directory. HTH, Chris Frank McGeough wrote:
Hi,
I've setup zope and zwiki to use for internal collaboration. I'm having fun and doing some useful stuff without knowing too much or appearing too stupid. I've decided to do something more adventuresome to learn some more. I'd like to tie in our SourceSafe version control system so I could do reports that list what has been checked in since a date or label. So I have to get input from the user from this and then use SourceSafe com interfaces to gather the data and put it in a nice format. Is this a good project for zope? It would be very useful for checking progress on projects when I'm off-site because using the SourceSafe UI over a modem has horrid performance problems. Along those lines would it be possible to use the Zope tree control to mimic the SourceSafe project tree stuff so the whole thing could be accessible using a modem?
Also, is there a backup facility for the zodb? I have built a few pages using zwiki and I'd like to ensure that they would survive a hard disk crash or other nastiness. Thanks.
Frank
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
At 2000-07-06 22:23 -0400, Chris McDonough <chrism@digicool.com> wrote:
To back up the ZODB, just copy the Data.fs file in the var directory. You may safely do this while Zope is running. To restore, reinstall Zope and all the products you're using and copy the Data.fs into the var directory.
I don't understand this advice. Couldn't the file change while being read? Wouldn't a better way be to pack the database and use the Data.fs.old file as the backup? David Trudgett
On Fri, 7 Jul 2000, David Trudgett wrote:
I don't understand this advice. Couldn't the file change while being read? Wouldn't a better way be to pack the database and use the Data.fs.old file as the backup?
If you are a belt-and-suspenders type, sure <grin>. Data.fs only gets appended to, and Zope is smart enough to ignore incomplete transactions on the end of the file when it starts up. So the database is *always* in a consistent state on disk from Zope's point of view, making it safe to back it up by just copying the live Data.fs. --RDM
AFAIK, it would be a bad idea a) if writes were not appends and b) if records written to the FileStorage were not written atomically. But neither is the case, so it's safe to just copy it without shutting it down. The only time this may not be the case is if it were copied during a pack operation. David Trudgett wrote:
I don't understand this advice. Couldn't the file change while being read? Wouldn't a better way be to pack the database and use the Data.fs.old file as the backup?
David Trudgett
Graham Chiu wrote: [...]
We're excited about the book and think that it will fill an important hole the current official Zope docs.
As soon as a content license is chosen we'll make our rough drafts available.
-Amos
Why not invite authors of popular/important products to contribute their own chapters?
Or, is this too radical <g>
I think it is a great idea. Give each of them an 'appendix' describing how they implemented their product, and why they chose that method. -- "Linux: the operating system with a CLUE... Command Line User Environment". seen in a posting on comp.software.testing
[Amos Latteier, on Thu, 06 Jul 2000] :: Michel Pelletier has been diligently working on a Zope book for O'Reilly :: for a number of months. I convinced him to take me on as a co-author and :: turn the book into official Zope documentation. O'Reilly is on board and :: is currently choosing between two different open content licenses YES!!! This is the best news I've ever heard. :)
participants (9)
-
Amos Latteier -
Bill Anderson -
Chris McDonough -
David Trudgett -
Eric L. Walstad -
Frank McGeough -
Graham Chiu -
Patrick Phalen -
R. David Murray