Greg Reddin ha scritto:
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... ;-)
Well, it can get pretty crazy. I think we should *at most* provide
support for the 3rd with an extensible object. If someone wants the
object to provide support for multiple dimensions then that's their
prerogative.
I really was joking :-P In fact I use an object with that express
(normally) two dimensions. So you have a line of choice (without locale)
or a plane (with locale); gee! this geometry thing was useful then! :-P
I wonder how hard it would be for you to extend DefinitionsFactory
with a KeyedDefinitionsFactory that provided the same method.
Uh you're right, I did not see it from this point of view, so I am
definitely going to implement outside of Tiles core. But that's still a
problem. I suppose that I need to extend TilesUtil, especially implement
TilesUtil.getDefinition, then maybe I need to override TilesServlet to
put my own implementation of TilesUtil. Then I should call
TilesUtil.setTilesUtil...
Err... sorry that's something I don't like. You are going to refactor
TilesUtil, aren't you? Using a class with static methods all over the
application is (IMHO) poor design... But maybe you are going to refactor
it so it is a false problem ;-)
Ciao
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
