Connect IQ 1.2.0 SDK beta!

Oh, I misunderstood. You're talking about some type of Date picker or input fields just for date/time in the property settings in GCM or GE. That could be useful, you're right.

Oh, I misunderstood. You're talking about some type of Date picker or input fields just for date/time in the property settings in GCM or GE. That could be useful, you're right.

Exactly that!

Sorry I should have been more clearer.

Exactly that!

Sorry I should have been more clearer.

Apologies! There is a date picker!!!

<setting propertyKey="myDate" title="title_date">
<settingConfig type="date" />
</setting>


Tie this to a number property myDate and there you go!

Thanks GARMIN!

Ok, so after some digging and reading I could not figure out exactly how to test the user configurability.

Then I checked for updates from within Eclipse, and two Connect IQ plugins were listed.

After updating, I noticed this brand new option on the Connect IQ menu: App Settings Editor!

So together with your properties.xml and App Settings Editor, you can now test this!

Sounds like you've got the right idea. :) Since this is a beta, you'll be able to build and test apps that use app settings in the simulator, but we don't yet have a release of Garmin Connect Mobile or Garmin Express that is publicly available to support app settings. This gives developers a chance to learn about the new features and prepare apps ahead of the final 1.2.0 SDK release (which is planned for this month!). Of course, testing on devices is best, and I understand why it may be frustrating to not have this available yet.

The upside is that Garmin has actually offered a beta release, which isn't something we commonly have done in the past!

I would want CIQ guys to make an official statement on this.
isn't it that Usually the older rev SDK, while does include the newer stuff API (which may not be utilised by us / me etc) will end up being outdated and perhaps have some of the APIs stripped out and then developers are asked to always use the latest SDK regardless?

Appreciate the CIQ guys to chime in rather than us debating.

One quick comment before I address the question above. I know a lot of this thread of discussion stems from data field memory use increasing in later SDKs. We're looking at ways to possibly trim back the overhead on data fields to free up some memory.

As far as how we'll handle support for aging devices, here's the plan (taken from the developer blog):

We plan to have a new major version of Connect IQ every year. For every major version, we plan to have four minor releases spaced out across two years. This means a product launched alongside a Connect IQ major version will get two years of maintenance: the first two releases (X.1.z and X.2.z) will have new features, while the later versions (X.3.z and X.4.z) will focus on bug fixes, feature alignment with the next major revision when possible, and maintenance. Releases come out in the first and third quarter of each year. Products that launch with on a major version of Connect IQ may upgrade to the next major version of Connect IQ if they can meet the minimum requirements.

Hopefully that explains things and gives you confidence that we're not going to force obsolescence every time we add new stuff to the API. :)

I have had issues list this on my Mac when I download Connect IQ from Eclipse. When I download from Garmin's site it works. Something about downloading from Eclipse can cause the files to extract incorrectly.

I am going to give it a try, thanks!

Sounds like you've got the right idea. :) Since this is a beta, you'll be able to build and test apps that use app settings in the simulator, but we don't yet have a release of Garmin Connect Mobile or Garmin Express that is publicly available to support app settings. This gives developers a chance to learn about the new features and prepare apps ahead of the final 1.2.0 SDK release (which is planned for this month!). Of course, testing on devices is best, and I understand why it may be frustrating to not have this available yet.

The upside is that Garmin has actually offered a beta release, which isn't something we commonly have done in the past!

It was late last night and there was no one around to tell me to RTFM! :-)

The stuff about configuring the app settings is actually well documented!
Next time I'll start RTFM ;-)

Guess I was too excited when discovering the release of 1.2.0 beta to bother with the documentation.

I am going to give it a try, thanks!

Problem solved!

New developer here! I grabbed the 1.2 SDK, Eclipse, and set everything up. I can run a simple Watch Face app fine.

HOWEVER...the reason I got all this stuff was because Garmin claimed that the 1.2 SDK contained emulators for the Edge 1000 and that I could test stuff out on a real Edge 1000 device with beta firmware. I can't find how to build something to a simulated Edge 1000 from Eclipse...it's not one of the selectable target devices. All I can select are a bunch of watches. I'm just trying to make a "Data field".

Edit: Found my error. I downloaded the 1.1.4 SDK mistakenly. 1.2 works as advertised! :)