[jbosstools-issues] [JBoss JIRA] (JBIDE-11602) Provide first class support for client side development

Tue Dec 11 08:57:18 EST 2012

    [ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740151#comment-12740151 ] 

Denis Golovin edited comment on JBIDE-11602 at 12/11/12 8:56 AM:
-----------------------------------------------------------------

Regarding the VJET...

In May of 2012 VJET project was proposed as open source project under the [Eclipse Web Tools Platform Project (WTP)|https://www.ebayopensource.org/index.php/VJET/HomePage]. As the proposal was accepted it moved to http://eclipse.org/vjet/ in late November.

Advantages:

- It works. It needs just to add its compability to a project to be able to use VJET JavaScript editor, Content Assist and so on.
- Provides [Content Assists, Syntax, Semantic Checking for JavaScipts| https://www.ebayopensource.org/wiki/display/VJET/Code+Assistance+Features] and [Code Search|https://www.ebayopensource.org/wiki/display/VJET/Code+Search+Features].
- [Provides Type Declarations|https://www.ebayopensource.org/wiki/display/VJET/Importing+VJET+JavaScript+Type+Libraries] using VJETDoc (form of JavaScript comment syntax used to add type information to JavaScript source code).
- Provides Execution/Debugging facilities. 
- It's integrated into WTP HTML Editor (this means that it's already integrated into JBoss Tools HTML Editor as well) 
- It's an Open Source Project under the [Eclipse Web Tools Platform Project (WTP)|http://eclipse.org/vjet/] and it's alive (opposite to JSDT) 
- Since it was introduced it became more reliable and stable. 

Disadvantages:

- Slowness. It makes Eclipse (and JBT/JBDS) to work significantly slower. The reason is VJET has to compile JavaScripts, build Type info and dependency models as well as to perform Syntax and Semantic checking on the fly.
- Generates too much debug output (but probably it will gone after some time) 
- It still requires to add its capabilities to a project (not a big problem)
- It doesn't solve the Minified jQuery problems as well as some other validation problems even it tries to replace JSDT validation with the own one (I may be mistaken, but I guess it disabled the JSDT Validation when enabled). But I'm sure VJET validation is significantly better that the JSDT one.
- It doesn't solve WTP HTML problems (like that is described in https://issues.jboss.org/browse/JBIDE-3728 Invalid Javascript error - an old Upstream issue (WTP 3.0.3) that still is reproducible today)

Related JSDT [issues list|https://issues.jboss.org/issues/?jql=labels%20in%20(jsdt%2C%20vjet)].

Note: It requires a newer Orbit version than we're using in latest JBDS 6.0/JBT 4.0 Target Platforms.

      was (Author: vrubezhny):
    Regarding the VJET...

In May of 2012 VJET project was proposed as open source project under the [Eclipse Web Tools Platform Project (WTP)|https://www.ebayopensource.org/index.php/VJET/HomePage]. As the proposal was accepted it moved to http://eclipse.org/vjet/ in late November.

Advantages:

- It works. It needs just to add its compability to a project to be able to use VJET JavaScript editor, Content Assist and so on.
- Provides [Content Assists, Syntax, Semantic Checking for JavaScipts| https://www.ebayopensource.org/wiki/display/VJET/Code+Assistance+Features] and [Code Search|https://www.ebayopensource.org/wiki/display/VJET/Code+Search+Features].
- Provides Type Declarations using VJETDoc (form of JavaScript comment syntax used to add type information to JavaScript source code.
- Provides Execution/Debugging facilities. 
- It's integrated into WTP HTML Editor (this means that it's already integrated into JBoss Tools HTML Editor as well) 
- It's an Open Source Project under the [Eclipse Web Tools Platform Project (WTP)|http://eclipse.org/vjet/] and it's alive (opposite to JSDT) 
- Since it was introduced it became more reliable and stable. 

Disadvantages:

- Slowness. It makes Eclipse (and JBT/JBDS) to work significantly slower. The reason is VJET has to compile JavaScripts, build Type info and dependency models as well as to perform Syntax and Semantic checking on the fly.
- Generates too much debug output (but probably it will gone after some time) 
- It still requires to add its capabilities to a project (not a big problem)
- It doesn't solve the Minified jQuery problems as well as some other validation problems even it tries to replace JSDT validation with the own one (I may be mistaken, but I guess it disabled the JSDT Validation when enabled). But I'm sure VJET validation is significantly better that the JSDT one.
- It doesn't solve WTP HTML problems (like that is described in https://issues.jboss.org/browse/JBIDE-3728 Invalid Javascript error - an old Upstream issue (WTP 3.0.3) that still is reproducible today)

Related JSDT [issues list|https://issues.jboss.org/issues/?jql=labels%20in%20(jsdt%2C%20vjet)].

Note: It requires a newer Orbit version than we're using in latest JBDS 6.0/JBT 4.0 Target Platforms.

> 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 source editing
>            Reporter: Sebastien Deleuze
>            Assignee: Victor Rubezhny
>              Labels: jsdt, vjet
>             Fix For: 4.1.x
>
>
> 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