I agree that the documentation needs to be pulled together. I don't program in web2py very often - I'm trying to run a business and we use web2py for our internal applications, but they don't get worked on every day or even every month. However, I do think web2py is an excellent framework. Cohesive documentation is missing, and to that end I have done the following:
- kept all the mailing list mails since I joined the group (nearly 7000 mails) - kept the draft books that Massimo put together - bookmarked Alto Ego - bookmarked the API documentation - bookmarked the CAS, T2 and Examples documentation - printed the cheat sheet - ordered the book (I'm in the UK, so I've no idea when it will arrive) Even now, when I'm reading the mailing list (I don't read every mail), I keep seeing reference to things I didn't know existed. I'm hoping that the book will pull a lot of this together, but right now when I'm using web2py I feel as if I'm almost out of my depth the whole time, and I am sure there are many web2py features that I don't use because I don't even know about them. To get to the point: please don't start another cookbook. Let's consolidate what already exists and then build on it. Keith --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
