On 13/10/2009, at 16:35, David Kaneda wrote: > Jorge, > > jQTouch is certainly a framework for iPhone web development. The > motion/animations, touch response, etc. is optimized for Mobile > WebKit. I could easily add "backwards compatibility" with clunky, > Javascript-based animations and laggy touch responses, doubling the > codebase, but this is not the goal. Mobile WebKit is currently > serving over 90% of web traffic — soon enough the Pre and Android > will also be supported. I don't think this specialization speaks to > the framework's quality (or mine!) in any way. > > Best, > Dave
Dave, I know because I develop (web) apps for the iPhone too, that it's not so difficult to make it work in FF, Chrome and Opera too. It's just a liitle bit more of work, just a little bit. And the benefits are huge, because the same page/app can then be used in a desktop, which is a BIG plus. I told Sean the other day, here, that one easy but essential change I did to my hyper-forked iui was to wrap it in a max-width: limited, centered container so that it doesn't fill the whole screen side-to- side when on a desktop. This simple change makes it much more user- friendly on a (big) screen, and it doesn't affect the appearance on the iPhone. All of these 3 other browsers come with excellent debuggers which are of great help: Opera has the DragonFly (it's fantanstic, pretty good), Chrome the same webInspector as Safari, and FF has (of course) FireBug. So it's not that debugging the CSS or the JS in any of those is difficult at all. -- Jorge. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
