i've run into a lot of situations developing voicetribe where i'm using
webmarktupcontainers when it seems like it should not be needed.
the code gets verbose and harder to read than it should be.
two quick feature ideas to reduce this:
1. a TagModifier component which extends WebMarkupContainer and
adds a SimpleAttributeModifier and/or provides an overrideable
method
for simple pull model attribute modification. this means:
final WebMarkupContainer cellStyle = new WebMarkupContainer
("cellStyle");
cellStyle.add(new SimpleAttributeModifier("class", classname);
add(cellStyle);
becomes just:
add(new TagModifier("cellStyle", "class", classname));
or
add(new TagModifer("cellStyle", "class")
{
public String getAttribtueValue() { return classname; }
});
2. a new wicket tag to make it possible to associate markup with one
or more components in terms of the visibility of the enclosing
markup.
this is actually a very common problem and messy to code.
in the first case, there is only one component:
<wicket:enclosure>
{ component }
</wicket:enclosure>
if the component is visible, the enclosure markup is also visible.
if the component is hidden, the markup is hidden with it.
in the case where there is more than one component nested in the
enclosure, we could specify which component to look at for visibility:
<wicket:enclosure visibility="label">
{ components }
</wicket:enclosure>
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
