2009/2/23 Musachy Barroso <musa...@gmail.com> > > I definitely agree that a thoughtful design is the right starting place. > > Taking this to the extreme, one thing that I mentioned in my earlier post > > (without too much thought) was that perhaps some kind of standardized > > specification for binding ajax features to standard struts tags > (including > > perhaps standardized widget tags - which may not be functional without > the > > plugin) would be something worth thinking about as there are an > increasing > > number of struts-ajax library integration each with their own integration > > mechanisms and syntax. Given the variety of ajax implementations, this > might > > be ambitious at the moment, but definitely worth a thought. This would > > probably take the form of some kind of standardized <bind/> tag spec with > > specified behaviour for implementations. > > > > I think we should keep simple, and down to JQuery. I don't think it is > worth the effort to go with some generic interface where multiple > libraries can be plugged in. IMO that would add more complexity, lots > of bugs and zillions of questions on the mailing lists(just supporting > one library has been hard). I would say the same thing about the > widgets, adding anything else beyond the jquery datepicker would be > too much.
I agree. In addition to the datepicker, I think the tabbed pane widget is quite useful (I have already implemented it actually). I'd also like to see an autocompleter, but there is no native jQuery-UI widget for it yet (though a couple of strong candidates) and I remember the dojo autocompleter being a bit of a headache. > > > At the moment, I have taken the other route and integrated a few jquery > > ajax-enabled tags, but it shouldn't be too much work to switch these to a > > <bind/> tag implementation. So far, I have integrated the div, anchor, > > submit and tabbed pane tags (using a custom head tag to inject jquery > > dependencies). I have NOT implemented the full set of tag attributes for > > these that dojo provided, opting to start with the minimal, critical > > attributes first. For the binding I have implemented a very lightweight > > custom publish/subscribe jQuery extension framework which is one of the > few > > things I really liked about the dojo framework. (I'll be sharing this > once > > on jquery as well once well tested) > > > > Topics is one of the things that would be very nice to have, and I > agree that we should start very small. > Subscription/publishing using topics is provided in the jquery-subcribe framework I've put together and heavily used by the generated jquery code. This is included in js files injected by head tag > > > Perhaps surprisingly, I have currently implemented the templates using > the > > javatemplates plugin (not yet freemarker), simply because I've been too > lazy > > to pick up the freemarker template syntax which I'm not very familiar > with > > yet (this might be a great starting place for some collaborative help). > > I really like JQuery's one-liners, so maybe it won't be that hard to > read in java code, if it get complex then I'd suggest swtiching to > FreeMarker. > Not excessively complex at the moment but getting there. Will implement with freemarker soon i hope. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
