Saturday, April 21, 2012

[Gd] Fridaygram: student photographers, space video, shuttle sights

| More

Google Developers Blog: Fridaygram: student photographers, space video, shuttle sights

Author Photo
By Scott Knaster, Google Developers Blog Editor

As regular Fridaygram readers know, at Google we love to get students involved in coding and other pursuits. For example, last fall we announced the Google Photography Prize, which was open to student photographers around the world. More than 20,000 students from 146 countries submitted entries in the few months the competition was open.

A panel of judges whittled these entries to 100, and then to 10 finalists. You can read more about the competition and see a slideshow of the amazing work of these photographers.



Photo by Sasha Tamarin

Let’s move from still photos to video – and out into space, with a look at what video creator Alex Rivest calls "the best view in the solar system". This video shows what astronauts see from the International Space Station, from various points of view. When you watch this video, you can really see what Alex means. And it kind of makes you want to go check it out for yourself.

As long as we’re already out in space, we can’t resist a final mention of one of our favorite Fridaygram topics, the U. S. Space Shuttle. Earlier this week, shuttle Discovery was flown to its new home at the National Air and Space Museum in Washington, DC, producing some incredible sights before arriving. Happy retirement, Discovery.


On the land or in the sky, Fridaygram posts are just for fun. They're designed for your Friday and weekend enjoyment. Each Fridaygram item must pass only one test: it has to be interesting to us nerds.
URL: http://googledevelopers.blogspot.com/2012/04/fridaygram-student-photographers-space.html

[Gd] Changes to deprecation policies and API spring cleaning

| More

Google Developers Blog: Changes to deprecation policies and API spring cleaning

Author PhotoBy Adam Feldman, APIs Product Manager

It’s 2012. These days technology moves fast and we want to keep our developer products moving and innovating fast, too. In an effort to align our pace of development with the market, we did a careful analysis of our API deprecation policies. Based on our conclusions, we've decided to adopt a one-year policy for some APIs, remove the policy for other APIs and make the policy itself simpler and clearer. This doesn't mean we have changed the way we think about our APIs - we are more committed than ever to offering stable and relevant APIs to our developer community.

Most of these changes will happen over the next several years, but today we are giving you advance notice. As always, we will strive to keep changes to a minimum and announce them in a timely manner.

One-year API deprecation policies

As part of our effort to evolve our developer platform (like introducing the Google APIs Terms of Service), we are moving some services to a one-year deprecation policy, a common industry practice among similar APIs. The four services moving to a one-year policy are:
Google App Engine, Google Maps/Earth APIs and YouTube API will wind down their current 3-year deprecation policy and will transition to the one-year policy in April 2014. Google Cloud Storage keeps its current one-year policy. To be very clear, we are not deprecating the APIs themselves.

Clearer deprecation policy language

For the above APIs, we've shortened our deprecation policy to be clearer and more concise. The new policy simply states that we will strive to provide one year notice before making breaking changes. For details, see each API's Terms of Service, such as the Google Maps/Earth APIs.

Removal of deprecation policies

For Google's other APIs, we are removing the deprecation policy - not the API. In most cases, this change will not take effect until April 2015. Check the following affected APIs' Terms of Service for details: Accounts API, AdSense Host API, Chart Tools API, Checkout API, Contacts API, Custom Search API, Documents API, Doubleclick for Publishers API, Feed API, Google Apps Admin APIs, Libraries API, Orkut API, Picasa Web Albums API, and Prediction API.

During the remainder of the deprecation period, these APIs will also benefit from the clearer deprecation policy language. Our commitment to the underlying APIs remains unchanged. We will continue to work very hard to communicate any changes to our APIs well in advance, regardless of the APIs' deprecation policy.

Retirement of older APIs

In addition, we are announcing the deprecation of several older APIs and versions. Please visit the documentation for each API for more information about the deprecation period and suggested alternatives:
Our commitment to developers

Our change in policy is designed to make it easier for us to bring you the technology you’ve come to expect from Google: technology that excels at ease-of-use and scalability, and enables you to focus on building your unique application. Our team remains committed to existing APIs as well as building powerful new Google technology into our developer platform.


