I still think a cookbook/template/sample approach like the ajax_table in MochiKit is better unless you want to gear every TurboGears user to a particular model(RoR or to a less extend Nevow), which I assume was not the initial intend.
Kevin Dangoor wrote: > On 10/12/05, Ian Bicking <[EMAIL PROTECTED]> wrote: > > But when it comes down to it, there's a lot of grunt work and > > experimental programming that has to go on, to see how this stuff works > > in realistic situations. I think false starts should be expected, and > > that's fine as long as there's no premature commitment (which makes it a > > little questionable for TG 0.9, IMHO -- unless you have a plan for how > > deprecated features will work). > > I should note that the idea with including some amount of CRUD in 0.9 > is to put something out there and see if people think it's on the > right track for their needs. If it will take too long to do that > reasonably, or if people hate the feature as it appears in 0.9, it > will be tossed for 1.0. If, on the other hand, it makes it into 0.9 > and people like the general direction, then it will likely get refined > a bit and then 1.0 comes out. > > I do have thoughts in mind regarding deprecating features (post 1.0), > and you can be sure that major changes will be discussed on the list. > > Kevin > > -- > Kevin Dangoor > Author of the Zesty News RSS newsreader > > email: [EMAIL PROTECTED] > company: http://www.BlazingThings.com > blog: http://www.BlueSkyOnMars.com
