+1 on this.  Although it's more work, if it's going to really be
framework-independent then we need to support at least some of the
major javascript kits.

-ian

On Dec 11, 2:40 pm, Alberto Valverde <[EMAIL PROTECTED]> wrote:
> On Dec 11, 2006, at 12:47 AM, Lee McFadden wrote:
>
>
>
> > I think that if ToscaWidgets are to be truly framework independant
> > then the core widgets shouldn't use a JS library at all.This is more or 
> > less what I've been thinking about as I've meditated
> the issue more carefully...
>
> How about not including *any* JS library at all?
>
> I mean, my idea for ToscaWidgets (the ToscaWidgets distribution egg
> itself) since I splitted the forms into a separate distribution was
> to provide only the core "framework" to build widgets with.  In fact,
> the only Widget it bundles at the moment is
> toscawidgets.js_interface.mochikit which is needed for the
> "add_event_handler" stuff (which I'm thinking to remove as well).
>
> Since I decided to remove the Genshi dependancy on the widgets core
> to allow flexibility it now seems contradictory to "force" a specific
> JS library to users....
>
> So now my plan for action is:
>
> 1) new ToscaWidgetsMochi egg with the mochikit widget
> 2) new ToscaWidgetsJQuery egg with the jQuery widget and wrappers for
> the cool accordions, tabs, bells and whistles.
> 3) js_interface.core.EventAware bye, bye... so no ties to any
> specific events API. the js_inteface.functions wrappers (which I'm
> about to rewrite as the current implementation sux) should enable
> writting EventAware mixins using the JS library of choice.
> 
> Does it sound reasonable?
> 
> Alberto


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