At 06:51 AM 6/21/2002 +0200, you wrote:
>I think that's a good idea.
>.... and the first formal reserved Avalon attribute key name would be ?
How about
"avalon:display-name" = display name directly typed in
"avalon:display-name-rk" = Display name looked up from resource
"avalon:description" = description name directly typed in
"avalon:description-rk" = description name looked up from resource
>>As long as that interpretation is restricted to specific "well known"
>>attributes or is considered container specific then I would be fine with that.
>
>Umm, don't like limiting this to well-know attributes. For example, I
>would want to include a description of the component as an i18n resource
>value and I wouldn't like to be restricted on what keys I could use.
No container will be looking up keys it does not know. So the container
limits the keys anyways?
> The alternative is to include a flag in an attribute defintion to
> indicate that the value is an i18n key. The default being FALSE.
Thats the path to the darkside. I could imagine ending up with 50-60
different flags on attributes which are flags on features ;)
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