Adam Feldman is a Product Manager, focusing on all of Google's APIs and making sure Google provides the best possible platform to developers.

Posted by Scott Knaster, Editor
URL: http://googledevelopers.blogspot.com/2012/04/changes-to-deprecation-policies-and-api.html

[Gd] An Update to our Deprecation Policy

| More

YouTube API Blog: An Update to our Deprecation Policy

As you might have seen announced on our Google Developers blog, the deprecation policies associated with many of Google’s APIs are changing. We want to highlight the specific way this affects YouTube API developers.

As of today, our YouTube API deprecation policy states:

Google will announce if we intend to discontinue or make backwards incompatible changes to this API or Service. We will use commercially reasonable efforts to continue to operate the YouTube API without these changes until the later of: (i) one year after the announcement or (ii) April 20, 2015, unless (as Google determines in its reasonable good faith judgment):
    • required by law or third party relationship (including if there is a change in applicable law or relationship), or
    • doing so could create a security risk or substantial economic or material technical burden.
This Deprecation Policy doesn't apply to versions, features, and functionality labeled as "experimental."

Please note that while the deprecation policy listed above is current as of the date of this blog post, the definitive version of the policy can always be found in our Terms of Service.

Cheers,
—Jeff Posnick, YouTube API Team
URL: http://apiblog.youtube.com/2012/04/update-to-our-deprecation-policy.html

Friday, April 20, 2012

[Gd] Dev Channel Update for Chromebooks

| More

Chrome Releases: Dev Channel Update for Chromebooks



The Dev channel has been updated to 20.0.1105.0 (Platform version: 2153.0.0) for Chromebooks (Acer AC700, Samsung Series 5, and Cr-48). This release contains functional, security and stability improvement.

Release highlights:
  • Updates to Chrome - see this blog post for details
  • Switched to open source touchpad driver on Cr-48 
  • Introduced redesigned UI to Cr-48
  • Introduced option for natural scrolling direction

Known issues:
  • Some regressions in particular touch use cases
  • 122868 - Some flickering seen when opening websites or new tabs. Workaround: Switch to another tab and and switch back to clear the blocky or flickering screen. In some cases, a machine restart may be required.
  • 29370 - Video playback sometimes does not work properly when multiple tabs are open. Audio continues but video may stop or stutter. Workaround: Close some tabs or restart machine to clear posible memory issues, and replay video.
If you find new issues, please let us know by visiting our help site or filing a bug. Interested in switching to the Beta channel? Find out how. You can submit feedback using ‘Report an issue’ under the wrench menu.

Danielle Drew & Karen Grunberg
Google Chrome
URL: http://googlechromereleases.blogspot.com/2012/04/dev-channel-update-for-chromebooks_20.html

[Gd] App Engine and Google’s new Deprecation Policy

| More

Google App Engine Blog: App Engine and Google’s new Deprecation Policy

As you may have seen on the Google Developer’s Blog today, Google is changing the Deprecation Policy for all Developer products as a matter of corporate policy. We would like to clarify how this impacts App Engine and you, our customers.

Once the new deprecation policy takes effect, App Engine’s new Deprecation Period will be one year, the longest deprecation period Google offers across APIs and developer products. Practically, this means that Production Features deprecated after the new policy takes effect will continue to be supported at least until 2015 or for one year, whichever period is longer. In our four year history, we have only deprecated one Production Feature, the Master/Slave Datastore, and in that case it was in favor of a more reliable alternative.  We take considerable care that once a feature has graduated from Experimental status it will stand the test of time, and we do not anticipate frequent deprecations in the future.  

Although the official deprecation period is one year, at a minimum, if it does become necessary to deprecate a feature of App Engine we will give our customers enough advance notice to adjust their applications accordingly. Some very large customers might require more than one year; please contact us and we’d be happy to work with you to understand your specific needs.

We want to reiterate that Google strongly supports App Engine and is excited about its steady growth.  You can see the change in our upcoming new Terms of Service (which will take effect July 20, 2012) and as always if you have any questions or comments, please let us know in our Group.

- Posted by Greg D’Alesandre, Senior Product Manager, App Engine Team
URL: http://googleappengine.blogspot.com/2012/04/app-engine-and-googles-new-deprecation.html

Thursday, April 19, 2012

[Gd] Beta Channel Update for Chromebooks

| More

Chrome Releases: Beta Channel Update for Chromebooks

The Beta channel has been updated to 19.0.1084.30 (Platform version: 2046.44.0) for Chromebooks (Acer AC700 and Samsung Series 5).  This release contains stability improvements. If you find new issues, please let us know by visiting our help site or filing a bug. Interested in switching channels? Find out how. You can submit feedback using ‘Report an issue’ under the wrench menu.Orit Mazor
Google Chrome
URL: http://googlechromereleases.blogspot.com/2012/04/beta-channel-update-for-chromebooks_19.html

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

The Beta channel has been updated to 19.0.1084.30 for Windows, Mac, Linux, and Chrome Frame. 

Take a look at the changelog to see what happened in this release, we've update the localization and fixed a number of stability issues.

If you'd like to get on the Beta channel, you can download it from our Beta download page. If you find a new issue, please let us know by filing a bug.

Anthony Laforge
Google Chrome
URL: http://googlechromereleases.blogspot.com/2012/04/beta-channel-update_18.html

Wednesday, April 18, 2012

[Gd] Code Jam’s Sprint to Google I/O

| More

Google Developers Blog: Code Jam’s Sprint to Google I/O

Author Photo
By Igor Naverniouk, Software Engineer, Code Jam

Last Friday, we kicked off our Code Jam qualification round where over 36,000 programmers from around the world competed for a chance to be one of the 25 finalists invited to New York for the final showdown. While registration for Code Jam is now closed, we didn’t want to keep you waiting a whole year to re-try your luck.



Starting tomorrow, April 19 at 7:00 AM PDT / 14:00 UTC, we will be running a Code Jam sprint. The stakes, you ask? The first 100 developers to solve a two-part challenge will be given the opportunity to purchase tickets to Google I/O, which sold out in just over 20 minutes this year.

You don’t have to be a seasoned Code Jam veteran to participate, but you’ll want to register in advance. This ensures that the only thing between you and your ticket to Google I/O is a single challenge and a few quick clicks. In case you want a warm up, check out our Code Jam quick-start guide and practice questions.

The URL for the challenge will be posted to our +Google Developers page promptly tomorrow, April 19 at 7:00 AM, so don’t miss your chance to code your way to Google I/O this year!

Code Jam is a worldwide programming competition in which contestants may use any programming language to solve algorithmic problems. Although registration for Code Jam 2012 is now closed, developers can still compete in our Sprint to Google I/O for a chance to purchase a ticket to the conference for $900.


As his main job, Igor Naverniouk builds analytics for Google Play. In his 20% time, he works on programming challenges for Code Jam.

Posted by Scott Knaster, Editor
URL: http://googledevelopers.blogspot.com/2012/04/code-jams-sprint-to-google-io.html

[Gd] Back to Morocco: g|maroc 2012

| More

Google Developers Blog: Back to Morocco: g|maroc 2012

Author Photo
By Rania Hadi, MENA Outreach Manager

View this post in Arabic

Last May, I joined the MENA Outreach team and was swiftly transported to Rabat for my first event (as an organizer) in Morocco. it is hard to believe that a year has passed, but here we are again, preparing for our upcoming g|maroc event!

Our first g|day of 2012 was in Jeddah, and we had a great time learning from, and interacting with, the vibrant tech and business communities - and I even got to exercise my Arabic skills on stage. We hope the fun and energy continues at g|maroc 2012, to be held in the city of Mohammedia, on June 7-8. We chose this location to be between Casablanca and Rabat, but we look forward to having many people attend from all around Morocco.

I’m looking forward to a few things: interacting with participants, testing my French and Arabic skills (fingers crossed), and especially, the new and updated sessions. Based on participant feedback from our previous events, we’re changing the content and format this time to make sure we cover topics that are useful for advanced users. We’ll also have Google engineers, product managers, and business leaders available to answer any questions.

g|maroc isn’t just about us, though; we also want to showcase Moroccan talent! If you have created or built something cool using a Google product, technology, or tool, be sure to tell us about it while registering. You may get the chance to present at g|maroc, so be detailed and show us what you’ve got.

