I would rather not support it at all if it is that limited. Like I said before, we would support an advanced lookup with <wicket:message key="foo"> but something very basic with <bar wicket:message="bar=foo" />. I don't want to explain this to users, and I don't like the inconsistency. I'm for the best solution, not the easiest for us to implement or maintain.
Eelco On 9/19/06, Johan Compagner <[EMAIL PROTECTED]> wrote: > i think i still prefer the doing it once by loading the markup. > The maybe we loose some advanced localization but i find this acceptable. > What options do we then loose? > > If these options work then it is fine: > > Xxxx.html > gets its messages from: > > Xxxx.properties > > MyApplicaiton.properties > > and there own Localization component should be able to resolve it by key (if > they are comming from a database) > > johan > > > > On 9/19/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > > You are mixing things here. Markup tags become component tags if they > > have a wicket:id. This is the only rule. <wicket:xxx > because by > > default it doesn't have a wicket:id gets an id automatically > > (<auto>-xxx) assigned for the markup tag to become a component tags. > > The same happens to autolinks, <body> etc and it happens at markup > > load time and hence just once per component *type*. > > > > While rendering a component *instance* the resolvers are applied and > > in case of <span wicket:message="myMessage" wicket:id="<auto>-1234"> a > > resolver could localize an attributes values. The resolver in these > > case would actually be independent from any component type as it would > > look for wicket:message in the current tag only and on the fly modify > > the attribute. > > > > Juergen > > > > > > On 9/19/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > On 9/18/06, Juergen Donnerstag < [EMAIL PROTECTED]> wrote: > > > > We do that already in other cases. Make it an auto component and you > > > > can easily hook a resolver on it. > > > > > > That would only work for tags that are not component tags to begin. As > > > soon as you would decide to put wicket:id in it, it wouldn't go > > > through a component resolver and would thus not be processed, right? > > > > > > Eelco > > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > > opinions on IT & business topics through brief surveys -- and earn cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > _______________________________________________ > > > Wicket-develop mailing list > > > Wicket-develop@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/wicket-develop > > > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveys -- and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Wicket-develop mailing list > > Wicket-develop@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wicket-develop > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Wicket-develop mailing list > Wicket-develop@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-develop > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
