One thing that would probably be helpful is just to get some of the links
that are presented here into the official website.  Maybe I wasn't looking
at the right spot, but while I had found web2pysplices, and the appliances
section on the main website, until this thread I've never seen
http://web2py.com/plugins/ (Is it listed from the main page at all?  I
checked main page, Download, Documentation, Staff, Support at the top and a
^F for plugin found no hits.)

On Sat, May 29, 2010 at 1:14 AM, Robert O'Connor <robby.ocon...@gmail.com>wrote:

> Some of the cookbooks are handy.
>
> What if somebody provided a way to do "wizard" style user interfaces.
> (I requested information on a separate thread -- which is currently
> awaiting moderation)
>
> There is both a lack of official documentation and even resources of
> those who've used it! I've done google searches and turned up nil in a
> lot of cases! I'll try to contribute a bit when I figure out how to do
> what i want. Blogs are the number one untapped resource for learning
> new things.
>
> --rob
>
> On May 12, 11:11 am, Thadeus Burgess <thade...@thadeusb.com> wrote:
> > We need tutorials, a beginners, intermediate, and expert level on
> > web2py apps, each going into different details of web2py step by step
> > line by line.
> >
> > --
> > Thadeus
> >
> > On Wed, May 12, 2010 at 4:17 AM, cjrh <caleb.hatti...@gmail.com> wrote:
> > > On May 12, 6:11 am, Richard <richar...@gmail.com> wrote:
> > >> The book was a huge improvement but there is certainly more to be
> > >> done. Unfortunately this kind of work is not fun so happens slowly.
> >
> > > I am happy to volunteer help for documentation.  I enjoy improving
> > > documentation.
> >
> > >> Would it be worth migrating useful content to the book (and slices)
> > >> and close the legacy apps (AlterEgo, wiki)?
> >
> > > Yes, I think so.   Try to focus on the official documentation as much
> > > as possible.  My 2nd edition copy of the book here looks about 325
> > > pages, which is already quite long.  From a publisher point-of-view,
> > > it may make more economic sense to split the official documentation
> > > into two books, e.g. a "reference" manual and a "user" manual, the
> > > former concerned with formal specifications of the classes and
> > > structure of the framework, and the latter focused on how the
> > > framework must be used to create applications?  It should be easy to
> > > do this via Lulu.
>

Reply via email to