In that case, you wouln't need a prefix, as the component attribute property is all you need. Then we would stop putting the '-' between the component name and the component name.
I don't know much about the parsing in Wicket, but I can think of parser problems. Also - as a user/ possible team mate - I'd find it much less clear whether a tag represents a Wicket component.
Eelco
Matthew Watson wrote:
Would it be possible to add say an additional setComponentAttributePrefix() method (defaults to "wicket-") that appends to the start of component attribute, this would allow arbitrary naming, i.e...
getSettings().setComponentAttributePrefix("hello");
Which in the html would equate too
<input id="helloXYZ" type="text"/>
Matt
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
