On Jul 19, 1:37 pm, Sean Gilligan <[email protected]> wrote: > On 7/18/10 4:45 AM, RobG wrote: > > > The point of many of the criticisms (such as adding listeners to the > > window object, using get/setAttribute instead of DOM properties, using > > non-standard properties instead of classes) is that there are more > > robust ways of doing the same thing that are standards compliant and > > therefore far less subject to future failure. > > I understand and would like to fix many/most of these things over time. > (However, the chance that any of these things will effect someone in the > browser on a modern, touch-capable, mobile device that has any real > market share is almost indistinguishable from zero.) iUI has had some > real issues like critical sections, poor transitions performance, broken > form handling, and lack of extensibility. These are the issues that > actually affect people and I have tried to focus on them. > > I'm also a less experienced Javascript coder than Joe Hewitt and am > reluctant to change his code unless I'm fixing a bug or adding something > of clear value to users. I'm not opposed to this kind of cleanup, it's > just not on the top of my priority list. I'm also afraid that it might > break something. It would be great if someone who has your level of > knowledge would be willing to take the time to understand the complete > codebase, the backwards-compatibility issues our users would face when > upgrading, make some patches via Mercurial, test them (perhaps even > create some test cases and/or unit tests) etc.
Ok, I'll implement fixes for the DM criticisms and let you know. I'll have questions about what certain bits do, and it will need additional testing. Also, it seems to me that with fixes to addEventListener and the XHR request stuff, the basic script could quite easilly accommodate IE also. If you are going to add more complex transitions, that may be an issue but I think IE 9 is going to be pretty good and hopefully the version on Windows Phone 7 (or whatever it's called) will use it. So when the new mobile Windows OS is released, you could be more or less ready. It might seem like WebKit based browsers are all the go right now, but MS has a habbit of outlasting the competition by sheer persistance regardless of how far behind they start. -- Rob -- 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.
