To avoid possible clashes in node.js and io.js sources (once they have same versions), we could perhaps force users to download sources of io.js manually (and select it then in NB).

Petře, io.js allows to use ES6 [1] - I guess we are not ready for it in the JS editor, right?

Thanks.
[1] https://iojs.org/es6.html

I think it would be cool to support it, I'm just not sure how to let user know about it. Have Node.js/io.js everywhere? And when creating new project, should there be io.js mentioned as well? Or should it be support in term of "not mentioned anywhere but working fine if one uses it" :) ?

About the sources, does that mean to have configuration for both Node and IO? In case of the "secret" support, wouldn't it be "enough" to try to recognize io.js from node.js based on given path to the binary (if it ends with io/io.exe or node/nodejs/node.exe). If it fails, user can always set sources manually?

(In reply to Vladimir Riha from comment #3)
> I think it would be cool to support it, I'm just not sure how to let user
> know about it. Have Node.js/io.js everywhere? And when creating new project,
> should there be io.js mentioned as well? Or should it be support in term of
> "not mentioned anywhere but working fine if one uses it" :) ?

The last option I would say. At least for NB 8.1.

> About the sources, does that mean to have configuration for both Node and
> IO? In case of the "secret" support, wouldn't it be "enough" to try to
> recognize io.js from node.js based on given path to the binary (if it ends
> with io/io.exe or node/nodejs/node.exe). If it fails, user can always set
> sources manually?

One can always select sources manually so this is fine. Whether to detect and download proper sources needs to be investigated.

Thanks.

(In reply to Tomas Mysik from comment #2)
> Petře, io.js allows to use ES6 [1] - I guess we are not ready for it in the
> JS editor, right?
> 
> Thanks.
> [1] https://iojs.org/es6.html

No we are not ready for ES6. It will be probably planned for the next release.

So, if NetBeans detects io.js (based just on the CLI name, must start with "io"), it will automatically download io.js sources. Such sources are then treated as any other node.js sources, so there is no difference between node.js and io.js. This can, of course, lead to this: once node.js sources with the same version as io.js ones are released, there can be "clashes". But, I don't think that this should be a big problem and happen very often (user will prefer just one platform I guess). Moreover, user can easily solve it - either by downloading sources again or manually selecting any directory.

Thanks.

http://hg.netbeans.org/web-main/rev/e01f3e81486d

Integrated into 'main-silver', will be available in build *201501310002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/e01f3e81486d
User: Tomas Mysik <tmysik@netbeans.org>
Log: #249924 - Consider support of io.js

Minor improvement + should work on Mac as well.

Thanks.

http://hg.netbeans.org/web-main/rev/6006106e6244

Integrated into 'main-silver', will be available in build *201502030002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/6006106e6244
User: Tomas Mysik <tmysik@netbeans.org>
Log: #249924 cont'd - Consider support of io.js

Fixed for Mac. Minor refactoring & improvement.

It makes sense for Martin to have a look at V8 debugging compatibility. io.js is using a new version of V8.

Would it be worthy/possible to also be "sensitive" to project problem "Node.js: Missing node.js sources" and show "Io.js: Missing io.js sources" for io.js?

Btw I might misunderstood Tomas' comment about ES6 support. Io.js sources are written in ES6 and some of used ES6 syntax breaks code completion for some modules (fs for example)

(In reply to Vladimir Riha from comment #11)
> Would it be worthy/possible to also be "sensitive" to project problem
> "Node.js: Missing node.js sources" and show "Io.js: Missing io.js sources"
> for io.js?

I will try to look at it but I don't think so; we don't support io.js officially, we just try not to break it :) Let's think about it more for the next release.

Please, report it as a new issue.

Thanks.

(In reply to Tomas Mysik from comment #13)
> 
> Please, report it as a new issue.
> 
> Thanks.

Sure, will do.

I tried to use project with iojs, sources were downloaded OK, the same if global NodeJS is set to io.js. It seems OK to me


Product Version: NetBeans IDE Dev (Build 201502040002)
Java: 1.8.0_25; Java HotSpot(TM) Client VM 25.25-b02
Runtime: Java(TM) SE Runtime Environment 1.8.0_25-b17
System: Linux version 3.13.0-35-generic running on i386; UTF-8; en_US (nb)