Pebble Developer Blog

The time has almost come for Pebble Classic and Pebble Steel to get firmware 3.x!

This is great news for users who get access to all the improvements and fixes since 2.x, as well as new features such as timeline, Quiet Time, no more eight app limit, Standby Mode, and last but not least one new color (gray)!

But let us not forget about Basalt and Chalk app developers, who also have a lot to get excited about - a huge new user base of Aplite watch wearers!

This blog post aims to help developers using SDK 2.x features and APIs to migrate their apps to a single 3.x codebase. As well as bringing compatibility to all older watches when they upgrade to firmware 3.x, these changes will also serve to remove a lot of complex and ugly conditional code that has needed to exist in the meantime. Let's fix some apps!

In the last Tips and Tricks blog post we looked at drawing transparent images on both the Aplite and Basalt platforms.

This time around, we will look at a wscript modification that can allow you to build a Pebble project when you have two completely separate sets of C source files; one set for Aplite, and another for Basalt.

Note: This technique can be applied only to local SDK projects, where access to wscript is available. This means that it cannot be used in CloudPebble projects.

Ever wondered how to draw transparent images in a Pebble app? This post will walk you through the process.

In this post, we'll be using a sample image with a transparency component, shown below: