I've been reluctant to do direct API documentation because things are still somewhat in flux. At least with the book I can be somewhat general in the examples and cover the most important parts as opposed to explicit detail for every last field, method, etc. I'm not saying that the API doesn't need more work on docs, just that it's hard for me to prioritize that right now.
Derek PS - Have you looked at our book? It's far from complete but I think it already has enough content to make a good starting point... On Wed, Nov 26, 2008 at 2:47 PM, David Stein <[EMAIL PROTECTED]> wrote: > > On Wed, Nov 26, 2008 at 11:22 AM, David Pollak > <[EMAIL PROTECTED]> wrote: > > David, > > > > We are actively working on documentation. Please see a number of recent > > posts on the subject. > > > > David > > Yes, I've been following those posts. Having a couple of books out > will be great. Books take time to write though, certainly much more > time than it takes to update the Scaladocs. What do you guys, the > committers, think about putting your book efforts on hold until the > API is documented? At the very least, I'd encourage you guys to not > submit code from now on which isn't documented. It's just too much > work to go back later and add it, as we all know from our own > experiences no doubt. > > DS > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
