On 3/7/06, David Binger  wrote:
>
> On Mar 6, 2006, at 10:11 PM, larryt@winfirst.com wrote:
>
> > web frameworks are complicated.  They inherently require expertise in
> > the "solution domain" to glue even nicely fitting pieces together.
> > So, absent the user documentation mentioned previously in this thread,
> > lesser programmers migrate to bigger packages with more pieces fitted
> > straight out of the box.  Unfortunately, the bigger projects also
> > attract documenters; maybe they follow the heards of lesser
> > programmers.
>
> I agree that accessibility is a primary obstacle.  QP's purpose is
> partly to address this, though we still need to (and intend to)
> write a user guide.

It's actually harder with larger projects.  The beauty of Quixote is
you can print the entire source and read it in half an hour.  You can
then follow the execution sequence of the altdemo and get most of your
questions answered.  One thing that helped a lot is doc/demo.html,
which explains each part of the demo.

TG comes with a build-your-own demo (the wiki) but that's about the
only documentation it has, aside from a couple HOWTOs on the
command-line tool and test system.    Everything else requires
browsing through the CherryPy/Kid manuals or groping through the
source, keeping an eye for which CherryPy features have been
overridden in TG and which have not.  The new TG features (form
widgets, auth) have not been documented at all.  Of course they plan
to fix all this, but it's a large task.

--
Mike Orr 
(mso@oz.net address is semi-reliable)