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.
