Saturday, March 5, 2011

[Gd] AdWords API v201101 launch -- providing enhanced reporting, generic selectors, support for filtering and more

| More

AdWords API Blog: AdWords API v201101 launch -- providing enhanced reporting, generic selectors, support for filtering and more

We’re pleased to announce the launch of AdWords API v201101, which allow you to more efficiently run reports, as well as implement campaign experiments and other recently released advertising features at scale. Through the AdWords API forum and developer events we’ve heard frequent requests for the newly available services. We’ve highlighted some of the new features below. A complete list of changes is available in the v201101 release notes.

v201101 highlights:
  • Easily run reports across clients: ReportDefinitionService now supports My Client Center (MCC) cross-client reports, which are fetched asynchronously. The ReportDefinition type has two new fields with which you specify retrieval of a cross-client report, and all report types have new fields for use in cross-client reporting. In addition, the following new reports have been added: Geo Performance, Demographic Performance, Ad Extensions Performance,  Destination URL and Creative Conversion. See Report Types for more information.
  • Greater data control and filtering with a single generic selector: The get operations for a number of services now use a single generic selector, rather than service-specific selectors. The generic selector provides more control over the data returned, lets you filter on almost any field, and specify sorting and paging. For information about migrating your code, see the Selector Migration Reference.
  • Try out campaign experiments: A campaign can now try out sets of ads experimentally by using the ExperimentData in the AdGroupAd type. A new set of report fields provide information about how an advertiser experiment performed. The Ad Group Performance, Campaign Performance, Keywords Performance, and Managed Placements Performance reports each have a field that lets you segment on the control arm or experiment arm. In addition, a report field for each statistic indicates the significance in the change of that statistic in the experiment arm. For more information about campaign experiments, see the AdWords Campaign Experiments overview.
  • Differentiate locations for desired targeting: A new setting for the Campaign type --  GeoTargetTypeSetting -- lets you specify how to apply geo targeting. The setting lets you differentiate between the user’s physical location and the location that’s targeted in the search. 
  • Run interest-based advertising at scale (coming soon): Adwords API will fully support interest-based advertising via the ConversionTrackerService, which enables you to create a new conversion event and get the Javascript tag to create new lists. This service will be released in the coming weeks.
Deprecation timeline for previous versions
With the release of equivalent functionality in v201101, the following versions and services will be deprecated:
  • API versions v13 (ReportService and TrafficEstimatorService only), v200909, v201003, v201008
  • BidLandscapeService (being moved to the DataService)
We will be sunsetting these versions and services in August 2011.

As with every new version of the AdWords API, we encourage you to review the resources in the AdWords API client libraries. If you have any questions please post them on the AdWords API forum.

Posted by Katie Wasilenko, AdWords API Team
URL: http://adwordsapi.blogspot.com/2011/03/adwords-api-v201101-launch-providing.html

Friday, March 4, 2011

[Gd] Something old, something new: Technology meets tradition for the Royal Wedding

| More

Google App Engine Blog: Something old, something new: Technology meets tradition for the Royal Wedding

[Cross-posted from the Europe Developer Blog]


As you may have heard, the UK is gearing up for a very special wedding on April 29, when Prince William and Catherine Middleton will be married in Westminster Abbey in London.


Unlike many previous Royal Weddings, this event will have its own website – and we're honoured that St. James’s Palace has chosen to use Google’s computing infrastructure to power the site.


The site, which just went live at www.officialroyalwedding2011.org, is hosted on Google App Engine, which allows developers easily to build and host their web applications on Google's own computing infrastructure. It's a great way to run apps quickly, more securely, and at scale, which makes it ideal for such an important national occasion. The site will be regularly updated by St. James’s Palace in the run up to the wedding day.


This was a great team effort between Accenture, who built the site, the web design agency Reading Room who led on the design and creative work, and the App Engine team.


We hope it proves to be the perfect marriage of tradition and modernity as we approach the big day.

URL: http://googleappengine.blogspot.com/2011/03/something-old-something-new-technology.html

[Gd] Chrome OS Beta Channel Update

| More

Google Chrome Releases: Chrome OS Beta Channel Update


The Chrome OS Beta channel has been updated to R10 release 0.10.156.46 including the new Chrome 10 Beta, new trackpad and several stability and functional improvements over the previous release. This release contains the following security fixes:
  • Scratchpad application security vulnerability fix