Registration opens today, and it’s free. So register now, tell your friends about it, and let us know what you want to see at the event. Morocco was a fantastic first start for me, and I hope the tradition continues!


Rania Hadi has been with Google since 2004 and now works on Outreach in the Middle East & North Africa. She focuses on building relationships and promoting Google technologies with the developer and tech communities.

Posted by Scott Knaster, Editor
URL: http://googledevelopers.blogspot.com/2012/04/back-to-morocco-gmaroc-2012.html

[Gd] Add SPDY support to your Apache server with mod_spdy

| More

Google Developers Blog: Add SPDY support to your Apache server with mod_spdy

Author Photo
Bryan
Author Photo
Matthew

By Matthew Steele and Bryan McQuade,
PageSpeed Insights Team


At Google, we strive to make the whole web fast. Our work in this area includes PageSpeed, Google Chrome, and the SPDY protocol, among other efforts. In December of 2011, to make it easy for you to enable the SPDY (pronounced "SPeeDY") protocol on your sites, we released an early beta of mod_spdy, an Apache module that adds SPDY support to the Apache HTTPD server. We’ve spent the last few months working with our early adopters to fix bugs and tune performance of the module. Today, we’re launching a version of mod_spdy that we encourage you to try on your web server.

Installing mod_spdy

To install mod_spdy on your Apache 2.2 server, simply download the appropriate mod_spdy Debian or RPM package for your platform, or compile from source. Once installed, your Apache server will begin using SPDY to communicate with SPDY-compatible browsers (e.g. Google Chrome, Android, and recent versions of Firefox). SPDY runs over HTTPS, so any HTTP (non-HTTPS) traffic on your site will not be affected by mod_spdy. Further, since SPDY requires server-side support for the NPN TLS HTTPS extension, which is not available in most current Apache environments, a version of mod_ssl with NPN support is included with the mod_spdy packages.

Enabling SPDY for your site improves performance in several ways:
  • The server and browser can compress HTTP headers, saving bytes on the network.
  • Multiple resource requests can be multiplexed over a single TCP connection, saving connections on the network.
  • The browser can request all page resources at once instead of a few at a time, which reduces the number of network round-trips needed between server and client.
We've tested mod_spdy using locally-mirrored pages from popular websites, and have seen significant speedups compared to serving via plain HTTPS – comparable to the gains that Google’s own servers achieve by using SPDY – with no extra configuration and negligible effect on Apache’s CPU and memory usage. In extreme cases, for example, pages with many small resources, we’ve seen mod_spdy reduce load times by more than 50%.



How mod_spdy works in Apache

Implementing SPDY in Apache posed several interesting challenges. For example, multiplexing is an important performance feature of SPDY which allows for multiple requests in a single SPDY session to be processed concurrently, and their responses interleaved down the wire. However, due to the serialized nature of the HTTP/1.1 protocol, the Apache HTTP server provides a one-request-per-connection architecture. Apache’s connection and request processing normally happens in a single thread, like so:


single thread

This works well for HTTP, but it presents a problem for multiplexed protocols like SPDY because in this flow, each connection can only process one request at a time. Once Apache starts processing a request, control is transferred to the request handler and does not return to the connection handler until the request is complete.

To allow for SPDY multiplexing, mod_spdy separates connection processing and request processing into different threads. The connection thread is responsible for decoding SPDY frames and dispatching new SPDY requests to the mod_spdy request thread pool. Each request thread can process a different HTTP request concurrently. The diagram below shows the high-level architecture.


multiple threads

Happily, all this is almost completely invisible to users and server administrators alike--you can continue to use your existing Apache modules and configurations.

Download mod_spdy for your platform and give it a try, and let us know what you think on our mailing list. mod_spdy is an open-source project and we welcome contributions. We are continuing to add new features, tune performance, and improve support for up-and-coming versions of the SPDY protocol.


Matthew Steele and Bryan McQuade are Software Engineers on the Google PageSpeed Insights Team in Cambridge, MA. When not working on mod_spdy, they focus on developing tools to help site owners understand how to speed up their sites.

