+1 for having a seperate key attribute that automatically does a
getText() lookup for the label.
This was one thing that is annoying in WW since we tried to I18Nize our
whole app. The url thing didn't bother me as much, but I'm all for a
shorthand notation if it makes sense. (Url/Button links tend to be
rather verbose no matter what)
On a slightly related note, the other thing we did was change the
default button-style submit to render as:
<input type="button"...
rather than
<button ...
Since <button doesn't work the same on all browsers. (type="button" was
what we used before switching to WW) I'm not sure if this is something
that should be changed in the core tags, but I thought I'd throw it out
there.
Tom
Ted Husted wrote:
On 1/12/07, Joe Germuska <[EMAIL PROTECTED]> wrote:
Anyway, am I the only one who finds this syntax tedious?
No, you are not.
* https://issues.apache.org/struts/browse/WW-1517
Just looking for a patch ...
I don't see a problem with having one tag for the simplest (and most
common case) of a single parameter, and then switching to the
url/param idiom when there are multiple.
-Ted.
---------------------------------------------------------------------
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]
