Hi Christopher, thanks for posting the roadmap. Looks good, but I think Error Handling should have a higher priority, since this (possibly) effects ALL users...
Integration of callbacks seems to me not that big architectural change, but has the benefit of keeping the core iUi clean from 'workarounds'. So - IMHO - these items (error handling, callbacks) should be raised. > * Identify if we can replace current orientation hacks with > onorientationchange event. Due to the amount of 1.0.2 versions of the iPhone out here, I'd suggest lowering this point, because the current implementation works across versions and a change could break core functionality. > * Make sure that iUI works properly with desktop Safari 3. While adding support to Safari 3 it also would be nice to have the UI running well on Firefox (and *maybe* Safari 2 - not sure). This is just a matter of additional css and should not harm iUi development. 0.02 andy at 10.10.2007 2:51 Uhr, Christopher Allen wrote: > * More error handling. > > * Investigate larger architecture issues, such as optional callbacks, --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
