Just a quick update.... Sean, Following your recommendations I downloaded the .40 dev1 version and the original zip.
The bad news first - Something was broken in the merge. The problem exists in the app as packaged in both dev versions. The good news - It does work in the original zip submitted. If I get done with the mountain of homework I have for tomorrow night, I plan to try and start comparing the differences to see what might be different and causing the problem. More good news I have spent considerable time studying the iUI.js and am starting to have a semi comfortable understanding of what's going on in there. Yeah for me! On a side note, in another previous thread I had mentioned trying to find ways to override the default Back button behavior for special circumstances like forms and things. I posed the idea of adding attributes like backButtonHack = "true", altBackButtonHref = "location to go to", altBackButtonText = "name of page to go back to", and something like noHistoryStack = "true" for forms, to the container tag for pages I wanted special back button control on. You said these were good ideas but would like to see them implemented without non standard html attributes. As I have been studying the js file, and learning more about how it works, I have several ideas for mods to make these options possible, but they all involve checking for these type of attributes when iUI updates the page and during the click event handler for links. I am curious how you could let the script know to activate these type of mods only on certain pages without the use of non standard attributes. Suggestions? The last question comes from a learning developer's perspective. I noticed iUI already uses a few non standard attributes. If browsers ignore tags and attributes they don't understand, is there a practical reason, besides clean standardized markup, to not use these types of attributes for use in scripts and such? Thanks in advance for feedback on any or all of this everyone! Vic Hudson On Tue, Feb 2, 2010 at 2:28 AM, Victor Hudson <[email protected]> wrote: > Thanks for the idea Sean. I will try the other dev version and > original zip when I get a chance. It may not be till Thursday night > due to work and classes. I will keep every one posted on results though. > > Vic > > On Feb 2, 2010, at 2:13, Sean Gilligan <[email protected]> wrote: > > > Vic Hudson wrote: > >> In the rail ticket app go to Buy a ticket>New Journey > >> > >> All selects convert to panel and display proper when you click them, > >> but only the To, From, and Date fields update properly on the form > >> when returning from picking option. All of the others just continue > >> to > >> display the original selections and I'm not sure if the hidden form > >> inputs the script adds are getting updated or not. > >> > >> Anyone else seeing this? > > > > I just reproduced the problem in (desktop) Safari 4. > > > >> Ideas? > >> > >> > > > > You might want to try downloading the 0.40-dev1 release and/or the > > original zip that was submitted to the project and seeing if it > > works properly. It's an attachment to Issue 178: > > http://code.google.com/p/iui/issues/detail?id=178 > > > > I very well might have broken something as I was making changes for > > integration. > > > > -- 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]<iphonewebdev%[email protected]> > > . > > For more options, visit this group at > http://groups.google.com/group/iphonewebdev?hl=en > > . > > > -- 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.
