On 10/25/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
I hate that I have to call setRequired on form components, yet I don't
introduce RequirecDropDownChoice, and vote to remove RequiredTextField
probably same for: Component.setResponsePage() vs.
RequestCycle.get().setResponsePage()
It is bloating our api, and doesn't give anything extra you can't
already achieve by creating your own, custom component that does
exactly as you wish. And Wicket is advocating creating custom
components.
BTW How often do you *really* have to add the label to the link? Only
once in a menu panel? How often do you just have some text in the
markup?
What is the benefit of doing so if you can just add a <wicket:message>
in the markup?
We use links on and around all kinds of stuff, including: <tr>, <td>,
<div> <span> <img> etc.
Laziness is a bad motivator for expanding an api as has been said time
and time again on these mailinglists
Sure. My problem with the whole thing is that is has been applied very
selectively. There have been a zillion ajax methods and convenience
classes in the last few months for instance, which weren't extensively
discussed, and thus no-one cried about it.
Is this a really big thing? To Johan, me and some users it is. Does it
have a big impact on the API? No, not like I proposed it, as it is
something you specifically have to look for.
Eelco
