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

[Victor Rubezhny (JIRA)]

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

Victor Rubezhny commented on JBIDE-11602:
-----------------------------------------

Regarding JSDT.

In short: it's more dead than alive, but...

Tonight some discussion have taken a continuation at wtp-dev at eclipse.org mailing list.

There is an alternate variant have being developed by John Peberdy <john at peberdy.ca>. In short, for the Type Resolution he used "NJSDoc as the data source" which "works by executing code in a modified Rhino runtime and analyzing the resulting structure". 

He proposes that his JSDT clone is slightly effective and doesn't require to many resources (such as memory and CPU) for the Type Resolution. Also he plans to:

{quote}
    Use JSDoc comments to hint types
    Add ability to manually hint the type of a local variable (an example of this in Scheme is here [2])
    Built in support for AMD spec and maybe CommonJS modules
    Improve performance, eliminate more JDT specific code
{quote}

And finally, he hopes to merge its JSDT clone back to WTP.

It seems this project is interresting for the Eclipse Source Editing and JSDT team:

{quote}
John,
We're looking forward to seeing how well it all works.  I'm particularly 
interested in how/where/if those manual hints are stored between editor 
sessions.

Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing and JSDT
IBM Rational
{quote}

So, some movement may come with JSDT not so far.
                
> 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
>             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