Eclipse is deprecated?

6444768 over 4 years ago

I am not able to find the Connect IQ developers page related to the Eclipse Plugin. Installation, setting up, etc...

Whether Eclipse plugin declared deprecated and their references removed from the documentation?

Top Replies

Shent-Aurkhan (SHN) over 4 years ago in reply to flowstate +1

peterdedecker jim_m_58 flowstate Many thanks for your precious help,

But I think I will still use Eclipse...

FlowState, I don't agree with you when you said you would not recommand eclipse for newbies…
dpawlyk over 4 years ago in reply to flowstate +1

I think people need to suck it up and migrate off of Eclipse.

VS Code is very popular. It squeezed out another popular editor (Brackets) that I was using.
dpawlyk over 4 years ago in reply to flowstate +1

My point about it being popular is that it’s part of the explanation of why you won’t have a choice (at least, for Monkey C).

It doesn’t matter which you prefer, it’s going to be Visual Studio…

All Replies

peterdedecker over 4 years ago in reply to flowstate

flowstate said:
I think there's an extension for that, but it only works with C# projects (which have support for "project references"). I saw another one which actually creates the symlink for you. I don't know enough about the architecture of VS Code to guess whether something like this possible. Like would it be possible for an extension to programmatically add more folders to the set of folders to be searched when you press CTRL-SHIFT-F? How would this interact with search excludes?

I saw an extension that allowed to define virtual folders ( https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.virtual-folders ). Potentially something like that could be used to re-implement the Eclipse Link Source feature.

No time to look into this now nor experience with vscode extensions, but I see the source code is avaialable, which could be a start.

flowstate over 4 years ago in reply to peterdedecker

peterdedecker said:
I saw an extension that allowed to define virtual folders ( https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.virtual-folders ). Potentially something like that could be used to re-implement the Eclipse Link Source feature.

Idk, doesn't really seem to fit the bill, except for the fact that it seems to have (currently limited) support for files outside the workspace:

"Due to a vscode API limitation, files are only added to the view as they are opened. The downside of this is that when you reopen vscode, the view will be empty. As each file is visited, it will get added to the view.

...

Cons:

doesn't show SCM status
no close button
doesn't show icons (at the moment)
doesn't show foldername for files which aren't directly in the current workspace (at the moment)"

For me, having source control status is pretty useful.

You could put all your shared files in a git submodule, and still refer to them in monkey.jungle file.

The big downside would be if you have a workspace with multiple projects that reference the shared project - you'd get multiple hits for the same search. The other issue is you'd have files in the workspace which may not actually be used by any of the projects.

I would argue that a git submodule is still the best solution for this kind of thing, because you can pin a submodule to a specific version, which lets you update your util library for project B without worrying about breaking project A.

There's also this.

https://marketplace.visualstudio.com/items?itemName=VolcanicBytes.virtual-workspace

"This extension allows you to save all the opened editors into a file, that can be restored later."

Seems to have lots of limitations. I wanted to quote them here but the forum hates us.

Maybe the best thing to do is put in a feature request to the VS Code team.