iain duncan wrote: > >> Now I really dislike the way the term "user" has been used on this >> thread, first of all everyone here is a programmer or wants to be, >> second we all are here because we think python is better for webapps >> then any of the mayor deployed technologies, so we are not average >> user not average programmers. So thinks like expecting your users to >> <insert task here> are just totally out of place, I'll accept that >> kind of argument if we where programming something like wesnoth or >> even a tool like azureus. But saying that you can't contribute here >> because your "an user" it's just not acceptable at least to me. Now >> saying that you are a newbie that doesn't understand much of the >> internals that's fine but then help on something else. > > I'm sorry, but the above is totally ridiculous. To say that just because > someone is a good enough programmer to start *using* tg that they should > then also > > - have time to develop > - have time to doc > - be good enough to do the above > - feel obligated to do the aboe > > is a vast oversimplification. And is guaranteed to turn off potential > new users. If I didn't think your attitude towards that was in the > minority of the dev core, it would turn me right off from contributing > to TG. There is a very very big difference between the python chops to > use TG and to develop TG. And if you can't see that, than you certainly > won't be able to write docs appropriate for the *new* tg user. Unless > you think TG should be so elitist as not to cater to these new users? > > Writing docs is like *teaching*. I have previously taught music for a > living so I know what a frustrated student looks like. If you expect > them not to complain, than seriously, might as well not be in the doc > team. >
I'm afraid I entirely agree with Ian here. A user is a user period. His/Her job is to make applications with TG that eventually bring along more people to think TG is the right tool. The big problem of this thread I think is that we may be talking of different things at once (well I did anyway). TG needs: * a very good introductory course for beginners * a complete API documentation * a more in depth diving into the internal of the framework for developers Look at the PostgreSQL documentation [1]. This is what I'm talking about and even though their doc is not perfect it brings all those pieces together quite well. - Sylvain [1] http://www.postgresql.org/docs/8.2/interactive/index.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
