time for a vote? Which kind do we want now?

i like the simple parsing one:

<input type="submit" value="wicket:i18n:my_key"/>

or if we want default values:

<input type="submit" value="Default Value" wicket:message="value:my_key"/>

both are fine by me and we could support both versions just fine.

johan


On 8/3/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Time for a vote then? Does anyone see any potential problems with the
whole issue?

Eelco


On 8/3/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> my primary concern is making it easy for our users.
>
> we are not talking about just wicket: we are talking about wicket:i18n: and
> wicket:packaged: prefixes - what do you really think the odds are with a
> user collission?
>
> i agree that it is not as clean/safe as a separate attribute, but it is
> quicker/easier to read.
>
> but i think we will walk in circles on this one so lets agree to disagree.
>
> the nice thing about wicket is that markup loading is pluggable, so i can
> write a filter that uses my scheme, and you can write a filter that uses
> yours. we make both of them available, and the users can choose which one
> they want to add :)
>
> -Igor
>
>
>
> On 8/3/06, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
> > * Igor Vaynberg:
> >
> > > well..this  is what  it would  be...checking every  attribute of
> > > every tag. this will be done only once when the markup is loaded
> > > into the cache so there wont be a performance hit.
> >
> > Attribute values  are arbitrary  strings.  I wouldn't  parse that.
> > What if I put wicket:something on purpose?  I don't expect a weird
> > exception to be throwed.
> >
> > Attribute names on the contrary  are normalized and you can safely
> > add new constructs, as allowed by XML namespaces.
> > --
> >      Jean-Baptiste Quenot
> > aka  John Banana Qwerty
> > http://caraldi.com/jbq/
> >
> >
> -------------------------------------------------------------------------
> > 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-user mailing list
> > Wicket-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wicket-user
> >
>
>
> -------------------------------------------------------------------------
> 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-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>
>

-------------------------------------------------------------------------
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-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-------------------------------------------------------------------------
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-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to