You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code assist now just doesn't work. I tried for http._ ant app._ in Express project.
It showed some beautiful menu with 10-15 option, but none where related to Node.js
Why did you close this issue? Do you mean we are going to use VJET Editor rather than improving our Nodeclipse Editor? I think the choice will lead to be not seamless editing and debugging. How do you think?
Do you mean we are going to use VJET Editor rather than improving our Nodeclipse Editor? I think the choice will lead to be not seamless editing and debugging. How do you think?
We are not going to use VJET Editor. Currently it is worse for Node.js than Node[clipse] Editor.
However some users may want. And there are some other editors as I mentioned in #8
And yes, having several Editors may make it vague. But I am for giving users choice.
However, making full-featured JavaScript Editor is HUGE job. For example Code Assist is like adding information, that JavaScript code doesn't have from other files, guessing what type of variable will be in run-time.
I personally believe that we should leverage good things in Eclipse community, rather than try to undertake big projects. We should listen to Node.js developers to learn what is the most time-consuming activity or not possible thing and help with that. Starting with things, that can be done quicker.
Activity
paulvi commentedon Apr 15, 2013
Hey, that was for VJET editor.
https://github.com/Nodeclipse/nodeclipse-blog/blob/master/Blog.md#vjet
tomotaro1065 commentedon Apr 19, 2013
Why did you close this issue? Do you mean we are going to use VJET Editor rather than improving our Nodeclipse Editor? I think the choice will lead to be not seamless editing and debugging. How do you think?
paulvi commentedon Apr 20, 2013
The opening problem is not related to Nodeclipse.
For general Code Assist Improving, there should be concrete ideas how to do it.
tomotaro1065 commentedon Apr 20, 2013
No. It's an issue of Nodeclipse Editor.
I'm thinking now how to improve it.
It may be related to supporting TypeScript on Nodeclipse in the future.
paulvi commentedon Apr 21, 2013
Then this issue becomes too general, and never will be closed.
I suggest to add Microsoft TypeScript support issue, like #12 CoffeeScript debugging support.
Note: our issues become discussions, and we need some sort of voting feature in GitHub to know what is the most hot and desired feature.
paulvi commentedon Apr 21, 2013
We are not going to use VJET Editor. Currently it is worse for Node.js than Node[clipse] Editor.
However some users may want. And there are some other editors as I mentioned in #8
And yes, having several Editors may make it vague. But I am for giving users choice.
However, making full-featured JavaScript Editor is HUGE job. For example Code Assist is like adding information, that JavaScript code doesn't have from other files, guessing what type of variable will be in run-time.
I personally believe that we should leverage good things in Eclipse community, rather than try to undertake big projects. We should listen to Node.js developers to learn what is the most time-consuming activity or not possible thing and help with that. Starting with things, that can be done quicker.
NodeEditor is changed to be based on JSDT editor
paulvi commentedon Mar 31, 2014
closing