Posted by Scott Knaster, Editor
URL: http://googledevelopers.blogspot.com/2012/04/add-spdy-support-to-your-apache-server.html

[Gd] Dev Channel Update

| More

Chrome Releases: Dev Channel Update

The Dev channel has been updated to 20.0.1105.0 for Windows, Mac, Linux and Chrome Frame.  This build contains following updates:

All


Windows
  • Fixed a crash in the Cloud Print connector when connecting via Remote Desktop (Issue: 122996)
  • Fixed incorrect program icon being shown in the task switcher. (Issue: 118368)
  • Fixed downloads page drag/drop. (Issue: 122946)

Known Issues
  • [Mac 10.6] Video isn’t displayed when entered into presentation mode (pressing cmd + shift + f) (Issue: 123911)

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome
URL: http://googlechromereleases.blogspot.com/2012/04/dev-channel-update_17.html

[Gd] Upgrading Old Embed Codes

| More

YouTube API Blog: Upgrading Old Embed Codes

We’d like to let the community know about an upcoming change that will affect some developers using Flash-only players in their webpages or applications. Previously, a URL like http://www.youtube.com/v/VIDEO_ID would default to the ActionScript 2 version of the Flash player, and it was necessary to explicitly add in the version=3 URL parameter to request the newer, ActionScript 3-based player. Starting on Wednesday, May 2, we will be changing the default behavior so that the ActionScript 3 player will be loaded in those scenarios.

This change to the default version affects both the Embedded and Chromeless Flash players. Developers who are using the newer <iframe> embedded player will not see any change, as that already defaults to the ActionScript 3 player when Flash playback is needed.

If for some reason you explicitly need the ActionScript 2 version of the player, perhaps because you’re hosting it from within a parent Flash container that was written in ActionScript 2, then you should change your code to explicitly add in the version=2 URL parameter to the player URL. Most developers will not need to do this, though, and they’ll automatically get the benefits of the modern ActionScript 3 playback experience without having to change their code.

As we’ve previously announced, the ActionScript 2 players are all officially deprecated, and have been for several years now. Our plan is to shut them down completely starting in October of this year, so while it is still possible to explicitly request them with version=2 if they’re needed, our recommendation is that you do not continue to rely on the ActionScript 2 player in your code.

Cheers,
—Jeff Posnick, YouTube API Team
URL: http://apiblog.youtube.com/2012/04/upgrading-old-embed-codes.html

[Gd] Approval Workflow using Apps Script

| More

Google Apps Developer Blog: Approval Workflow using Apps Script

Editor’s Note: This blog post is authored by Dito’s Steve Webster who is a Google Apps Script Top Contributor - Saurabh Gupta

Ethics Disclosure Review Workflow

Recently a company who operates retail stores throughout a few states reached out to Dito. When their associates conduct business discussions with vendors or customers where monetary exchanges are involved, their Ethics Disclosure policy requires a log for each event, a supervisor approval, and committee review.

The customer’s existing disclosure review process was cumbersome and time consuming. The employees would add a disclosure review request to a spreadsheet with 29 columns. The new review request would then be reviewed by their supervisor. The supervisor and the employee would go back and forth exchanging emails and making changes to a dense spreadsheet until an approval was granted. It was clear that the customer needed a workflow solution. They decided to hire Dito to build a workflow solution based on Google Apps Script.

Workflow Solution based on Google Apps Script

To make the process more user friendly and productive, Dito decided to build a user interface to collect ethics disclosure events, make updates, and automate the routing of email notifications. Writing a Google Apps Script to create a user interface (UI), enabled associates to interact with their contacts to select their supervisor’s email address and simplify the data collection with list boxes. The script sends approval emails with HTML form radio buttons, text box, approve/decline buttons, and a “Post” command to invoke other workflow scripts. Below are some of the main design points for this Approval Workflow script.


1. Disclosure Review Workflow

The Disclosure Review workflow requires (a) Associates to fill out the Ethics Disclosure form. (b) Supervisor to either approve or decline the submission. (c) If supervisor approves, the Ethics Disclosure Committee is notified. (d) If supervisor declines, the associate is notified to make corrections. (e) After improving the submission, the workflow repeats itself.