In addition to all Chrome 10 new features (see Chrome 10 blogpost), there are several Chrome OS great improvements including:  
  • 3G modem activation fixes 
  • 3G connection to the carrier fixes 
  • Wi-Fi connectivity/Out of the Box fixes 
  • New trackpad and sensitivity setting adjusted
  • Auto update engine and debugging improvements 
  • Power optimizations 
  • GTalk video/chat optimizations
  • Audio CPU utilization improvements 
  • Improved on screen indicators: brightness, network status, update icon
There is one known issue:
  • [Bug 12085] Audio does not pick up until browser refresh upon lid re-open
You can find full list of fixes that are in Chrome OS R10 in the chromium-os bug tracker . If you find new issues, please let us know by visiting our help site or filing a bug.
Josafat Garcia
Google Chrome 
URL: http://googlechromereleases.blogspot.com/2011/03/chrome-os-beta-channel-update.html

[Gd] Beta Channel Update

| More

Google Chrome Releases: Beta Channel Update


The Chrome Beta channel has been updated to 10.0.648.127 for all platforms.  This release fixes the following issue:
  • [Bug 74709] Clicking "Disable individual plug-ins" in Options causes crash
Full details about the Chrome 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.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/03/beta-channel-update_03.html

[Gd] Beta Channel Update

| More

Google Chrome Releases: Beta Channel Update

The Chrome Beta channel has been updated to 10.0.648.126 for all platforms.  This release contains stability improvements and UI tweaks. There is one known issue:

  • [Bug 74709] Clicking "Disable individual plug-ins" in Options causes crash

Full details about the Chrome 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.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/03/beta-channel-update.html

Thursday, March 3, 2011

[Gd] Fragments For All

| More

Android Developers Blog: Fragments For All

[This post is by Xavier Ducrohet, Android SDK Tech Lead. — Tim Bray]

A few weeks ago, Dianne Hackborn wrote about the new Fragments API, a mechanism that makes it easier for applications to scale across a variety of screen sizes.

However, as Dianne noted, this new API, which is part of Honeycomb, does not help developers whose applications target earlier versions of Android.

Today we’ve released a static library that exposes the same Fragments API (as well as the new LoaderManager and a few other classes) so that applications compatible with Android 1.6 or later can use fragments to create tablet-compatible user interfaces.

This library is available through the SDK Updater; it’s called “Android Compatibility package”.

URL: http://android-developers.blogspot.com/2011/03/fragments-for-all.html

