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?
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?
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…
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.
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…
now I have it but it only launch the first project on the list when I launch the sim
even if the right file is opned in the OPEN EDITORS...
I've found that:
- Run (CTRL-F5) runs the last thing you built. Only if you just opened VS Code (so there's no previous build) will it prompt you to build the current project.
- CTRL-SHIFT-P > Monkey C: Build Current Project will build the project associated with the currently focused .jungle or .mc file
So in most cases, it's really a 2-step process: build current project, then run.
As Jim pointed out, it may be easier to just create a launch.json file for each of your projects.
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, I mean, I'm a newbie, I've never used Dev Environment before Garmin Stuff and I spend more time trying to make it works or find answer I don't understand on forum (Time out error, no settings found) or launch sim with right device etc than on my app...
Probably for PRO like you VScode is better, but for newbie, Eclipse is much easier to use.
Have a great day.
Unless you have used VS Code before, I'd say that Eclipse is easier to pick up. Right now I use both,
FlowState, I don't agree with you when you said you would not recommand eclipse for newbies, I mean, I'm a newbie, I've never used Dev Environment before Garmin Stuff and I spend more time trying to make it works or find answer I don't understand on forum (Time out error, no settings found) or launch sim with right device etc than on my app...
Probably for PRO like you VScode is better, but for newbie, Eclipse is much easier to use.
Have a great day.
Maybe for Garmin stuff, because the VS Code plugin is less mature than the Eclipse plugin.
But overall, VS Code is much more modern than Eclipse, and it's continually receiving bug fixes and feature updates. Even in cases when VS Code and Eclipse do similar things (like Eclipse's CTRL-3 Quick Access vs VS Code's CTRL-SHIFT-P command palette), I find VS Code to be much more usable.
With Eclipse, I can't tell the difference between the 2021 version and the 2017 version. Which is fine if the goal is to have stable software that never changes.
I'll just point out that AlphaMonkey explained that Garmin switched to VS Code because Eclipse is too complex and presents too high of a learning curve for new devs. I wish I had a link to the video.
As someone who develops for my day job, I will say I have a lot of complaints about VS Code, but I would still recommend it over Eclipse. VS Code does happen to be the most popular IDE amongst developers, according to several surveys. As far as popularity goes, the Eclipse subreddit has 3k members, but the VS Code subreddit has 80k members.
I say all of this as someone who used Eclipse for years at my day job (and I used to tell people how it was so much better than the IDE we used before).
When I switched to VS Code, I never looked back. You'll also see lots of similarities between VS Code and other popular modern IDEs/editors like Sublime Text and IntelliJ. Can't really say the same for Eclipse.
There have also been people (including Garmin employees) who posted about how they absolutely hated Eclipse and were happy to see VS Code support arrive.
And speaking of bugs in the Garmin VS Code plugin, there were a ton of bugs in the Garmin Eclipse plugin, too. It used to be that if you opened an MC file twice (like in a split view), edits to one view would not be reflected in the other view. Certain dialogs would be unusable on HiDPI/Retina screens. I could go on and on.
I'm not going to tell you whether you have to love or hate Eclipse or VS Code, but I think it's pretty indisputable that a large part of the dev community has moved on from Eclipse a long time ago.
I think people need to suck it up and migrate off of Eclipse.
The difference in UX is night and day, IMO.
Speaking of Eclipse vs. VS Code for noobs, I just randomly searched this:
[https://www.google.com/search?client=firefox-b-d&q=eclipse+vs+code+noob+friendly]
And landed here:
[https://www.reddit.com/r/linuxquestions/comments/q366pt/linux_beginner_friendly_ide/]
A few ppl suggesting VS Code here:
This comment stood out to me:
"Edit: Regarding Eclipse I think it is one of the most horrible IDEs I ever used in my life. Unfortunately at work I have to for some legacy projects :/"
One might say that popularity / popular opinion isn't everything, but the relative popularity of VS Code compared to Eclipse means that many more useful extensions exist for VS Code, like Bracket Pair Colorizer. I can find a similar extension for Sublime Text and IntelliJ, but not Eclipse.
TL;DR it's fine to like things which are unpopular and dislike things which are popular (we all do it from time to time), but don't be surprised if popular things are more well-supported and widespread than unpopular things.
Like Garmin didn't migrate to VS Code to punish Eclipse users, they did it because they literally think that VS Code is simpler and more popular, and that the move will encourage Connect IQ development.
I also happen to think it's a lot more modern, and has a lot of quality-of-life features like multiple cursors, a useful command palette, a modern integrated terminal, a quick way to find editors using fuzzy search, etc. Even when Eclipse has similar features, they just don't work as well (e.g. CTRL-3 in Eclipse vs CTRL-SHIFT-P in VS Code or Sublime Text)
EDIT: I'm not suggesting VS Code is perfect by any means, just that I would choose it over Eclipse, and that it's not a bad choice overall, for almost any kind of development.
VS Code is very popular. It squeezed out another popular editor (Brackets) that I was using.
Yep, popularity isn't everything, but it's important and it's helpful. Like the example I gave with extensions. People are going to develop useful extensions for the popular editors, not the dead editors.
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 Code or nothing.
The developers of Brackets halted work on it and told people to us VS Code instead. That’s kind of usual.
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 Code or nothing.
Yep, I agree. I wanted to say the same thing, but historically this forum has been very anti-VS Code and pro-Eclipse, so ¯\_(ツ)_/¯.
I mean VS Code could be the worst editor in the world, but it wouldn't matter since Garmin has decided to go in that direction. Also goes to the point about how I really don't think it's a mistake that the Eclipse docs have been removed from Garmin's Getting Started page for devs. Eclipse support isn't "deprecated", but they sure don't want to point people in that direction.
Yup. All that.
People might be pro-Eclipse because that’s what they are used to.
I was already using VS Code. So, I don’t care too much about dropping Eclipse. Though, there are some adjustments to doing MC work in VS Code.