I'm always sorry to see a good open source project with little or no documentation and a myriad of them are in this sad state. Luckily, web2py doesn't have this problem.
The existence of the documentation is this fairly complete form is one of the reasons I chose web2py over other python frameworks. I don't think having 40 pages more or less would make me consider web2py faster or slower. But a lack of a chapter in the book might have made me choose another framework. I agree that new users need simple examples, but not at the expense of an in depth manual. If there is a consensus that web2py book can be intimidating for a complete begginer, perhaps someone can write a short "My first web2py project" in a book form, or something similar? I personally think this can be better served with blog articles and publishing of slices. Perhaps the growh of web2py userbase has slowed a bit..? I'm not sure that it did though. I don't have any insight into statistics to think one way or another and I don't trust my perception with this. What did slow down is the pace of web2py releases, hasn't it? The period between releases is longer than it used to be. On Saturday, September 7, 2013 9:54:45 AM UTC+2, webpypy wrote: > > > As Massimo said, " the main advantage/objective of web2py framework is to > be the easiest and fastest to develop web applications". > > I think the rate of growing popularity/interest was high for versions < > 2.0 , compared with versions >= 2.0 . > Maybe because of the big size of manual for versions >2.0 , The big manual > means it is not expected to be the easiest and fastest anymore. > > I suggest explaining the features through well documented > examples/appliances, keeping the manual small... > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