[Gd] GPU acceleration + old drivers = :(

| More

Chromium Blog: GPU acceleration + old drivers = :(

Over the last few months, we’ve made a lot of progress using graphics hardware (commonly referred to as the GPU) to make Chrome faster and more power-efficient. However, as we’ve rolled out features like WebGL and GPU-accelerated HTML5 video, we noticed a troubling trend: users with old graphics drivers experienced a significant increase in crashes when using these features. Because stability is one of Google Chrome’s core principles, we’ve recently become stricter about requiring up-to-date drivers and graphics hardware by adding ranges of old drivers to Google Chrome’s software rendering list.

Developers should continue to ensure that the software-rendered version of their sites work properly for users without GPU-accelerated browsers, so we expect most content to continue to function normally for Google Chrome users with out-of-date drivers -- albeit, without the same performance you might expect from Chrome. WebGL content on out-of-date systems will currently not display, but we are working to provide a software path so that these systems can run basic 3D applications.

As our ability to determine whether a machine can reliably use GPU features improves, we hope to extend hardware acceleration support to more and more users. Here are some steps you can take to maximize the chances that Chrome will run fully hardware-accelerated on your computer:

  1. Use the latest major version of your operating system (such as Windows 7 or Mac OS 10.6)
  2. Install all system updates and driver updates that are available for your system.

Posted by Henry Bridge, Product Manager
URL: http://blog.chromium.org/2011/03/gpu-acceleration-old-drivers.html

Wednesday, March 2, 2011

[Gd] Press Start: launching Google Game Developer Central

| More

The official Google Code blog: Press Start: launching Google Game Developer Central

Today, the annual Game Developers Conference (GDC) officially kicks off in San Francisco. From browser technologies to cloud storage solutions, Google has many products and services that can be useful to game developers. Until now, it was hard for developers to track down information on how Google can help them build, distribute and monetize their games. This is why we are excited to release Google Game Developer Central.


Google Game Developer Central provides an overview of Google products and services that are particularly relevant to game developers. You’ll be able to explore different platforms like Chrome, learn about technologies such as GWT, WebGL and HTML5, and check out monetization options like AdMob.

This is just the first iteration of Google Game Developer Central. In the next few months, we plan to add additional content to make this an even better resource for all game developers. If you’d like to give us feedback on how to improve the site, please join our developer forum or for those of you at GDC, stop by our booth on the expo floor. We look forward to meeting you in person!



By Ian Ni-Lewis, Game Developer Relations Team
URL: http://googlecode.blogspot.com/2011/03/press-start-launching-google-game.html

[Gd] Mentoring organization applications now being accepted for Google Summer of Code!

| More

The official Google Code blog: Mentoring organization applications now being accepted for Google Summer of Code!

(Cross-posted from the Google Open Source Blog.)


Interested in finding bright, enthusiastic new contributors to your open source project? Apply to be a mentoring organization in our Google Summer of Code program. We are now accepting applications from open source projects interested in acting as mentoring organizations.

Now in its 7th year, Google Summer of Code is a program designed to pair university students from around the world with mentors at open source projects in such varied fields as academia, language translations, content management systems, games, and operating systems. Since 2005, over 4,500 students from 85 countries have completed the Google Summer of Code program with the support of over 300 mentoring organizations. Students earn a stipend for their work during the program, allowing students to gain exposure to real-world software development and an opportunity for employment in areas related to their academic pursuits, thus “flipping bits, not burgers” during their school break. In return, mentoring organizations have the opportunity to identify and attract new developers to their projects and these students often continue their work with the organizations after Google Summer of Code concludes.

This year we’re excited to expand the scope of the program by encouraging experienced Google Summer of Code mentoring organizations to refer newer, smaller organizations they think could benefit from the program to apply to be mentoring organizations.

The deadline for applying to be a mentoring organization for Google Summer of Code is Friday, March 11th at 23:00 UTC (3pm PST). The list of accepted organizations will be posted on the Google Summer of Code site on Friday, March 18th. Students will then have 10 days to reach out to the accepted organizations and discuss their ideas before we begin accepting student applications on March 28th.

Please visit our Frequently Asked Questions page for more details. You can also check out the Mentor Manual and timeline for additional information. Good luck to all of our mentoring organization applicants!


By Stephanie Taylor, Open Source Team
URL: http://googlecode.blogspot.com/2011/02/mentoring-organization-applications-now.html

[Gd] Introducing Expletus

| More

Google Web Fonts: Introducing Expletus

Q: What inspired you to create the font?

It was a single x in a logo that started me off, but it was largely a search for my own opinions in type design so in a way you could say Expletus Sans was 'self-inspired'.

Q: Did you try to accomplish something specific with this font, and did you succeed?

I wanted to create a look that was completely different from everything I knew. I feel like I definitely succeeded in this.

Q: What kinds of documents are most appropriate for this font?

It could be used for anything that needs a good dose of elegance. I would personally love to see it in identity work.

Q: Designing a new font is a long journey. What inspires you to keep motivated throughout all the different stages?

Ones I put my mind to something, I finish it. With designing a typeface I feel like I have no choice. Once I've started, I get obsessed with perfection. Apart from that, it was the many great responses I got on the internet on my work that kept me motivated.

Q: What is your favourite part of the type design process, and why?

The very beginning. Trying to work out the basic lines of a concept and see the skeleton of the typeface emerge. It pleases me most, because it's the fastest and most rewarding process. After that it's months of tiny little details.

Q: Can you recommend how other type designers can learn the skills involved in making a font like this?

Start drawing or straight on the computer and post your work on as many type-related websites as you can think of. Take your time to read through feedback and never dismiss an idea before you have seen it. Don't give yourself a deadline. You'll never make it in time.

Q: What are your favourite fonts, and why?

All fonts by Robert Slimbach, because of his brilliant eye for perfection. Dolly, because of it's comfortable, yet fresh feel. The Centro superfamily, for excellence throughout all styles. Many more, for even more different reasons.

Q: What do you think could be improved about the type design process?

Multiple Master should be used more extensively and automated processes like iKern are underrated.

Q: How do you feel about publishing your font as an open source project?

It just happened to me. I never particularly thought about it, until you knocked at my door. It seems like a good way to start and increases the chance of seeing my work in use. I feel like it gives me the chance to make the world just a little bit more beautiful and let others enjoy that too, without charge.


Posted by Dave Crossland
URL: http://googlewebfonts.blogspot.com/2011/03/introducing-expletus.html

[Gd] Introducing Expletus

| More

Google Web Fonts: Introducing Expletus

Q: What inspired you to create the font?

It was a single x in a logo that started me off, but it was largely a search for my own opinions in type design so in a way you could say Expletus Sans was 'self-inspired'.

Q: Did you try to accomplish something specific with this font, and did you succeed?

I wanted to create a look that was completely different from everything I knew. I feel like I definitely succeeded in this.

Q: What kinds of documents are most appropriate for this font?

It could be used for anything that needs a good dose of elegance. I would personally love to see it in identity work.

Q: Designing a new font is a long journey. What inspires you to keep motivated throughout all the different stages?

Ones I put my mind to something, I finish it. With designing a typeface I feel like I have no choice. Once I've started, I get obsessed with perfection. Apart from that, it was the many great responses I got on the internet on my work that kept me motivated.

Q: What is your favourite part of the type design process, and why?

The very beginning. Trying to work out the basic lines of a concept and see the skeleton of the typeface emerge. It pleases me most, because it's the fastest and most rewarding process. After that it's months of tiny little details.

Q: Can you recommend how other type designers can learn the skills involved in making a font like this?

Start drawing or straight on the computer and post your work on as many type-related websites as you can think of. Take your time to read through feedback and never dismiss an idea before you have seen it. Don't give yourself a deadline. You'll never make it in time.

Q: What are your favourite fonts, and why?

All fonts by Robert Slimbach, because of his brilliant eye for perfection. Dolly, because of it's comfortable, yet fresh feel. The Centro superfamily, for excellence throughout all styles. Many more, for even more different reasons.

Q: What do you think could be improved about the type design process?

Multiple Master should be used more extensively and automated processes like iKern are underrated.

Q: How do you feel about publishing your font as an open source project?

It just happened to me. I never particularly thought about it, until you knocked at my door. It seems like a good way to start and increases the chance of seeing my work in use. I feel like it gives me the chance to make the world just a little bit more beautiful and let others enjoy that too, without charge.


Posted by Dave Crossland
URL: http://googlewebfonts.blogspot.com/2011/03/introducing-expletus.html

[Gd] Changes to minimum password length for Google Apps accounts

| More

Google Apps Developer Blog: Changes to minimum password length for Google Apps accounts

As part of our continuous efforts to help our users protect their information, we recently launched 2-step verification for all Google accounts. Starting March 14, we will also increase the minimum password length requirement for Google Apps accounts from 6 characters to 8.

This new policy aligns Google Apps accounts with consumer accounts that already require passwords to be at least 8 characters long.

Existing users can keep their current password even if it doesn’t match the new security requirements, but they will be required to comply when changing their password for the first time. Administrators will also need to comply when resetting passwords for users.

With this change, passwords set via the Google Apps Control Panel from March 14 will need to be at least 8 characters long. Calls to the Provisioning API that try to set a user's password that is shorter than 8 characters will also fail with an InvalidPassword error message. For more information on how to programmatically manage user accounts, please check the Provisioning API Developer’s Guide.

Posted by Claudio Cherubino, Google Apps APIs Team

Want to weigh in on this topic? Discuss on Buzz

URL: http://googleappsdeveloper.blogspot.com/2011/03/changes-to-minimum-password-length-for.html

[Gd] [Libraries][Update] MooTools 1.3.1

| More

Google AJAX API Alerts: [Libraries][Update] MooTools 1.3.1

MooTools has been updated to 1.3.1
URL: http://ajax-api-alerts.blogspot.com/2011/03/librariesupdate-mootools-131.html

Tuesday, March 1, 2011

[Gd] Dev Channel Update

| More

Google Chrome Releases: Dev Channel Update

The Dev channel has been updated to 11.0.686.0 for All platforms

All
  • Updated V8 - 3.1.6.1
  • Accelerated compositing turned on by default (use --disable-accelerated-layers to disable).
  • Fixed a bug affecting the bookmark manager and other extensions. (Issue 43448)
  • FTP: fixed a compatibility issue. (Issue 72060)
Windows
  • GPU acceleration and WebGL disabled for Windows XP
  • Windows Restart Manager restores Chrome on update-triggered restarts. (Vista/2008+).
Mac
  • Fix bugs related to the new infobar UI (Issue 73357) and Issue 73590))
