Hi Doug,
On using Node.js we have:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=9479 - Use of node.js
installation on user environment Version: v0.12.2 and later
The CQ is resolved, so JSDT can use the user's existing Node.js
installation (we aren't able to redistribute it).
Regards,
Victor Rubezhny
On 10/12/2015 11:38 AM, Doug Schaefer wrote:
From: <[email protected]
<mailto:[email protected]>> on behalf of Angelo zerr
<[email protected] <mailto:[email protected]>>
Cool. I was hoping that but. Ian’s done some great work with
J2V8 and we should make sure we can use it from Eclipse
projects. If there are performance issues, we should try and
fix them. At the end of it, it’s the same engine that node uses.
I think in my side (tern.java) we could improve something too.
Yes, it would be a shame, but it’s the reality we face at
Eclipse. We really need modern web development tooling to be
one of the core pieces of the Eclipse IDE. And being able to
add support for new frameworks quickly is very important.
Angular 2 and React are critical there IMHO, Angular 1 and
Ember are probably in the mix there too. And as we all know
there’s a new one every day :).
We need to do what we need to do, though. Hopefully we can
work this out with tern. If it doesn’t, we need to consider
alternatives.
Please not ethat Orion uses now tern, so for license term, tern
should be OK to be adopted by Eclipse IDE, no?
Tern isn’t the issue. I see we do have CQ’s that approve Tern and
Acorn for use with Orion. The issue is with the run times. We could
start with Nashorn. J2V8 would need to be IP approved before we could
use it.
I know Max has dealt with the legal issues with these components. Be
good to hear from him on where things are :).
Doug.
Regard's Angelo
Regard's Angelo
2015-10-11 0:02 GMT+02:00 Dawid Pakuła <[email protected]
<mailto:[email protected]>>:
Hi,
currently it’s not possible to do many things in JSDT
by design (JDT history). JSDT build thirth semi model
(something between AST and language model) during it’s
inference process. This model have a lot of
limitations like:
1. Unable to change return type based on arguments
2. Unable to register method/field without AST
3. Unable to drop fields wrongly detected by default
inferencer
So a lot of context based completions and semantic
analysis aren’t possible without second index and
additional (external) processing.
Via bug 466589 [1] I requested porting DLTK inference
engine as fully pluggable, simple and fast alternative
to current.
[1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=466589
--
Dawid Pakuła
+48 795 996 064 <tel:%2B48%20795%20996%20064>
On 10 October 2015 at 23:12:37, Doug Schaefer
([email protected] <mailto:[email protected]>) wrote:
Thanks Gorkem, that's what I suspected.
I guess the other side of that question, why couldn't
we do the same as what tern does in JSDT? For QML we
have been working on an ANTLR 4 grammars for
JavaScript and still need to make sure it's correct
and then do the hard part, the semantic analysis. But
it could be a path to success as well.
Sent from my BlackBerry 10 smartphone on the Rogers
network.
Original Message
From: Gorkem Ercan
Sent: Saturday, October 10, 2015 12:06 PM
To: General discussion of project-wide or
architectural issues.
Reply To: General discussion of project-wide or
architectural issues.
Subject: Re: [wtp-dev] Draft JSDT plan is now on Wiki
On 9 Oct 2015, at 21:43, Doug Schaefer wrote:
> Quick question on the tern.java integration. If I¹m
correct, it looks
> like
> it¹s optional depending on whether tern.java is
installed on the
> user¹s
> system. What are the arguments against making a
tighter integration if
> tern is so much better than JSDT could ever do.
>
It is legal. tern.java uses tern.js which uses
node.js. Our current CQs
for node.js, and npm are
for prerequisite exempt only and it is not enough for
tighter
integration.
Also tern.js and all its npm dependencies needs to go
through legal
process.
Until eclipse makes its peace with node.js and npm,
we will continue to
have restrictions on
utilizing tools that are based on node.js.
> I don¹t think I need to state this but we do want
the best user
> experience
> possible so the user doesn¹t have to concern
themselves about
> installing
> stuff they probably don¹t know about.
>
> Doug.
>
> On 2015-10-09, 11:37 AM,
"[email protected]
<mailto:[email protected]> on behalf of
> Gorkem
> Ercan" <[email protected]
<mailto:[email protected]> on behalf of
> [email protected]
<mailto:[email protected]>>
> wrote:
>
>>
>> I have moved the draft JSDT plan to wiki [1] and
cleaned up the
>> bugzilla
>> references.
>> I think it is still missing a few bugzillas but
feel free to
>> add/remove,
>> contribute.
>>
>> Once we are happy with it we can move it to
eclipse project
>> management
>> portal.
>>
>> [1] https://wiki.eclipse.org/JSDT/JSDT_Neon_Plan
>> --
>> Gorkem
>> _______________________________________________
>> wtp-dev mailing list
>> [email protected] <mailto:[email protected]>
>> 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
> [email protected] <mailto:[email protected]>
> 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
[email protected] <mailto:[email protected]>
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
[email protected] <mailto:[email protected]>
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
[email protected] <mailto:[email protected]>
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
[email protected] <mailto:[email protected]>
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
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev
--
CONFIDENTIALITY NOTICE: This email and files attached to it are
confidential. If you are not the intended recipient you are hereby notified
that using, copying, distributing or taking any action in reliance on the
contents of this information is strictly prohibited. If you have received
this email in error please notify the sender and delete this email.
_______________________________________________
wtp-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev
