Hi Greg!
Greg Reddin ha scritto:
Here's the way I see it: We see the tiles definitions set as a
2-dimensional data set. One axis is the name and the other is the
locale. There's the added wrinkle that definition data from one name
can inherit data from another name. By adding "channel" to the mix I
think you are adding a 3rd dimension. In your Dimensions architecture
do you choose a definition based on name, channel, *and* locale or
only name and channel?
Actually Dimensions chooses from name, user role and channel, or only
name and user role, or only name and channel. Locale is not supported
but it's a question of extension. In fact you can define whatever
dimension you want.
Sincerely, I didn't care of Locale for two reasons:
1) The previous developer didn't care :-P
2) I thought that was more important to put support to device and user,
than support to locale. In fact, there are some situations where layout
disposition depending on locale may be important (I'm thinking of arab
countries, where the most important part of the page is on the right,
instead of the left). But anyway it seemed (to me) less important
comparing to the fact that a person with a PDA needs a lighter interface.
But what about adding an API that requires a generic Object key
parameter to support the 3rd dimension?
That would be fine! But to support also the 4th, the 5th... ;-)
I'm not sure if the use case is common enough to make it part of the
core API. If not, could it be added to an extension?
I am wondering where it can be put... What do you think of that "key
provider" I wrote about in my last mail? You can change the name if you
like :-P
Again, I can see where you are coming from, but I really don't think
we should lose the locale dimension that's already there.
Ok, anyway "request.getLocale" is not enough...
Thoughts?
Written above ;-)
Ciao
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
