Of course Pylons knowledge doesn't harm. However, it is a little bit the other way around.
I have now two webapps running TG2 and didn't use any Pylons before: TG2 is good jump into Pylons. It has a good quickstart template and chooses reasonable defaults. Setting some components as defaults also means, that the documentation can be more concrete: showing how to use problems with Genshi, SA, repoze.what in this combination. Of course, once you are more experienced, it is usually no problem to abstract from that description. So, I recommend you, just to start your next project with TG2 :-). Michael On 11 Dez., 06:44, Chris Miles <[EMAIL PROTECTED]> wrote: > On 11/12/2008, at 4:36 PM, Mark Ramm wrote: > > >> I assume Beaker is also the recommended caching solution for > >> TG2, but would like clarification. > > > Yes, beaker is the built in caching mechanism of TG2. Beaker supports > > memcached, and lots of other back-ends. It also doesn't suffer from > > the so-called dog-pile effect i the same way as some other > > web-framework's built in caching mechanisms do, because it's just > > plain awesome. > > That's good. I've decided to learn standard Pylons before looking at > TG2 in detail. I assume a lot of Pylons knowledge will make working > with TG2 much easier. > > For those that haven't already found it, James Gardner's Pylons book > is available to read free online and has been invaluable for my Pylons > learning. http://pylonsbook.com/ > > Cheers, > Chris Miles --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
