Victor Hudson wrote:
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.
Thanks for the sleuthing. I must have broken something. You may be
able to find it by looking at diffs in revision control...
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.
I hope so, let me know.
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!
Great!
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?
Well the noHistoryStack and backButtonHack option(s) would be easy to
implement with a CSS class and iui.hasClass() Finding a 'standard'
place to put an href or a string is little tougher. One approach that
could be used is an element within each fragment/page/div/ul that
contains the link and title. That element could then be hidden by
iui.css. Could you explain (remind?) what the use case is and exactly
how the alt location and alt text are used?
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?
These are good questions. I ask them myself ;-)
The original developer of iUI chose to use the non-standard attributes.
Some folks are very dogmatic about following the standard closely and
not using nonstandard attributes, but, in practice, I have not seen the
non-standard attributes have not caused much trouble. However, I have
tried not to use them as I've added features (although I did do it in
one case.)
The non-standard tags will result in error messages from HTML validators
and could potentially conflict with attributes added as part of the HTML
5 spec, for example. There might be a few other possible bad outcomes.
My preference is to avoid using them if there is an (easy?) alternative.
I'm certainly open to discussing this further.
-- 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].
For more options, visit this group at
http://groups.google.com/group/iphonewebdev?hl=en.
