Greg Reddin wrote:

>
> Yes, I understand, and I still have your messages from about a month
ago in my inbox and have not forgotten your requests, though I'm not  sure
I fully understand what you are trying to do.

The typical scenario is:
1) take the HttpServletRequest, in particular a bean (in session scope)
that represents a logged-in user and the HTTP request header (from which I
can identify a device).
2) depending on the particular user and the particular device, send a
different page appearance (read: Tiles definition) for the same name of a
tiles definition.
For instance, if I have a Tiles definition called "page.index" (for the
homepage), you can have a homepage for the occasional visitor on a
PC-Browser, a different homepage for a customer on a PDA, etc...
At the moment, can Tiles (even if in the sandbox) do it?

> Anyway, after you  read my next mail and see the commit message
associated with it you  will hate me for sure :-)

Especially when I read that you erased the "xmlDefinition" package... ;-)

> But please know that I fully hope to  support what you are trying to do.
However we may need to negotiate  on the specifics a bit.  The thing I
*do* understand about your  extension to Tiles is that it relies on a
piece of Tiles  functionality I am factoring out.  So, we'll either have
to start  over and factor it back in or we'll have to devise another means
of  factoring it in.

Ok. Fast answer:
1) ComponentDefinition.getDefinition(String name, ServletRequest request)
2) DefinitionsFactory.init(Map params, ServletContext context)

(1) is for getting a different definition depending on the request;
(2) is for getting resources in the implementation of DefinitionsFactory.

>
> So, please be patient with me.  I'm trying to shrink the footprint  and
learning curve of Tiles now while we have a shot at doing so.   If, in the
process, I inadvertently remove functionality that people  are relying on,
then I'll either back up or put it back in another  way.  I *will* work
with you to help you get going even if it means I  have to help refactor
your code :-)

That's no problem, I made a branch in the CVS to put the old code in a
safe ;-)

> In the meantime, remember that  Tiles is in the sandbox.  You should not
be relying on any API  stability or compatibility with anything else.  It
is experimental  and guaranteed to change.

Dimensions (with Tiles standalone) too.

>
> Look for another message from me soon and we can take the discussion
from there.
>
> Thanks,
> Greg
>

Thanks to you ;-)
By the way I am going to post a patch with the small "hacks" I made (about
loading config parameters). You'll see a bug report soon...

Antonio Petrelli


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to