Re: [wtp-dev] Improve Phaser Editor JSDT support

[Arián Fornaris Fernández <boniatillo@xxxxxxxxx>]

Hi Angelo,

Very nice work, I am cloning it. Yet I am not sure that migrate to a
different type inference engine (like tern or vjet) is the best for my
project in this moment, but I think in your code I will find some
answers to my questions.

Thanks very much,
Arian

On Fri, Sep 11, 2015 at 12:58 PM, Angelo zerr <angelo.zerr@xxxxxxxxx> wrote:
> It seems that Phaser uses JSDoc comments
> https://github.com/photonstorm/phaser/blob/v2.4.3/src/core/Game.js, so you
> could generate a tern JSON Type Definition from Phaser JavaScript code. So
> you will able to support any version and a lot of editor (like Web Browser
> too).
>
> 2015-09-11 18:54 GMT+02:00 Angelo zerr <angelo.zerr@xxxxxxxxx>:
>>
>> Hi Arian
>>
>> I think it should be a good idea that you write a tern plugin
>> http://ternjs.net/ (it is written in JavaScript) and after you can use in
>> any editor like Emacs, Vim, Sublime, Atom and Eclipse with tern.java
>> https://github.com/angelozerr/tern.java which extends JSDT compeltion to use
>> ternjs.
>>
>> If you are interested to write a tern plugin, I could help you.
>>
>> Regard's Angelo
>>
>> 2015-09-11 18:45 GMT+02:00 Arián Fornaris Fernández
>> <boniatillo@xxxxxxxxx>:
>>>
>>> Hello,
>>>
>>> I am developing Phaser Editor (http://phasereditor.boniatillo.com), an
>>> editor for the game engine http://phaser.io .
>>> I am interested in the JSDT type inference, there is any document I
>>> can read to understand how it works? A technical overview or something
>>> like that? Right now JSDT is working very well with the Phaser API,
>>> but yet there are things I would like to get much better.
>>> What I did is to generate a JavaScript API file and I added it to the
>>> classpath container, but yet this is not perfect, it requires some
>>> tweaks to express certain type relations (like namespaces).
>>>
>>> What I would like to do is to provide an extension point to generate
>>> the JavaScript model in the fly, dynamically, and pass it to the type
>>> inference, without the need to parse a JS API file. The other thing I
>>> would like to do is to improve the jsdoc type annotations, I think it
>>> is a good way to declare static types in JSDT.
>>>
>>> Thanks very much for JSDT, it is really awsome.
>>>
>>> Arian Fornaris
>>> _______________________________________________
>>> wtp-dev mailing list
>>> wtp-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>
>>
>
>
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev