Unfourtunately I've been very busy, and out of town a LOT over the
last month and a half.  So I haven't been able to move things forward
as quickly as I'd like.

At the same time we've been waiting on three major things:


1) ToscaWidgets integration
2) Transaction handling middleware
3) SQLAlchemy's preffered connection mechanism to settle down.

Fortunately 3 is now complete, and I've heard from somebody that they
have been working on 2.

At the same time I've been playing with various mechanisms for picking
out the template/engine/content type to return, and I have some code
samples for a couple different approaches -- but I'm not 100% sold on
which approach to use yet.

I should bring this up on the trunk list...

I'm hoping to have more time to work on TG 2 in September,

--Mark Ramm

On 8/26/07, Steve Bergman <[EMAIL PROTECTED]> wrote:
>
> There was a flurry of activity in late June regarding TG2 which seems
> to have pretty much died out by early July.  Would anyone care to give
> a status report on the progress of pygears/TG2?  Or is there already
> someplace that such summaries are available?
>
> With the "best of breed" components that make up TG1.0 (SQLObject,
> CherryPy, Mochikit, Kid) mostly deprecated in favor of a completely
> new "best of breed" stack (SQLAlchemy, Paste, ?, Genshi), little news
> of how pygears is progressing being available, and an average posting
> rate of one message per day on the turbogrears-trunk list, a person
> could be forgiven for simply assuming that TurboGears was dead.
>
>
> >
>


-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to