Developers will probably want to take a variety of approaches to handling mobile vs. desktop, so we should probably be careful about being too opinionated here and only offering one inflexible approach. For some of this stuff, it might make more sense to offer some recipes and/or a plug-in rather than, for example, hard-coding directory structures or mobile browser lists into the framework. Perhaps we should only make changes to the framework to handle things that cannot be handled at the application level (e.g., bytecode compilation issues with conditional layouts) or that are likely to be useful under a variety of approaches to multi-layout sites. Anthony
On Saturday, July 23, 2011 5:43:30 PM UTC-4, Ross Peoples wrote: > Not sure about which directory structure works best, but as for falling > back, it tries to go to the most specific device first, then will fallback > to the desktop html if not found. So an iPad will go to the tablet, if > there's no view for that, should it fall back to mobile, or to desktop? > > That and figuring out the best directory structure for this would be a good > idea. I guess we'd have to get more opinions on the matter. Maybe Massimo > has a preference? :) >
