Eclipse Community Forums: Project Proposals » VJET JavaScript Toolkit Proposal available for review

Home » General (non-technical) » Project Proposals » VJET JavaScript Toolkit Proposal available for review(New Proposal)

Show: Today's Messages :: Show Polls :: Message Navigator

VJET JavaScript Toolkit Proposal available for review [message #885285]

Tue, 12 June 2012 18:40

Justin Early

Messages: 5
Registered: July 2009

Junior Member

Today the VJET JavaScript Toolkit project which is currently hosted under ebayopensource.org is proposed to be moved to the eclipse web tools platform. Please see the proposal www.eclipse.org/proposals/webtools.vjet/ for more information.

Please leave comments / questions for VJET proposal under this topic.

Thanks,

Justin

Report message to a moderator

Re: VJET JavaScript Toolkit Proposal available for review [message #889807 is a reply to message #885285]

Tue, 19 June 2012 17:36

Benjamin Cabé

Messages: 201
Registered: July 2009
Location: Toulouse, France

Senior Member

Hi Justin!

You might remember our discussions at EclipseCon 2012... It think it would be interesting to find synergies between VJET and Lua Development Tools, especially when it comes to your DLTK fork and how you enhanced it to support VJET Doc.
That'd be great if you could add myself to the list of interested parties, on behalf of the Koneki project!

Kudos for this proposal, and long life to VJET! Smile

Benjamin.

My blog: http://blog.benjamin-cabe.com

Report message to a moderator

Re: VJET JavaScript Toolkit Proposal available for review [message #890069 is a reply to message #889807]

Wed, 20 June 2012 21:51

Justin Early

Messages: 12
Registered: June 2012

Junior Member

Bonjour Benjamin. Yes I remember meeting how is life in France?

I will add your name to interested parties.

I am definitely interested in how Lua dev tools is using DLTK and if you are forking or using DLTK without any modifications. Also our fork of DLTK is renamed so that we do not collide with other tools. github.com/ebayopensource/vjet/blob/master/extmod/dltk/core/org.eclipse.dltk.console.ui/META-INF/MANIFEST.MF and most of the mods have the comment START EBAY MOD so we can review.

Report message to a moderator

Re: VJET JavaScript Toolkit Proposal available for review [message #891960 is a reply to message #890069]

Tue, 26 June 2012 17:00

Justin Early

Messages: 5
Registered: July 2009

Junior Member

Thanks for all the feedback from web tools PMC. I will be posting it here shortly

Report message to a moderator

Re: VJET JavaScript Toolkit Proposal available for review [message #891963 is a reply to message #891960]

Tue, 26 June 2012 17:17

Justin Early

Messages: 5
Registered: July 2009

Junior Member

Today I attended the web tools PMC.

Here are some of the questions that were raised about the project.

Why did we choose web tools as a top level project?

JavaScript is the language of the web. JavaScript is prevalent in every browser on the web.

We want to provide the best experience for web development with Eclipse. To do this we need to provide VJET capabilities in script blocks in html based editors such as HTML, JSP, etc. and we need to work better with other tooling capabilities such as integration with CSS toolkit to show the list of css selectors in multiple js frameworks where css selectors are passed as arguments.

How do you plan on working along side JSDT tooling?

In the short term we can be a separate VJET JS facet that users can select.

In the longer term we would like to integrate more with JSDT tooling. For example, The JSDT debugging work is great work. The power of debugging in the browser with native js runtime rather than using Apache Rhino runtime I know is preferred when there are portability issues. Another example I gave would be to change the implementation of the code assist to include vjet code assist module.

Do users have to use VJETDoc?

VJETDoc is not required for single file js usage it is completely optional. JS can be written without any VJETDoc. With VJETDoc more information can be known not just inferred. This can correct the VJET inference engine. VJETDoc provides optional typing and dependency management that is not verbose and is similar to method/property declarations made in other languages. Library owners currently can extend VJET using VJET Type library JavaScript api and/or use VJET Java extension points. Library owners/ metadata owners can write to VJET for their interpretation of jsdocs and JavaScript api extensions can be built due to the differences in how meta data is declared such as a mixture of JSDoc formats/mixture of JS api and JsDocs. For example when a JavaScript methods arguments takes precedence over jsdocs for defining a class name.

Example of how VJET Doc is optional --
www.ebayopensource.org/wiki/display/VJET/Type+Declarations+Using+VJETDoc

For multiple JS files VJETDoc can be used
www.ebayopensource.org/wiki/display/VJET/JS+code+assist+and+validation+for+two+or+more+js+files

More details on VJET Doc:
www.ebayopensource.org/wiki/display/VJET/Overview+of+VJETDoc

What is the web tools take on this?

We want to make a standards based solution for javascript support which is based on web standards. Then provide extra capabilities enabled through facet selection. We prefer collaboration over competition when possible.

Let me know if I missed anything.

Report message to a moderator

Re: VJET JavaScript Toolkit Proposal available for review [message #893002 is a reply to message #891963]

Mon, 02 July 2012 09:03

Ralf Sternberg

Messages: 1313
Registered: July 2009

Senior Member

Hi Justin,

great to see VJet moving to Eclipse! Your demo at EclipseCon was really impressive, this JavaScript editor could make our life much easier. Is there a way to try the Editor with Eclipse 4? Trying to install from update site or marketplace fails because the dependency to the platform excludes 4.0.0.

Regards, Ralf

Report message to a moderator

Re: VJET JavaScript Toolkit Proposal available for review [message #893100 is a reply to message #893002]

Mon, 02 July 2012 15:55

Justin Early

Messages: 12
Registered: June 2012

Junior Member

Thanks. Currently VJET doesn't support Juno. VJET works with Helios and Indigo versions of Eclipse. I will add supporting eclipse 4/ Juno to future plans.

Report message to a moderator

Re: VJET JavaScript Toolkit Proposal available for review [message #894633 is a reply to message #893100]

Mon, 09 July 2012 21:37

Justin Early

Messages: 12
Registered: June 2012

Junior Member

I have been asked what is the difference between current JavaScript tooling in eclipse and VJET. Here is a stab at the answer... this is not an exhaustive list just a start.

1. There is meta model which can be used to model many
concepts of a structured typed language, JavaScript floating
functions and object literals/json, and mixin concepts.
2. The metamodel population default implementation is to use static analysis to populate the model which allows for invalid code to be parsed where running the js code requires no syntax errors and is more expensive to run in an authoring environment.
2. VJET has a validation engine that validates the semantics not just syntax such as if a doc says an argument should be a String VJET validates that the argument passed is a String.
3. VJET code assist which can propose accurate assist for function call
backs, object literal assist where there are known names, known name spaces, known global functions, etc.
4. ability to extend VJET using VJET js, using Java extensions, or Eclipse java extension points.
5. VJET comes with a default multiple - browser type library which can be validated
against and openly extended.
6. Multiple type libraries support for common js libraries
7. VJETDoc - a simple comment syntax for defining method, property, variable types when needed.
8. Support for cross js file assist using declaration.

Report message to a moderator

Re: VJET JavaScript Toolkit Proposal available for review [message #899820 is a reply to message #885285]

Thu, 02 August 2012 12:57

Chuck Bridgham

Messages: 35
Registered: July 2009

Member

The WTP PMC welcomes this contribution, and the scope of features this will bring to the community. We welcome incubation under the WTP project,
and as stated in the proposal, we recommend continued focus on integrating with the existing Javascript tools to form a single cohesive javascript project.
This should be a goal of the incubation period before graduation. With cooperation between the projects and allowing best features of each to survive,
there will be less overlap and user confusion. When it comes time to graduate these factors can be used to evaluate membership into the WTP project or possibly
as a seperate project under Tools.

We look forward to working with you!

This represents a positive vote for moving forward with incubation.

Thanks - Chuck Bridgham

Report message to a moderator