Hans, I have already offered to do the screen captures as my bit to the doc effort. As soon as the marching orders are released I'll work it.
I might suggest one addendum sometime in the future. The book itself covers what I call the application developers view. That's appropriate considering the target is envisioned as a teaching tool. But a simple 1-2 pages that would suggest a breadcrumb of the gluon code to review for deeper insights might be a worthy addition someday. (Somebody will probably point me to an AlterEgo article that does this.....) JohnMc On Jul 17, 10:32 am, "Hans Donner" <[email protected]> wrote: > i m seeing many posts about the doc needing improvement, and some discusions > about it should be done in the wiki that is not there yet. > However, i see little that people offer documentation or patches that work on > the documentation. > > please, can we see more of the latter and less of the first? also, do no > point only to massimo that he should provide it. > document what is not clear to you, and after help from this list, complete > it and submit it so it can be added to the documentation or examples. > > hans > > ------- Original Message ------- > From: viniciusban <[email protected]> > To: web2py Web Framework <[email protected]> > Sent: 17/07/2009, 15:57:14 > Subject: [web2py:26736] Re: The 80/20 rule > > On Jul 16, 11:49 pm, mdipierro <[email protected]> wrote: > > > We can add more and more features to web2py with the effect that: > > - web2py grows in complexity to the point that it becomes harder to > > maintain > > - web2py gets slower > > I think these 2 are not good choices because a good framework must be > fast and simple. You achieved that already. > > I'd choose to improve free documentation. I really find myself > confused with web2py's documentation. > I think the free available resources must be improved and we won't see > many developers until it gets stronger. > > > Finally, this community has to do a better job at outreach. You should > > talk to your friends and blog about web2py. You must talk about the > > applications you build with it. We do not lack developers. We lack > > salesmen. > > I just started it the day before yesterday, in Brazilian > Portuguese:http://aprenda-web2py.blogspot.com > In 2 days it has about 300 views with virtually no sharing. > > We have a strong Django community, but we don't have statistics about > how many are really *working* with it. > > I talked to Alvaro Justen about it and we'll write some posts from the > web2py user's point of view. > > It won't be a manual, absolutelly! It'll be a blog with practical > web2py development emphasis. Maybe a lot of howtos and many principles > explained. > > I started this blog with 2 posts "selling" some nice features about > web2py. > The first one, I got from web2py's homepage. > > The other one talks about the "backwards compatibility" thread I > started this week, but translated. > As I said before, I think this is some of the most important web2py's > characteristics. > > I can see many advantages in web2py and I will write about them in a > series of posts, emphasizing the time-to-market web2py allows us to > have. > > -- > Vinicius Assef. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
