--On Wednesday, June 06, 2001 11:50:43 AM -0700 jimbo
[EMAIL PROTECTED] wrote:
I hope this helps. I wanted to add my feelings on the whole documentation
issue. It seems to me that the whole process caters around developers
too much.
I have to disagree with you **in the context of this
On Wed, 6 Jun 2001, jimbo wrote:
I believe that if you are a true developer you will/can figure out the api given
the vast information available today.
For example the dcworkflow product was just released. I believe the best
documentation would be how-to actually use the product.
Ah,
Hmm, I'm surprised that 2 days has passed with no comment from zope-dev
and no comments in the Wiki. I hear constant complaints about lack of a
polished API. I expected this post to generate lots of interest.
What say ye, zope-dev? Is this something we should be doing, or would
you prefer a
On Mon, 4 Jun 2001, Amos Latteier wrote:
I encourage you to check it out and leave your comments, criticisms, and
suggestions.
I like. That pretty much captures it :)
There is one thing, though. Let's say I have this class NiceBigCar. The
developers docs from what you suggest are fine,
--On Wednesday, June 06, 2001 11:57:06 AM -0400 Paul Everitt
[EMAIL PROTECTED] wrote:
Hmm, I'm surprised that 2 days has passed with no comment from zope-dev
and no comments in the Wiki. I hear constant complaints about lack of a
polished API. I expected this post to generate lots of
Jimbo, I concur 100%.
I am a Zope newbie (relatively speaking - since February) but I have been
developing Web Information Systems since '95. My tool of choice was
perl/CGI. I attended a DEVX conference in December of '99 and was
introduced to Java Servlets and the J2EE spec. I knew this was
