Zope Book, was Re: [Zope-dev] The bleak Future of Zope?

Peter Sabaini peter at sabaini.at
Wed Apr 21 19:20:10 EDT 2004


Paul Winkler wrote:
> On Wed, Apr 21, 2004 at 08:10:26PM +0200, Peter Sabaini wrote:
> 
>>* Reference: IMHO one of the trickier things, especially for the API 
>>Ref. because one would first have to decide what constitutes the API and 
>>what is simply Zope core...
> 
> 
> The long-term solution, I think, is to fix the API mess itself. Eek.
> I have a proposal about this here:
> http://dev.zope.org/Wikis/DevSite/Proposals/SanitizeHelpSysAndAPIReference
> ... but I think this will take a while, and I'd rather get
> the book updated first.
> 
> I think it's worth hand-massaging the API reference chapter for
> the 2.7 book and fixing the embedded docs later.
> Yes, I volunteer to do this :-)

Brave... and while I'd really like to have a clean API Reference, you 
are probably right that its more important to get the main book updated 
first.

>>* A chapter TOC: it would be great if we could have an inter-chapter 
>>table of contents; would greatly help navigation esp. in longer chapters 
>>-- I seem to recall that someone once mentioned working on such a 
>>feature -- Paul maybe?
> 
> 
> The book already has an inter-chapter TOC at the beginning ;-)
> Chris and I worked on an intra-chapter TOC at Pycon. 
> My stuff is in backtalk CVS on sourceforge.
> http://cvs.sourceforge.net/viewcvs.py/backtalk/BackTalk/
> Just needs a bit of cleanup and it'll be ready to go.

Yay! And, judging by the CVS, done pretty straightforward (I was afraid 
of having to do several parsing passes and such). Cool.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3216 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20040422/1736b004/smime-0001.bin


More information about the Zope-Dev mailing list