For the CSS bit, I think you could achieve your goal using CssResource that's in the trunk to create conditional CSS based on the user agent. One thing I'm unsure about is if you'll be able to decipher different mobile platforms based on the user.agent string along. I think if you're following a tableless layout, you shouldn't have too much trouble going to a mobile platform since most of your changes will happen in CSS.
With regards to mobile permutations, there was some chatter on GWTC that mobile permutations might be coming to GWT, but I guess we'll see where that goes. -- Arthur Kalmenson On Tue, Aug 4, 2009 at 6:38 AM, grue<michael.gruetz...@googlemail.com> wrote: > > Hi, > > I have to add a mobile-optimized version to an existing gwt > application. After digging through the docs I found out that deferred > binding is the technology of chioce. I believe I understand how it > basically works but how do I use it in that specific use case? > The mobile UI of our application differs a lot from the standard > version so I need seperate stylesheets, and seperate GWT controls (we > use composites a lot). Since the basic layout of our application is > done in the .html file I would also need a separate html file. > Now the question is: how do I do that? Are there any best practices? > > I'd really appreciate any hint. > > Best regards, > Michael > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
