-
Notifications
You must be signed in to change notification settings - Fork 77
Improving Code Assist #7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey, that was for VJET editor. |
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? |
The opening problem is not related to Nodeclipse. |
No. It's an issue of Nodeclipse Editor. |
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. |
We are not going to use VJET Editor. Currently it is worse for Node.js than Node[clipse] Editor. 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. |
closing |
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
The text was updated successfully, but these errors were encountered: