one thing i'm really loving about this... especially with the new idea of <wicket:params> to express params on html tags... is that joe blow can walk up to wicket and pretty much get it by looking at it.
what else could <wicket:component> mean? likewise <wicket:params> is fairly obvious and has the effect of partitioning off all the wicket related values into a separate little area in the file. this approach is way better than tapestry, where this stuff seemed cryptic and mixed together when it's not hard-to-find.
Jonathan Locke wrote:
this works in my version of IE and mozilla as well as in dreamweaver (coding and preview). the only "downside" is that there's a red squiggly under the <wicket:component> tag if you do this in a non-XHTML markup file. big whoop. the world will be moving on.
to extend this, it would be interesting to make components attachable to the namespace using the ApplicationSettings approach i mentioned earlier. the core components could provide a way of registering their own abbreviations in to the XHTML namespace. if you optionally registered components this way, you could say:
<wicket:boxBorder width = "7">this is a test</wicket:boxBorder>
to use box border as a presentation-only component (with no name and no java code to attach the component).
the alternative non-abbreviated syntax would be:
<wicket:component class = "wicket.markup.html.border.BoxBorder width = "7">this is a test</wicket:component>
or you could attach the box border in java code in the usual way:
<wicket:component name = "myBoxBorder">this is a test</wicket:component>
Jonathan Locke wrote:
i'm kindof starting to like this idea...
we would still have <tag id = "wicket-componentName"> to attach components to regular html tags
components would be <wicket:component name = "componentName" param1 = "value1" param2 = "value2">
and then we could get rid of the whole square bracket syntax by using our new namespace. borders would be more intuitive, for example, if they used some kind of extensible, self-documenting
region and marker tagging:
<wicket:region name = "border">
<wicket:marker name = "body"/>
</wicket:region>
as long as people can still limp along in regular html (in case they're stuck there), it looks like xhtml has a lot to offer.
we get a whole tagging namespace within the markup language!
jon
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
