Hi Rik, Just wanted to let you know you're _completely_ wrong :-). "Changing context in Zope" is exactly what I was looking for and I find myself referencing it frequently. I'll take your points seriously though: after fiddling with Zope for some weeks now I've found some errors in some documentation and I'll contact the authors off-list. I must say I'm quite satisfied with the Zope documentation. It's fragmented, yes, but there's a lot of it. I've got a big pile of printouts on my desk, bigger than anything available for PHP e.g., and it's just a subset of what can be gotten from the Zope site. I for one attribute my difficulties in implementing Zope more to the complexity and huge feature-set of the Zope engine, than to a lack of documentation. Good documentation helps, but it does not make Zope intrinsically easier. :*CU# Rik Hoekstra <hoekstra@fsw.leidenuniv.nl> writes:

Ok, that's it. Two points (ok I'm grumpy tonight)

1) I can't believe docs are really an issue with anyone. <whining mode> Let me take myself as an example (yes this is whining!). I have squeezed out three drafts of a chapter for ZBook called changing context in Zope. They were almost completely made up of examples. I got exactly one (1) response to the first draft from anyone either on the ZDP list or elsewhere (thanks Patrick).

Now, it may well be they are completely worthless or off target, but then please say so, so I can save myself the trouble.

Say anything. I asked for feedback repeatedly. It is not exactly motivating to write documentation if there is no feedback at all. That makes it appear as though there is no need for documentation - or did I get this wrong.

This also what Open Source is about as far as I'm concerned- _co_ operation</whining mode>

-- *** Guido A.J. Stevens *** mailto:gyst@nfg.nl *** *** Net Facilities Group *** tel:+31.43.3618933 *** *** http://www.nfg.nl *** fax:+31.43.3560502 ***