[ https://issues.jboss.org/browse/JBIDE-16271?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16271: ---------------------------------------- Right now we have the following JQM features: 1. JQM content assist 2. JQM tab in Properties View 3. JQM Palette It's not a big problem to support #1 (content assist), and #2 (properties view) for both JQM versions 1.3 and 1.4. We just implement these features for 1.4 reusing 1.3 where possible and the corresponding version will be used depending on [version] in JQM JS link: jquery.mobile-[version].*.js declared in the page. If there is no version number (e.g. there is some local custom build JS lib) we could use the default (the latest) one. It's not so easy for #3 (Palette). We may have no jquery.mobile-[version].*.js link in the page at all. But we could add a new tag lib group to the palette: *JQuery Mobile 1.4* and rename the existing one *JQuery Mobile* to *JQuery Mobile 1.3*. If there is no JQM lib link in the page we can expand the group with the latest version. If there is a link with particular version then we could expand the corresponding JQM group in Palette View and fold the other (rest of them if we have more than 2 groups) of JQM groups. Another option we could use is a some kind of project (page) preference which user have to set to let JBT know what version of JQM he is going to use. Max, WDYT? -- 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