I think there are some valid points you guys brings up, and to just dismiss
them would be silly.  On the other hand there is some very positive stuff
happening in terms of collaboration with Pylons and Turbogears.  It seems
painfully obvious that Pylons and Turbogears need to work together as much
as possible so the smart/motivated people are not replicating
work...registration/identity/wsgi/sqlalchemy/toscawidgets stuff etc.
I think this is happening as I type this so lets all help this process along
and channel our energy into this direction :)



On 6/25/07, Dieter <[EMAIL PROTECTED]> wrote:
>
>
> <quote>
> The main problems with TurboGears is it has been realized that there
> are
> issues with some of the functionality in 1.0 which is why 2.0 is being
> created and several key components are being swapped out or upgraded;
> SQLObject to SQLAlchemy, Kid to Genshi, CherryPy 2 to CherryPy 3, and
> a few
> other changes.
> </quote>
>
> That is exactly the reason for the confusion about the future of TG.
> Maybe my TG 1.0 projects will run without any changes even in TG 1.1
> or 2.0, but I don't know for sure. So, now I'm porting my projects to
> Pylons, at least the Pylons developers have a clearer vision of the
> future of their framework.
>
> And the Pylons online docs are much better than the TurboGears docs. I
> haven't seen any real progress in the TurboGears online docs and this
> really turns me off this formerly promising framework. And the TG book
> which I also bought is unfortunately not better than the online docs,
> in fact it is one of the worst and confusing technical books I have
> ever read.
>
>
> >
>


-- 
http://www.blog.noahgift.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to