TurboGears2 status update

[Mark Ramm]

TurboGears 2 is now heavily refactored, and working again.

We've moved a bunch of stuff to do object dispatching and @expose()
style controller methods into Pylons proper, as well as refactored the
pylons wsgiapp to allow for a common base with tg2.

TurboGears 2 trunk requires a fresh checkout both turbogears trunk
(from subversion) and of Pylons (from mercurial).

Once you have both TG and Pylons checked out and regesterd with
"setup.py develop" you can create a new project with:

paster create -t turbogears2 projectname

object dispatch should work the way you expect it to. if you are used
to sticking stuff on cherrypy.request you can now use the "context"
object (pylons.c) which provides threadlocal, requestlocal storage.

I'll be building up a bunch more tests in TurboGears 2 this week, and
we'll be doing a TurboGears 2 sprint next Saturday at Stanford
University. (Remote participation is not only welcomed, it's
encouraged!).

--
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog

[Kevin Horn]

Way to go Mark, et. al.!

With TG2 now (hopefully) in a usable state, we can move on with a few things in Docudo.  Some issues:
1) Mgmt of the Docuo repos
2) Selecting an initial backend
3) The "Working Copy Problem"

I'll try to get an email out on each of these later today.

Also, I may need a couple of pointers on checking out pylons, since I've not done it before, nor have I used mercurial.  I'll ask if I need it.

Thanks, guys!

Kevin Horn

On Nov 4, 2007 9:42 PM, Mark Ramm <mark.mch...@gmail.com> wrote:

TurboGears 2 is now heavily refactored, and working again.

We've moved a bunch of stuff to do object dispatching and @expose()
style controller methods into Pylons proper, as well as refactored the
pylons wsgiapp to allow for a common base with tg2.

TurboGears 2 trunk requires a fresh checkout both turbogears trunk
(from subversion) and of Pylons (from mercurial).

Once you have both TG and Pylons checked out and regesterd with
"setup.py develop" you can  create a new project with:

paster create -t turbogears2 projectname

object dispatch should work the way you expect it to.  if you are used
to sticking stuff on cherrypy.request you can now use the "context"

object (pylons.c ) which provides threadlocal, requestlocal storage.