It's -very- easy to use. Just strip your pages down and let the device do a lot of the work (via the IUI CSS/JS) - I converted our WordPress-based site in maybe 15-20 minutes on my first try. It was tricky when loading up the subpages, I figured out the difference between the full-loading pages and the AJAX-requested pages. The AJAX ones you don't call a header/footer - that seems to make the device "ignore" the page load. So those pages loaded via simple <a href="foo.php">ajax call</a> should be just a page fragment essentially; it replaces the body of the page, but not the entire page. On 1/7/08, Steve Finkelstein <sf@xxxxxxxxxxxxx> wrote: > Thanks for the reply Mike. > > I suppose ultimately I'd need to dig into the JavaScript (hopefully it's not > compressed) to figure out the PHP routing. I believe re-writing my > application with the framework would be quite extensive and just not > feasible at this particular point in time, although I should consider it in > the future if my application remains problematic and this is a solid > solution. The concept of calling back-end code via anchor tags though is > something I've never seen. > > - sf > > > On 1/7/08, mike <mike503@xxxxxxxxx> wrote: > > It's probably using IUI (the iPhone UI CSS/JS that Joe Hewitt created, > > now being maintained at http://code.google.com/p/iui/) which allows > > you to request the page to be loaded via AJAX based on how you setup > > the link. > > > > <a href="foo.php">this will load via AJAX</a> > > > > <a href="foo.php" target="_self">this will load like a normal page > link</a> > > > > This is how I *believe* it works, I just implemented IUI partially on > > a site at work a few days ago and the final thing for me to work out > > the kinks is whether or not to load certain pages using the AJAX > > method (and show the cute little "loading" circle thing) or reload the > > entire page. > > > > Remember it's all just Javascript trickery with CSS that works great > > on Safari browsers (and works almost identical actually now in > > Firefox...) > > > > It's very easy to implement, I had some initial confusion too how it > > routes the requests but I think I figured it out there ^^ > > > > > > > > On 1/7/08, Steve Finkelstein <sf@xxxxxxxxxxxxx> wrote: > > > Hi folks, > > > > > > Probably the most impressive application I've run into for the iPhone > has to > > > be Facebook's implementation. I'm looking for ways to improve my > application > > > to be as responsive as theirs. Unfortunately it has quite a way to go. > Does > > > anyone know how this form of 'routing' works? > > > > > > For instance the home page for iphone.facebook.com looks something like: > > > > > > http://iphone.facebook.com/#home.php > > > > > > then if you click on profile it'll route you to something that looks > like > > > > > > http://iphone.facebook.com/#profile.php?id=XXXX > > > > > > Is this actually 'leaving' the page and requesting profile.php? I'm > > > completely confused with the hash mark in front of the PHP file and the > > > mechanics behind this style. It seems to be extremely well implemented > > > though and I'd like to learn more about it. I'm having a ton of issues > with > > > my application now where Ajax calls randomly do not get sent to the > server. > > > I haven't figured out why, maybe mobile safari is caching request URLs. > But > > > I'm looking to rebuild parts of the architecture to get it to work, and > > > would love to understand the mechanism being used above. > > > > > > Does anyone know what is going on with the browser and HTTP requests > with > > > the methodology listed above? Any further reading? > > > > > > Thanks! > > > > > > - sf > > > > > > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