Known Issues
  • HTML5 videos don't play on Vimeo.com (Issue 74451)
  • Gmail renders with narrower lines.

More details about additional changes are available in the 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

Karen Grunberg
Google Chrome
URL: http://googlechromereleases.blogspot.com/2011/02/dev-channel-update_28.html

[Gd] Stable Channel Update

| More

Google Chrome Releases: Stable Channel Update

The stable channel has been updated to 9.0.597.107 for all platforms. This release contains the following security fixes.

Security fixes and rewards:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

Congratulations to the diverse range of researchers featuring in this patch. We’re pleased to announce that the Chromium Security Rewards program has now crossed $100,000 of rewards.

  • [$1000] [54262] High URL bar spoof. Credit to Jordi Chancel.
  • [$500] [63732] High Crash with javascript dialogs. Credit to Sergey Radchenko.
  • [$1000] [68263] High Stylesheet node stale pointer. Credit to Sergey Glazunov.
  • [$1000] [68741] High Stale pointer with key frame rule. Credit to Sergey Glazunov.
  • [$500] [70078] High Crash with forms controls. Credit to Stefan van Zanden.
  • [$1000] [70244] High Crash in SVG rendering. Credit to Sławomir Błażek.
  • [64-bit Linux only] [70376] Medium Out-of-bounds read in pickle deserialization. Credit to Evgeniy Stepanov of the Chromium development community.
  • [$1000] [71114] High Stale node in table handling. Credit to Martin Barbella.
  • [$1000] [71115] High Stale pointer in table rendering. Credit to Martin Barbella.
  • [$1000] [71296] High Stale pointer in SVG animations. Credit to miaubiz.
  • [$1000] [71386] High Stale nodes in XHTML. Credit to wushi of team509.
  • [$1000] [71388] High Crash in textarea handling. Credit to wushi of team509.
  • [$1000] [71595] High Stale pointer in device orientation. Credit to Sergey Glazunov.
  • [71717] Medium Out-of-bounds read in WebGL. Credit to miaubiz.
  • [$1000] [71855] High Integer overflow in textarea handling. Credit to miaubiz.
  • [71960] Medium Out-of-bounds read in WebGL. Credit to Google Chrome Security Team (Inferno).
  • [72214] High Accidental exposure of internal extension functions. Credit to Tavis Ormandy of the Google Security Team.
  • [$1000] [72437] High Use-after-free with blocked plug-ins. Credit to Chamal de Silva.
  • [$1000] [73235] High Stale pointer in layout. Credit to Martin Barbella.
