I am not sure what you mean by including my code in the dev package, but I would like to keep DBSprockets out on it's own. I think there are resources available for other frameworks, and I would like to make sure sprockets does not get too coupled with TG. I think what you meant is including dbsprockets in the setup.py, which I am of course ALL FOR. If you want to package it on a release CD, no problem, DBSprockets is MIT, so use it however you want. If you want me to update some docs about how to use the forms in TG2 I can do that too. I just finished my round of docs on DBSprockets, and I have a few more tickets to commit before DBSprockets starts to move onto v0.3. v0.2 is really useful for TG2 the goal of v0.3 is going to be to spread out to other frameworks with dbmechanic and make things "look nicer".
Thanks for the update. -chris On Jan 17, 8:34 pm, "Mark Ramm" <[EMAIL PROTECTED]> wrote: > I'm minus one laptop for the rest of the week, due to some hardware > troubles, so I'll be online less, and less able to make progress on > TG2. And fortunately for everybody, lots of other people are pushing > TG2 forward in my absense. > > Fred has been making good progress on the Toolbox replacement, and a > few sample tools. Chris is looking at making a DBMechanic based > replacement for catwalk in the new toolbox. > > I think we should take the toolbox code itself and put it into a > tg-dev package, which we can update much more frequently than the main > TG2 package (which should have a stable interface for as long as > possible). > > Chris has made some very easy to use automatic form generation > features in DBSprockets, and they are extremely well tested, powerful, > and make creating simple forms really easy, and make TG2 demo really > well, so I'd like to suggest that we include DBSprockets in the main > TG2 package, but it's possible that we ought to move this into the dev > package. What do you all think? > > It looks like Kevin Horn has made some good progress on getting some > code written that will allow us to test the quickstart template in our > regular TG2 testing. This an important step forward as the template > represents most of the "untested" code (and it is code!) in the tg > package. > > We're still on the very bleeding edge of Pylons and WebOb development, > so there are a few python 2.4 issues to iron out, but life is fun out > here on the edge ;) > > -- > Mark Ramm-Christensen > email: mark at compoundthinking dot com > blog:www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
