RE: [Zope] Wish for the next Zope Release: Doc tab for every Zope entity

2000-09-01 Thread Chris McDonough
gt; > >The other objects can have properties, which could be documentation. > > > >-Original Message----- > >From: Philipp Auersperg [mailto:[EMAIL PROTECTED]] > >Sent: Friday, September 01, 2000 6:23 AM > >To: [EMAIL PROTECTED] > >Subject: [Zope] Wish for the

RE: [Zope] Wish for the next Zope Release: Doc tab for every Zope entity

2000-09-01 Thread Philipp Auersperg
which could be documentation. > >-Original Message- >From: Philipp Auersperg [mailto:[EMAIL PROTECTED]] >Sent: Friday, September 01, 2000 6:23 AM >To: [EMAIL PROTECTED] >Subject: [Zope] Wish for the next Zope Release: Doc tab for every Zope >entity > > >Mostly

RE: [Zope] Wish for the next Zope Release: Doc tab for every Zope entity

2000-09-01 Thread Chris McDonough
ies, which could be documentation. -Original Message- From: Philipp Auersperg [mailto:[EMAIL PROTECTED]] Sent: Friday, September 01, 2000 6:23 AM To: [EMAIL PROTECTED] Subject: [Zope] Wish for the next Zope Release: Doc tab for every Zope entity Mostly when developing a project it

[Zope] Wish for the next Zope Release: Doc tab for every Zope entity

2000-09-01 Thread Philipp Auersperg
Mostly when developing a project it should be documented as well :) The best would be a strucutral documentation that can be generated out of the project so that it always keeps track of the software and is up to date   - Python has that because there are the doc strings for classes and metho