I agree with Renee, Wes et al that having some kind of 'official' ajax plugin is almost a requirement for a serious UI framework as serious now. I've used ajax feature pretty heavily on the last 4 projects (all using struts) I've worked on. The first two using dojo, and the last two using a homegrown jquery integration which has turned into my plugin that Wes referred to. I am a fairly heavy user of jquery now and would certainly provide support a struts plugin. I am very impressed by Johannes' plugin especially considering how quickly/solidly it's come together. I think as Wes said, we should combine our efforts together now to provide something we can all support together. For example, while Johannes' plugin focuses heavily on interface features/ widgets and effects, mine focuses more on the event handling and integrating events between componenent or custom js code (using a publish/subscribe framework). Looking at the respective code bases I think that these feature sets can be combined fairly easily.
To summarize, I'm +! for the plugin and will help implement and support it if/when approved. - Eric On Sun, Jul 26, 2009 at 8:06 PM, Musachy Barroso <musa...@gmail.com> wrote: > I am also a jquery user, so I can help support this. > > musachy > > On Sun, Jul 26, 2009 at 9:39 AM, Wes Wannemacher<w...@wantii.com> wrote: > > [thread snip] > > > > I looked through the code and it is fairly straightforward. There are > > Components, Beans and freemarker files. I didn't notice anything overly > complex > > in the build process. It looks like Johannes used eclipse, but setup the > > source tree just like any maven project (src/main/java, > src/main/resources). > > There are no unit tests that I saw, but I don't think this should block > us > > from bringing into the sandbox (if we do promote this to being part of > > struts). > > > > At this point, I think I am going to defer to Martin, as far as moving > > forward. I think whichever way we go, I am going to volunteer to work on > this. > > If we bring it in to Apache, obviously I'll support it, but if we don't I > will > > probably start posting patches at Google Code. Personally, I'd rather see > it > > become part of Apache since it will gain more exposure (and transitively, > > better support). I don't think it's a finished product, but it's much > closer > > than my plugin and will probably be easier to support than the existing > ajax > > plugin. > > > > I'd like to hear back from Martin, or anyone else against adoption before > I > > start working on it. If we decide not to bring it in, I can respect that, > but > > if we do bring it in, the first thing will be to maven-ize it, and use > the > > struts2-plugin artifact as the parent, etc. > > > > -Wes > > > > -- > > Wes Wannemacher > > Author - Struts 2 In Practice > > Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more > > http://www.manning.com/wannemacher > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > > For additional commands, e-mail: dev-h...@struts.apache.org > > > > > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
