List Info

Thread: TurboGears2 status update
TurboGears2 status update
user name
 2007-11-04 21:42:17 
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

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Docudo" group.
To post to this group, send email to docudogooglegroups.com
To unsubscribe from this group, send email to
docudo-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/docudo?hl=en
-~----------~----~----~----~------~----~------~--~---
Re: TurboGears2 status update
user name
 2007-11-05 08:06:18 

  


  

    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"


I9;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.mchristensengmail.com">mark.mchristensengmail.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&quot; 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

--~--~---------~--~----~------------~-------~--~----~

You received this message because you are subscribed to the Google Groups "Docudo" group. 
 To post to this group, send email to docudogooglegroups.com 
 To unsubscribe from this group, send email to docudo-unsubscribegooglegroups.com 
 For more options, visit this group at http://groups.google.com/group/docudo?hl=en 
 -~----------~----~----~----~------~----~------~--~---





  

  
  
   
     
    






 [1-2]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )