Yeah, I agree.. Leaving it at chaining are probably best fit..
Martijn Dashorst wrote:
While I like the language, I think it is a wrong path, because the
number of methods would explode:
new TextField().setRequired().setInvisible().isDisabled();
For each setFoo action you would get a setNotFoo action, and
corresponding isNotFoo query.
Martijn
On Tue, Aug 26, 2008 at 11:40 AM, Jan Kriesten
<[EMAIL PROTECTED]> wrote:
Hi Uwe,
new TextField(..).setRequired().setVisible().setEnabled()
instead of having to
new TextField(..).setRequired(true).setVisible(true).setEnabled(true)
what do you think ?
naaaaah - you're just lazy. ;-) Not more convenience-methods, there are already
too many...
Best regards, --- Jan.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
