Date: 2004-09-24T10:00:22
Editor: MichaelMcGrady <[EMAIL PROTECTED]>
Wiki: Apache Struts Wiki
Page: StrutsCatalogFiveMultipleButtonSolutions
URL: http://wiki.apache.org/struts/StrutsCatalogFiveMultipleButtonSolutions
no comment
Change Log:
------------------------------------------------------------------------------
@@ -24,20 +24,19 @@
The DispatchAction solutions are based on using the struts-config.xml to mine the
value of these tags. This too is over-engineering and overkill, even though with
MappingDispatchAction there are different uses for this sort of algorithm. We provide
alternative solutions that do all that the DispatchAction classes do without incurring
their overhead and their coupling to Struts.
There is the further problem of providing some sort of a generic solution. The work
on this page is but a small part of a much bigger solution that will soon be
presented. I use the following for my buttons:
-
-
- <crackwillow:image
- button='Crack_Willow_Chat.gif'
- mapBean='hkc'
- bgClrCode='banRtBgClr'
- txtClrCode='banRtTxtClr'
- font='Edwardian Script ITC'
- italic='false'
- bold='true'
- size='30'
- property='chatSend.dispatch'/>
-
-This tag creates the button Crack_Willow_Chat.gif dynamically and caches it with the
attributes listed. Eventually this will be added to this page. The main point,
however, is that we get rid of the over-engineering and obtain "input" from "input.x"
rather directly. For those who like the ImageButtonBean approach, more efficient ways
to do this sort of thing are presented on this page, requiring only a single button
that exists only for the life of a call, for example.
+{{{
+<crackwillow:image
+ button='Crack_Willow_Chat.gif'
+ mapBean='hkc'
+ bgClrCode='banRtBgClr'
+ txtClrCode='banRtTxtClr'
+ font='Edwardian Script ITC'
+ italic='false'
+ bold='true'
+ size='30'
+ property='chatSend.dispatch'/>
+}}}
+This tag creates the button Crack_Willow_Chat.gif (which reads "Crack Willow Chat"
and is localized) dynamically and caches it with the attributes listed. Eventually
this will be added to this page. The main point, however, is that we get rid of the
over-engineering and obtain "input" from "input.x" rather directly. For those who
like the ImageButtonBean approach, more efficient ways to do this sort of thing are
presented on this page, requiring only a single button that exists only for the life
of a call, for example.
Please do add your ideas at the end. Because much more is coming to this page, not
putting something in the middle would be appreciated.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
