Ha, oy, I certainly didn't mean to any sort of argument, but making cross-browser is more costly than a line here or there. Especially with jQTouch — using transform, translate() and CSS3 animations, instead of JS-based top/left animation, requires a hefty change in code, for something non-hardware accelerated. If you see current preview, jQTouch has 8 page transitions, most of which are only currently possible in WebKit (though FF is on its way). I agree, care for multiple browsers should be taken, just not at expense of doubling code. Yeah, it's also a matter of values (mine is in smooth transitions and replicating native iPhone functionality as closely as possible), but definitely not debugging.
Best, Dave On Oct 13, 2009, at 1:41 PM, Jorge Chamorro wrote: > > 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. > > .............................................................. Interface Design & Development www.davidkaneda.com 610 724 8033 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
