My "official line" on this kind of thing is that supporting multiple
devices is really multiple applications. There's plenty of room for
sharing in terms of back end data and maybe some abstract base
classes, but a small device application (to be effective and liked)
needs to be more than just the full app with the graphics turned down
a notch ... you need to focus on what the user would want to
accomplish remotely and optimize for that case.
I really want to avoid the idea that you can solve this with an XSLT
type solution ... that's programming inside a big ugly case statement
and is not going to give you good results.
You end up balancing a small amount of duplication vs. a very large
potential for unexpected consequences when making minor changes ("oh,
so changing the order of those buttons breaks the WAP version? Who
would have guessed?").
On Wed, Sep 2, 2009 at 2:10 PM, Alfie
Kirkpatrick<alfie.kirkpatr...@ioko.com> wrote:
> Am wondering about ways to support this scenario cleanly in T5, where
> visual layout is very different per device but the page classes could be
> quite similar (clearly this depends to a large extent on whether devices
> have radically different page flows and layouts).
>
>
>
> One obvious approach would be to have a base page class for each page
> and a subclass + device specific TML per device. The same approach could
> be used for components. Maybe this is the best and only way. I can see
> potential issues though, eg. if the base page class needs to inject a
> component, would it work to inject the component's base class?
>
>
>
> Does anyone else have experience of this or suggestions for different
> approaches?
>
>
>
> Thanks and regards, Alfie.
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
