I think we should remove these methods. They are quite easy to implement
yourself, and they limit the ways we can change ListView's internals.
I can see they are 'handy', but I feel they also mess up the idea that a
low level component should be one thing at a time.
Some other users seem to
Yea, I always wondered what the were there for. They seem like clutter to me.
+1
On 7/29/05, Eelco Hillenius [EMAIL PROTECTED] wrote:
I think we should remove these methods. They are quite easy to implement
yourself, and they limit the ways we can change ListView's internals.
I can see they
+1
-Igor
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast.
+1
I've allways wondered why are they there :)
-Matej
Eelco Hillenius wrote:
I think we should remove these methods. They are quite easy to implement
yourself, and they limit the ways we can change ListView's internals.
I can see they are 'handy', but I feel they also mess up the idea that a
+1
Eelco Hillenius wrote:
I think we should remove these methods. They are quite easy to
implement yourself, and they limit the ways we can change ListView's
internals.
I can see they are 'handy', but I feel they also mess up the idea that
a low level component should be one thing at a
+1
Hi Eelco,
Sorry I did not respond before on the list topic. I know too little about
Wicket, and you were just faster.
Thanks for proposing it,
Christian
On Fri, 29 Jul 2005 18:48:51 +0200, Eelco Hillenius
[EMAIL PROTECTED] wrote:
I think we should remove these methods. They are quite
