Setting component properties from tag attributes could be a valueable
addition to our arsenal. /IF/ we can do this /efficiently/ we could
support things like:
<a href="#" wicket:id="link" color="brown">set color</color>
private class ColorLink extends Link
{
private String color;
public void setColor(String color) { this.color = color; }
public String getColor() { return color; }
public void onClick()
{
...
}
};
where attribute color would be set the the color property on a ColorLink
instance.
I think this is a lot like Tapestry's informal parameters. Any readers
that have experience with that? And what do you think. Can it be a good
thing, or does it encourage scripting too much. Personally, I think that
it could help in cases where the properties to be set are really about
the visuals in the first place. In that case supporting this could be a
good idea.
Eelco
p.s. though this is a develop discussion, I hope on broader opinions
here which is why I posted to the user list.
-------------------------------------------------------
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. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
