Here’s something new to make sure every day doesn’t feel like groundhog day: you can now use custom classes in your code on the Web IDE and you will no longer get tripped up by if else(foo).
class X {
};
// no longer says X does not name a type
void doit(X &x) {
}
bool foo, bar;
void setup() {
X x;
doit(x);
if (bar) {
return;
}
// no longer confuses else if(foo) with a function declaration...
else if (foo)
return;
}
2/7/2017: Bug fixes and improvements to the Web IDE
We care a lot about the way that our tools help you achieve your goals and we know that sometimes the experience can be affected by bugs. This sprint we knocked some off and also added some small improvements.
Web IDE
Fixed: Users could change selected device when a flash was in progress. Sometimes, in a rush, users changed their starred device during a flash, and this caused some minor confusion. You will see a modal if you try this now, so hopefully, no more confusion around.
Fixed: Claiming a device is broken in the Web IDE, as it also loads products. After claiming a device, the list of products was loaded in the list of devices. This doesn’t happen anymore, now only your cool new device will be added to the list.
Fixed: Remember last code a user had open, reopen when they return We want you to be able to get back to your code fast, so after opening an app, next time you go to build.particle.io, you will be presented with the last app you’ve opened.
Fixed: Refresh devices doesn’t show newly claimed devices Claim a device through the CLI or the API? We’ll make sure it shows up when you hit the refresh button in the Devices sidebar.
Improved: Device selection Previously, if you deselected the active device, flash and verify were disabled until you selected a new one. You must now change your device target to another device to “un-select” the original one.
Improved: Console menu item now directs to /logs. Need a quick sneak peek of what your device is telling to the world? Click on the Console icon and we will show you. Not seeing anythings in the logs? Make sure you’re publishing events.
There is a new FAQ that describes how to use Eclipse, a free IDE for Windows, Mac, and Linux, along with OpenOCD, to do source-level debugging of code running on a Particle Photon, P1, or Electron.
Some of the things you can do:
You can see more information about your currently selected device in the bottom right corner of the Web IDE. It contains the following: Last Event Name, Last Event Data, Device Type, Device Name, Device Status, Device Version. Clicking on the lightbulb will signal the device.
Do you use functions or variables in your applications? You are now able to call functions & see the value of variables in Console. You can use the new functionality in two places: On the Devices page / On the devices page of a Product, just click on any device row to expand it and you will see the new view.
3/23/2017: API now sorts device lists by last connection time by default
GET /v1/devices and GET /v1/products/:productIdOrSlug/devices will now sort devices by the last time they connected to the cloud, with the most recently connected appearing first. This will help make it easier to quickly identify and interact with devices that are most active.
Library publish defaults to library in current directory
White list files when uploading library to avoid publishing unnecessary files (only include code files when publishing so you don’t publish .bin, .png, .pdf by mistake)
Cloud
Fix viewing large libraries in the Web IDE
Relax validation rules to allow renamed libraries and header-only libraries
3/31/2017: Major updates to mobile SDKs and support!
iOS - Major update to the cloud SDK (0.6.0) and device setup library (0.7.0), as well as documentation and examples updates.
A very notable community supported 100% pure Swift library for the Particle Cloud SDK - would allow you to create Swift style apps with no compromises and build native apps not just for iOS but also macOS, tvOS, watchOS, Linux and even backend applications using IBM’s Kitura framework!
Android - New app release (1.7) in Google Play Store and many updates to both the Cloud SDK (0.4.2) and device setup library (0.4.3). Expect many more updates and improvements coming to Android support soon.
A common scenario is a need to share your app with other users. From just sharing useful code/examples to basic collaboration. Now you can do this with any of your app in our Web IDE:
After sharing an app revision it will be available for anyone with the link. Note that any changes you make to the app after won’t be visible under the same link (you need to generate link for the new revision). Once you send the link to someone, they’ll be able to see your code, flash it to their devices or copy to their account and make changes:
Hey friends! We have released a new pre-release firmware v0.6.2-rc.1. Available now on https://build.particle.io for Core/Photon/P1/Electron.
This release addresses one very important Enhancement / Bug fix:
[PR #1283][Implements #1278] Restores 0.6.0-style Arduino compatibility by default, full Arduino compatibility when including Arduino.h
We have done extensive testing against all Particle Libraries currently published and if they were not compiling on 0.6.1, they are now compiling once again with 0.6.2-rc.1. Please give it a test and let us know if you find anything not working properly.
As a firmware engineer building a Particle product, it is important that you can rapidly iterate on new device firmwares, while still simulating the behaviors of production devices deployed in the field. Development devices allow you to do just this.
Development devices are special kinds of product devices marked specifically for internal testing, separate from the production fleet. Development devices are prevented from receiving any automatic product firmware updates from the Particle cloud. These devices will ignore both released product firmware as well as any firmware version it has been locked to run.
Mark a device as a development device in the Console, specifically on your product’s devices view:
Once you mark a device as a development device, you will see it marked with a special icon in the “Firmware” column:
Particle and Google Maps can now be used in tandem to easily find and track the location of Particle devices without the need for any additional hardware. Wi-Fi or Cellular networks are collected by a Particle device, and sent to Google’s Geolocation API in exchange for latitude/longitude coordinates.
Check out the tutorial for details on how to get started. To visualize your devices coordinates, check out the open source visualization app provided by the Google Maps team.
Hey friends! We have released a new pre-release firmware v0.6.2-rc.2. Available now on https://build.particle.io for Core/Photon/P1/Electron.
This release addresses one Bug fix and a new Feature:
[PR #1311][Implements CH1537] [Electron] Added support for Twilio SIMs by default in system firmware.
[PR #1310] Fixes a error when <algorithm> has already been included before the math.h header. Now we only include math.h when Arduino compatibility is requested. (math.h was not included in 0.6.0).
Hey friends! We have released a new default firmware v0.6.2. Available now on https://build.particle.io for Core/Photon/P1/Electron.
This release addresses one very important Enhancement / Bug fix, and a new Feature
[PR #1311][Implements CH1537] [Electron] Added support for Twilio SIMs by default in system firmware.
[PR #1283][Implements #1278] Restores 0.6.0-style Arduino compatibility by default, full Arduino compatibility when including Arduino.h
[PR #1310] Fixes a error when <algorithm> has already been included before the math.h header. Now we only include math.h when Arduino compatibility is requested. (math.h was not included in 0.6.0).