Max Ischenko wrote:
> Hello Mike,
> 
> On 10/22/07, *Mike Orr* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
> 
> 
>     So, to toscawidget or not to toscawidget?  I'm about to write some
>     forms soon.  I was going to learn TW because I assumed it would be
>     better in the long term when I add more Javascript features, and
>     better to start with it now than to rewrite my forms in it later.  Is
>     TW really that bad?  I don't care about a few extra dependencies as
>     long as I know who's using them.

I'm obviously biased in regards to this so I hope a happy user chimes in
instead of giving my opinion. :)

> 
> You 've got to use it for a while to make a judgement. It was a fine
> idea and I don't want to spread FUD. My problems with TW were:
> 
>  - rough (random bugs)

I'd really appreciate some tickets at TG's trac to nail them.

>  - hard to use (basically no docs)

Fair enough. This is something I would really have liked to solve long
ago but seems like some sort of mental blockade of mine. I've tried  my
best to personally give support in TW's mailing list to anyone needing
help (secretly hoping users would fill the docs gap :) but experience
has shown it's no substitute for real documentation. I hope to have time
to change this soon.

>  - too complicated an implementation.

Ironically enough one of the reasons I spun TW out of TG's widgets was
to simplify the implementation. I suspect the use of RuleDispatch
greatly contributes to this perception, this is something I plan to
change too. [1]

>  - development stalled

?? [2]

Regards,
Alberto

[1] http://tinyurl.com/263mfy
[2] http://tinyurl.com/ysk68z

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

Reply via email to