Hi,
Where we can find documentation about news about SDK 4.0?
Is there any update on API?
Best regards,
Hi,
Where we can find documentation about news about SDK 4.0?
Is there any update on API?
Best regards,
My feeling is that at some point, support of the eclipse plugin will end, but I doubt it will be soon. What I did since back this was announced in October, was use both to get acquainted with VS code.…
For people that have previously used VS Code, the switch might be easier. For people who haven't, and have used Eclipse for CIQ for a long time, it's not. The workflow is different, lots more use…
I've been mostly developing Java EE for the last 20 years and been using InteliJ and Eclipse. I'm not against new IDEs and I'll have a look at VSC again and see how it has developed. I guess it's mostly…
I think this post should help you out.
https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/welcome-to-connect-iq-4-0
hi,
I receive an email where was written "We are moving from Eclipse to the Visual Studio Code IDE."
Does it mean that Eclipse will be left behind in the futur or I translated it badly?
Travis' link indicates what's in the preview to test.
There's more in 4,0 coming and you may see references in the docs included with the SDK, but in some cases, a device with 4.0 will be needed even in the sim.
My feeling is that at some point, support of the eclipse plugin will end, but I doubt it will be soon. What I did since back this was announced in October, was use both to get acquainted with VS code. using the same project folders in both That way you can do things like run in VS Code, while still using the app settings editor in eclipse.
Many thanks, I guess I will have to also.
Did I miss something with the new SDK ? Installed, tried to test it (Eclipse and VScode), but what can I build with it ?
You can try your existing apps, and there's some things you can see in the sim or with side loading, in addition to monkey types, which is a compile time thing.
You can do things like stretch/shrink bitmaps to fit the screen. Using the widget template as a base, you can do things like this:
<bitmap id="id_monkey" x="center" y="center" filename="../drawables/monkey.png" scaleX="75%" scaleY="75%" scaleRelativeTo="screen"/>
where the bitmaps is 75% of the screen size on all devices.
Another neat thing is that when you build an app, the launcher_icon is automatically properly sized for the target device.
Remember, this is only a preview and only the 1st, so there are other things still in the works, and you can't use it to build iq files right now. There will also be stuff that will only work on a target device with CIQ 4.0, but there aren't any of those right now.
Ok, thank you Jim for the infos.
Personally, I'm a bit "meh" on VS Code, do you know what was the driving force behind the switch?
I'm guessing because of relative popularity amongst devs, as well as a desire to (somewhat) modernize Connect IQ.
Speaking as someone who switched (professionally) from Eclipse to VS Code, it's like night and day. In terms of usability, there's no comparison, IMO. Eclipse is perceived to be slow, buggy, having a poor UX, etc. for very good reasons. (Also IMO).
(I've also used IntelliJ and I can see why pure Java developers love it compared to Eclipse. For anything other than pure Java development, I'd probably stick with VS Code.)
VS Code isn't perfect, but the choice between Eclipse and VS Code is a no-brainer, IMO. (I'm also speaking as someone who used to be skeptical of VS Code, until I actually used it. I was actually one of the Eclipse apologists who was like "Eclipse isn't *that* bad...")
Anyway, regardless of whether VS Code is "objectively" "better", it makes sense to go where all the devs are.
https://wakatime.com/blog/43-wakatime-2020-programming-stats
(There's actually a lot of other editors in this list that I would prefer over Eclipse, too....)
Personally I can't wait until Monkey C in VS Code has full feature parity with the Eclipse Monkey C plugin, then I never have to open Eclipse ever again.