I will definitely not judge TG's state of documentation because
CherryPy's one is still rough around the edge and not so much user friendly.

However I come down to the conclusion that the problem, beyond having
more people, is that you can't write proper documentation as long as the
project spends so much in changing the product itself.

I think the CP's documentation will get better and better as we go
because CP is now stable enough that it will unlikely chang
fundamentally for quite some time.

>From an external POV (really since I actually don't use TG), TurboGears
seems should stop developing new features, pause and trim down a lot
what his a requirement and what is not.

The huge volume of messages on this list is not only due to the
framework popularity but because people look for information they can't
find elsewhere. This is not a good sign.

Personally it's like TG tries to do everything at once and therefore
finishes nothing at all. It's harsh and probably wrong but that's a
feeling I can't help having.

For instance when widgets started I thought "this is too huge when the
core of the framework is not stable yet". Widgets should have waited. In
fact I'd dare say that they should be dropped from TG2 core features
list until TG2 is actually stable and usable.

I fear for TG more and more. People are willing but will also loose
appetite if there is no visibility.

Sorry for sounding negative. I hope TG will recover and be shiny as it
once was when Kevin introduced it but currently it looks well... a mess
to me (again this is from a completely external POV).

One more note, recently we were discussing over at #cherrypy and I
stated that if I needed a web framework today I'd certainly opt for
Pylons over TG. People who know my relative passion for  WSGI (<wink />)
but I can't help it. When I look at Pylons it seems stable, clear and
fairly well documented. It gives me the core features I need and let me
do the fancy stuff as I would require. I don't think this is a problem
of technology used underneath but simply because the guys behind Pylons
have not tried to make it bigger than the project could cope with. TG
has missed that opportunity with TG1 I think and should rectify that
with TG2.

Of course I understand a lot has been done on TG and some people around
here seem to have done a fantastic job but maybe the team should step
back and understand what should be their focus. And if they already do
they might want to be a little more public about it :)

- Sylvain

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