<snip> > I'd be interested to hear the arguments against the inclusion of a JS > library, I can't see any reasonable such argument, but would be happy > to hear your opinions! My main concern is that not choosing a default > JS library will negatively impact the success of tg while making a > choice will boost its popularity and does not require lot of work > since it's mainly a communication effort.
</snip> I can agree to most of the points you made. For me the important thing would be (which you also mention) that it doesn't pollute core, and comes as e.g. dependency to tg.devtools. The lessons to be learned from TG1 & MochiKit teach us that. OTOH I think they *are* learned, as we now depend on TW, instead of including a widget-framework. But I guess this is more a matter of resources: creating a compellin show-case with client-side code is something that needs them, and IMHO those who step up to do it should get the choice of their tools. Diez --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