2. Disclosure Review Request Form

Dito developed a custom review request form. A form was developed using Google Apps Script’s UI Services. The form provides the ability to look up data to populate such things as a drop-down list box. This form allowed real-time email look-ups by using the Apps Script’s Contacts service.  First efforts included per character look-ups in a list box, but since they have over 1,000 users, it was best to enter the first and/or last name of their supervisor before initiating the look-up (see code snippet below).


var byName = ContactsApp.getContactsByName(searchKey);
for (var i in byName) {
var emailStr = byName[i].getPrimaryEmail();
// If there is no 'primary' email, try again for the next email
if (emailStr == null)
var emailStr = byName[i].getEmails()[0].getAddress();
// If emailStr is still null, try again by getting the next email
if (emailStr == null)
var emailStr = byName[i].getEmails()[1].getAddress();
}

Another dynamic field was the “activity type”.  Depending on the selection more form fields are displayed. For example, if the activity type is “Meals”, display a list box to select lunch or dinner.


3. Approve or Reject directly in Gmail

When an associate submits his/her review request by using the custom form within a spreadsheet, their supervisor receives an email with easy-to-read HTML formatted results.  The approval decision, as well as a comment field (e.g. decline reason), is made within the email. This is more productive and prevents unnecessary back and forth into the spreadsheet.

If the request is declined by the supervisor, the associate who submitted the review request receives an email and can review the details. The email also contains a “Continue” button which opens the form in a new browser tab. After corrections are submitted, the supervisor receives another email and the workflow repeats itself.

When approved, the Ethics Disclosure Committee is notified by sending a group email within the script.


4. Saving Workflow History

Since history records existed in their original spreadsheet form and they wanted to insert these records into the new work flow spreadsheet as a one-time task, an Apps Script was used to copy the data.  Of course their columns did not match the new spreadsheet.  By using a mapping approach and a “read once” and “write once” technique, the Apps Script quickly made the changes.


function myFunction() {
var ss = SpreadsheetApp.getActiveSpreadsheet();
var sheet = ss.getSheetByName('Sheet 1');
var rowsWithData = sheet.getRange(2, 1, sheet.getLastRow(),
sheet.getLastColumn()).getValues()
var sheet1Data = [];
var sheet2Data = [];
for (var i = 0; i < rowsWithData.length; i++) {
switch (rowsWithData[i][4]) // This is the activity type
{
...
case "Gift":
sheet1Data.push([rowsWithData[i][12], rowsWithData[i][13],
rowsWithData[i][14]]);
sheet2Data.push([rowsWithData[i][15]]);
continue;
...
default:
continue;
}
}
sheet.getRange(2, 6, sheet1Data.length, 3).setValues(sheet1Data);
sheet.getRange(2, 12, sheet2Data.length, 1).setValues(sheet2Data);
}

Google Apps Script is very powerful and Dito uses it to build interesting solution for its customers. If you are using Google Apps then be sure to use Google Apps Script. You’ll be amazed with what you can build with it.



Steve Webster   profile

Google Sites and Scripts expert from Dito specializing in training and application development. When not busy finding solutions to enhance customer capability in Google Apps, Steve shares examples of his work in the Google Apps Developer Blog.


URL: http://googleappsdeveloper.blogspot.com/2012/04/approval-workflow-using-apps-script.html

Tuesday, April 17, 2012

[Gd] Chrome for Android Beta Update

| More

Chrome Releases: Chrome for Android Beta Update

Chrome for Android Beta has been updated to 0.18.4409.2396 (Chrome 18.0.1025.133) on Google Play.  As mentioned on the Chrome Blog, this update includes a number of new features, as well as the following changes:
  • Allow for download of files to the device
  • Complex Text Layout (CTL) and Right to Left (RTL) text support in rendered pages
  • Enable old-style YouTube embed content to be played via native YouTube app
  • Support for country-specific suggested search engines.

Known issues:

  • 115732 : External links don't open in new tabs if multiple links are opened
  • 113041 : No way to auto-hide the toolbar
  • 114964 : Error pages are not optimized for mobile / Android devices
  • Other notable issues listed here
