[jbosstools-issues] [JBoss JIRA] (JBIDE-16271) Support jquery mobile 1.4

[ https://issues.jboss.org/browse/JBIDE-16271?page=com.atlassian.jira.plugi... ] Vineet Reynolds edited comment on JBIDE-16271 at 12/20/13 8:00 AM: ------------------------------------------------------------------- Here's a summary of the changes I believe are required to support 1.4 (and eventually 1.5 as well, since some of the markup involves deprecated features) : * JS/CSS widget - we should use jQM 1.4 when configured. And also upgrade the version of jQuery used to 1.10.2 instead of 1.9.1 (the jQM 1.3 release was tested against 1.9.1). jQuery 2.x should also be made available in some way for the end-user. jQueryMobile 1.3.x supports only jQuery 1.x, whereas jQuery Mobile 1.4 supports both jQuery 1.x and 2.x. * Themes should be limited to ‘a’ and ‘b’ from ‘a’ through ‘e’. The preview should also be updated to be version specific. Themes a and b in jQM 1.3 are different from those in 1.4. This is true of all widgets in the palette where themes are modifiable via the dialog - there are several (page, popup, panel, table etc.) and I'm not listing all of them for brevity. * Dialog widget - the dialog is deprecated in 1.4 and is expected to be removed in 1.5. See the Button and Link widget for the impact on JBDS. This shouldn’t impact JBDS tooling for the Dialog widget in the palette since we use the recommended “data-dialog” attribute to designate a jQM page as a dialog. * Field containers widget - The markup {{data-role="fieldcontain"}} has been deprecated in 1.4 and will be removed in 1.5. Other widgets like Select, Toggle (slider flip toggle switch) and Text input also generate this markup. * Button widget/ Link widget - The ‘open dialog’ action is deprecated in 1.4 and is expected to be removed in 1.5. It adds {{data-rel="dialog"}} markup that needn’t be used anymore. Dialog pages are expected to be designated in markup. * The 1.4RC1 release notes state - “Deprecated class ui-disabled. Use class ui-state-disabled instead”. This currently affects button markup generated by JBDS. Overall, it is the change in themes (pt. 2 above) that sticks out, since none of the markup relies on features removed in jQM 1.4 RC1. The rest are deprecated and expected to be removed in 1.5 or later. Additionally, there are some new widgets/features that you may wish to consider supporting: * Flipswitch (uses a input type of checkbox instead of select) * Filterable elements. Filters are not restricted to listviews, via the {{data-filter="true"}} markup. * Popups now display arrows via the {{data-arrow="true"}} attribute. * Tabs widget is now available ({{data-role="tabs"}}). * Sliders can show tooltips via {{data-popup-enabled="true"}} attribute and can show values via {{data-show-value="true"}} attribute. was (Author: vineet.reynolds): Here's a summary of the changes I believe are required to support 1.4 (and eventually 1.5 as well, since some of the markup involves deprecated features) : * JS/CSS widget - we should use jQM 1.4 when configured. And also upgrade the version of jQuery used to 1.10.2 instead of 1.9.1 (the jQM 1.3 release was tested against 1.9.1). * Themes should be limited to ‘a’ and ‘b’ from ‘a’ through ‘e’. The preview should also be updated to be version specific. Themes a and b in jQM 1.3 are different from those in 1.4. This is true of all widgets in the palette where themes are modifiable via the dialog - there are several (page, popup, panel, table etc.) and I'm not listing all of them for brevity. * Dialog widget - the dialog is deprecated in 1.4 and is expected to be removed in 1.5. See the Button and Link widget for the impact on JBDS. This shouldn’t impact JBDS tooling for the Dialog widget in the palette since we use the recommended “data-dialog” attribute to designate a jQM page as a dialog. * Field containers widget - The markup {{data-role="fieldcontain"}} has been deprecated in 1.4 and will be removed in 1.5. Other widgets like Select, Toggle (slider flip toggle switch) and Text input also generate this markup. * Button widget/ Link widget - The ‘open dialog’ action is deprecated in 1.4 and is expected to be removed in 1.5. It adds {{data-rel="dialog"}} markup that needn’t be used anymore. Dialog pages are expected to be designated in markup. * The 1.4RC1 release notes state - “Deprecated class ui-disabled. Use class ui-state-disabled instead”. This currently affects button markup generated by JBDS. Overall, it is the change in themes (pt. 2 above) that sticks out, since none of the markup relies on features removed in jQM 1.4 RC1. The rest are deprecated and expected to be removed in 1.5 or later. Additionally, there are some new widgets/features that you may wish to consider supporting: * Flipswitch (uses a input type of checkbox instead of select) * Filterable elements. Filters are not restricted to listviews, via the {{data-filter="true"}} markup. * Popups now display arrows via the {{data-arrow="true"}} attribute. * Tabs widget is now available ({{data-role="tabs"}}). * Sliders can show tooltips via {{data-popup-enabled="true"}} attribute and can show values via {{data-show-value="true"}} attribute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira