2nd thoughts on this. Tooltips are configured on each element that uses
them, so the head thing is not a good idea. I still think that we should
split the "tooltipConfig" attribute into 2 or 3 simple attributes, instead
of asking users to create a map for them. "tooltipConfig" will still work
but would be deprecated for 2.1.
musachy
On 4/5/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
I'm replacing tooltips in core 2.1 with domTT, but I find the whole
tooltip configuration a little bit "weird". It needs to be configured at the
form that contains the fields with the information icons, with something
like (from example.jsp):
<s:form action="exampleSubmit"
tooltipConfig="%{'jsTooltipEnabled':'true'}">
my OGNL is not very good, but did "%{'jsTooltipEnabled':'true'}" ever
created a map? Anyway, it doesn create it now. #{'jsTooltipEnabled':'true'}
is out of the question with jsp 2.1 and "[EMAIL
PROTECTED]@{'jsTooltipEnabled':'true'}"
doesn't feel right. I'd propose that we configure tooltips on head.
<s:head jsTooltips="true" tooltipDelay="5000" tooltipEffect="fade" ... />
Using domTT we can attach tooltips to any element, which has been
requested a few times and could be done with little effort. What do you
think?
musachy
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
