struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Al Sutton" <al.sut...@alsutton.com>
Subject Re: [s2] Let's get out Struts 2.1.1
Date Thu, 21 Feb 2008 18:02:16 GMT
I, for one, would love to see two classes of struts/ajax tags in S2.1;

Class 1 - Core support tags that all ajax plugins support which would allow 
developers to swap backends.
Class 2 - Plugin specific tags, for covering those ajax framework specific 
functions which are just too cool to leave out.

I'd suggest that Class 1 comes from all the tags which were in S2.0 core and 
moved out to the plugin in S2.1, this would give S2.0 users a smoother 
migration path knowing that they can chop and change ajax plugins to find 
one they like without the risk of wasting time on a plugin that doesn't 
deliver what they need.

Al.

----- Original Message ----- 
From: "Wes Wannemacher" <wesw@wantii.com>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Thursday, February 21, 2008 5:36 PM
Subject: Re: [s2] Let's get out Struts 2.1.1


>I may get boos on this, but I've thought about creating a hand-rolled
> AJAX plugin. I like the available JS frameworks like
> Prototype/Dojo/JQuery, but it does seem like there are a lot of
> gotchas with any one of them. Having written some XHR processing in
> vanilla javascript, sometimes I wonder how hard it would be to
> maintain a tag library specifically developed to integrate with
> Struts2... The benefit would be in maintenance, since it would be more
> closely tied to the development of Struts2 (and possibly performance,
> though a lot of work was done in the dojo-plugin), but the
> disadvantage would be that a lot of JS code would need developed up
> front. Another thought I've had on the topic is to separate the
> concerns within the AJAX components, you have a set of widgets
> (tabbedpanel, divs, autocompleter) and a set of components related to
> processing (JSON, XHR, etc). It would be great to make these two
> things separated to the point that the YUI widgets could be dropped in
> and combined with the Prototype processing so that the YUI tabbedpanel
> could be populated by JQuery calls... The goal would be to give a
> somewhat savvy AJAX developer the freedom to pull in the widgets they
> like combined with the JS code style they prefer.
>
> -- 
> Wesley Wannemacher
> President, Head Engineer/Consultant
> WanTii, Inc.
> http://www.wantii.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message