Reporting my latest finding and thought about jQuery Mobile just in case anyone interested in using jQM Frameworks and following this thread.
On Dec 23, 2010, at 2:07 AM, MichaelMD wrote: > Remember that a lot of the low-end/older phone browsers out there in > real world use don't handle javascript. It's built with progressive enhancement in mind, if a browsing device doesn't support javascript, it will do without just fine. All contents are accessible, viewable by the user, just no fancy magic touch that you expect from touchscreen. It's very promising for mobile web development, but I am still waiting for the first stable release. The following comment is also a reminder for myself: >From what I have learned thus far specifically for the jQM, I think we, >especially people who are still in the box of " low-end/older phones/browsers" >don't handle javascript really must re-evaluate the thinking (that Javacript = >no support for older browsers/devices/screen reader) and brush up the >knowledge/skills for the ever changing web development if we are to stay in >the job for another decade or the half (I am assuming majority member in this >list are seasoned web workers) and compete with the bright young kids. HTML5, CSS3, Mobile Web Developement, IE9, IE6 no more, progressive enhancement javascript (such an old yet new phrase for 2011), I feel pretty excited to try working hard on staying inline with the bright young kids in year 2011. Closing thought for my not-so-bad 2010. tee ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [email protected] *******************************************************************