If you find a new issue, please let us know by filing a bug.  More information on Chrome for Android is available on the Chrome site.

Srikanth Rajagopalan
Google Chrome
URL: http://googlechromereleases.blogspot.com/2012/04/chrome-for-android-beta-update.html

[Gd] Stable Channel Update

| More

Chrome Releases: Stable Channel Update


The Chrome Stable channel has been updated to 18.0.1025.163 on Mac.  


This release fixes issues with fonts (Issue: 108645).


Interested in hopping on the stable channel?  Find out how.  If you find a new issue, please let us know by filing a bug.

Karen Grunberg
Google Chrome

URL: http://googlechromereleases.blogspot.com/2012/04/stable-channel-update_16.html

[Gd] Register now for the global Dart hackathon

| More

Google Developers Blog: Register now for the global Dart hackathon

Author PhotoBy Seth Ladd, Developer Advocate

Cross-posted with the Chromium Blog

The Dart team invites you to the first global Dart hackathon, a collaboration between the Dart team and the developer community. Sign up and have fun hacking on Dart to build modern client and server side web apps and libraries.

Current hackathon locations include:
  • North America:
    • Silicon Valley, California, USA
  • South America:
    • São Paulo, Brazil
  • Europe and Middle East:
    • London, England
    • Prague, Czech Republic
    • Tel Aviv, Israel
  • Asia:
    • Bacolod City, Philippines
    • Chandigarh, India
    • Goa, India
    • Karnataka, India
    • Manipal, India
    • New Delhi, India
    • Seoul, Korea
    • Tokyo, Japan
Hackathon dates vary by location. Check out the full list for the schedule.



The Dart project is still in technology preview, which means you’ll be hacking on early access code, but that’s all part of the fun. We’re eager to see what you build, and we hope you can make it. Register today!






Seth Ladd is a Developer Advocate with the Chrome team, and is having a grand ol' time learning Dart.

Posted by Scott Knaster, Editor
URL: http://googledevelopers.blogspot.com/2012/04/register-now-for-global-dart-hackathon.html

Monday, April 16, 2012

[Gd] Register now for the global Dart hackathon

| More

Chromium Blog: Register now for the global Dart hackathon

The Dart team invites you to the first global Dart hackathon, a collaboration between the Dart team and the developer community. Sign up and have fun hacking on Dart to build modern client and server side web apps and libraries. Current hackathon locations include:
  • North America:
    • Silicon Valley, California, USA
  • South America:
    • São Paulo, Brazil
  • Europe and Middle East:
    • London, England
    • Prague, Czech Republic
    • Tel Aviv, Israel
  • Asia:
    • Bacolod City, Philippines
    • Chandigarh, India
    • Goa, India
    • Karnataka, India
    • Manipal, India
    • New Delhi, India
    • Seoul, Korea
    • Tokyo, Japan
Hackathon dates vary by location. Check out the full list for the schedule.The Dart project is still in technology preview, which means you’ll be hacking on early access code, but that’s all part of the fun. We’re eager to see what you build, and we hope you can make it. Register today!



Posted by Seth Ladd, Developer Advocate
URL: http://blog.chromium.org/2012/04/register-now-for-global-dart-hackathon.html

[Gd] Updates to rich snippets

| More

Official Google Webmaster Central Blog: Updates to rich snippets

Webmaster level: All

Today we’re announcing two updates to rich snippets.

First, we’re happy to announce that product rich snippets, which previously were only available in a limited set of locales, are supported globally.  Users viewing your site’s results in Google search can now preview information about products available on your website, regardless of where they’re searching from. Here’s an example of a product rich snippet:
A product rich snippet from www.google.fr
Second, we’ve updated the rich snippets testing tool to support HTML input. We heard from many users that they wanted to be able to test their HTML source without having to publish it to a web page. This is now supported by the tool, as shown below.
Preview rich snippets from HTML source
If you have any questions or feedback about these changes, please let us know in our Help Forum. You can find more information about rich snippets in our Help Center and Webmaster Education site.

Posted by Anthony Chavez, Product Manager
URL: http://googlewebmastercentral.blogspot.com/2012/04/updates-to-rich-snippets.html