[
https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi...
]
Victor Rubezhny edited comment on JBIDE-11602 at 10/23/13 11:13 AM:
--------------------------------------------------------------------
I proposed a patch for the [Bug 417465 - \[JSDT\] JavaScript Validation reports max 100
problems per .js
file|https://bugs.eclipse.org/bugs/show_bug.cgi?id=417465].
The issue states that no more than only 100 problems are to be reported on a JavaScript
file, so we can't see all (most of) problems for some JavaScripts - mostly minified
JavaScripts - and as such the validation becomes not useful for such files.
The patch provides a preference for the maximum number of problems reported per unit that
can be modified at "JavaScript -> Validator -> Errors/Warnings" JSDT
Preference Page.
The issue is mentioned here: [Remove default JSDT in Luna or Fix it?(JavaScript
Development Tools open
issues)|http://www.eclipse.org/forums/index.php/t/544073/] and has
'P3 blocker' Importance.
On 2012.11.23 I've got the confirmation that this issue is marked as RESOLVED FIXED
with Target Milestone 3.6: [Bug 417465 - \[JSDT\] JavaScript Validation reports max 100
problems per .js
file|https://bugs.eclipse.org/bugs/show_bug.cgi?id=417465]
was (Author: vrubezhny):
I proposed a patch for the [Bug 417465 - \[JSDT\] JavaScript Validation reports max
100 problems per .js
file|https://bugs.eclipse.org/bugs/show_bug.cgi?id=417465].
The issue states that no more than only 100 problems are to be reported on a JavaScript
file, so we can't see all (most of) problems for some JavaScripts - mostly minified
JavaScripts - and as such the validation becomes not useful for such files.
The patch provides a preference for the maximum number of problems reported per unit that
can be modified at "JavaScript -> Validator -> Errors/Warnings" JSDT
Preference Page.
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
Priority: Critical
Labels: jsdt, vjet
Fix For: 4.2.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:
http://www.atlassian.com/software/jira