4 ms·

Related note: Has anyone tried using this: http://code.google.com/p/iui/ http://code.google.com/p/iui/

cpr 17y ago
Yes, that's been around for quite a while. We used it for the built-in help files in our iPhone app (Grafly, a graphing calculator).
- csbrooks 17y ago
  Ok, thanks. I'm wondering how users on mobile browsers which aren't iPhones would react to that interface...? (And also, how well it would render.)
  - rufo 17y ago
    It works well enough on Android and Palm Pre, although without the fancy OpenGL-accelerated CSS transforms (it gracefully degrades to more traditional CSS animations if WebKit transitions are not available). The underlying HTML is just a bunch of unordered lists and divs, and all the advanced behavior is via CSS and Javascript - if you want to make sure it'll work on less-capable browsers it's doable, but you'll need to keep an eye on how you're loading things. You may wind up needing to to browser sniffing on the server and serving up different HTML if you see various browsers; we didn't get that far in the project we worked on.
  - seiji 17y ago
    Not sure about iUI, but jQTouch uses webkit-enhanced markup so any webkit engine will read it correctly. jQTouch apps look great in desktop Safari, iPhones, and Android devices. It's even marginally passable in firefox. Though, Android is very late getting some features (HTML5 manifests, local storage, and navigator.geolocation) and I'm still not sure if it supports support CSS animations.
rufo 17y ago
We used iUI for the PAX scheduling app a friend and I hacked together in a few days (best seen on iPhone, mostly works on Android): http://pax.expojunkie.com/ http://pax.expojunkie.com/ iUI is a pretty decent way to get going quickly - it's a fairly simple framework once you start digging into it, and you can make some decent looking stuff. The AJAX loading of sub-pages is a nice touch and is handled well. We had to do a lot of the fancier map scrolling/etc. ourselves, though, and there are still a ton of shortcomings that we can't get around due to lack of native events (fixed toolbars, proper scrolling, a few other fiddly things that you might notice but are too esoteric to mention here.) jQTouch is getting a lot of buzz right now, and we might look at rewriting ExpoJunkie using it early next year: http://www.jqtouch.com/ http://www.jqtouch.com/

cpr 17y ago

Yes, that's been around for quite a while. We used it for the built-in help files in our iPhone app (Grafly, a graphing calculator).

csbrooks 17y ago
Ok, thanks. I'm wondering how users on mobile browsers which aren't iPhones would react to that interface...? (And also, how well it would render.)
- rufo 17y ago
  It works well enough on Android and Palm Pre, although without the fancy OpenGL-accelerated CSS transforms (it gracefully degrades to more traditional CSS animations if WebKit transitions are not available). The underlying HTML is just a bunch of unordered lists and divs, and all the advanced behavior is via CSS and Javascript - if you want to make sure it'll work on less-capable browsers it's doable, but you'll need to keep an eye on how you're loading things. You may wind up needing to to browser sniffing on the server and serving up different HTML if you see various browsers; we didn't get that far in the project we worked on.
- seiji 17y ago
  Not sure about iUI, but jQTouch uses webkit-enhanced markup so any webkit engine will read it correctly. jQTouch apps look great in desktop Safari, iPhones, and Android devices. It's even marginally passable in firefox. Though, Android is very late getting some features (HTML5 manifests, local storage, and navigator.geolocation) and I'm still not sure if it supports support CSS animations.

rufo 17y ago

We used iUI for the PAX scheduling app a friend and I hacked together in a few days (best seen on iPhone, mostly works on Android): http://pax.expojunkie.com/ http://pax.expojunkie.com/ iUI is a pretty decent way to get going quickly - it's a fairly simple framework once you start digging into it, and you can make some decent looking stuff. The AJAX loading of sub-pages is a nice touch and is handled well. We had to do a lot of the fancier map scrolling/etc. ourselves, though, and there are still a ton of shortcomings that we can't get around due to lack of native events (fixed toolbars, proper scrolling, a few other fiddly things that you might notice but are too esoteric to mention here.) jQTouch is getting a lot of buzz right now, and we might look at rewriting ExpoJunkie using it early next year: http://www.jqtouch.com/ http://www.jqtouch.com/