]
Victor Rubezhny commented on JBIDE-11602:
-----------------------------------------
Regarding the question on support for the latest jQuery library in VJet...
I found the issue in BugZilla on updating the VJet jQuery Type Libraries: [Bug 399447 -
Update Jquery type library to 1.9 |https://bugs.eclipse.org/bugs/show_bug.cgi?id=399447].
The issue is new and not targeted yet, so jQuery 1.9.1 is not supported at the moment.
The other issue - [Bug 395742 - vjet initial contribution of type libraries
|https://bugs.eclipse.org/bugs/show_bug.cgi?id=395742] (Resolved, fixed) states that the
following versions are supported:
- jQuery 1.4
- jQuery Mobile 1.0 Alpha 4.1 (Requires JQuery Type lib)
More detail on Type Libraries and their versions included to the contribution see: [Bug
395742 - vjet initial contribution of type libraries
|https://bugs.eclipse.org/bugs/show_bug.cgi?id=395742]
Provide first class support for client side development
-------------------------------------------------------
Key: JBIDE-11602
URL:
https://issues.jboss.org/browse/JBIDE-11602
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml/html source editing
Reporter: Sebastien Deleuze
Assignee: Victor Rubezhny
Labels: jsdt, vjet
Fix For: 4.1.x
Attachments: jbosstools-add-vjet-dependencies-patch.patch,
jquery-1.5.1.min.js.jpg, jquery.tagcanvas.min.js.jpg,
nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg,
nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg,
nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project-After-Insertion.jpg,
nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project.jpg,
nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg,
nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project.jpg,
nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg,
nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project.jpg,
nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg,
nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg,
nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg,
vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg,
vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg,
vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg,
vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg,
vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg,
vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg,
vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg,
vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg,
vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg,
vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg
Web application development is currently moving in many projects from end to end server
side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside +
pure client side technologies GUI (Backbone.js for example).
Eclipse has been always been quite bad in the field of advanced Javascript development.
JSDT was a good start, but its development has been stopped for a few years, and in its
current status, it is not really a good tool for real HTML5/JS dev. From what I know,
there is no roadmap for strong move on this field in the WTP team. The only real Eclipse
initiative for client side development is Orion (
http://www.eclipse.org/orion/) outside of
the IDE.
The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
My question is : is there any plan to consider client side development as a first class
citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ?
Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and
my guess is this lack may be a significant blocking point in the following years.
Thanks in advance for your feedback.
--
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: