Hi Andrew,
Responses in-line below...
Andrew Myers wrote:
I am really not sure what the aims of the iUI project are in terms of
supporting devices other than "iThings"
iUI started as an iPhone-only framework, but it tries hard to support
other standards-based browsers that are similar to the iPhone. The key
feature required is addEventListener - iUI does not try to support the
IE event model and probably never will (IE9 is supposed to support
addEventListener so it may work there) iUI works well on Android and on
PalmPre/WebOS as well as on Firefox (desktop) We will accept patches
for any other device that is mostly compatible and only requires minimal
changes.
I was at Texas JavaScript last week and spoke with both John Resig and
Douglas Crockford about this issue and they confirmed my suspicion that
there really is no industry-standard definition for the class of device
iUI aims to support. John Resig spoke about adding mobile support to
jQuery and talked about supporting A-level and B-level mobile devices.
iUI intends to support mostly A-level devices, but there is no formal
definition at this point. I'm hoping that will change as the industry
supports.
We're definitely open to feedback and patches in this area. To some
extent what we support depends upon the commuity.
however one of my reasons for looking at iUI in preference to
something like jQTouch is that it seems to well enough to work on
Opera Mini making any site I create with it available to a lot of
other devices.
Was it a conscious decision that iUI should work with Opera or is it
just a nice side effect?
Probably a side effect, but we're trying to play as nice as possible
without giving up features or getting to big/complicated.
Obviously I don't expect all the fixed positioning, etc. to work in
Opera, I really just want to know it degrades well enough to be
useable so in some regards I'd like to know that some of these
extensions will also work to some extent as well.
I think that some extensions will support a more narrow range of devices
(and platform/browser version as well) One of the main goals of
extensions is to decouple there development from that of the core (as
much as possible) Fell free to look at the existing extensions in the
sandbox and to adopt one if it's looking lonely...
Esssentially my main reason for developing a "web app" rather than an
"iPhone app" is that I want it to be available on more than just Apple
devices. Am I on my own here, or is this a consideration for others
as well?
You and I are mostly on the same page and I think most of the community
would agree. Some say iPhone-only, others say it should support
everything including IE. But I think what I've outlined here is close
to the viewpoint of the typical iUI developer.
-- Sean
--
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.
