jQuery Forum

- run on desktop browsers as well as mobiles (specifically IE8,9) 

  so that you could build one codebase, with slight modifications to take advantage

  of tablet and desktop form factors (as alluded to by the mail app & desktop UI elements

  of http://jquerymobile.com/designs/)

  Just like sencha touch does for webkit only today, but for more browsers.

  Even IE9 only would already be great - I am more skeptical about ability to bring a

  JQM quality experience to Windows Mobile 7 (with its IE7/8 code base...)

  there are so many useful JQuery plugins (specifically for UI), it would be nice if they

  could play directly with JQM. That is not the case today with most (any?) I am aware of

  Even the standard JQUI datepicker will not work out of the box without some bushwhacking

  Is there a way we could make JQM co-exist w JQUI & 3rd party plugins rather than requiring

  rewrites of all of them (I am sure the more mainstream ones will come along for the ride but

  it will take time) Would it not make sense to leverage the significant existing efforts into JQUI ?

  

  (like Metrowerks Codewarrior had 20 years ago or visual basic form editor or apples interface builder)

  Two similar ones exist for Sencha ext, a similar (but desktop oriented framework)

  http://tof2k.com/ext/formbuilder/ and http://www.projectspace.nl/

  To enable this, we'd need a declarative "data-only" way to specify a whole UI in JQM.

  That is quite doable (see also this thread) We have preliminary architecture on top of

  JQM that allows not just data specification but addition of event handlers and observers -

  so just like in VB you can add onClick, onKeydown etc js code as data in a js object / builder tool.

  Not that drag&drop UI builders are a silver bullet but they sure can speed up prototyping

  and development. It is also a very fast way to debug new widgets in various containers.

And while dreaming of such lofty topics, the more down to earth:

- eliminate the dipping mobile safari location bar on every hash # update of the url

- allow a proper relative "back" button "history[-1]" rather than hardcoding destinations (like jQtouch)

- a more generic spec for list items (see also this thread)