Documentation for settings / resources

Former Member over 8 years ago

I used this great page https://developer.garmin.com/index.p...garmin-devices for finding out what directories to use for settings for what watch.

The above page is out of date - it doesn't contain vivoactive 3

The page that should really contain all the information about resources: https://developer.garmin.com/connect...urce-compiler/ doesn't have any of this information at all.

Can anyone help? At the moment, I am just trying to find out how to create resources for vivoactive 3. Long term - are all the folder names documented somewhere?

If if a specific directory doesn't exist for Va3, then which one is it using? Is there a page that lists all the watches resolutions and shapes and colour and feature capabilities?

(it's like hitting your head against a concrete wall)

Thank you kindly

jim_m_58 over 8 years ago

The page you reference is a bit outdated and missing a few devices - it's from the Summit last April. Have you looked in the Programmer's guide in the 2.3.4 SDK (it's in the top level ove the SDK when it's installed and available from the ConnectIQ menu in eclipse).

But for the va3, it's
resources_vivoactive3

You can also use families, so
resources-round-240x240

could be used for all round devices with a 240x240 resolution. (va3, approach S60, Fenix 5, 935, etc)

The "resources" part is standard, and there are a number of variations after that, like specific device, family, and language

2.4.0 introduces "Jungles", but there's no need to switch to that. (the beta just came out)

Former Member over 8 years ago

To find the name to use for a device, I look at the manifest.xml file. After you add the device as one to support, the manifest.xml shows you the device name you need to reference.

As an example:
<iq: Products>
<iq???????: Product id="vivoactive_hr"/>
<iq???????: Product id="vivoactive3"/>
</iq???????: Products>

Then just add resources_ before it and bingo, you are good to go.

Former Member over 8 years ago

For future reference NightHawk, you can always look in the devices.xml file included in the bin/ directory of the SDK. Each <device> should contain the device ID and an associated family.

Former Member over 8 years ago

True, since I use Eclipse, the manifest.xml is there for the project I am working on and always has the devices I am currently aiming for. Just simpler for me. To each their own.