i dont think i would want to support something that is
markup-placement-specific. we have formcomponentlabel that does this
and it works in all situations. dont know, this is my opinion, others
may have different ones.
-igor
On Tue, Apr 1, 2008 at 4:32 PM, Gerolf Seitz <[EMAIL PROTECTED]> wrote:
yeah, that would take away the convenience it's made for and
would probably result in some more emails on [EMAIL PROTECTED]
if that's a blocker, i'm okay with that.
Gerolf
On Tue, Apr 1, 2008 at 10:56 PM, Igor Vaynberg <[EMAIL PROTECTED]>
wrote:
> if that is in markup _after_ the component an
if that is in markup _after_ the component and component doesnt have
setoutputmarkupid(true) what happens?
-igor
On Tue, Apr 1, 2008 at 1:26 PM, Gerolf Seitz <[EMAIL PROTECTED]> wrote:
> what do you guys think about this?
> i talked to Jan about this and i think this could really remove
> some
what do you guys think about this?
i talked to Jan about this and i think this could really remove
some boilerplate code.
I have implemented it based on WicketMessageTagHandler.
the wicket:for attribute is only processed on label tags.
"wicket:message" in the example would have to be something dif
