Direct download of windows SDK or assistance with sdk manager

So I downloaded the sdk manager and it says it has downloaded the sdk  and downloaded the device type I want to try and make apps and faces for but I can't go any further....  The image attached is as far as I am able to go... Please explain what I am doing wrong  and if possible a Direct download would be help full for windows... And yes I HAVE JAVA INSTALLED!!!!

thank you

Crags

  • While you can use the command line interface, you probably want to use Eclipse of VS Code.  Eclipse had been used with CIQ for years, and VS Code is still being developed.

    See https://developer.garmin.com/connect-iq/sdk/ as once you install eclipse, you need the CIQ plugin

    Also, check out https://developer.garmin.com/connect-iq/connect-iq-basics/getting-started/

  • I am unsure what you  mean and that still didn't explain what my issue with downloading the SDk is...

  • You've downloaded the SDK and devices.  You just need something to use them.  The "X" next to the SDK version indicated you have it downloaded, and the grayed out "Current SDK" indicates it's your current one.

    Look in /users/(you)/AppData/roaming/Garmin/connectiq, and you'll see a devices and SDK folder

  • As Jim said, you've already downloaded the SDK. The SDK manager is only for downloading the SDK and devices.

    In order to develop Connect IQ apps, you need to use an IDE which has support for Monkey C (the CIQ language) and the Connect IQ SDK.

    Garmin supports the following IDEs for Connect IQ development:

    - Eclipse (https://www.eclipse.org/downloads/)

    and

    - Visual Studio Code (https://code.visualstudio.com/)

    Once you've installed one of these IDEs, the next step is to install the Connect IQ plugin or extension which provides support for CIQ/Monkey C within the IDE (e.g syntax highlighting, building, etc.)

    - Eclipse: Follow instructions here (Install the Eclipse Plug-in): https://developer.garmin.com/connect-iq/sdk/

    - Visual Studio Code: Install Monkey C extension from here: [https://marketplace.visualstudio.com/items?itemName=garmin.monkey-c]

    I would personally recommend VS Code unless you are already comfortable (and happy) with Eclipse. However, as Jim pointed out, Garmin's support for CIQ in Visual Studio Code is incomplete. Notably, debugging is not supported. (I have rarely used the debugger in Eclipse, though.)

    As Jim mentioned, there is also a 3rd option if you don't want to use either of Eclipse or Visual Studio Code: you can build apps from the command line by directly running various SDK commands. This is not recommended for beginners as it's not documented (IIRC), so you would have to figure things out by running the various actions (e.g. build) in VS Code or Eclipse anyway, and observing what commands are run. However, the command line can be useful for automating builds for multiple projects (for example).

  • Thank you for the  reply... very helpful..... I am not familiar with either so which would be the simplest? 

  • Eclipse is complete, as been around for years, and simpler in many ways for CIQ.  Also, it's what in the documentation.  I'd never used Eclipse when I started and was able it pick it up fairly quickly.  VS Code is still considered alpha/beta.

  • Thank you for the response..... Also my apologies if I came across a bit ungrateful.... I am happy for the advise and help...

    regards 

    Crags

  • TL;DR on an individual basis, some people may prefer Eclipse over VS Code. But as far as I can tell, the big picture is that VS Code is much more popular than Eclipse. (Otherwise why would Garmin switch focus?)

    I can also see why some people would dislike/hate VS Code (I have my own issues with it), but my personal opinion is that VS Code is still better than Eclipse, and if I had to choose between the two, I would pick VS Code. If you ever want to do any other kind of dev work (even just for fun), VS Code is much more of a "industry standard" now compared to Eclipse.

    Source: I am a full-time dev who once used Eclipse every day, and now uses VS Code every day. I wouldn't switch back if you paid me to. For further context, I used to tell my coworkers how great Eclipse was (when we used to standardize on something that was worse.) Things change and tools evolve, but Eclipse hasn't evolved (IMO).

    You could try both and see which one you like better. Keep in mind that, supposedly, Connect IQ support for Eclipse will eventually by phased out, so VS Code will be the supported CIQ environment in the future.

    Then again, the VS Code Monkey C plugin still has several bugs and limitations compared to the Eclipse CIQ plugin, so there is that.

    Eclipse is complete, as been around for years, and simpler in many ways for CIQ.  Also, it's what in the documentation.  I'd never used Eclipse when I started and was able it pick it up fairly quickly.  VS Code is still considered alpha/beta.

    I disagree that VS Code is considered alpha/beta. I'd like to see a citation for that, as while Microsoft does have Alpha builds for VS Code, it also releases stable versions regularly, and the stable version is what you get when you go to the website.

    It's also been around for 6 years, and the current version is 1.58.2. (Typically "pre-release" software has 0 as the first version component.)

    Yes Eclipse has been around for 19 years, but the flipside of that is it rarely changes or improves (as you said, it's "complete"). I haven't noticed any differences in the last 5 years or so. On the other hand, VS Code is constantly adding new features.

    Facts/observations:

    - VS Code was the most popular dev environment according to a stackoverflow survey in 2019 (chosen by 50% of respondents). Eclipse came in 7th place (with a 14.4% share): [https://insights.stackoverflow.com/survey/2019#development-environments-and-tools]

      - To put this in perspective, Eclipse lost out to Vim (25.4%), a 30-year old clone of a 45 year old editor whose interface hasn't changed significantly since the beginning.

    - In a 2019 CIQ dev summit video, Garmin themselves stated that they switched from Eclipse to VS Code because Eclipse is too complex (which resulting a high barrier to entry, for new devs).

    Unfortunately I don't have a link to this video (which is apparently unlisted on youtube), but you have to ask yourself why Garmin would switch focus from Eclipse to VS Code, unless they perceived some sort of benefit either for themselves or for developers (which also benefits them by attracting more devs).

    - One advantage to popularity (regardless of whether that popularity is "valid" or not), is widespread 3rd-party support. For instance, there are several useful VS Code plugins which just aren't available for eclipse.

    For example, this plugin has 3 million downloads: [https://marketplace.visualstudio.com/items?itemName=CoenraadS.bracket-pair-colorizer-2]

    I was able to find equivalent plugins to the above for other popular editors like Sublime and Intellij, but not for Eclipse.

    - Several people on these forums, including Garmin employees, have expressed that they like VS Code. Others have outright stated that they hate Eclipse (but that's just their opinion, of course.)

    One example:

    https://forums.garmin.com/developer/connect-iq/f/discussion/164015/eclipse-code-formatting-code-completion/893546#893546

    My personal opinion/experiences:

    - The usability of Eclipse is terrible. Even when Eclipse and VS Code do similar things, I've personally found that VS Code does them better. (Such as filtering open editors by name or searching for commands by name.)

    Furthermore, VS Code can do a lot of things that Eclipse can't (like edit with multiple cursors, outside of the context of rectangular selection.)

    - VS Code isn't perfect, but I'm a full-time dev, and I don't know anyone at a modern company who prefers Eclipse over other modern IDEs such as VS Code or IntelliJ (which, like Eclipse, is primarly focused on Java development). I mention IntelliJ because it's also roughly 20 years old, but unlike Eclipse, it's still evolving and improving, and therefore people still like to use it (IMO). (IntelliJ came 4th with a 25% share in the stackoverflow survey). For example, IntelliJ also supports multiple cursors (outside of rectangular selection.)

    I will say that the Monkey C plugin for VS Code is def not complete, and it could use a lot of usability tweaks. But that doesn't really reflect on VS Code itself.

  • I will say that the Monkey C plugin for VS Code is def not complete, and it could use a lot of usability tweaks. But that doesn't really reflect on VS Code itself.

    And this topic is about VS Code and Eclipse in relation to CIQ, not in general.  For someone that uses neither and is just starting with CIQ, today I'd recommend Eclipse.

    When the "usability tweaks" happen with VS Code, my recommendation may change.

  • FWIW, VSCode on Mac is definitely Beta! I spent a day unsuccessfully attempting to migrate from Eclipse. There are also some documented limitations around the sim.

    I'm going to leave it for 12 months before trying again.

    I think the principle is good, I just haven't got time to debug anyone's code but my own!