Chris Evans
Google Chrome Security Team
URL: http://googlechromereleases.blogspot.com/2011/02/stable-channel-update_28.html

Sunday, February 27, 2011

[Gd] Heading for GDC

| More

Android Developers Blog: Heading for GDC

[This post is by Chris Pruett, who writes regularly about games here, and is obviously pretty cranked about this conference. — Tim Bray]

Android will descend in force upon the Game Developers Conference in San Francisco this week; we’re offering a full day packed with sessions covering everything you need to know to build games on Android.

From 10 AM to 5 PM on Tuesday the 1st, North Hall Room 121 will be ground zero for Android Developer Day, with five engineering-focused sessions on everything from compatibility to native audio and graphics. Here's a quick overview; there’s more on the Game Developer Conference site:

  • Building Aggressively Compatible Android Games — Chris Pruett

  • C++ On Android Just Got Better: The New NDK — Daniel Galpin and Ian Ni-Lewis

  • OpenGL ES 2.0 on Android: Building Google Body — Nico Weber

  • Android Native Audio — Glenn Kasten and Jean-Michel Trivi

  • Evading Pirates and Stopping Vampires Using License Server, In App Billing, and AppEngine — Daniel Galpin and Trevor Johns

Our crack team of engineers and advocates spend their nights devising new ways to bring high-end game content to Android, and a full day of sessions just wasn't enough to appease them. So in addition, you can find incisive Android insight in other tracks:

Finally, you can visit us in the Google booth on the GDC Expo floor; stop by, fondle the latest devices, and check out the awesome games that are already running on them. We're foaming at the mouth with excitement about the Game Developers Conference next week, and you should be too.

Hope to see you there!

URL: http://android-developers.blogspot.com/2011/02/heading-for-gdc.html