• Replies 5 replies
  • Subscribers 22 subscribers
  • Views 1413 views
  • Users 0 members are here
Options
Related

Eclipse -> VS code migration

SylvainMasaki

Hello,

I'm trying to make the migration of my project, but nothing operate even I follow explanation here:

https://developer.garmin.com/connect-iq/connect-iq-basics/your-first-app/

For me, it's not enough clear compare to eclipse setting, is there somewhere a clear and explicit procudure to do it?

Thnaks for your help

Best regards

Sylvain

  • Nothing different actually，just open your project in the vscode. I suggest u not migrate right now. Wait the next non-buggy version

  • in reply to li2niu

    HI,

    Thanks! I'm waiting some update and still continue my developpement with eclipse

  • in reply to SylvainMasaki

    The VS Code stuff actually first came out a year ago, and it's now "feature compatible", meaning you can do the same things as eclipse, but it's a bit different how you do things.  You're going to start seeing things you can't do in eclipse, with using the "f6pro System 5 preview" device being one of them.

  • in reply to jim_m_58

    I hate Eclipse and I'd encourage everyone to move away from it for reasons that have nothing to do Monkey C, but I also understand if people want to stay on it for a little while longer due to any perceived issues. I still need it to use older versions of the CIQ SDK when I want to test existing apps in the store (of course nothing is stopping me from doing that.)

    jim_m_58 said:
    You're going to start seeing things you can't do in eclipse, with using the "f6pro System 5 preview" device being one of them.

    This is a bug IMO. The reason Eclipse won't run the F6Pro System Preview device is because the run dialog has a dropdown setting to "Choose a Target API Level", and 3.3 is missing from the dropdown, which is required for that device, so the device won't run. Yet 4.1 is available, so you can run the Venu 2 System 5 preview.

    IIRC,  said a while back that setting doesn't even do anything and should probably be removed, so I'm wondering if it should be. (There's no equivalent run setting in the VS Code extension). (For example, whether I run FR230 with target API level 1.3.x or 1.4.x, it makes no difference to the value of DeviceSettings.monkeyVersion.)

    The workaround here is to run the app from the command line or terminal after building (or after a failed run). (This requires the simulator to already be running. You can launch the sim from Eclipse using CTRL-6, using Menu > Connect IQ Start Simulator, or by running the app for a different device)

    In Windows:

    - Create a text file called ciq_sim.cmd with the following contents and place it either in your app's bin folder or somewhere in your path:

    for /f "usebackq tokens=*" %%a in (`type %APPDATA%\garmin\Connectiq\current-sdk.cfg`) do "%%a\bin\monkeydo" "%1" "%2"

    - Navigate to your app's bin folder in Command Prompt or PowerShell (Windows Terminal in Windows 11) and type:

    .\ciq_sim.cmd YOUR_APP.prg fenix6prosystem5preview

    In MacOS, just type the following directly into Terminal (or you could also make this into a script):

    "$(cat ~/Library/Application\ Support/Garmin/ConnectIQ/current-sdk.cfg)"/bin/monkeydo YOUR_APP.prg fenix6prosystem5preview

  • in reply to flowstate

    I find Eclipse easier to use with CIQ, but VS Code is the way things are headed.  When I add a folder to the VS Code workspace, it's exactly the same folder as is in my Eclipse Workspace, so it's easy to switch back and forth for most things.  It helps with learning VS Code, as you can fall back to Eclipse if you're having trouble finding/doing something in vs code.