Date: 2004-09-21T15:37:26 Editor: MichaelMcGrady <[EMAIL PROTECTED]> Wiki: Apache Struts Wiki Page: StrutsCatalogFiveMultipleButtonSolutions URL: http://wiki.apache.org/struts/StrutsCatalogFiveMultipleButtonSolutions
no comment Change Log: ------------------------------------------------------------------------------ @@ -602,7 +602,7 @@ [http://www.husted.com/struts/tips/001.html Ted Husted's use an ImageButtonBean to represent an image button tip] -''** Note on link to "Ted Husted's use of an ImageButtonBean": This is an old heavy solution which was proposed here originally as an option to Ted's solution using JavaScript. The guts of this solution came from another author altogether whose name I have regretably forgotten but whom was credited on the page. Indeed, on that page a detailed discussion of Ted's JavaScript solution was presented. The beginning of this wiki was original entitled soething like "ImageButton without JavaScript". This is, at any rate, in my opinion, a very outmoded solution. This solution uses the update.x nature of the name in the request parameters name/value pair to get a [SomeObject].getName().getX() rather than finding a "field" (name or request parameter) with suffix of .x. The solutions are equivalent except that this one creates an object for each command you need. This solution requires that you create a button for each command and that proliferates the button objects. The solution on this page, inspired as an improvement to the code the author of this link calls "Ted Husted's use of an ImageButtonBean", uses only one button in its best form and less in the second best form. The button solutions themselves, including especially the one called ImageButtonBean are inferior. My testing, at any rate, indicates that this solution is super slow relatively speaking. You can, you might note, use "update.firstChoice", "update.secondChoice", etc. and do fancier things with this pattern. I first awoke from my dogmatic slumber on these buttons when a member of this list noted that there was no need to go with all these button objects. If you look at the actual use of this pattern, it is not particularly inviting.'' +''** Note on link to "Ted Husted's use of an ImageButtonBean": This is an old heavy solution which was proposed here originally as an option to Ted's solution using JavaScript. The guts of this solution came from '''Antonio Lagnada''' (http://j2ee-01.lagnada.com/struts/html-buttons.htm) and was credited at http://wiki.apache.org/struts/StrutsCatalogMultipleImageButtonsWithNoJavaScript?action=recall&date=1083359181 . When Ted changed from his JavaScript based solution, cited on the same wiki, I don't know. I believe, however, that Antonio is the originator of this pattern. This is, at any rate, in my opinion, a very outmoded solution. This solution uses the update.x nature of the name in the request parameters name/value pair to get a [SomeObject].getName().getX() rather than finding a "field" (name or request parameter) with suffix of .x. The solutions are equivalent except that this one creates an object for each command you need. This solution requires that you create a button for each command and that proliferates the button objects. The solution on this page, inspired as an improvement to the code the author of this link calls "Ted Husted's use of an ImageButtonBean", uses only one button in its best form and less in the second best form. The button solutions themselves, including especially the one called ImageButtonBean are inferior. My testing, at any rate, indicates that this solution is super slow relatively speaking. You can, you might note, use "update.firstChoice", "update.secondChoice", etc. and do fancier things with this pattern. I first awoke from my dogmatic slumber on these buttons when '''Larry Young''' noted that there was no need to go with all these button objects. He has his own better solution too. If you look at the actual use of this pattern, it is not particularly inviting. Larry was right and I hope the work I have done on his prompting is worth someone's time.'' == Comments == CommentPageForCritiques --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
