Hi all,
> > Any thoughts? Frederic Daoud :)
>
> I think Freddy had the idea of creating chaining methods without the
> "set" prefix in order to preserve the JavaBean setter notation. So
> the above example becomes:
>
> TextField passwordField = new
> PasswordField("password").maxLength(20).minLength(5).required(true);
>
> Column column = new
> Column("age").format("{0,number,#,###}").textAlign("right");
That is exactly right, and it is what I did in a little tool called
chainer[1] which I then used specifically to generate chainer methods
for use with Click :-)
So, indeed, a while back I was suggesting this enhancement, and I
still think it's a nice idea. Keep the setter methods as they are,
thus preserving the JavaBeans conventions, and add chainer methods
without the "set" prefix.
The question is, in which Click classes to do this, to improve the API
without bloating it.
Cheers,
Freddy
[1]:http://code.google.com/p/chainer/
