On 13/10/2009, at 19:49, David Kaneda wrote:
> 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 But Dave, if you don't do it this way it won't either run in other "smartphones" than the iPhone, at that would be another BIG *minus* ! -- 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 -~----------~----~----~----~------~----~------~--~---
