> Pyramid seems to have purposefully left the 'client/browser' area untouched, > concentrating on the server but to me a framwork these days has to address > the client/browser side of the equation as well. It is where the bar is being > raised to with respect to web frameworks. RIA development, while being a > twisted path, seems to be converging towards the benefits that the web has > brought (ease of deployment) with the benefits of client/server (RAD). > > I'm curious to know what others think, if tg plans to address this piece in > the pyramid puzzle.
The pyramid puzzle is I think destined to (and was designed to) include two layers under the same Pylons Project banner. There's the low level, fast, flexible, powerful framework that makes very few assumptions, and maximizes flexibility. But then there's another related project that configures all of that in a standard way, includes a lot more "batteries" and works to provide lots of opt in options to the users of Pyramid layer, and lots of defaults to this higher layer. If we go through with a merger I expect that the TurboGears development community is going to be much more interested and much more active on this second layer. Which is natural because it's a reasonable outgrowth of the TurboGears philosophy. --Mark Ramm -- 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.
