1) Yes, I definitely feel that the documentation can be improved and is abit overwhelming for a new TG user. I know this is work-in-progress.
2) Again the skeleton is also overwhelming , but TG has alot to offer and I feel this a good start for someone to explore a big portion of the TG stack. On Thursday, February 14, 2013 10:00:41 PM UTC+2, Mengu wrote: > > Hi everyone, > > Recently a colleague of mine wanted to use Python for a new project he > was starting. I showed him his options beginning with TurboGears of > course however he choose Django. I asked him why and he told me two > things. > > 1) TurboGears documentation is too much distributed and poorly > written. Especially the tutorial was not compact. > > 2) TurboGears generates too much for a skeleton application. Why I > cannot have a simple and clean application and then simply configure > what I want later on? > > So, let's discuss these two points. From a perspective of a non-TG > developer and even non-Python developer. > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
