Saturday, September 25, 2010
Friday, September 24, 2010
This release focused on resolving minor bug fixes or crashes. More details about additional changes are available in the svn log of all revisions.
You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel.
If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry
- The overview and sandbox documentation have been updated to reflect changes in the newer versions of the AdWords API.
- The geotargeting codes section have been updated to include the latest information. Province and city codes are now available for all supported countries.
- New code lists for mobile carriers and mobile platforms have been added.
- A listing of the available report fields for each type report have been added. This can act as a supplement to the information provided by the ReportDefinitionService.getReportFields() method.
- The forum has been directly integrated into the documentation for easy access to the knowledge of the AdWords API community.
(View larger image)
We’re always looking for new ways to improve our documentation, so if you have any ideas, let us know on the forum.
- Eric Koleda, AdWords API Team
[Gd] New features for the Chrome Web Store developer preview: Google Checkout integration & previewing for your apps
Chromium Blog: New features for the Chrome Web Store developer preview: Google Checkout integration & previewing for your appsWe’re excited to share with you some new features that we just added to the developer preview of the Chrome Web Store:
Starting today, you can sign up for a Google Checkout merchant account via your developer dashboard. If you’re planning to use Chrome Web Store Payments to charge for apps, you’ll need to complete this setup before you can accept payments. If you already have a merchant account with Google Checkout, you’ll be able to associate it with your items in the store. Signing up for Chrome Web Store Payments is currently available to developers based in the US who have a US bank account. We’re working hard to also enable payments for international developers and will update you with a blog post once we have more details. If you have more questions about setting up your merchant account, see this help article we created.
We also added the ability to see how your app will appear in the store. When you preview an uploaded app, you’ll see our new design of the app’s landing page. As before, your apps are only visible to you during the developer preview until the store launches later this year.
We added several options to help you customize this page with your own header image and a larger icon. You can also upload promotional images for your app now, which will appear as banners whenever your app is featured in the store. To learn more about these new options, we encourage you to read our guidelines about creating good images and icons for apps in the store.
We’ll continue to work on the web store design and add polish, but with today’s launch you can get your app’s landing page ready for the launch. For questions and feedback, we invite you to join our developer discussion group and come back to the Chromium blog for more announcements about the Chrome Web Store.
Posted by Qinming Fang, Software Engineer
Thursday, September 23, 2010
Google is dedicated to making the Internet relevant and useful to Arabic speakers, and to developing meaningful and local products for the Middle East. We fully realise that we cannot foster this growing Internet ecosystem alone, and we therefore believe that tech entrepreneurs and developers have the opportunity to transform the Web for the world and for the Middle East.
So for the first time ever in Egypt and Jordan, Google is very excited to host its Google Days, in Cairo between December 8th and 10th for G-Egypt, and Amman between December 12th and 14th for G-Jordan.
Each day of the 3-day conference will cater to a different audience, spanning computer science students and professors, professional developers, webmasters, entrepreneurs, small businesses and tech marketers. Take a look at our sites (G-Egypt and G-Jordan) to learn more about the G-day that might fit your appetite. You must pre-register on the websites as space is limited - you will then be fully registered as soon as we send you a confirmation.
Some of Google’s best and most engaging engineers, product managers, business managers and leadership will be speaking about Google’s open web and mobile technologies. Attendees will have the chance to interact with Googlers and explore Google’s technologies through a combination of tech talks and breakout sessions. We’re getting ready to make these events fun, insightful and interesting so we hope to see you there !By Sebastian Trzcinski-Clément, Developer Relations for the Middle East and Northern Africa
More details about additional changes are available in the SVN revision log. If you find new issues, please let us know by filing a bug. Want to change to another Chrome release channel? Find out how.
Wednesday, September 22, 2010
Cross-posted from the Lat Long Blog.
We’re sharing some news today that we hope webmasters will find exciting. As you know, we’re constantly working to organize the world’s information - be it textual, visual, geographic or any other type of useful data. From a local search perspective, part of this effort means looking for all the great web pages that reference a particular place. The Internet is teeming with useful information about local places and points of interest, and we do our best to deliver relevant search results that help shed light on locations all across the globe.
Today, we’re announcing that your use of Rich Snippets can help people find the web pages you’ve created that may reference a specific place or location. By using structured HTML formats like hCard to markup the business or organization described on your page, you make it easier for search engines like Google to properly classify your site, recognize and understand that its content is about a particular place, and make it discoverable to users on Place pages.
You can get started by reviewing these tips for using Rich Snippets for Local Search. Whether you’re creating a website for your own business, an article on a newly opened restaurant, or a guide to the best places in town, your precise markup helps associate your site with the search results for that particular place. Though this markup does not guarantee that your site will be shown in search results, we’re excited to expand support for making the web better organized around real world places.
Posted by Carter Maslan, Director of Product Management, Local Search
When Google Chrome Frame went into beta in June, the team set aggressive goals for speed and stability before delivering a stable channel release. We wanted it to start much faster and to reduce crashes by an order of magnitude. After months of polishing, Google Chrome Frame now starts three times faster on Windows Vista and Windows 7 and the most common conflicts with other plug-ins have been fixed.
Thanks in part to how simple it is to enable rendering with Google Chrome Frame, sites like DeviantART, Hootsuite, and github have added support, and Ruby on Rails is making a better-performing, more standards compliant experience the default for all users of Rails apps. Google applications like Orkut, Google Docs, and YouTube have already begun adding Google Chrome Frame support. Gmail and Google Calendar are planning to adopt Google Chrome Frame in the near future to improve performance and ease the transition for users as they drop support for legacy browsers.
A stable release is just the beginning for Google Chrome Frame. We’ve set aggressive goals for future releases: we’re working on making start-up speed even faster and removing the current requirement for administrator rights to install the plug-in. Expect more improvements and features in the near future, as we plan to release on the same schedule as Google Chrome.
We would not have made it this far without strong community support and feedback. The users and contributors to the preview versions have helped improve and shape the product in huge ways. If you’d like to get involved or just see what’s coming soon, you can subscribe to the new beta channel or if you are adventurous, try the dev channel to experience the very latest. The whole team continues to listen to your feedback through our project forum and we look forward to working with you to improve Google Chrome Frame even further.
Posted by Tomas Gunnarsson, Software Engineer and Robert Shield, Software Engineer
Registration opens today for Google Developer Day in Europe and Russia! As you saw from our agenda announcement, they promise to be jam-packed with great speakers and fantastic content.
Register to attend on the following dates, in the following places:
Stay updated on Developer Day news by following us at:
- Germany: Google Produkt Compass blog
- Russia: Developer blog and @gddru
- Czech Republic: Google Česká republika blog and @gddcz
Look forward to seeing you there!By Ben Wallace, Developer Marketing EMEA
[This post is by Dan Galpin, an Android Developer Advocate specializing in games and comics. — Tim Bray]
The Securing Android LVL Applications blog post makes it clear that an Android developer should use an obfuscation tool such as Proguard in order to help safeguard their applications when using License Server. Of course, this does present another question. How should one integrate such a tool with the Android build process? We’re specifically going to detail integrating Proguard in this post.
Before you Begin
You must be running the latest version of the Android SDK Tools (at least v7). The new Ant build rules file included with v7 contains hooks to support user-created pre and post compile steps in order to make it easier to integrate tools such as Proguard into an Android build. It also integrates a single rules file for building against all versions of the Android SDK.
Adding an Optimization Step to build.xml
First, you’ll have to get Proguard if you don’t yet have it.
If you’ve been using Eclipse to do your development, you’ll have to switch to using the command line. Android builds are done using Apache Ant. A version of Ant ships along with Eclipse, but I recommend installing your own version.
The Android SDK can build you a starter build.xml file. Here is how it’s done:
android update project --path ./MyAndroidAppProject
If all works well, you’ll have a shiny new build.xml file sitting in your path. Let’s try doing a build.
You should end up with an unsigned release build. The command-line tools can also sign your build for you. You’ll notice that the android tool created a local.properties file in your directory. It will contain the sdk.dir property. You can have it make you a signed build by adding the location of your keystore and alias to this file.
Copy these files into your root directory (where the build.xml file sits). To add Proguard to your build, you first need to edit your local properties file to add the location of the directory that Proguard is installed in:
Finally... you need to add our script to your build file and have it override a few targets. To do this, we use the XML “entity” construct. At the top of your build.xml file, add an entity that references our script file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE project [
<!ENTITY add-proguard-release SYSTEM "add-proguard-release.xml">
You’re not done yet. Somewhere within the project tag add the reference to our entity to include our script.
<project name="MyProjectName" default="help">
That’s it! In many cases, calling
Will give you an obfuscated build. Now test and make sure that it hasn’t broken anything.
But Wait, My App is Crashing Now
Most crashes happen because Proguard has obfuscated away something that your application needs, such as a class that is referenced in the AndroidManifest or within a layout, or perhaps something called from JNI or reflection. The Proguard configuration provided here tries to avoid obfuscating most of these cases, but it’s still possible that in edge cases you’ll end up seeing something like a
You can make edits to the procfg.txt file to keep classes that have been obfuscated away. Adding:
-keep public class * [my classname]
should help. For more information about how to prevent Proguard from obfuscating specific things, see the Proguard manual. Specifically, the keep section. In the interest of security, try to keep as little of your application unobfuscated as possible.
The standard settings provided in procfg.txt will be good for many applications, and will catch many common cases, but they are by no means comprehensive. One of the things that we’ve done is had Proguard create a bunch of output files in the obf directory to help you debug these problems.
The mapping.txt file explains how your classes have been obfuscated. You’ll want to make sure to keep this around once you have submitted your build to Market, as you’ll need this to decipher your stack traces.
Tools such as Proguard make the binary of your application harder to understand, and make your application slightly smaller and more efficient at the same time, at the cost of making it slightly more challenging to debug problems in the field. For many applications, the tradeoff is more than worthwhile.
Tuesday, September 21, 2010
In addition to making your app easier to use, OpenID can improve security for applications by reducing the number of places you need to enter a password. Of course, it’s also important to strengthen the security of the places you are entering your password, and yesterday’s launch of Two-step verification does just that.
Until yesterday, Google Apps customers using Google Apps’ built-in authentication mechanisms needed to provide a username and password (something they knew) to log in. Our launch of 2-factor authentication, which we’re calling Two-step verification, enables users of Premier, Education and Government Editions to additionally require having something in possession- a mobile phone- to log in.
So, if you’re a Marketplace developer and your customer asks you if your app supports 2-factor auth, you can answer an emphatic “yes” and send them over to the Marketplace to add your app to their domain.
Posted by Ryan Boyd, Google Apps Marketplace Team
Want to weigh in on this topic? Discuss on Buzz
The Google Chrome team is hitting the road. From now through October, we’re giving 21 talks about HTML5 and related Google Chrome topics at 16 events, in 16 cities and 9 countries, and on 4 continents. Phew!
Check out our schedule below. Registration for almost all these events is open, so come say hi and learn more about HTML5.
|9/24||Atlanta, United States||Web Directions USA||HTML5||Michael Mahemoff|
|9/25||San Francisco, United States||TechCrunch Disrupt Hack Day||Chrome Web Store||Seth Ladd|
|9/26||Berlin, Germany||JSConf EU||HTML5||Paul Irish|
|9/28||Tokyo, Japan; Kyoto, Japan||Google Developer Day Japan (Japanese)||Installable Web Apps, Google Chrome Extensions, Google Chrome Developer Tools||Eiji Kitamura, Mikhail Naganov, Alexei Masterov|
|9/29||New York, United States||NYC GTUG Meetup||Chrome Web Store||Jan Kleinert|
|10/1||Taipei City, Taiwan||Google DevFest Taiwan||HTML5||Arne Roomann-Kurrik|
|10/2||New York, United States||Open Video Conference||HTML5||Paul Irish|
|10/5||Hong Kong Island, Hong Kong||Google DevFest Hong Kong||HTML5||Arne Roomann-Kurrik|
|10/8||Amsterdam, Netherlands||Fronteers Conference||HTML5||Paul Irish|
|10/8||Jakarta, Indonesia||Google DevFest Indonesia||HTML5||Arne Roomann-Kurrik|
|10/9||Hilversum, Netherlands; San Francisco, United States||HTML5 Game Jam||HTML5||Marcin Wichary, Paul Irish|
|10/9||Los Altos Hills, United States||Silicon Valley Code Camp||HTML5, Installable Web Apps, Google Chrome Extensions, Chrome Web Store, Native Client||Eric Bidelman, Ernest Delgado|
|10/10||Bangkok, Thailand||Google DevFest Thailand||HTML5||Arne Roomann-Kurrik|
|10/15||Aizu-Wakamatsu City, Japan||Aizu IT Forum (Japanese)||HTML5||Eiji Kitamura|
|10/16||Boston, United States||jQuery Boston Conference||HTML5||Paul Irish|
|10/29||São Paulo, Brazil||Google Developer Day Brazil||HTML5, Installable Web Apps, Google Chrome Extensions, Chrome Web Store, Google Chrome Developer Tools, Native Client, Google Chrome Frame||Eric Bidelman, Ernest Delgado|
Posted by Brian Kennish, Developer Advocate
Monday, September 20, 2010
Today, we’re taking themes one step further. Each theme now has ads rendered with a different look and feel to match the overall style used for the search results.
The outcome is harmony between search results and ads, which we think makes for a great user experience. The following screenshots are examples of search results and ads rendered with three different themes - espresso, minimalist and green sky.
We hope you agree that your visitors will enjoy themed ads. As always, be sure to send us your feedback.
Posted by: Ben Lisbakken, Software Engineer and John Skidgel, Senior Interaction Designer