Moving Dojo plugin to archive
What are the reasons for moving it? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Moving Dojo plugin to archive
2011/4/26 Jason Pyeron jpye...@pdinc.us: What are the reasons for moving it? It's support the old version of Dojo - 0.4 as I can recall Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
RE: Moving Dojo plugin to archive
-Original Message- From: Lukasz Lenart [mailto:lukasz.len...@googlemail.com] Sent: Tuesday, April 26, 2011 14:26 To: Struts Developers List Subject: Re: Moving Dojo plugin to archive 2011/4/26 Jason Pyeron jpye...@pdinc.us: What are the reasons for moving it? It's support the old version of Dojo - 0.4 as I can recall Updating the dojo support is on my todo list, whould that keep it alive? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
RE: Moving Dojo plugin to archive
Potentially. IMO non-trivial-enough to be worth it, although a mirror of the jQuery tags would be enough for me. Dave On Apr 26, 2011 2:42 PM, Jason Pyeron jpye...@pdinc.us wrote: -Original Message- From: Lukasz Lenart [mailto:lukasz.len...@googlemail.com] Sent: Tuesday, April 26, 2011 14:26 To: Struts Developers List Subject: Re: Moving Dojo plugin to archive 2011/4/26 Jason Pyeron jpye...@pdinc.us: What are the reasons for moving it? It's support the old version of Dojo - 0.4 as I can recall Updating the dojo support is on my todo list, whould that keep it alive? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Moving Dojo plugin to archive
On Tue, Apr 26, 2011 at 2:49 PM, Dave Newton wrote: Potentially. IMO non-trivial-enough to be worth it [...] I meant not worth it. d. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Moving Dojo plugin to archive
2011/4/26 Jason Pyeron jpye...@pdinc.us: -Original Message- From: Lukasz Lenart [mailto:lukasz.len...@googlemail.com] Sent: Tuesday, April 26, 2011 14:26 To: Struts Developers List Subject: Re: Moving Dojo plugin to archive 2011/4/26 Jason Pyeron jpye...@pdinc.us: What are the reasons for moving it? It's support the old version of Dojo - 0.4 as I can recall Updating the dojo support is on my todo list, whould that keep it alive? That would be cool :-) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin
2010/8/24 Martin Cooper mart...@apache.org: If there's a good reason for not having the code in the main trunk, even when it's not part of the distribution, then I suppose it could be moved back to the sandbox, or even to the archive. Basically not, it can stay where it is right now. There is a minor problem when you want to build the plugin with non-English Locales. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ Kapituła Javarsovia 2010 http://javarsovia.pl - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin
On Sat, Aug 21, 2010 at 8:51 AM, Dave Newton davelnew...@gmail.com wrote: Should the Dojo plugin be removed from the distro now? WW-3484 was just entered against it--if it's not going to be supported, I guess I'd vote for stripping it out and putting the code elsewhere like on Google or something. Removing it from the release / distribution seems fine if that's what we want. I'm not so sure about moving the code elsewhere, though. If someone else wants to pick it up and copy it somewhere to work on, it's up to them, not us, where they want to take it and what source control system they want to use. If there's a good reason for not having the code in the main trunk, even when it's not part of the distribution, then I suppose it could be moved back to the sandbox, or even to the archive. -- Martin Cooper Thoughts? Dave - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Dojo plugin
Should the Dojo plugin be removed from the distro now? WW-3484 was just entered against it--if it's not going to be supported, I guess I'd vote for stripping it out and putting the code elsewhere like on Google or something. Thoughts? Dave
Re: Dojo plugin
On 8/21/10 11:51 AM, Dave Newton wrote: Should the Dojo plugin be removed from the distro now? Wasn't it deprecated in 2.1? Doesn't that mean we can just kill it in 2.2? -Dale - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin
I would think so, but that's just me. (I would like to see it live on Google Code, though, so if anybody *wants* to support it, they could.) On Sat, Aug 21, 2010 at 12:00 PM, Dale Newfield d...@newfield.org wrote: On 8/21/10 11:51 AM, Dave Newton wrote: Should the Dojo plugin be removed from the distro now? Wasn't it deprecated in 2.1? Doesn't that mean we can just kill it in 2.2? -Dale - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Discussion - drop Dojo plugin
To include others in out talk ;-) -- Forwarded message -- From: Lukasz Lenart lukasz.len...@googlemail.com Date: 2010/3/24 Subject: Re: Discussion - drop Dojo plugin To: Wes Wannemacher w...@wantii.com Ups... I sent it only to you instead to the group ;-) 2010/3/24 Wes Wannemacher w...@wantii.com: My main thought is this - Let's try to get Johannes Gephart's JQuery plugin incorporated into Struts 2.2.x... +1 you are right, it would be nice to have it as a replacement / alternative for Dojo plugin. His showcase looks great and I'm working on a few things for a project here that I will eventually incorporate into either core or his plugin, but JQuery is one heckuva lot easier to work with and maintain than Dojo ever was/will be. If so there shouldn't be anyone who would complain ;-) If you are working toward a 2.1.9 release, let's get that out and then I'll send an email to the PMC about inviting him to be a committer. Although he hasn't done many patches, etc. I'll argue that his plugin would be a great contribution and his direct support will help Struts 2's continued success... Ok, but I'm still blocked by moving Ognl 3.0 to central repo :P Regards -- Łukasz http://www.lenart.org.pl/ Kapituła Javarsovia 2010 http://javarsovia.pl - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: How to build dojo plugin???
I see this type of behavior when there is a dependency, side effect, between tests. An example of this is STATIC variables and I have seen this same type of effect many times when running JUnits with IntelliJ v.s maven IntelliJ reinstates the JUnit Runner class for each test method, and therefore starts with a clean slate for static variables. I believe starting with IJ 4.5, to implement the rerun failed test, IJ changed the behavior to differ from just using maven. I find this difference in running JUnits valuable since they find latent bugs in the JUnit tests, but they can have funny consequences: Funny story I had a case where a co-worker kept breaking the JUnits because he was using eclipse and was FIXING the expected results of the tests to pass when run under eclipse. However, doing this would break the tests running under IntelliJ, I would FIX the tests running under IntelliJ, which would break the tests running under eclipse. This continued for several weeks, and we both kept FIXING the tests. Finally I realized what was going on and fixed the static initialization problem and the problem went away. Funny Story Hope this helps -Rob On 8/26/2009 10:30 AM, Lukasz Lenart wrote: Hi, I discovered another strange thing. When I just launch the test from IDEA with -Duser.country=US -Duser.language=en, then it pass. But when I use maven with the same settings, only two test fail :P testSimple(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) testSimpleDisabled(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) I've tried to use the latest maven version, JDK5 and JDK6, but no lock. Any ideas? Regards - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: How to build dojo plugin???
Hi, I discovered another strange thing. When I just launch the test from IDEA with -Duser.country=US -Duser.language=en, then it pass. But when I use maven with the same settings, only two test fail :P testSimple(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) testSimpleDisabled(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) I've tried to use the latest maven version, JDK5 and JDK6, but no lock. Any ideas? Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: How to build dojo plugin???
I feel a disturbance in the force ;) musachy On Wed, Aug 26, 2009 at 7:30 AM, Lukasz Lenartlukasz.len...@googlemail.com wrote: Hi, I discovered another strange thing. When I just launch the test from IDEA with -Duser.country=US -Duser.language=en, then it pass. But when I use maven with the same settings, only two test fail :P testSimple(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) testSimpleDisabled(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) I've tried to use the latest maven version, JDK5 and JDK6, but no lock. Any ideas? Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - 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
How to build dojo plugin???
Hi, I'm desperate ;-( I'm trying to build and install struts2-dojo-plugin from source but each time I'm getting errors in test. I've tried with different locales but no luck: mvn install -Duser.country=US -Duser.language=en What to do? Please help! testSimple(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) Time elapsed: 0.141 sec FAILURE! junit.framework.ComparisonFailure: expected:...idvalue=2008-03-03[lang=iname=hinputName=dojo.hdisplayWeeks=trueadjustWeeks=truestartDate=2008-02-02endDate=2008-01-01]weekStartsOn=gsta... but was:...idvalue=2008-03-03[T00:00:00lang=iname=hinputName=dojo.hdisplayWeeks=trueadjustWeeks=truestartDate=2008-02-02T00:00:00endDate=2008-01-01T00:00:00]weekStartsOn=gsta... testSimpleDisabled(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) Time elapsed: 0.109 sec FAILURE! junit.framework.ComparisonFailure: expected:...idvalue=2008-03-03[lang=iname=hinputName=dojo.hdisplayWeeks=trueadjustWeeks=truestartDate=2008-02-02endDate=2008-01-01]weekStartsOn=gsta... but was:...idvalue=2008-03-03[T00:00:00lang=iname=hinputName=dojo.hdisplayWeeks=trueadjustWeeks=truestartDate=2008-02-02T00:00:00endDate=2008-01-01T00:00:00]weekStartsOn=gsta... testDateParsing(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) Time elapsed: 0.079 sec FAILURE! junit.framework.AssertionFailedError: expected:2007 but was:6 Thanks in advance -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: How to build dojo plugin???
something changed in the way the dates are formatted I guess. 2008-03-03 vs 2008-03-03T00:00:00 I thought it was using the second one already. Maybe you just need to update the tests. On Tue, Aug 25, 2009 at 11:49 AM, Lukasz Lenartlukasz.len...@googlemail.com wrote: Hi, I'm desperate ;-( I'm trying to build and install struts2-dojo-plugin from source but each time I'm getting errors in test. I've tried with different locales but no luck: mvn install -Duser.country=US -Duser.language=en What to do? Please help! testSimple(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) Time elapsed: 0.141 sec FAILURE! junit.framework.ComparisonFailure: expected:...idvalue=2008-03-03[lang=iname=hinputName=dojo.hdisplayWeeks=trueadjustWeeks=truestartDate=2008-02-02endDate=2008-01-01]weekStartsOn=gsta... but was:...idvalue=2008-03-03[T00:00:00lang=iname=hinputName=dojo.hdisplayWeeks=trueadjustWeeks=truestartDate=2008-02-02T00:00:00endDate=2008-01-01T00:00:00]weekStartsOn=gsta... testSimpleDisabled(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) Time elapsed: 0.109 sec FAILURE! junit.framework.ComparisonFailure: expected:...idvalue=2008-03-03[lang=iname=hinputName=dojo.hdisplayWeeks=trueadjustWeeks=truestartDate=2008-02-02endDate=2008-01-01]weekStartsOn=gsta... but was:...idvalue=2008-03-03[T00:00:00lang=iname=hinputName=dojo.hdisplayWeeks=trueadjustWeeks=truestartDate=2008-02-02T00:00:00endDate=2008-01-01T00:00:00]weekStartsOn=gsta... testDateParsing(org.apache.struts2.dojo.views.jsp.ui.DateTimePickerTagTest) Time elapsed: 0.079 sec FAILURE! junit.framework.AssertionFailedError: expected:2007 but was:6 Thanks in advance -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - 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
Re: How to build dojo plugin???
2009/8/25 Musachy Barroso musa...@gmail.com: something changed in the way the dates are formatted I guess. 2008-03-03 vs 2008-03-03T00:00:00 Yeah, I noticed that but I've been thinking it's related to Locale but I've tried different combinations. I thought it was using the second one already. Maybe you just need to update the tests. I did that and I'm up-to-date, but still the same. Any other ideas? Regards -- Lukasz http://www.lenart.org.pl/ http://dailylog.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: How to build dojo plugin???
On Tuesday 25 August 2009 02:59:47 pm Lukasz Lenart wrote: 2009/8/25 Musachy Barroso musa...@gmail.com: something changed in the way the dates are formatted I guess. 2008-03-03 vs 2008-03-03T00:00:00 Yeah, I noticed that but I've been thinking it's related to Locale but I've tried different combinations. I thought it was using the second one already. Maybe you just need to update the tests. I did that and I'm up-to-date, but still the same. Any other ideas? I'm pretty sure that both of the dates listed above are in the iso8601 format, or whatever the iso format is. It is the format that JSON uses to serialize dates. The standard for the format allows you to only specify the parts that are significant, so 2008-03-03 is as legit as 2008-03-03T00:00:00. But the problem is that there is no built-in support in either java or javascript, so using it is often a PITA. -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin deprecated
+1 for removing the First-Class AJAX support line. Al. Frank W. Zammetti wrote: I don't know, I think Andreas' point has at least some validity... the page he linked to does in fact state: *First-class AJAX support* - Add interactivity and flexibility with AJAX tags that look and feel just like standard Struts tags. Seems like if that's no longer the case, to whatever extent it's no longer the case, then that line should be removed from that page or modified as necessary, in the interest of honest advertising if nothing else. Just being able to use any AJAX library you wish, as Al correctly states, doesn't by extension mean that S2 has first-class AJAX support. At least, *I* wouldn't consider it first-class support. What Martin said is of course valid as well: if someone out there wants these tags/plugin to exist, put in the effort. The Struts team has the right to do what they want with the project, and you have the right to not use S2 if it doesn't meet your needs... better still, MAKE IT meet your needs and give back... I think you'll find many people being quite grateful to you for your efforts. Frank -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin deprecated
Guys, Am Do, 15.01.2009, 07:36, schrieb Martin Cooper: Let's be clear about this. * Lots of people think that the Dojo-based AJAX tags would be useful if they worked with the latest versions of Dojo, or some other toolkit. * Few, if any, people want to use them in their current form. Hmm, that is not what I am experiencing - I know a lot of people using the dojo tags for exactly what it is capable right now, basically doing some asynchronous page updates and form validation. As long as the examples in the showcase app work, there will IMO be people still be using this feature. Now that 2.1 is out, we should not tell people that the current ajax tags are going to be dropped in a later version of 2.1 - this is IMO up to a 2.2 version. * Nobody has stepped up and offered to migrate these tags to anything else, whether that's a newer version of Dojo or another toolkit. Well said. So, the short answer is, step up or shut up. We'd be happy to see someone take on this task, but I have had it up to _here_ with people who complain and expect someone else to do the work. -- Martin Cooper On Wed, Jan 14, 2009 at 10:19 PM, Andreas Joseph Krogh andr...@officenet.no wrote: On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote: Thanks for the info. It would be a shame if the sx tags were to disappear because they are easy to use especially the sx:submit validate=true... with Ajax validation. But I suppose its alot of work to upgrade/maintain the DOJO plugin. I think there should be a warning-sign about this on the web ( http://struts.apache.org/2.1.6/index.html). Built-in AJAX-support (first-class AJAX support) is one of the things Struts2 announces as a main-feature, and with the dojo-plugin going away this isn't true any more. This means Struts-2.1 no longer has any decent ui-tags? -- Andreas Joseph Krogh andr...@officenet.no Senior Software Developer / CEO +-+ OfficeNet AS| The most difficult thing in the world is to | Karenslyst Allé 11 | know how to do a thing and to watch | PO. Box 529 Skøyen | somebody else doing it wrong, without | 0214 Oslo | comment.| NORWAY | | Tlf:+47 24 15 38 90 | | Fax:+47 24 15 38 91 | | Mobile: +47 909 56 963 | | +-+ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin deprecated
Frank W. Zammetti wrote: I don't know, I think Andreas' point has at least some validity... the page he linked to does in fact state: *First-class AJAX support* - Add interactivity and flexibility with AJAX tags that look and feel just like standard Struts tags. Seems like if that's no longer the case, to whatever extent it's no longer the case, then that line should be removed from that page or modified as necessary, in the interest of honest advertising if nothing else. Just being able to use any AJAX library you wish, as Al correctly states, doesn't by extension mean that S2 has first-class AJAX support. At least, *I* wouldn't consider it first-class support. Exactly. I'm not bashing anyone, just pointing out that it might be wise not to advertise AJAX-support so much now that it might not be the case anymore. What Martin said is of course valid as well: if someone out there wants these tags/plugin to exist, put in the effort. The Struts team has the right to do what they want with the project, and you have the right to not use S2 if it doesn't meet your needs... better still, MAKE IT meet your needs and give back... I think you'll find many people being quite grateful to you for your efforts. Frank Struts-2.1 with AjaxAnywhere fits my needs very well:-) -- Andreas Joseph Krogh andr...@officenet.no Senior Software Developer / CEO +-+ OfficeNet AS| The most difficult thing in the world is to | Karenslyst Allé 11 | know how to do a thing and to watch | PO. Box 529 Skøyen | somebody else doing it wrong, without | 0214 Oslo | comment.| NORWAY | | Tlf:+47 24 15 38 90 | | Fax:+47 24 15 38 91 | | Mobile: +47 909 56 963 | | +-+ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin deprecated
In fact the tags are a lot better in 2.1 than they were in 2.0. The problem is that for a long time we (as in struts 2 committers) have stopped trying to catch up with Dojo versions and updating the tags accordingly. This deprecation is the official announcement of my previous sentence. If they never get updated, then they will be dropped, and at that point, I think it is fair to update the Struts 2 description (remove AJAX from it). musachy On Thu, Jan 15, 2009 at 5:01 AM, Andreas Joseph Krogh andr...@officenet.no wrote: Frank W. Zammetti wrote: I don't know, I think Andreas' point has at least some validity... the page he linked to does in fact state: *First-class AJAX support* - Add interactivity and flexibility with AJAX tags that look and feel just like standard Struts tags. Seems like if that's no longer the case, to whatever extent it's no longer the case, then that line should be removed from that page or modified as necessary, in the interest of honest advertising if nothing else. Just being able to use any AJAX library you wish, as Al correctly states, doesn't by extension mean that S2 has first-class AJAX support. At least, *I* wouldn't consider it first-class support. Exactly. I'm not bashing anyone, just pointing out that it might be wise not to advertise AJAX-support so much now that it might not be the case anymore. What Martin said is of course valid as well: if someone out there wants these tags/plugin to exist, put in the effort. The Struts team has the right to do what they want with the project, and you have the right to not use S2 if it doesn't meet your needs... better still, MAKE IT meet your needs and give back... I think you'll find many people being quite grateful to you for your efforts. Frank Struts-2.1 with AjaxAnywhere fits my needs very well:-) -- Andreas Joseph Krogh andr...@officenet.no Senior Software Developer / CEO +-+ OfficeNet AS| The most difficult thing in the world is to | Karenslyst Allé 11 | know how to do a thing and to watch | PO. Box 529 Skøyen | somebody else doing it wrong, without | 0214 Oslo | comment.| NORWAY | | Tlf:+47 24 15 38 90 | | Fax:+47 24 15 38 91 | | Mobile: +47 909 56 963 | | +-+ - 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
Re: Dojo plugin deprecated
Rene Gielen wrote: Hmm, that is not what I am experiencing - I know a lot of people using the dojo tags for exactly what it is capable right now, basically doing some asynchronous page updates and form validation. I said this once a long time ago; I'll throw it out again now. I think a core (and low) level of Ajax functionality should be defined and we should provide plugins for a couple different JavaScript frameworks (jQuery, Prototype, whatever else people want to contribute). For anything even remotely complicated enough JavaScript is required that the tags quickly become insufficient, so for me the list boils down to what Rene listed plus a couple of others: * Form validation * Form submission w/ target update * Links w/ target update Er, there were two more but now I forgot. I'm not fundamentally opposed to keeping the existing Dojo tags available, or UI tags in general, but it's a tough battle to keep them up-to-date and general-purpose enough to make everybody (here, by everybody, I mean anybody) happy. As long as the examples in the showcase app work, there will IMO be people still be using this feature. I'll bet I could break it in like two minutes. I *knew* I had a niche to fill. Dave - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
RE: Dojo plugin deprecated
Just to be clear, I'm not complaining about the Dojo plugin being deprecated ( I understand the reasons for deprecation ). I was just trying to determine the future of the Struts Ajax sx: tags so I can find an alternative solution for my needs if need be. Gus. -Original Message- From: mfncoo...@gmail.com [mailto:mfncoo...@gmail.com]on Behalf Of Martin Cooper Sent: Thursday, 15 January 2009 7:36 p.m. To: Struts Developers List Cc: Gustave Pheiffers Subject: Re: Dojo plugin deprecated Let's be clear about this. * Lots of people think that the Dojo-based AJAX tags would be useful if they worked with the latest versions of Dojo, or some other toolkit. * Few, if any, people want to use them in their current form. * Nobody has stepped up and offered to migrate these tags to anything else, whether that's a newer version of Dojo or another toolkit. So, the short answer is, step up or shut up. We'd be happy to see someone take on this task, but I have had it up to _here_ with people who complain and expect someone else to do the work. -- Martin Cooper On Wed, Jan 14, 2009 at 10:19 PM, Andreas Joseph Krogh andr...@officenet.no wrote: On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote: Thanks for the info. It would be a shame if the sx tags were to disappear because they are easy to use especially the sx:submit validate=true... with Ajax validation. But I suppose its alot of work to upgrade/maintain the DOJO plugin. I think there should be a warning-sign about this on the web ( http://struts.apache.org/2.1.6/index.html). Built-in AJAX-support (first-class AJAX support) is one of the things Struts2 announces as a main-feature, and with the dojo-plugin going away this isn't true any more. This means Struts-2.1 no longer has any decent ui-tags? -- Andreas Joseph Krogh andr...@officenet.no Senior Software Developer / CEO +-+ OfficeNet AS| The most difficult thing in the world is to | Karenslyst Allé 11 | know how to do a thing and to watch | PO. Box 529 Skøyen | somebody else doing it wrong, without | 0214 Oslo | comment.| NORWAY | | Tlf:+47 24 15 38 90 | | Fax:+47 24 15 38 91 | | Mobile: +47 909 56 963 | | +-+
Dojo plugin deprecated
Hi there, My understanding is the Dojo plugin is deprecated on Struts 2.1.x Does this mean the ajax tags sx will eventually be removed from Struts 2.1.x or will a replacement for Dojo be put in place so we can continue to use the ajax sx tags. Thanks Gus
Re: Dojo plugin deprecated
It means they will eventually be removed or not updated, unless someone comes up with the code to upgrade them to a newer version of Dojo, or a different framework (no volunteers so far). musachy On Wed, Jan 14, 2009 at 4:52 PM, Gustave Pheiffers gpheiff...@pavtech.com wrote: Hi there, My understanding is the Dojo plugin is deprecated on Struts 2.1.x Does this mean the ajax tags sx will eventually be removed from Struts 2.1.x or will a replacement for Dojo be put in place so we can continue to use the ajax sx tags. Thanks Gus -- 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
RE: Dojo plugin deprecated
Thanks for the info. It would be a shame if the sx tags were to disappear because they are easy to use especially the sx:submit validate=true... with Ajax validation. But I suppose its alot of work to upgrade/maintain the DOJO plugin. Gus. -Original Message- From: Musachy Barroso [mailto:musa...@gmail.com] Sent: Thursday, 15 January 2009 11:05 a.m. To: Struts Developers List Subject: Re: Dojo plugin deprecated It means they will eventually be removed or not updated, unless someone comes up with the code to upgrade them to a newer version of Dojo, or a different framework (no volunteers so far). musachy On Wed, Jan 14, 2009 at 4:52 PM, Gustave Pheiffers gpheiff...@pavtech.com wrote: Hi there, My understanding is the Dojo plugin is deprecated on Struts 2.1.x Does this mean the ajax tags sx will eventually be removed from Struts 2.1.x or will a replacement for Dojo be put in place so we can continue to use the ajax sx tags. Thanks Gus -- 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 - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin deprecated
On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote: Thanks for the info. It would be a shame if the sx tags were to disappear because they are easy to use especially the sx:submit validate=true... with Ajax validation. But I suppose its alot of work to upgrade/maintain the DOJO plugin. I think there should be a warning-sign about this on the web (http://struts.apache.org/2.1.6/index.html). Built-in AJAX-support (first-class AJAX support) is one of the things Struts2 announces as a main-feature, and with the dojo-plugin going away this isn't true any more. This means Struts-2.1 no longer has any decent ui-tags? -- Andreas Joseph Krogh andr...@officenet.no Senior Software Developer / CEO +-+ OfficeNet AS| The most difficult thing in the world is to | Karenslyst Allé 11 | know how to do a thing and to watch | PO. Box 529 Skøyen | somebody else doing it wrong, without | 0214 Oslo | comment.| NORWAY | | Tlf:+47 24 15 38 90 | | Fax:+47 24 15 38 91 | | Mobile: +47 909 56 963 | | +-+
Re: Dojo plugin deprecated
Let's be clear about this. * Lots of people think that the Dojo-based AJAX tags would be useful if they worked with the latest versions of Dojo, or some other toolkit. * Few, if any, people want to use them in their current form. * Nobody has stepped up and offered to migrate these tags to anything else, whether that's a newer version of Dojo or another toolkit. So, the short answer is, step up or shut up. We'd be happy to see someone take on this task, but I have had it up to _here_ with people who complain and expect someone else to do the work. -- Martin Cooper On Wed, Jan 14, 2009 at 10:19 PM, Andreas Joseph Krogh andr...@officenet.no wrote: On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote: Thanks for the info. It would be a shame if the sx tags were to disappear because they are easy to use especially the sx:submit validate=true... with Ajax validation. But I suppose its alot of work to upgrade/maintain the DOJO plugin. I think there should be a warning-sign about this on the web ( http://struts.apache.org/2.1.6/index.html). Built-in AJAX-support (first-class AJAX support) is one of the things Struts2 announces as a main-feature, and with the dojo-plugin going away this isn't true any more. This means Struts-2.1 no longer has any decent ui-tags? -- Andreas Joseph Krogh andr...@officenet.no Senior Software Developer / CEO +-+ OfficeNet AS| The most difficult thing in the world is to | Karenslyst Allé 11 | know how to do a thing and to watch | PO. Box 529 Skøyen | somebody else doing it wrong, without | 0214 Oslo | comment.| NORWAY | | Tlf:+47 24 15 38 90 | | Fax:+47 24 15 38 91 | | Mobile: +47 909 56 963 | | +-+
Re: Dojo plugin deprecated
The other thing to remember is that S2 doesn't stop you taking any of the existing AJAX frameworks and using them directly in your JSPs, so it's no like the change has completely barred the use of AJAX functionality. Al. Martin Cooper wrote: Let's be clear about this. * Lots of people think that the Dojo-based AJAX tags would be useful if they worked with the latest versions of Dojo, or some other toolkit. * Few, if any, people want to use them in their current form. * Nobody has stepped up and offered to migrate these tags to anything else, whether that's a newer version of Dojo or another toolkit. So, the short answer is, step up or shut up. We'd be happy to see someone take on this task, but I have had it up to _here_ with people who complain and expect someone else to do the work. -- Martin Cooper On Wed, Jan 14, 2009 at 10:19 PM, Andreas Joseph Krogh andr...@officenet.no wrote: On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote: Thanks for the info. It would be a shame if the sx tags were to disappear because they are easy to use especially the sx:submit validate=true... with Ajax validation. But I suppose its alot of work to upgrade/maintain the DOJO plugin. I think there should be a warning-sign about this on the web ( http://struts.apache.org/2.1.6/index.html). Built-in AJAX-support (first-class AJAX support) is one of the things Struts2 announces as a main-feature, and with the dojo-plugin going away this isn't true any more. This means Struts-2.1 no longer has any decent ui-tags? -- Andreas Joseph Krogh andr...@officenet.no Senior Software Developer / CEO +-+ OfficeNet AS| The most difficult thing in the world is to | Karenslyst Allé 11 | know how to do a thing and to watch | PO. Box 529 Skøyen | somebody else doing it wrong, without | 0214 Oslo | comment.| NORWAY | | Tlf:+47 24 15 38 90 | | Fax:+47 24 15 38 91 | | Mobile: +47 909 56 963 | | +-+ -- == Funky Android Limited is registered in England Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin deprecated
I don't know, I think Andreas' point has at least some validity... the page he linked to does in fact state: *First-class AJAX support* - Add interactivity and flexibility with AJAX tags that look and feel just like standard Struts tags. Seems like if that's no longer the case, to whatever extent it's no longer the case, then that line should be removed from that page or modified as necessary, in the interest of honest advertising if nothing else. Just being able to use any AJAX library you wish, as Al correctly states, doesn't by extension mean that S2 has first-class AJAX support. At least, *I* wouldn't consider it first-class support. What Martin said is of course valid as well: if someone out there wants these tags/plugin to exist, put in the effort. The Struts team has the right to do what they want with the project, and you have the right to not use S2 if it doesn't meet your needs... better still, MAKE IT meet your needs and give back... I think you'll find many people being quite grateful to you for your efforts. Frank -- Frank W. Zammetti Author of Practical Dojo Projects and Practical DWR 2 Projects and Practical JavaScript, DOM Scripting and Ajax Projects and Practical Ajax Projects With Java Technology (For info: apress.com/book/search?searchterm=zammettiact=search) My look ma, I have a blog too! blog: zammetti.com/blog Al Sutton wrote: The other thing to remember is that S2 doesn't stop you taking any of the existing AJAX frameworks and using them directly in your JSPs, so it's no like the change has completely barred the use of AJAX functionality. Al. Martin Cooper wrote: Let's be clear about this. * Lots of people think that the Dojo-based AJAX tags would be useful if they worked with the latest versions of Dojo, or some other toolkit. * Few, if any, people want to use them in their current form. * Nobody has stepped up and offered to migrate these tags to anything else, whether that's a newer version of Dojo or another toolkit. So, the short answer is, step up or shut up. We'd be happy to see someone take on this task, but I have had it up to _here_ with people who complain and expect someone else to do the work. -- Martin Cooper On Wed, Jan 14, 2009 at 10:19 PM, Andreas Joseph Krogh andr...@officenet.no wrote: On Wednesday 14 January 2009 23:42:18 Gustave Pheiffers wrote: Thanks for the info. It would be a shame if the sx tags were to disappear because they are easy to use especially the sx:submit validate=true... with Ajax validation. But I suppose its alot of work to upgrade/maintain the DOJO plugin. I think there should be a warning-sign about this on the web ( http://struts.apache.org/2.1.6/index.html). Built-in AJAX-support (first-class AJAX support) is one of the things Struts2 announces as a main-feature, and with the dojo-plugin going away this isn't true any more. This means Struts-2.1 no longer has any decent ui-tags? -- Andreas Joseph Krogh andr...@officenet.no Senior Software Developer / CEO +-+ OfficeNet AS| The most difficult thing in the world is to | Karenslyst Allé 11 | know how to do a thing and to watch | PO. Box 529 Skøyen | somebody else doing it wrong, without | 0214 Oslo | comment.| NORWAY | | Tlf:+47 24 15 38 90 | | Fax:+47 24 15 38 91 | | Mobile: +47 909 56 963 | | +-+ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Dojo plugin proposal(my last one I promise)
We have talked about this Ad nauseam, and it is obvious that we don't have anyone willing to fix all the current bugs, upgrade the Dojo plugin, or write a replacement. 2.1 is around the corner and I think we should let users know that the Dojo plugin won't be maintained anymore. So my proposal is to deprecate it at once. regards musachy -- 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
Re: Dojo plugin proposal(my last one I promise)
--- On Sat, 12/20/08, Musachy Barroso wrote: We have talked about this Ad nauseam, and it is obvious that we don't have anyone willing to fix all the current bugs, upgrade the Dojo plugin, or write a replacement. 2.1 is around the corner and I think we should let users know that the Dojo plugin won't be maintained anymore. So my proposal is to deprecate it at once. +1 I wonder if the plugin was on Google/etc. if more people would work on it or try to upgrade the Dojo version? There's enough code in there that makes me think a straight conversion to Dojo 1.0 is non-trivial, but I haven't looked at it in awhile. I know I don't know enough Dojo to be very helpful, and my own needs aren't related to Dojo, although I still think a common interface into multiple Ajax/etc. implementations would be a good idea and would help with that aspect of things. Dave - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin proposal(my last one I promise)
+1 Den 20. des.. 2008 kl. 19.27 skrev James Holmes ja...@jamesholmes.com: +1 and agree with Dave on moving the Dojo stuff into a plugin that is hosted somewhere else and can be maintained by more people. On Sat, Dec 20, 2008 at 11:38 AM, Dave Newton newton.d...@yahoo.com wrote: --- On Sat, 12/20/08, Musachy Barroso wrote: We have talked about this Ad nauseam, and it is obvious that we don't have anyone willing to fix all the current bugs, upgrade the Dojo plugin, or write a replacement. 2.1 is around the corner and I think we should let users know that the Dojo plugin won't be maintained anymore. So my proposal is to deprecate it at once. +1 I wonder if the plugin was on Google/etc. if more people would work on it or try to upgrade the Dojo version? There's enough code in there that makes me think a straight conversion to Dojo 1.0 is non-trivial, but I haven't looked at it in awhile. I know I don't know enough Dojo to be very helpful, and my own needs aren't related to Dojo, although I still think a common interface into multiple Ajax/etc. implementations would be a good idea and would help with that aspect of things. Dave - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin proposal(my last one I promise)
On Sat, Dec 20, 2008 at 10:27 AM, James Holmes ja...@jamesholmes.comwrote: +1 and agree with Dave on moving the Dojo stuff into a plugin that is hosted somewhere else and can be maintained by more people. I'm fine with deprecating it, but I'm not in favour of just dumping it at Google Code in the hope that someone will show up who wants to work on it. I'd prefer to encourage someone who does actually want to work on it to make that move if they so choose. Creating a Google Code project that is essentially still-born doesn't make sense to me. -- Martin Cooper On Sat, Dec 20, 2008 at 11:38 AM, Dave Newton newton.d...@yahoo.com wrote: --- On Sat, 12/20/08, Musachy Barroso wrote: We have talked about this Ad nauseam, and it is obvious that we don't have anyone willing to fix all the current bugs, upgrade the Dojo plugin, or write a replacement. 2.1 is around the corner and I think we should let users know that the Dojo plugin won't be maintained anymore. So my proposal is to deprecate it at once. +1 I wonder if the plugin was on Google/etc. if more people would work on it or try to upgrade the Dojo version? There's enough code in there that makes me think a straight conversion to Dojo 1.0 is non-trivial, but I haven't looked at it in awhile. I know I don't know enough Dojo to be very helpful, and my own needs aren't related to Dojo, although I still think a common interface into multiple Ajax/etc. implementations would be a good idea and would help with that aspect of things. Dave - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Dojo plugin proposal(my last one I promise)
Do we have a plugins area we can check it into? I'd be interested in helping update this project to the latest version of Dojo. Matt On Sat, Dec 20, 2008 at 11:45 AM, Martin Cooper mart...@apache.org wrote: On Sat, Dec 20, 2008 at 10:27 AM, James Holmes ja...@jamesholmes.comwrote: +1 and agree with Dave on moving the Dojo stuff into a plugin that is hosted somewhere else and can be maintained by more people. I'm fine with deprecating it, but I'm not in favour of just dumping it at Google Code in the hope that someone will show up who wants to work on it. I'd prefer to encourage someone who does actually want to work on it to make that move if they so choose. Creating a Google Code project that is essentially still-born doesn't make sense to me. -- Martin Cooper On Sat, Dec 20, 2008 at 11:38 AM, Dave Newton newton.d...@yahoo.com wrote: --- On Sat, 12/20/08, Musachy Barroso wrote: We have talked about this Ad nauseam, and it is obvious that we don't have anyone willing to fix all the current bugs, upgrade the Dojo plugin, or write a replacement. 2.1 is around the corner and I think we should let users know that the Dojo plugin won't be maintained anymore. So my proposal is to deprecate it at once. +1 I wonder if the plugin was on Google/etc. if more people would work on it or try to upgrade the Dojo version? There's enough code in there that makes me think a straight conversion to Dojo 1.0 is non-trivial, but I haven't looked at it in awhile. I know I don't know enough Dojo to be very helpful, and my own needs aren't related to Dojo, although I still think a common interface into multiple Ajax/etc. implementations would be a good idea and would help with that aspect of things. Dave - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- http://raibledesigns.com - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [PROPOSAL] Deprecate or remove Dojo plugin
It's interesting to see the list of dojo sponsors and supporters (http://dojotoolkit.org/foundation) on the one side, and the slow and always API breaking development on the other. If they had a 1.0 out a year ago, along with a stable API, it might have had a chance to become something like a standard, but this is actually not the case. Another interesting point to me is that dojo seems to focus more and more on building fully dynamic UIs with Javascript, but compared to do the same with ExtJS, GWT-Ext or GWT, using Dojo is a real pain. Dave Newton schrieb: --- On Tue, 7/22/08, Paul Benedict [EMAIL PROTECTED] wrote: Isn't Dojo the defacto ajax standard on the web? In terms of deployments I'd put money on Prototype and/or jQuery. Not that it's a large sample size, but I don't know *anybody* using Dojo outside of S2. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
My hand are full for the next couple of weeks (releases at work), but I can jump in and help from time to time. Ted, do you want get started on them? I would suggest we setup a project in the sandbox. musachy On Thu, Jul 24, 2008 at 5:40 PM, Jeromy Evans [EMAIL PROTECTED] wrote: Ted Husted wrote: I'd suggest that we put a replacement together before pulling the Dojo plugin out of the distribution (I can help). We could at least deprecate Dojo in the meantime. -T. I can help too but I'm moving house today so may be offline for a while (it takes weeks to get a new adsl2 connection in this country). I committed some minimal remote div, anchor, submit and tabbed panel tags to the yuiplugin a while ago. I'd rewrite all the javascript again to not mess with the namespace if I were using them but they may prompt some ideas. http://code.google.com/p/struts2yuiplugin/downloads/list - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Yes, I just want to get a handle on GXP first, to see if there's any synergy between the two proposals. (Trying to get the tests to run now.) On Sun, Jul 27, 2008 at 11:55 AM, Musachy Barroso [EMAIL PROTECTED] wrote: My hand are full for the next couple of weeks (releases at work), but I can jump in and help from time to time. Ted, do you want get started on them? I would suggest we setup a project in the sandbox. musachy On Thu, Jul 24, 2008 at 5:40 PM, Jeromy Evans [EMAIL PROTECTED] wrote: Ted Husted wrote: I'd suggest that we put a replacement together before pulling the Dojo plugin out of the distribution (I can help). We could at least deprecate Dojo in the meantime. -T. I can help too but I'm moving house today so may be offline for a while (it takes weeks to get a new adsl2 connection in this country). I committed some minimal remote div, anchor, submit and tabbed panel tags to the yuiplugin a while ago. I'd rewrite all the javascript again to not mess with the namespace if I were using them but they may prompt some ideas. http://code.google.com/p/struts2yuiplugin/downloads/list - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
I was thinking about all this last night. One thing that might be useful is to provide enough information to implement existing tags in raw Dojo/JavaScript--there's enough being done by the S2 components/tags that it might throw a lot of people off to write it by hand. Sort of a migration guide. Dave --- On Thu, 7/24/08, Ted Husted [EMAIL PROTECTED] wrote: From: Ted Husted [EMAIL PROTECTED] Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin To: Struts Developers List dev@struts.apache.org Date: Thursday, July 24, 2008, 3:48 PM I'd suggest that we put a replacement together before pulling the Dojo plugin out of the distribution (I can help). We could at least deprecate Dojo in the meantime. -T. On Thu, Jul 24, 2008 at 3:44 PM, Musachy Barroso [EMAIL PROTECTED] wrote: So is the consensus so far that we should have a few, very simple tags, based on another framework, and take the dojo plugin out of struts? musachy On Thu, Jul 24, 2008 at 7:20 AM, Dave Newton [EMAIL PROTECTED] wrote: One solution would be to provide the backing components for simple use-cases (like sx:a... and sx:submit... at least) and an integration with a couple JavaScript libraries, hopefully making it obvious enough that people could then implement their own back-end. With simple components updating on backing library updates is easier, and (in theory) it makes it easier to understand how users can extend or create additional tags to suit their needs. So I vote +1 for removing the existing Dojo plugin (+0 for deprecating) and +1 for creating the simplistic components and example integrations. Dave --- On Tue, 7/22/08, Musachy Barroso [EMAIL PROTECTED] wrote: From: Musachy Barroso [EMAIL PROTECTED] Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin To: Struts Developers List dev@struts.apache.org Date: Tuesday, July 22, 2008, 9:34 AM I think Dave also had a JQuery plugin somewhere, isn't that right? musachy On Tue, Jul 22, 2008 at 7:49 AM, alvins [EMAIL PROTECTED] wrote: +1 to remove. Valid points raised by all. I personally use JQuery in my daily life and have written my own tags to do these functions. I did previously look at the effort required to update the current tags to the latest dojo but it would be very time consuming and far easier to start from scratch. I think a large problem with the current dojo tags are that it is very complicated to do simple things (dojo itself is complicated relatively). With JQuery it is quite easy to do most of the things mentioned so am not sure on the benefits of tags. That said - if you made the tags powerful enough - they can be quite useful in a large number of cases - however the flipside is as you add functionality, maintainability becomes an issue. btw. If anybody is interested in some JQuery tags I could start a plugin..? -- View this message in context: http://www.nabble.com/-PROPOSAL--Deprecate-or-remove-Dojo-plugin-tp18573704p18587222.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted http://husted.com/ted/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Though I am not a struts 2 developer but I personally love Dave idea. I have now swtiched using dojo 1.1.1 and I had to write my own scripts to simiulate some of struts 2 tags [though not as neat as those tags]. With the information there, people can build on it and share it with others as well. - Original Message From: Dave Newton [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Friday, July 25, 2008 9:38:37 AM Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin I was thinking about all this last night. One thing that might be useful is to provide enough information to implement existing tags in raw Dojo/JavaScript--there's enough being done by the S2 components/tags that it might throw a lot of people off to write it by hand. Sort of a migration guide. Dave __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
So, essentially, the suggestion is this: http://wiki.apache.org/struts/AjaxStruts ...but expanded a lot :) Frank -- Frank W. Zammetti Author of Practical DWR 2 Projects and Practical JavaScript, DOM Scripting and Ajax Projects and Practical Ajax Projects With Java Technology for info: apress.com/book/search?searchterm=zammettiact=search Java Web Parts - javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! My look ma, I have a blog too! blog: zammetti.com/blog Struts Two wrote: Though I am not a struts 2 developer but I personally love Dave idea. I have now swtiched using dojo 1.1.1 and I had to write my own scripts to simiulate some of struts 2 tags [though not as neat as those tags]. With the information there, people can build on it and share it with others as well. - Original Message From: Dave Newton [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Friday, July 25, 2008 9:38:37 AM Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin I was thinking about all this last night. One thing that might be useful is to provide enough information to implement existing tags in raw Dojo/JavaScript--there's enough being done by the S2 components/tags that it might throw a lot of people off to write it by hand. Sort of a migration guide. Dave __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
One solution would be to provide the backing components for simple use-cases (like sx:a... and sx:submit... at least) and an integration with a couple JavaScript libraries, hopefully making it obvious enough that people could then implement their own back-end. With simple components updating on backing library updates is easier, and (in theory) it makes it easier to understand how users can extend or create additional tags to suit their needs. So I vote +1 for removing the existing Dojo plugin (+0 for deprecating) and +1 for creating the simplistic components and example integrations. Dave --- On Tue, 7/22/08, Musachy Barroso [EMAIL PROTECTED] wrote: From: Musachy Barroso [EMAIL PROTECTED] Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin To: Struts Developers List dev@struts.apache.org Date: Tuesday, July 22, 2008, 9:34 AM I think Dave also had a JQuery plugin somewhere, isn't that right? musachy On Tue, Jul 22, 2008 at 7:49 AM, alvins [EMAIL PROTECTED] wrote: +1 to remove. Valid points raised by all. I personally use JQuery in my daily life and have written my own tags to do these functions. I did previously look at the effort required to update the current tags to the latest dojo but it would be very time consuming and far easier to start from scratch. I think a large problem with the current dojo tags are that it is very complicated to do simple things (dojo itself is complicated relatively). With JQuery it is quite easy to do most of the things mentioned so am not sure on the benefits of tags. That said - if you made the tags powerful enough - they can be quite useful in a large number of cases - however the flipside is as you add functionality, maintainability becomes an issue. btw. If anybody is interested in some JQuery tags I could start a plugin..? -- View this message in context: http://www.nabble.com/-PROPOSAL--Deprecate-or-remove-Dojo-plugin-tp18573704p18587222.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
So is the consensus so far that we should have a few, very simple tags, based on another framework, and take the dojo plugin out of struts? musachy On Thu, Jul 24, 2008 at 7:20 AM, Dave Newton [EMAIL PROTECTED] wrote: One solution would be to provide the backing components for simple use-cases (like sx:a... and sx:submit... at least) and an integration with a couple JavaScript libraries, hopefully making it obvious enough that people could then implement their own back-end. With simple components updating on backing library updates is easier, and (in theory) it makes it easier to understand how users can extend or create additional tags to suit their needs. So I vote +1 for removing the existing Dojo plugin (+0 for deprecating) and +1 for creating the simplistic components and example integrations. Dave --- On Tue, 7/22/08, Musachy Barroso [EMAIL PROTECTED] wrote: From: Musachy Barroso [EMAIL PROTECTED] Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin To: Struts Developers List dev@struts.apache.org Date: Tuesday, July 22, 2008, 9:34 AM I think Dave also had a JQuery plugin somewhere, isn't that right? musachy On Tue, Jul 22, 2008 at 7:49 AM, alvins [EMAIL PROTECTED] wrote: +1 to remove. Valid points raised by all. I personally use JQuery in my daily life and have written my own tags to do these functions. I did previously look at the effort required to update the current tags to the latest dojo but it would be very time consuming and far easier to start from scratch. I think a large problem with the current dojo tags are that it is very complicated to do simple things (dojo itself is complicated relatively). With JQuery it is quite easy to do most of the things mentioned so am not sure on the benefits of tags. That said - if you made the tags powerful enough - they can be quite useful in a large number of cases - however the flipside is as you add functionality, maintainability becomes an issue. btw. If anybody is interested in some JQuery tags I could start a plugin..? -- View this message in context: http://www.nabble.com/-PROPOSAL--Deprecate-or-remove-Dojo-plugin-tp18573704p18587222.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
I'd suggest that we put a replacement together before pulling the Dojo plugin out of the distribution (I can help). We could at least deprecate Dojo in the meantime. -T. On Thu, Jul 24, 2008 at 3:44 PM, Musachy Barroso [EMAIL PROTECTED] wrote: So is the consensus so far that we should have a few, very simple tags, based on another framework, and take the dojo plugin out of struts? musachy On Thu, Jul 24, 2008 at 7:20 AM, Dave Newton [EMAIL PROTECTED] wrote: One solution would be to provide the backing components for simple use-cases (like sx:a... and sx:submit... at least) and an integration with a couple JavaScript libraries, hopefully making it obvious enough that people could then implement their own back-end. With simple components updating on backing library updates is easier, and (in theory) it makes it easier to understand how users can extend or create additional tags to suit their needs. So I vote +1 for removing the existing Dojo plugin (+0 for deprecating) and +1 for creating the simplistic components and example integrations. Dave --- On Tue, 7/22/08, Musachy Barroso [EMAIL PROTECTED] wrote: From: Musachy Barroso [EMAIL PROTECTED] Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin To: Struts Developers List dev@struts.apache.org Date: Tuesday, July 22, 2008, 9:34 AM I think Dave also had a JQuery plugin somewhere, isn't that right? musachy On Tue, Jul 22, 2008 at 7:49 AM, alvins [EMAIL PROTECTED] wrote: +1 to remove. Valid points raised by all. I personally use JQuery in my daily life and have written my own tags to do these functions. I did previously look at the effort required to update the current tags to the latest dojo but it would be very time consuming and far easier to start from scratch. I think a large problem with the current dojo tags are that it is very complicated to do simple things (dojo itself is complicated relatively). With JQuery it is quite easy to do most of the things mentioned so am not sure on the benefits of tags. That said - if you made the tags powerful enough - they can be quite useful in a large number of cases - however the flipside is as you add functionality, maintainability becomes an issue. btw. If anybody is interested in some JQuery tags I could start a plugin..? -- View this message in context: http://www.nabble.com/-PROPOSAL--Deprecate-or-remove-Dojo-plugin-tp18573704p18587222.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted http://husted.com/ted/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
yeah, that's what I had in mind. musachy On Thu, Jul 24, 2008 at 3:48 PM, Ted Husted [EMAIL PROTECTED] wrote: I'd suggest that we put a replacement together before pulling the Dojo plugin out of the distribution (I can help). We could at least deprecate Dojo in the meantime. -T. On Thu, Jul 24, 2008 at 3:44 PM, Musachy Barroso [EMAIL PROTECTED] wrote: So is the consensus so far that we should have a few, very simple tags, based on another framework, and take the dojo plugin out of struts? musachy On Thu, Jul 24, 2008 at 7:20 AM, Dave Newton [EMAIL PROTECTED] wrote: One solution would be to provide the backing components for simple use-cases (like sx:a... and sx:submit... at least) and an integration with a couple JavaScript libraries, hopefully making it obvious enough that people could then implement their own back-end. With simple components updating on backing library updates is easier, and (in theory) it makes it easier to understand how users can extend or create additional tags to suit their needs. So I vote +1 for removing the existing Dojo plugin (+0 for deprecating) and +1 for creating the simplistic components and example integrations. Dave --- On Tue, 7/22/08, Musachy Barroso [EMAIL PROTECTED] wrote: From: Musachy Barroso [EMAIL PROTECTED] Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin To: Struts Developers List dev@struts.apache.org Date: Tuesday, July 22, 2008, 9:34 AM I think Dave also had a JQuery plugin somewhere, isn't that right? musachy On Tue, Jul 22, 2008 at 7:49 AM, alvins [EMAIL PROTECTED] wrote: +1 to remove. Valid points raised by all. I personally use JQuery in my daily life and have written my own tags to do these functions. I did previously look at the effort required to update the current tags to the latest dojo but it would be very time consuming and far easier to start from scratch. I think a large problem with the current dojo tags are that it is very complicated to do simple things (dojo itself is complicated relatively). With JQuery it is quite easy to do most of the things mentioned so am not sure on the benefits of tags. That said - if you made the tags powerful enough - they can be quite useful in a large number of cases - however the flipside is as you add functionality, maintainability becomes an issue. btw. If anybody is interested in some JQuery tags I could start a plugin..? -- View this message in context: http://www.nabble.com/-PROPOSAL--Deprecate-or-remove-Dojo-plugin-tp18573704p18587222.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted http://husted.com/ted/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Ted Husted wrote: I'd suggest that we put a replacement together before pulling the Dojo plugin out of the distribution (I can help). We could at least deprecate Dojo in the meantime. -T. I can help too but I'm moving house today so may be offline for a while (it takes weeks to get a new adsl2 connection in this country). I committed some minimal remote div, anchor, submit and tabbed panel tags to the yuiplugin a while ago. I'd rewrite all the javascript again to not mess with the namespace if I were using them but they may prompt some ideas. http://code.google.com/p/struts2yuiplugin/downloads/list - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
ExtJS is a big no-no in my book. To use it in a commercial project you need to buy a license, which would put off a lot of commercial customers. Personally I use YUI for two reasons; 1) It's easy to separate out and include only the parts I need in my webapp so I don't end up with war bloat. 2) The mailing lists seemed reasonably active. Al. Martin Cooper wrote: On Tue, Jul 22, 2008 at 3:57 PM, Ted Husted [EMAIL PROTECTED] wrote: Dojo seems to get the most lip service, but I've seen persistence reports that YUI has broader acceptance. The thing is, it depends a whole lot on what you are doing with it. For example, the people I know who are developing rich client-side apps with JavaScript are using Ext JS or Dojo. None of them are using YUI because YUI simply isn't appropriate, or complete enough, for that kind of usage. It's perfectly fine, though, if what you want is to add some AJAXy capabilities to a more traditional web app. As another example, there are certainly plenty of people building point applications with Prototype and its friends, but if you're building something that needs to be extensible and include components from elsewhere, you almost certainly don't want to be using a framework that messes with core JavaScript types. -- Martin Cooper -Ted. On Tue, Jul 22, 2008 at 4:48 PM, Dave Newton [EMAIL PROTECTED] wrote: --- On Tue, 7/22/08, Paul Benedict [EMAIL PROTECTED] wrote: Isn't Dojo the defacto ajax standard on the web? In terms of deployments I'd put money on Prototype and/or jQuery. Not that it's a large sample size, but I don't know *anybody* using Dojo outside of S2. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted http://husted.com/ted/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Paul Benedict wrote: Dojo 0.4.3 is old :-) I didn't know that. No one wants to move it to 1.x or wherever they are now? Paul Many have tried. In general, the effort doesn't justify the result. ie. you put a lot of effort writing new templates and tags that predominately wrap and constrain dojo's own markup. This result is tags for widgets less capable than using dojo markup directly. The benefit is a user can use s:tabbedPanel instead of div dojoType=TabContainer, but if they use the latter they can receive all the support of the dojo user community. It's difficult to justify the effort for a sub-optimal solution that's going to generate more support questions: eg. how to I select a tab a button press, how to i change colour of tabs, why can't i nest tabs, why won't the back button remember the content of the last tab, etc, etc, etc, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
If this is the case, I would not recommend we create an ajax plugin, but call it the ajax-yui plugin or a ajax-whatever plugin so that people can use different ajax implementations. Paul On Wed, Jul 23, 2008 at 1:40 AM, Jeromy Evans [EMAIL PROTECTED] wrote: Paul Benedict wrote: Dojo 0.4.3 is old :-) I didn't know that. No one wants to move it to 1.x or wherever they are now? Paul Many have tried. In general, the effort doesn't justify the result. ie. you put a lot of effort writing new templates and tags that predominately wrap and constrain dojo's own markup. This result is tags for widgets less capable than using dojo markup directly. The benefit is a user can use s:tabbedPanel instead of div dojoType=TabContainer, but if they use the latter they can receive all the support of the dojo user community. It's difficult to justify the effort for a sub-optimal solution that's going to generate more support questions: eg. how to I select a tab a button press, how to i change colour of tabs, why can't i nest tabs, why won't the back button remember the content of the last tab, etc, etc, etc, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Having a simple taglib-based approach to do some of the more common AJAX-y things, maybe some widgets here and there too, means that Java developers can leverage their existing skills without having to take the plunge into heavy client-side development, which I can say from the experience of mentoring some junior-level teams can be a very difficult hill to climb, regardless of what whiz-bang library you choose to use to try and make it easier. The very nature of Javascript, for many Java developers, is a difficult leap to make. Today's whiz-bang libraries make things dead simple to perform ajax requests. For instance, with jQuery to get the contents of a url and place it in a div element #content: $(#content).load(url); I guess I fail to see how even junior-level team members would have a difficult learning curve with this. Learning jQuery quickly is easy to do and is much of the appeal. And as others have mentioned, the libraries such as jQuery have a great user base, with much to offer in terms of support. Just checkout the #jquery freenode irc channel, for instance. Part of being a developer is learning new technologies, and if those technologies are easy to use and powerful, then that's where the ROI really pays off. We should be nudging people in these directions with better documentation on how to best integrate with existing libraries. This would be a far better place to focus energy, imo. Bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
I think that ignores the underlying complexity of developing complex RIAs today. I would take any of the apps I've developed on the job over the past 5+ years and put them up against any out there in terms of complexity... when I talk to other developers about what they're doing it's nearly always the case that what they describe is orders of magnitude less complex than some of the project I've been involved in. And all the while I've had to mentor teams to get them up to speed so they could develop these applications with me. I'm not saying any of that to try and be impressive, I'm saying that so I can then say this: the paradigm shift of doing heavy client-side AJAX-based RIA development when you are used to doing the classic server-heavy model of web development isn't as simple as choosing a good library and doing some simple calls as you show. Things just aren't that simple once you move beyond level 1, so to speak :) Now, I suppose you could say that then a taglib approach is quickly going to become not up to the task either, which I'd agree with. You could further say that if that's the case, why not just start by learning a good library and forget about tags. There's some degree of correctness in that I think. But I've seen it time and time again: good Java developers who transition to a client-side model just seem to have trouble getting it, and whether you use tags or a library directly it doesn't seem to matter. Things that I, and I suspect you, would take for granted seem difficult for them to comprehend... things like following the applications' flow when things are moving from server to client, timing issues, dealing with security, not to mention the still less-than-optimal debugging capabilities available. But what I've *also* seen time and time again is that a tag-based approached is easier for them to wrap their brains around initially than using a library directly because it's closer to what they already know. Think about all you're taking for granted when you write $(#content).load(url); ... you assume they know about the DOM, that they understand the concept of a URL's response not overwriting the entire page... and what does that call look like when you have to deal with error callbacks? And timeout conditions? And security constraints? Is it still as simple as just that? If so then jQuery is more than good, it's freakin' miraclulous! Having a taglib, at least initially, that keeps those details away from them is a good thing... yes, they'll quickly outgrow them, but then they'll quickly come to the point you're at and want to use the libraries directly, and will at that point no longer be the huge mental leap that it was at the start. Frank -- Frank W. Zammetti Author of Practical DWR 2 Projects and Practical JavaScript, DOM Scripting and Ajax Projects and Practical Ajax Projects With Java Technology for info: apress.com/book/search?searchterm=zammettiact=search Java Web Parts - javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! My look ma, I have a blog too! blog: zammetti.com/blog Bob Tiernay wrote: Having a simple taglib-based approach to do some of the more common AJAX-y things, maybe some widgets here and there too, means that Java developers can leverage their existing skills without having to take the plunge into heavy client-side development, which I can say from the experience of mentoring some junior-level teams can be a very difficult hill to climb, regardless of what whiz-bang library you choose to use to try and make it easier. The very nature of Javascript, for many Java developers, is a difficult leap to make. Today's whiz-bang libraries make things dead simple to perform ajax requests. For instance, with jQuery to get the contents of a url and place it in a div element #content: $(#content).load(url); I guess I fail to see how even junior-level team members would have a difficult learning curve with this. Learning jQuery quickly is easy to do and is much of the appeal. And as others have mentioned, the libraries such as jQuery have a great user base, with much to offer in terms of support. Just checkout the #jquery freenode irc channel, for instance. Part of being a developer is learning new technologies, and if those technologies are easy to use and powerful, then that's where the ROI really pays off. We should be nudging people in these directions with better documentation on how to best integrate with existing libraries. This would be a far better place to focus energy, imo. Bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [struts-dev] [PROPOSAL] Deprecate or remove Dojo plugin
Frank W. Zammetti wrote: Think about all you're taking for granted when you write $(#content).load(url); It largely boils down to differences between how developers think the dom/language works and how it really works. The time it takes to have your developers watch Crockford's three lectures is *well* worth it. -Dale - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
+1 to remove. Valid points raised by all. I personally use JQuery in my daily life and have written my own tags to do these functions. I did previously look at the effort required to update the current tags to the latest dojo but it would be very time consuming and far easier to start from scratch. I think a large problem with the current dojo tags are that it is very complicated to do simple things (dojo itself is complicated relatively). With JQuery it is quite easy to do most of the things mentioned so am not sure on the benefits of tags. That said - if you made the tags powerful enough - they can be quite useful in a large number of cases - however the flipside is as you add functionality, maintainability becomes an issue. btw. If anybody is interested in some JQuery tags I could start a plugin..? -- View this message in context: http://www.nabble.com/-PROPOSAL--Deprecate-or-remove-Dojo-plugin-tp18573704p18587222.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
I think Dave also had a JQuery plugin somewhere, isn't that right? musachy On Tue, Jul 22, 2008 at 7:49 AM, alvins [EMAIL PROTECTED] wrote: +1 to remove. Valid points raised by all. I personally use JQuery in my daily life and have written my own tags to do these functions. I did previously look at the effort required to update the current tags to the latest dojo but it would be very time consuming and far easier to start from scratch. I think a large problem with the current dojo tags are that it is very complicated to do simple things (dojo itself is complicated relatively). With JQuery it is quite easy to do most of the things mentioned so am not sure on the benefits of tags. That said - if you made the tags powerful enough - they can be quite useful in a large number of cases - however the flipside is as you add functionality, maintainability becomes an issue. btw. If anybody is interested in some JQuery tags I could start a plugin..? -- View this message in context: http://www.nabble.com/-PROPOSAL--Deprecate-or-remove-Dojo-plugin-tp18573704p18587222.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
You would have to start the tags from scratch. musachy On Tue, Jul 22, 2008 at 1:56 AM, Lukasz Lenart [EMAIL PROTECTED] wrote: Hi, Disregarding what path we take, I think it is fairly obvious that the Dojo plugin will end up unmaintained, that's why we should users know that we do not plan on upgrading from 0.4.3. I'm just wondering, what have to be done to migrate to the latest version of Dojo toolkit? I'm not using S2 Ajax tags at all (for me DWR is enough ;-) and maybe that's the good point to start learnig them and also support future development? Regards -- Lukasz http://www.lenart.org.pl/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
You would have to start the tags from scratch. Very optimistic ;-) Maybe than, the jQuery is a better option to start from scratch.. Regards -- Lukasz http://www.lenart.org.pl/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
--- On Tue, 7/22/08, Musachy Barroso [EMAIL PROTECTED] wrote: I think Dave also had a JQuery plugin somewhere, isn't that right? I can neither confirm nor deny the existence of said project. I started to convert the Dojo tags to jQuery and stopped again pretty quickly; I only had s:a.../ with a single target. I started w/ the Dojo tag code, as I had wanted to make them as compatible as practical w/ the Dojo tags. My project then did everything via raw jQuery anyway, so they got put on hold. To answer somebody else's question, I gathered JavaScript in a couple of different ways across projects, including keeping it in a ThreadLocal String then spitting it out with a tag or appending it via an interceptor (not sure that was HTML-compliant though). I agree that having things like s:a... and an Ajax submit would be pretty nice--make the easy stuff drop-dead simple. Anything beyond that I'm less sure, and tying S2 itself to a particular client-side framework always worried me a bit. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Isn't Dojo the defacto ajax standard on the web? I know there is no such certification :-) but why deprecate something so popular? If anything, I would spin off the project into Codehaus and let the world continue writing it. Paul On Tue, Jul 22, 2008 at 10:18 AM, Dave Newton [EMAIL PROTECTED] wrote: --- On Tue, 7/22/08, Musachy Barroso [EMAIL PROTECTED] wrote: I think Dave also had a JQuery plugin somewhere, isn't that right? I can neither confirm nor deny the existence of said project. I started to convert the Dojo tags to jQuery and stopped again pretty quickly; I only had s:a.../ with a single target. I started w/ the Dojo tag code, as I had wanted to make them as compatible as practical w/ the Dojo tags. My project then did everything via raw jQuery anyway, so they got put on hold. To answer somebody else's question, I gathered JavaScript in a couple of different ways across projects, including keeping it in a ThreadLocal String then spitting it out with a tag or appending it via an interceptor (not sure that was HTML-compliant though). I agree that having things like s:a... and an Ajax submit would be pretty nice--make the easy stuff drop-dead simple. Anything beyond that I'm less sure, and tying S2 itself to a particular client-side framework always worried me a bit. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
--- On Tue, 7/22/08, Paul Benedict [EMAIL PROTECTED] wrote: Isn't Dojo the defacto ajax standard on the web? In terms of deployments I'd put money on Prototype and/or jQuery. Not that it's a large sample size, but I don't know *anybody* using Dojo outside of S2. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Tapestry is using Dojo too [1]. I'm not developing any AJAX application so my comments could be somewhat biased, but either the dojo toolkit is used or not in upcoming S2 versions, I think it is still worthwhile providing easy to use, good looking javascript/dhtml widgets to quickly solve form input problems for most applications. Input validation could become improved with more sophisticated widgets too. Also, the default packaging/integration of Dojo with S2 was known to have serious performance problems, lets not lose focus on this issue too. [1] http://tapestry.apache.org/tapestry4.1/ 2008/7/22 Dave Newton [EMAIL PROTECTED]: --- On Tue, 7/22/08, Paul Benedict [EMAIL PROTECTED] wrote: Isn't Dojo the defacto ajax standard on the web? In terms of deployments I'd put money on Prototype and/or jQuery. Not that it's a large sample size, but I don't know *anybody* using Dojo outside of S2. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Dojo seems to get the most lip service, but I've seen persistence reports that YUI has broader acceptance. -Ted. On Tue, Jul 22, 2008 at 4:48 PM, Dave Newton [EMAIL PROTECTED] wrote: --- On Tue, 7/22/08, Paul Benedict [EMAIL PROTECTED] wrote: Isn't Dojo the defacto ajax standard on the web? In terms of deployments I'd put money on Prototype and/or jQuery. Not that it's a large sample size, but I don't know *anybody* using Dojo outside of S2. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted http://husted.com/ted/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
+1 for Musachy's suggestion, and I'm also at a point where I could help with the implementation. As to Ajax-enabling some of the tags, there are several tag-based Ajax libraries out there that we could look at embedding or emulating. In this case, we wouldn't be adopting a general-purpose Ajax library, but special-purpose scripts designed to be used with tags. * Ajax Tags - http://ajaxtags.sourceforge.net * Prize Tags - http://jenkov.com/prizetags/index.html * JSON-taglib - http://json-taglib.sourceforge.net/ * AjaxParts Taglib - http://javawebparts.sourceforge.net/ Has anyone had good or bad experiences with tag-based libraries like these? -Ted. On Mon, Jul 21, 2008 at 11:33 PM, Musachy Barroso [EMAIL PROTECTED] wrote: I am not sure about that approach. On one hand it is very strutsish, in that is supports many ways of doing the same thing, and provides ways to extend what is provided, on the other hand, I think we should learn from other frameworks and just don't give users that many options, for they can be confusing, and frustrating when there is not enough documentation. Looking at ajax, and the ajax tags I think we have 2 kind of users: the power users, they won't use the ajax tag at all, unless they are doing something extremely simple. the beginners: they will use the ajax tags out of the box. When the beginners need to do something that is not provided by the tags out of the box, they start hacking away, and end up dumping the tags. So our target is the beginners, and they don't want customization, they just want to drop a few tags on their jsps and get it working. Based on that, I think we should either: don't provide any ajax tags at all, or just provide a very limited set of tags (like what Jeromy listed) with very little functionality to cover simple use cases, and use a reliable and simple framework for the implementation. Disregarding what path we take, I think it is fairly obvious that the Dojo plugin will end up unmaintained, that's why we should users know that we do not plan on upgrading from 0.4.3. musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
What does anyone think about donating the dojo plugin to codehaus? I think it's a better idea than letting the code go stale. You could even try donating to the dojotoolkit project. Paul On Tue, Jul 22, 2008 at 6:18 PM, Ted Husted [EMAIL PROTECTED] wrote: +1 for Musachy's suggestion, and I'm also at a point where I could help with the implementation. As to Ajax-enabling some of the tags, there are several tag-based Ajax libraries out there that we could look at embedding or emulating. In this case, we wouldn't be adopting a general-purpose Ajax library, but special-purpose scripts designed to be used with tags. * Ajax Tags - http://ajaxtags.sourceforge.net * Prize Tags - http://jenkov.com/prizetags/index.html * JSON-taglib - http://json-taglib.sourceforge.net/ * AjaxParts Taglib - http://javawebparts.sourceforge.net/ Has anyone had good or bad experiences with tag-based libraries like these? -Ted. On Mon, Jul 21, 2008 at 11:33 PM, Musachy Barroso [EMAIL PROTECTED] wrote: I am not sure about that approach. On one hand it is very strutsish, in that is supports many ways of doing the same thing, and provides ways to extend what is provided, on the other hand, I think we should learn from other frameworks and just don't give users that many options, for they can be confusing, and frustrating when there is not enough documentation. Looking at ajax, and the ajax tags I think we have 2 kind of users: the power users, they won't use the ajax tag at all, unless they are doing something extremely simple. the beginners: they will use the ajax tags out of the box. When the beginners need to do something that is not provided by the tags out of the box, they start hacking away, and end up dumping the tags. So our target is the beginners, and they don't want customization, they just want to drop a few tags on their jsps and get it working. Based on that, I think we should either: don't provide any ajax tags at all, or just provide a very limited set of tags (like what Jeromy listed) with very little functionality to cover simple use cases, and use a reliable and simple framework for the implementation. Disregarding what path we take, I think it is fairly obvious that the Dojo plugin will end up unmaintained, that's why we should users know that we do not plan on upgrading from 0.4.3. musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
On Tue, Jul 22, 2008 at 3:57 PM, Ted Husted [EMAIL PROTECTED] wrote: Dojo seems to get the most lip service, but I've seen persistence reports that YUI has broader acceptance. The thing is, it depends a whole lot on what you are doing with it. For example, the people I know who are developing rich client-side apps with JavaScript are using Ext JS or Dojo. None of them are using YUI because YUI simply isn't appropriate, or complete enough, for that kind of usage. It's perfectly fine, though, if what you want is to add some AJAXy capabilities to a more traditional web app. As another example, there are certainly plenty of people building point applications with Prototype and its friends, but if you're building something that needs to be extensible and include components from elsewhere, you almost certainly don't want to be using a framework that messes with core JavaScript types. -- Martin Cooper -Ted. On Tue, Jul 22, 2008 at 4:48 PM, Dave Newton [EMAIL PROTECTED] wrote: --- On Tue, 7/22/08, Paul Benedict [EMAIL PROTECTED] wrote: Isn't Dojo the defacto ajax standard on the web? In terms of deployments I'd put money on Prototype and/or jQuery. Not that it's a large sample size, but I don't know *anybody* using Dojo outside of S2. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted http://husted.com/ted/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
That would be totally fine, but I doubt anyone would be interested in Dojo 0.4.3 at this point. musachy On Tue, Jul 22, 2008 at 7:29 PM, Paul Benedict [EMAIL PROTECTED] wrote: What does anyone think about donating the dojo plugin to codehaus? I think it's a better idea than letting the code go stale. You could even try donating to the dojotoolkit project. Paul On Tue, Jul 22, 2008 at 6:18 PM, Ted Husted [EMAIL PROTECTED] wrote: +1 for Musachy's suggestion, and I'm also at a point where I could help with the implementation. As to Ajax-enabling some of the tags, there are several tag-based Ajax libraries out there that we could look at embedding or emulating. In this case, we wouldn't be adopting a general-purpose Ajax library, but special-purpose scripts designed to be used with tags. * Ajax Tags - http://ajaxtags.sourceforge.net * Prize Tags - http://jenkov.com/prizetags/index.html * JSON-taglib - http://json-taglib.sourceforge.net/ * AjaxParts Taglib - http://javawebparts.sourceforge.net/ Has anyone had good or bad experiences with tag-based libraries like these? -Ted. On Mon, Jul 21, 2008 at 11:33 PM, Musachy Barroso [EMAIL PROTECTED] wrote: I am not sure about that approach. On one hand it is very strutsish, in that is supports many ways of doing the same thing, and provides ways to extend what is provided, on the other hand, I think we should learn from other frameworks and just don't give users that many options, for they can be confusing, and frustrating when there is not enough documentation. Looking at ajax, and the ajax tags I think we have 2 kind of users: the power users, they won't use the ajax tag at all, unless they are doing something extremely simple. the beginners: they will use the ajax tags out of the box. When the beginners need to do something that is not provided by the tags out of the box, they start hacking away, and end up dumping the tags. So our target is the beginners, and they don't want customization, they just want to drop a few tags on their jsps and get it working. Based on that, I think we should either: don't provide any ajax tags at all, or just provide a very limited set of tags (like what Jeromy listed) with very little functionality to cover simple use cases, and use a reliable and simple framework for the implementation. Disregarding what path we take, I think it is fairly obvious that the Dojo plugin will end up unmaintained, that's why we should users know that we do not plan on upgrading from 0.4.3. musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
What does anyone think about donating the dojo plugin to codehaus? I think it's a better idea than letting the code go stale. You could even try donating to the dojotoolkit project. I am not sure what you mean by donating it to codehaus. If someone wants to support the plugin he may do so under the terms of the APLv2. The actual problem is that there is nobody who thinks that it is worth the work. Wether the code stales at codehaus or apache.. what is the difference? Piero - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Has anyone really looked into a comparison between using a taglib vs. a raw javascript framework across these dimensions: 1. Performance (page load time / bandwidth) (think s:head across most pages) 2. Expressiveness 3. Unobtrusiveness 4. Maintainability 5. Understandability 6. Modularity My experience has been that all of these are enhanced when using the later. I really don't see why even a taglib is even on the table. Perhaps I'm missing something here, but what is to be gained by unifying javascript libraries with a taglib façade? This smells of commons logging. -- From: Martin Cooper [EMAIL PROTECTED] Sent: Tuesday, July 22, 2008 7:36 PM To: Struts Developers List dev@struts.apache.org Cc: [EMAIL PROTECTED] Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin On Tue, Jul 22, 2008 at 3:57 PM, Ted Husted [EMAIL PROTECTED] wrote: Dojo seems to get the most lip service, but I've seen persistence reports that YUI has broader acceptance. The thing is, it depends a whole lot on what you are doing with it. For example, the people I know who are developing rich client-side apps with JavaScript are using Ext JS or Dojo. None of them are using YUI because YUI simply isn't appropriate, or complete enough, for that kind of usage. It's perfectly fine, though, if what you want is to add some AJAXy capabilities to a more traditional web app. As another example, there are certainly plenty of people building point applications with Prototype and its friends, but if you're building something that needs to be extensible and include components from elsewhere, you almost certainly don't want to be using a framework that messes with core JavaScript types. -- Martin Cooper -Ted. On Tue, Jul 22, 2008 at 4:48 PM, Dave Newton [EMAIL PROTECTED] wrote: --- On Tue, 7/22/08, Paul Benedict [EMAIL PROTECTED] wrote: Isn't Dojo the defacto ajax standard on the web? In terms of deployments I'd put money on Prototype and/or jQuery. Not that it's a large sample size, but I don't know *anybody* using Dojo outside of S2. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted http://husted.com/ted/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Has anyone had good or bad experiences with tag-based libraries like these? I used to maintain Ajax Tags, but I thought there were too many frameworks already and gave it away :). I haven't used any of the other ones. musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
On Tue, Jul 22, 2008 at 4:44 PM, Bob Tiernay [EMAIL PROTECTED] wrote: Has anyone really looked into a comparison between using a taglib vs. a raw javascript framework across these dimensions: Hey, don't look at me - I gave up using server-side rendering years ago! ;-) -- Martin Cooper 1. Performance (page load time / bandwidth) (think s:head across most pages) 2. Expressiveness 3. Unobtrusiveness 4. Maintainability 5. Understandability 6. Modularity My experience has been that all of these are enhanced when using the later. I really don't see why even a taglib is even on the table. Perhaps I'm missing something here, but what is to be gained by unifying javascript libraries with a taglib façade? This smells of commons logging. -- From: Martin Cooper [EMAIL PROTECTED] Sent: Tuesday, July 22, 2008 7:36 PM To: Struts Developers List dev@struts.apache.org Cc: [EMAIL PROTECTED] Subject: Re: [PROPOSAL] Deprecate or remove Dojo plugin On Tue, Jul 22, 2008 at 3:57 PM, Ted Husted [EMAIL PROTECTED] wrote: Dojo seems to get the most lip service, but I've seen persistence reports that YUI has broader acceptance. The thing is, it depends a whole lot on what you are doing with it. For example, the people I know who are developing rich client-side apps with JavaScript are using Ext JS or Dojo. None of them are using YUI because YUI simply isn't appropriate, or complete enough, for that kind of usage. It's perfectly fine, though, if what you want is to add some AJAXy capabilities to a more traditional web app. As another example, there are certainly plenty of people building point applications with Prototype and its friends, but if you're building something that needs to be extensible and include components from elsewhere, you almost certainly don't want to be using a framework that messes with core JavaScript types. -- Martin Cooper -Ted. On Tue, Jul 22, 2008 at 4:48 PM, Dave Newton [EMAIL PROTECTED] wrote: --- On Tue, 7/22/08, Paul Benedict [EMAIL PROTECTED] wrote: Isn't Dojo the defacto ajax standard on the web? In terms of deployments I'd put money on Prototype and/or jQuery. Not that it's a large sample size, but I don't know *anybody* using Dojo outside of S2. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted http://husted.com/ted/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
--- On Tue, 7/22/08, Bob Tiernay [EMAIL PROTECTED] wrote: I really don't see why even a taglib is even on the table. I think the issue was a let's make some of this cool stuff really easy for the people that don't know JavaScript. To steal the phrase: now you have two problems. I'm not sure it's worth keeping the Dojo tags as part of S2, particularly since client-side stuff varies so wildly across companies (even *within* companies), developers, projects, etc. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
On Tue, Jul 22, 2008 at 8:19 PM, Dave Newton [EMAIL PROTECTED] wrote: --- On Tue, 7/22/08, Bob Tiernay [EMAIL PROTECTED] wrote: I really don't see why even a taglib is even on the table. I think the issue was a let's make some of this cool stuff really easy for the people that don't know JavaScript. True. There are a lot of applications that don't need or want a full client-side front-end. For a lot of folks, full-page refresh is just fine most of the time, but there is still a key place or three where sprinkling in a little Ajax magic can make a big difference, without making any sweeping UI changes. We don't need to hookup an entire general -purpose Ajax framework for that. We just need to go in with a scalpel and add some simple Ajax scripts where they will do the most good. Of course, if an application has already elected to use a full clientde front-end, anything we do with the tags would be irrelevant. -Ted. To steal the phrase: now you have two problems. I'm not sure it's worth keeping the Dojo tags as part of S2, particularly since client-side stuff varies so wildly across companies (even *within* companies), developers, projects, etc. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted http://husted.com/ted/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
: they will use the ajax tags out of the box. When the beginners need to do something that is not provided by the tags out of the box, they start hacking away, and end up dumping the tags. So our target is the beginners, and they don't want customization, they just want to drop a few tags on their jsps and get it working. Based on that, I think we should either: don't provide any ajax tags at all, or just provide a very limited set of tags (like what Jeromy listed) with very little functionality to cover simple use cases, and use a reliable and simple framework for the implementation. Disregarding what path we take, I think it is fairly obvious that the Dojo plugin will end up unmaintained, that's why we should users know that we do not plan on upgrading from 0.4.3. musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
there is not enough documentation. Looking at ajax, and the ajax tags I think we have 2 kind of users: the power users, they won't use the ajax tag at all, unless they are doing something extremely simple. the beginners: they will use the ajax tags out of the box. When the beginners need to do something that is not provided by the tags out of the box, they start hacking away, and end up dumping the tags. So our target is the beginners, and they don't want customization, they just want to drop a few tags on their jsps and get it working. Based on that, I think we should either: don't provide any ajax tags at all, or just provide a very limited set of tags (like what Jeromy listed) with very little functionality to cover simple use cases, and use a reliable and simple framework for the implementation. Disregarding what path we take, I think it is fairly obvious that the Dojo plugin will end up unmaintained, that's why we should users know that we do not plan on upgrading from 0.4.3. musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PROPOSAL] Deprecate or remove Dojo plugin
With all the problems/questions and time that the ajax tags have caused, and not having any takers on porting to the latest Dojo release. I would propose to deprecate, or even remove the Dojo plugin, or at least let users know that we will not be upgrading to a newer Dojo version anytime soon. I still like the idea of some *very* basic tags to cover the most simple use cases, but I think Dojo was not the right tool for the job. We haven't released 2.1 yet, so this would be a perfect time to do this, as it is already on its own plugin. musachy -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
+1. I'd rather us not lose the AJAX tags, but rather implement with something more lightweight like Prototype, jQuery, or similar that's much easier to work with. On Mon, Jul 21, 2008 at 1:35 PM, Musachy Barroso [EMAIL PROTECTED] wrote: With all the problems/questions and time that the ajax tags have caused, and not having any takers on porting to the latest Dojo release. I would propose to deprecate, or even remove the Dojo plugin, or at least let users know that we will not be upgrading to a newer Dojo version anytime soon. I still like the idea of some *very* basic tags to cover the most simple use cases, but I think Dojo was not the right tool for the job. We haven't released 2.1 yet, so this would be a perfect time to do this, as it is already on its own plugin. musachy -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [PROPOSAL] Deprecate or remove Dojo plugin
-Original Message- From: Musachy Barroso [mailto:[EMAIL PROTECTED] Sent: Monday, July 21, 2008 10:36 AM To: Struts Developers List Subject: [PROPOSAL] Deprecate or remove Dojo plugin With all the problems/questions and time that the ajax tags have caused, and not having any takers on porting to the latest Dojo release. I would propose to deprecate, or even remove the Dojo plugin, or at least let users know that we will not be upgrading to a newer Dojo version anytime soon. I still like the idea of some *very* basic tags to cover the most simple use cases, but I think Dojo was not the right tool for the job. I would certainly agree with this, but I think it's important to emphasize that the solution is NOT to find a different framework or version to integrate into Struts. The best solution is to visualize how to facilitate integrating any capable JavaScript framework into a Struts-using application. That does not mean embedding a JavaScript framework into the Struts distribution. To a large extent, the biggest part of this solution is documentation, but it's possible that some other changes to the framework could make this easier. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Musachy Barroso wrote: With all the problems/questions and time that the ajax tags have caused, and not having any takers on porting to the latest Dojo release. I would propose to deprecate, or even remove the Dojo plugin, or at least let users know that we will not be upgrading to a newer Dojo version anytime soon. I still like the idea of some *very* basic tags to cover the most simple use cases, but I think Dojo was not the right tool for the job. This is a BIG call. Although I share the sentiment, the ajax tags are an often-stated great feature of S2. At least, that's what users comment until they need to do something sophisticated with the underlying library. I suggest an approach which is consistent with the above, should be in line with your thoughts Musachy and may even make Martin C happy: There are some core tags that must be provided/maintained by S2: - remote div - async submit of a form, targetting a div - async get (anchor tag), targetting a div We'd still supply those as tags as a minimum in say an ajax plugin. Rather than bundle ajax libraries with S2, we would only bundle a few templates for integration of those tags with common libraries. We use the existing theme's for this: eg. s:submit theme=dojo href=form.action/ s:submit theme=yui href=form.action/ s:submit theme=jquery href=form.action/ The templates implement the markup or inline javascript for a default/reference implementation. The template for the s:head tag would include the default scripts to setup the library. s:head theme=dojo will setup the bundled Dojo during the deprecated period s:head theme=jquery will include jquery dependencies from a default/overridden location (supplied by user). The s:head tag would be optional, but the user will be responsible for ensuring the library is available. Library-specific extensions for the tags would be specified via dynamic attributes only. All other dojo widget tags would be deprecated (tabbedPanel, autocompleter). NOTE: Ajax validation and client-side validation also deserve some discussion later. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
I am not sure about that approach. On one hand it is very strutsish, in that is supports many ways of doing the same thing, and provides ways to extend what is provided, on the other hand, I think we should learn from other frameworks and just don't give users that many options, for they can be confusing, and frustrating when there is not enough documentation. Looking at ajax, and the ajax tags I think we have 2 kind of users: the power users, they won't use the ajax tag at all, unless they are doing something extremely simple. the beginners: they will use the ajax tags out of the box. When the beginners need to do something that is not provided by the tags out of the box, they start hacking away, and end up dumping the tags. So our target is the beginners, and they don't want customization, they just want to drop a few tags on their jsps and get it working. Based on that, I think we should either: don't provide any ajax tags at all, or just provide a very limited set of tags (like what Jeromy listed) with very little functionality to cover simple use cases, and use a reliable and simple framework for the implementation. Disregarding what path we take, I think it is fairly obvious that the Dojo plugin will end up unmaintained, that's why we should users know that we do not plan on upgrading from 0.4.3. musachy On Mon, Jul 21, 2008 at 10:24 PM, Jeromy Evans [EMAIL PROTECTED] wrote: Musachy Barroso wrote: With all the problems/questions and time that the ajax tags have caused, and not having any takers on porting to the latest Dojo release. I would propose to deprecate, or even remove the Dojo plugin, or at least let users know that we will not be upgrading to a newer Dojo version anytime soon. I still like the idea of some *very* basic tags to cover the most simple use cases, but I think Dojo was not the right tool for the job. This is a BIG call. Although I share the sentiment, the ajax tags are an often-stated great feature of S2. At least, that's what users comment until they need to do something sophisticated with the underlying library. I suggest an approach which is consistent with the above, should be in line with your thoughts Musachy and may even make Martin C happy: There are some core tags that must be provided/maintained by S2: - remote div - async submit of a form, targetting a div - async get (anchor tag), targetting a div We'd still supply those as tags as a minimum in say an ajax plugin. Rather than bundle ajax libraries with S2, we would only bundle a few templates for integration of those tags with common libraries. We use the existing theme's for this: eg. s:submit theme=dojo href=form.action/ s:submit theme=yui href=form.action/ s:submit theme=jquery href=form.action/ The templates implement the markup or inline javascript for a default/reference implementation. The template for the s:head tag would include the default scripts to setup the library. s:head theme=dojo will setup the bundled Dojo during the deprecated period s:head theme=jquery will include jquery dependencies from a default/overridden location (supplied by user). The s:head tag would be optional, but the user will be responsible for ensuring the library is available. Library-specific extensions for the tags would be specified via dynamic attributes only. All other dojo widget tags would be deprecated (tabbedPanel, autocompleter). NOTE: Ajax validation and client-side validation also deserve some discussion later. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Deprecate or remove Dojo plugin
Hi, Disregarding what path we take, I think it is fairly obvious that the Dojo plugin will end up unmaintained, that's why we should users know that we do not plan on upgrading from 0.4.3. I'm just wondering, what have to be done to migrate to the latest version of Dojo toolkit? I'm not using S2 Ajax tags at all (for me DWR is enough ;-) and maybe that's the good point to start learnig them and also support future development? Regards -- Lukasz http://www.lenart.org.pl/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
dojo plugin
Hello All, Is there anyone that is trying to port the struts2-dojo-plugin from dojo 2.4.x to 1.1.1? I've downloaded de source, and will be trying to figure which struts widgets don't play well with the new dojo, but to be honest, i'm feel a bit lost in all that code, specially in the js stuff. From the posts i've seen musachy i think takes care of that; may be we could coodinate the work? Any pointer would be appreciated. Thanks Si quieres ser más positivo, pierde un electrón Miguel Ruiz Velasco S. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dojo plugin
Well, I have started 3 times so far, and quit each time. In my very own humble opinion I don't think it is worth all the effort. Our javascript code consists of wrappers around the dojo widgets to either fix bugs, or add functionality (like topics). Feel free to ask questions about the current implementation. musachy On Thu, Jul 10, 2008 at 12:20 PM, Miguel [EMAIL PROTECTED] wrote: Hello All, Is there anyone that is trying to port the struts2-dojo-plugin from dojo 2.4.x to 1.1.1? I've downloaded de source, and will be trying to figure which struts widgets don't play well with the new dojo, but to be honest, i'm feel a bit lost in all that code, specially in the js stuff. From the posts i've seen musachy i think takes care of that; may be we could coodinate the work? Any pointer would be appreciated. Thanks Si quieres ser más positivo, pierde un electrón Miguel Ruiz Velasco S. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dojo plugin
My take on it is that a limited amount of functionality is valuable--make the simplest use-cases extremely simple. Anything beyond that it's better to just use the framework raw; there are many advantages to that approach. Anything beyond simple use-cases requires JavaScript code anyway; might as well just use the language that's best suited to the task. My own jQuery plugin does this, the simple stuff can be done with tags; anything beyond that I do by hand. Dave --- On Thu, 7/10/08, Musachy Barroso [EMAIL PROTECTED] wrote: From: Musachy Barroso [EMAIL PROTECTED] Subject: Re: dojo plugin To: Struts Developers List dev@struts.apache.org Date: Thursday, July 10, 2008, 1:11 PM Well, I have started 3 times so far, and quit each time. In my very own humble opinion I don't think it is worth all the effort. Our javascript code consists of wrappers around the dojo widgets to either fix bugs, or add functionality (like topics). Feel free to ask questions about the current implementation. musachy On Thu, Jul 10, 2008 at 12:20 PM, Miguel [EMAIL PROTECTED] wrote: Hello All, Is there anyone that is trying to port the struts2-dojo-plugin from dojo 2.4.x to 1.1.1? I've downloaded de source, and will be trying to figure which struts widgets don't play well with the new dojo, but to be honest, i'm feel a bit lost in all that code, specially in the js stuff. From the posts i've seen musachy i think takes care of that; may be we could coodinate the work? Any pointer would be appreciated. Thanks Si quieres ser más positivo, pierde un electrón Miguel Ruiz Velasco S. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dojo plugin
One issue with Dojo 0.4 that comes with framwork is its lack for accessiblity, however; Version 1+ adds this capability.I know in my company there are a few people who use screen readers and that puts me personally on spot for using framework's ajax tags. - Original Message From: Dave Newton [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Thursday, July 10, 2008 1:19:47 PM Subject: Re: dojo plugin My take on it is that a limited amount of functionality is valuable--make the simplest use-cases extremely simple. Anything beyond that it's better to just use the framework raw; there are many advantages to that approach. Anything beyond simple use-cases requires JavaScript code anyway; might as well just use the language that's best suited to the task. My own jQuery plugin does this, the simple stuff can be done with tags; anything beyond that I do by hand. Dave __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now at http://ca.toolbar.yahoo.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dojo plugin
In fact, the very simple functionality i think we are talking about is the a and the submit tag, displaying in a target node of the same page, and perhaphs submiting using jdom. This is the functionality I find useful, and I agree to do the rest of things by hand using the raw framework. Si quieres ser más positivo, pierde un electrón Miguel Ruiz Velasco S. On Thu, Jul 10, 2008 at 2:00 PM, Struts Two [EMAIL PROTECTED] wrote: One issue with Dojo 0.4 that comes with framwork is its lack for accessiblity, however; Version 1+ adds this capability.I know in my company there are a few people who use screen readers and that puts me personally on spot for using framework's ajax tags. - Original Message From: Dave Newton [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Thursday, July 10, 2008 1:19:47 PM Subject: Re: dojo plugin My take on it is that a limited amount of functionality is valuable--make the simplest use-cases extremely simple. Anything beyond that it's better to just use the framework raw; there are many advantages to that approach. Anything beyond simple use-cases requires JavaScript code anyway; might as well just use the language that's best suited to the task. My own jQuery plugin does this, the simple stuff can be done with tags; anything beyond that I do by hand. Dave __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now at http://ca.toolbar.yahoo.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Future Dojo Plugin
I've seen a number of posts on this list about the different ajax frameworks and how much value there is in a Struts 2 taglib that wraps the ajax library (vs using the libraries directly). As a long time user of Struts (1 2) and ajaxtags.sourceforge.net for the past year I can say there most definitely has been an advantage to having a tag library that provides atleast a very common set of ajax functionality. In hopes of seeing an even richer ajax tag lib offering in Struts I thought I'd share the following article http://www.internetnews.com/dev-news/article.php/3750716/Declaring+Dojo+for+Ajax.htm6 which, atleast at first glance, seems to offer an easier way for taglibs to leverage an ajax libraries capabilities. At the bare minimum it sounds like it offers some insulation from underlying version changes. Enjoy, Jon
Re: Dojo plugin update using 1.1.0 framework
Given the discussion, how about the following idea; - Remove the dojo plug-in from the S2 codebase and put it, in it's current state, into a googlecode project. My main driver for doing the updates was to update the S2.1 code to bring it inline with the latest version, but perhaps we should put our hands up and admit that S2's focus is not on Ajax UI widgets and recommend that web developers go out and use whichever framework they want as opposed to limiting them to the choice made by the tag developers. After all, there is little in the way of S2.1 code for ajax, all we have is some code that acts as a wrapper to make dojo look like it's part of S2. We can put in the readme a pointer to the googlecode project, and see how it develops from there. What do people think? Al. - Original Message - From: Martin Cooper [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Sunday, April 06, 2008 3:16 AM Subject: Re: Dojo plugin update using 1.1.0 framework On Sat, Apr 5, 2008 at 5:35 PM, Jeromy Evans [EMAIL PROTECTED] wrote: Agreed. The Dojo 0.43 plugin in Struts2.1.1 contains significant improvements over the Dojo 0.40 tags bundled in 2.0.x. It's worth releasing as-is and I'd give it a +1 today. It sounds like there's enough people interested to complete a Dojo 1.x plugin. I also think it's worth creating a googlecode project for it until it reaches a certain level of maturity. The benefit of googlecode over the sandpit is the low barrier to contribute and informal releases. If you start the project at Google Code, remember that you will have to come through the Incubator, one way or another, to get the code back into Struts, even if that's just the IP Clearance route. And if, by low barrier to contribute, you mean that you want to grant committership to people who are not Struts committers, then remember that either those people will lose commit rights when you bring the code back here, or you will have to go through a different incubation process to deal with the additional committers. On the other hand, creating the project in the Struts sandbox means that it is immediately open to any Struts committer, all of the resources are already set up, and getting a release out is dependent only upon a vote to move the code from the sandbox to the main code line. I'd say that path will be a whole lot less hassle - unless, that is, you expect the Dojo 1.x plugin to be a major project that requires additional committers and spans an extended period of time to get into shape equivalent to that of today's Dojo plugin. -- Martin Cooper Musachy Barroso wrote: I don't think we should wait at all. Refactoring dojo out of core was one of the main things for 2.1 and it's been there for a year already. Unless Dojo 1.0 is a lot, way, way better than the older versions, I would say you will find lots of surprises. IMO you should set it up as a project on googlecode or somewhere else and we can all contribute/test and eventually bring it on (or just keep it there and get rid of our current plugin). my 2 centavos :) musachy On Sat, Apr 5, 2008 at 6:19 PM, Dave Newton [EMAIL PROTECTED] wrote: --- Al Sutton [EMAIL PROTECTED] wrote: Whilst I can see that there is an advantage to getting a 2.1 release out, my question would be do we want it to go out with a (very) old version of dojo as the demonstration of it's modern ajax capabilities?, and do we want to put developers through getting used to 0.4 as the bundled version and then jump to a much newer version as a minor version release? So the questions are how well tested are the new Dojo tags, and if they're not tested well enough how long would it take to test them? Lastly, how much rework, if any, is required to match the functionality of the 0.4x plugin? My impression is still that Dojo 1.0 is pretty different from Dojo 0.4x, and that this is a non-trivial project--but that's a guess made from ignorance. Is there any evidence to the contrary? Have the tags been tested (even manually) on the client side to bulk-verify behavior? Due to some immediate responsibilities, my availability for working on a Dojo 1.0 plugin is limited and conditional: -- I have some time I can dedicate to *testing* new Dojo tags. -- I don't have the time to learn Dojo 1.0 well and implement much changed and/or new functionality if both the cost and risk are high. -- The window within that time is available is short, and dwindling. -- The more people working on it the more likely I am to make the time because of a perceived lower risk. Nutshell: what's anybody's take on the effort this would require, and who's available to make that effort? Dave - To unsubscribe, e-mail: [EMAIL PROTECTED
Re: Dojo plugin update using 1.1.0 framework
Martin Cooper wrote: On the other hand, creating the project in the Struts sandbox means that it is immediately open to any Struts committer, all of the resources are already set up, and getting a release out is dependent only upon a vote to move the code from the sandbox to the main code line. I'd say that path will be a whole lot less hassle - unless, that is, you expect the Dojo 1.x plugin to be a major project that requires additional committers and spans an extended period of time to get into shape equivalent to that of today's Dojo plugin. -- Martin Cooper I agree transition from googlecode back into Apache is an important consideration and a googlecode decision should be made only after we understand the level of effort involved. My gut feeling is that a complete Dojo 1.x plugin requires significant effort and additional committers. Others would know better than me though. Do you have a contact over at the Dojo that : - is familiar with the current Struts Dojo capabilities and can give an indication of the effort to migrate to 1.x; or - more importantly, confirm whether recreating custom tags is a sensible approach at all. It may be better for both projects that we make a concerted effort to demonstrate dojo + struts integration rather than creating another plugin that encapsulates Dojo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dojo plugin update using 1.1.0 framework
--- Al Sutton [EMAIL PROTECTED] wrote: My main driver for doing the updates was to update the S2.1 code to bring it inline with the latest version, but perhaps we should put our hands up and admit that S2's focus is not on Ajax UI widgets Nobody has yet provided any information as to the potential cost of making Dojo 1.0 work and nobody answered my question regarding what level of functionality currently exists in the Dojo 1.0 plugin, so I'm pretty much unable to come to any cogent conclusion. If it came to a vote I'd probably say (a) leave the current Dojo plugin where it is, and (b) put any new tag plugins on Google Code (like my semi-dormant jQuery plugin and others people are working on). I don't know what the ASF policy is on endorsing particular code, but it seems like if a new plugin got to the point of being usable it would be simple enough to add a we currently recommend using... or among the better tag libraries are... or whatever. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dojo plugin update using 1.1.0 framework
Dave, I don't think anyone does have a good handle on how much work it would be to integrate Dojo 1.0 into the S2.1 tag framework. It's one of those things that the time taken to properly evaluate and estimate the work necessary may be longer than the time to do the work, and even when the work is under way there may be some unforeseen issues even if an estimate was made. The Dojo guys have tried to make it easier by providing an api change list from 0.4 to 0.9 then from 0.9 to 1.0, but how that applies to the S2.1 code is something that will only make sense to someone who has the code fresh in their mind. This is why I started to work on the changes and kept the code as a separate entity, that way if it does prove to be a mountain rather than a molehill there's nothing being held up, and if it turns out to be a molehill then we get all the benefits of supporting, matured code with a smaller footprint in a short period of time. Al. - Original Message - From: Dave Newton [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Sunday, April 06, 2008 3:18 PM Subject: Re: Dojo plugin update using 1.1.0 framework --- Al Sutton [EMAIL PROTECTED] wrote: My main driver for doing the updates was to update the S2.1 code to bring it inline with the latest version, but perhaps we should put our hands up and admit that S2's focus is not on Ajax UI widgets Nobody has yet provided any information as to the potential cost of making Dojo 1.0 work and nobody answered my question regarding what level of functionality currently exists in the Dojo 1.0 plugin, so I'm pretty much unable to come to any cogent conclusion. If it came to a vote I'd probably say (a) leave the current Dojo plugin where it is, and (b) put any new tag plugins on Google Code (like my semi-dormant jQuery plugin and others people are working on). I don't know what the ASF policy is on endorsing particular code, but it seems like if a new plugin got to the point of being usable it would be simple enough to add a we currently recommend using... or among the better tag libraries are... or whatever. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dojo plugin update using 1.1.0 framework
You can do, I'm keeping it on my system atm, so I'm happy to co-ordinate changes. Al. - Original Message - From: Karr, David [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Friday, April 04, 2008 11:32 PM Subject: RE: Dojo plugin update using 1.1.0 framework Is it appropriate at this point to submit a bug for this, and provide a patch for your changes? -Original Message- From: Al Sutton [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2008 11:18 PM To: dev@struts.apache.org Subject: Dojo plugin update using 1.1.0 framework [I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(] All, I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3. The two main changes that were necessary were; * baseRelativePath replaced by baseUrl to reflect changes in dojo API * parseContent removed due to removal from dojo API. By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1 If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip Thanks, Al. -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16442992.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dojo plugin update using 1.1.0 framework
I'm not sure how deep the tests are, but only two needed changing, and those two were the header tests which needed an update to reflect a removed config parameter and a pair of parameters that were combined and renamed. It's working for my needs at the moment, but I'm pretty more bugs will be discovered as people thrash it. Al. - Original Message - From: Dave Newton [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Saturday, April 05, 2008 1:03 AM Subject: RE: Dojo plugin update using 1.1.0 framework How deep are the client-side tests for the Dojo components? My impression was that a fair amount had changed moving from Dojo 0.4mumble - 1.0. I don't know the nature of all the changes that were made, but it makes me nervous. Musachy might have a better handle on this. Dave --- Karr, David [EMAIL PROTECTED] wrote: Is it appropriate at this point to submit a bug for this, and provide a patch for your changes? -Original Message- From: Al Sutton [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2008 11:18 PM To: dev@struts.apache.org Subject: Dojo plugin update using 1.1.0 framework [I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(] All, I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3. The two main changes that were necessary were; * baseRelativePath replaced by baseUrl to reflect changes in dojo API * parseContent removed due to removal from dojo API. By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1 If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip Thanks, Al. -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16442992.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dojo plugin update using 1.1.0 framework
All of the bits are left in place so that the source can be re-integrated as easily as possible when appropriate. At the moment it's a drop in replacement in the struts2 tree, further down the line the svn directories will provide the ability to merge the changes in as smoothly as possible. I've deliberately avoided publishing a jar to avoid people going Hey, theres a jar, let me dump it in my app, wait a minute it doesn't work, thats just cr**, and moving on. If people want to use the code they'll need to understand it's a work in progress. Al. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Saturday, April 05, 2008 1:47 AM Subject: Re: Dojo plugin update using 1.1.0 framework This point is clear to me,but ,why don´t you leave a only the jar available instead the all structure (.pom, src, etc) because is not working with mvn. thanks Herrera Al Sutton wrote: It's a download URL for a zip file, not a maven repository. I don't want people to confuse it with the official S2.1 dojo plugin. Al. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Friday, April 04, 2008 2:19 PM Subject: Re: Dojo plugin update using 1.1.0 framework is the source correct (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip); I cant execute mvn package command. - java.lang.RuntimeException: java.io.FileNotFoundException: C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags\ajax\a.html Herrera Al Sutton wrote: [I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(] All, I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3. The two main changes that were necessary were; * baseRelativePath replaced by baseUrl to reflect changes in dojo API * parseContent removed due to removal from dojo API. By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1 If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip Thanks, Al. -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework-tp16442992p16491430.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework-tp16442992p16508212.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dojo plugin update using 1.1.0 framework
I think there's been a lot of back end changes, but they have a couple of API change docs at http://dojotoolkit.org/book/dojo-porting-guide-0-4-x-0-9 and http://dojotoolkit.org/book/dojo-porting-guide-0-9-x-1-0 My stuff is definitely a work in progress, so I'm sure people will hit bugs, but at least we now starting the move :). Al. - Original Message - From: Musachy Barroso [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Saturday, April 05, 2008 3:18 AM Subject: Re: Dojo plugin update using 1.1.0 framework How deep are the client-side tests for the Dojo components? My impression was that a fair amount had changed moving from Dojo 0.4mumble - 1.0. Pretty much the whole thing changed, as far as I know. musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dojo plugin update using 1.1.0 framework
-Original Message- From: Al Sutton [mailto:[EMAIL PROTECTED] Sent: Saturday, April 05, 2008 12:44 AM To: Struts Developers List Subject: Re: Dojo plugin update using 1.1.0 framework All of the bits are left in place so that the source can be re-integrated as easily as possible when appropriate. At the moment it's a drop in replacement in the struts2 tree, further down the line the svn directories will provide the ability to merge the changes in as smoothly as possible. I've deliberately avoided publishing a jar to avoid people going Hey, theres a jar, let me dump it in my app, wait a minute it doesn't work, thats just cr**, and moving on. If people want to use the code they'll need to understand it's a work in progress. That's great, but you're effectively limiting the audience of people who can test this. I don't know how to build it. I tried, but I couldn't. I'm sure it's obvious to people familiar with the structure of Struts2, or using Maven2. I don't have enough of either yet. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Saturday, April 05, 2008 1:47 AM Subject: Re: Dojo plugin update using 1.1.0 framework This point is clear to me,but ,why don´t you leave a only the jar available instead the all structure (.pom, src, etc) because is not working with mvn. thanks Herrera Al Sutton wrote: It's a download URL for a zip file, not a maven repository. I don't want people to confuse it with the official S2.1 dojo plugin. Al. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Friday, April 04, 2008 2:19 PM Subject: Re: Dojo plugin update using 1.1.0 framework is the source correct (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip); I cant execute mvn package command. - java.lang.RuntimeException: java.io.FileNotFoundException: C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags \ajax\a.html Herrera Al Sutton wrote: [I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(] All, I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3. The two main changes that were necessary were; * baseRelativePath replaced by baseUrl to reflect changes in dojo API * parseContent removed due to removal from dojo API. By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1 If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip Thanks, Al. -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16491430.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16508212.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dojo plugin update using 1.1.0 framework
Hi, I'd propose to get out 2.1.1 test build asap and integrate the latest dojo stuff into 2.1.2-dev as well as the other updated plugins. I'd volunteer for this unless Musachy has time to do so. So we can test all other features and enhancements we integrated in the past months and can continue with the development of S2.1.x. What do you think? cheers, Rainer -Original Message- From: Al Sutton [mailto:[EMAIL PROTECTED] Sent: Saturday, April 05, 2008 12:44 AM To: Struts Developers List Subject: Re: Dojo plugin update using 1.1.0 framework All of the bits are left in place so that the source can be re-integrated as easily as possible when appropriate. At the moment it's a drop in replacement in the struts2 tree, further down the line the svn directories will provide the ability to merge the changes in as smoothly as possible. I've deliberately avoided publishing a jar to avoid people going Hey, theres a jar, let me dump it in my app, wait a minute it doesn't work, thats just cr**, and moving on. If people want to use the code they'll need to understand it's a work in progress. That's great, but you're effectively limiting the audience of people who can test this. I don't know how to build it. I tried, but I couldn't. I'm sure it's obvious to people familiar with the structure of Struts2, or using Maven2. I don't have enough of either yet. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Saturday, April 05, 2008 1:47 AM Subject: Re: Dojo plugin update using 1.1.0 framework This point is clear to me,but ,why don´t you leave a only the jar available instead the all structure (.pom, src, etc) because is not working with mvn. thanks Herrera Al Sutton wrote: It's a download URL for a zip file, not a maven repository. I don't want people to confuse it with the official S2.1 dojo plugin. Al. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Friday, April 04, 2008 2:19 PM Subject: Re: Dojo plugin update using 1.1.0 framework is the source correct (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip); I cant execute mvn package command. - java.lang.RuntimeException: java.io.FileNotFoundException: C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags \ajax\a.html Herrera Al Sutton wrote: [I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(] All, I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3. The two main changes that were necessary were; * baseRelativePath replaced by baseUrl to reflect changes in dojo API * parseContent removed due to removal from dojo API. By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1 If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip Thanks, Al. -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16491430.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16508212.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Rainer Hermanns aixcept Mariahilfstrasse 9 52062 Aachen - Germany w: http://aixcept.de/ t: +49-241-4012247 m: +49-170-3432912 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dojo plugin update using 1.1.0 framework
David, No problem, the easiest was to compile is to download Struts2 head (instructions at http://struts.apache.org/dev/builds.html), locate the plugins\dojo directory, delete it, and replace with the directory from the zip file. As for the compiling, follow the build instructions for struts after you've done the replacement. Al. - Original Message - From: Karr, David [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Saturday, April 05, 2008 4:09 PM Subject: RE: Dojo plugin update using 1.1.0 framework -Original Message- From: Al Sutton [mailto:[EMAIL PROTECTED] Sent: Saturday, April 05, 2008 12:44 AM To: Struts Developers List Subject: Re: Dojo plugin update using 1.1.0 framework All of the bits are left in place so that the source can be re-integrated as easily as possible when appropriate. At the moment it's a drop in replacement in the struts2 tree, further down the line the svn directories will provide the ability to merge the changes in as smoothly as possible. I've deliberately avoided publishing a jar to avoid people going Hey, theres a jar, let me dump it in my app, wait a minute it doesn't work, thats just cr**, and moving on. If people want to use the code they'll need to understand it's a work in progress. That's great, but you're effectively limiting the audience of people who can test this. I don't know how to build it. I tried, but I couldn't. I'm sure it's obvious to people familiar with the structure of Struts2, or using Maven2. I don't have enough of either yet. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Saturday, April 05, 2008 1:47 AM Subject: Re: Dojo plugin update using 1.1.0 framework This point is clear to me,but ,why don´t you leave a only the jar available instead the all structure (.pom, src, etc) because is not working with mvn. thanks Herrera Al Sutton wrote: It's a download URL for a zip file, not a maven repository. I don't want people to confuse it with the official S2.1 dojo plugin. Al. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Friday, April 04, 2008 2:19 PM Subject: Re: Dojo plugin update using 1.1.0 framework is the source correct (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip); I cant execute mvn package command. - java.lang.RuntimeException: java.io.FileNotFoundException: C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags \ajax\a.html Herrera Al Sutton wrote: [I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(] All, I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3. The two main changes that were necessary were; * baseRelativePath replaced by baseUrl to reflect changes in dojo API * parseContent removed due to removal from dojo API. By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1 If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip Thanks, Al. -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16491430.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16508212.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dojo plugin update using 1.1.0 framework
I'm split on this. Whilst I can see that there is an advantage to getting a 2.1 release out, my question would be do we want it to go out with a (very) old version of dojo as the demonstration of it's modern ajax capabilities?, and do we want to put developers through getting used to 0.4 as the bundled version and then jump to a much newer version as a minor version release? Al. - Original Message - From: Rainer Hermanns [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Saturday, April 05, 2008 4:22 PM Subject: RE: Dojo plugin update using 1.1.0 framework Hi, I'd propose to get out 2.1.1 test build asap and integrate the latest dojo stuff into 2.1.2-dev as well as the other updated plugins. I'd volunteer for this unless Musachy has time to do so. So we can test all other features and enhancements we integrated in the past months and can continue with the development of S2.1.x. What do you think? cheers, Rainer -Original Message- From: Al Sutton [mailto:[EMAIL PROTECTED] Sent: Saturday, April 05, 2008 12:44 AM To: Struts Developers List Subject: Re: Dojo plugin update using 1.1.0 framework All of the bits are left in place so that the source can be re-integrated as easily as possible when appropriate. At the moment it's a drop in replacement in the struts2 tree, further down the line the svn directories will provide the ability to merge the changes in as smoothly as possible. I've deliberately avoided publishing a jar to avoid people going Hey, theres a jar, let me dump it in my app, wait a minute it doesn't work, thats just cr**, and moving on. If people want to use the code they'll need to understand it's a work in progress. That's great, but you're effectively limiting the audience of people who can test this. I don't know how to build it. I tried, but I couldn't. I'm sure it's obvious to people familiar with the structure of Struts2, or using Maven2. I don't have enough of either yet. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Saturday, April 05, 2008 1:47 AM Subject: Re: Dojo plugin update using 1.1.0 framework This point is clear to me,but ,why don´t you leave a only the jar available instead the all structure (.pom, src, etc) because is not working with mvn. thanks Herrera Al Sutton wrote: It's a download URL for a zip file, not a maven repository. I don't want people to confuse it with the official S2.1 dojo plugin. Al. - Original Message - From: Pedro Herrera [EMAIL PROTECTED] To: dev@struts.apache.org Sent: Friday, April 04, 2008 2:19 PM Subject: Re: Dojo plugin update using 1.1.0 framework is the source correct (http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip); I cant execute mvn package command. - java.lang.RuntimeException: java.io.FileNotFoundException: C:\Temp\struts_dojo1.1\dojo\..\..\core\src\site\resources\tags \ajax\a.html Herrera Al Sutton wrote: [I'm posing this via nabble because the apache mail servers are saying my last 3 attempts to send this via my normal mailbox are spam :(] All, I have a barely tested version of the dojo plug-in which uses Dojo 1.1 instead of 0.4.3. The two main changes that were necessary were; * baseRelativePath replaced by baseUrl to reflect changes in dojo API * parseContent removed due to removal from dojo API. By barely tested I mean it passes the inbuilt maven tests (after they've been modified due to the changes above), so I would appreciate anyone else's help in either checking this into subversion so can start to be official, or grab it, thrash it, and discuss problems here so we can get it into a state fit for S2.1 If you want to download the source with svn directories you can from http://www.alsutton.com/dojo_1_1_0_for_2_1_1.zip Thanks, Al. -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16491430.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Dojo-plugin-update-using-1.1.0-framework -tp16442992p16508212.html Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
Re: Dojo plugin update using 1.1.0 framework
--- Al Sutton [EMAIL PROTECTED] wrote: Whilst I can see that there is an advantage to getting a 2.1 release out, my question would be do we want it to go out with a (very) old version of dojo as the demonstration of it's modern ajax capabilities?, and do we want to put developers through getting used to 0.4 as the bundled version and then jump to a much newer version as a minor version release? So the questions are how well tested are the new Dojo tags, and if they're not tested well enough how long would it take to test them? Lastly, how much rework, if any, is required to match the functionality of the 0.4x plugin? My impression is still that Dojo 1.0 is pretty different from Dojo 0.4x, and that this is a non-trivial project--but that's a guess made from ignorance. Is there any evidence to the contrary? Have the tags been tested (even manually) on the client side to bulk-verify behavior? Due to some immediate responsibilities, my availability for working on a Dojo 1.0 plugin is limited and conditional: -- I have some time I can dedicate to *testing* new Dojo tags. -- I don't have the time to learn Dojo 1.0 well and implement much changed and/or new functionality if both the cost and risk are high. -- The window within that time is available is short, and dwindling. -- The more people working on it the more likely I am to make the time because of a perceived lower risk. Nutshell: what's anybody's take on the effort this would require, and who's available to make that effort? Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
