Skip to content

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

Closed
tomotaro1065 opened this issue Apr 14, 2013 · 7 comments
Closed

Improving Code Assist #7

tomotaro1065 opened this issue Apr 14, 2013 · 7 comments
Assignees
Milestone

Comments

@tomotaro1065
Copy link
Member

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

@paulvi
Copy link
Member

paulvi commented Apr 15, 2013

@paulvi paulvi closed this as completed Apr 19, 2013
@tomotaro1065
Copy link
Member Author

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?

@tomotaro1065 tomotaro1065 reopened this Apr 19, 2013
@paulvi
Copy link
Member

paulvi commented 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
Copy link
Member Author

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
Copy link
Member

paulvi commented 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
Copy link
Member

paulvi commented Apr 21, 2013

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.

@paulvi
Copy link
Member

paulvi commented Mar 31, 2014

closing

@paulvi paulvi closed this as completed Mar 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants