If you use Google Chrome and like to live on the edge, you might want to try Chrome Canary, which almost every day has a new version, as it gets the latest features on daily basis. Of course, because it's built every day, sometimes it's not very stable and it falls right off the leading edge it's balanced on.
Now, the Chrome team in the most recent Canary builds have added cool new features to the developer tools section -- specifically, you can now test mobile environments by simulating different screen sizes and by emulating touch events using the mouse. If you haven't visited Chrome's developer tools before, you might be pleasantly surprised at all the nifty things available there.
These features are on the Settings page of developer tools. To get to developer tools, click the Wrench in Chrome, then choose Tools > Developer Tools.
Now on to context. This little open source library is now avilable and let you add "context menus" to a Google Maps API application. Here's a sample of what that looks like:
Also, in other Google developers news, Google announces that in the upcoming weeks, some of the older "Android C2DM" Client Login authentication keys will expire. "If you generated the token you're currently using to authenticate with the C2DM servers before October 2011, it will stop working," posted Adnroid Developers team.
"If the response from the C2DM servers contains an Update-Client-Auth header, you'll need to replace the current token with the one included in the header."
The team suggest that you start using the Update-Client-Auth response header to update tokens regularly, as keys will expire periodically from now on. "For example, have a look at the Chrome to Phone service hosted on code.google.com; this code takes care of authenticating via Client Login and then sending a message," explains the team.
"Alternatively, you can manually generate a new Client Login token now and replace the one currently in use. ClientLogin can be used with any application that can make an HTTPS POST request. The POST request should be structured as a form post with the default encoding application/x-www-form-urlencoded," the team explained.
If your request fails or if you are prompted for captchas, please read ClientLogin for Installed Applications.