Friday, June 21, 2013

[Gd] Dev Channel Update for Chrome OS

| More

Chrome Releases: Dev Channel Update for Chrome OS

The Dev channel has been updated to 29.0.1541.3.
  • Platform version: 4287.1.0 for all platforms except the Google Pixel, the HP Chromebook and the Samsung Chromebox
  • Platform version: 4287.2.0 for cr-48.
This build contains a number of added features and stability improvements.

Notable Updates:
  • A fix to hangout windows now loading
  • A fix to the clock being out of sync

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...’ in the Chrome menu (3 horizontal bars in the upper right corner of the browser).

Ben Henry
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/06/dev-channel-update-for-chrome-os.html

[Gd] Fridaygram: Loon balloons, black holes, browser games

| More

Google Developers Blog: Fridaygram: Loon balloons, black holes, browser games

Author Photo
By Scott Knaster, Google Developers Blog Editor

This week we announced Project Loon, a cool and kind of crazy project that launches Internet-connected balloons and shares their connection with people below on Earth. These are not your typical birthday balloons: they’re 15 meters wide, and they rise to an altitude of 20 km, where winds carry them around the world. Software computes where the balloons should go to provide the best network coverage, and the balloons are then steered and moved as necessary.



Sailing along in the stratosphere is an essential aspect of Project Loon. The stratosphere is far above general air traffic and weather, so Loon balloons don’t have to worry about that. On the other hand, the environment is not friendly, with thin atmosphere and -50°C temperatures. But because the balloons are designed for these conditions, they can survive happily.

Moving further away from Earth, all the way to deep space, astronomers have found 26 new black holes right here in the neighborhood, in the Andromeda galaxy next door. Scientists using the Chandra X-Ray Observatory detected the black holes by observing telltale bursts of X-rays as the black holes ingested the outer atmosphere of ordinary stars. And this is just the start: there are likely thousands more black holes in Andromeda. So if Internet balloons ever make to Andromeda, we now know some places to avoid.

Finally, if you’re looking for something fun to do this weekend, you can spend time with a trio of nifty Chrome Experiment games released over the past couple of weeks: Roll It is a classic boardwalk game with the modern twist of using your mobile device as a controller, Racer builds a race track and soundtrack from several mobile devices put together, and Cube Slam lets you play an old-school arcade game over the Internet with friends (and if you have no friends, you can play against a virtual bear). Have fun!


From distant galaxies to ursine videogame opponents, Fridaygram rolls wide and deep. We cover fun stuff that isn’t always directly related to writing code, just in case you need an end-of-week break. If you’re having too much fun with our trio of games and you want to learn something instead, you can read about how we built each of them: Roll It, Racer, Cube Slam.
URL: http://googledevelopers.blogspot.com/2013/06/fridaygram-loon-balloons-black-holes.html

[Gd] Reaffirming our commitment to open documentation

| More

Google Developers Blog: Reaffirming our commitment to open documentation

Author PhotoBy Ashleigh Rentz, Developer Programs team

Since 2006, we’ve believed in freely licensing our developer documentation. We believe this is best for all of us, both Google and the developer community. We most often rely on the Creative Commons Attribution 3.0 license for documentation and the Apache 2.0 license for code samples.

The freedom to reuse code samples encourages the wider adoption of our APIs and spares you from having to reinvent the wheel when you begin using our products. The freedom to create derivative works from our documentation is beneficial to book authors, bloggers, and even non-English speakers when members of the developer community translate our docs into additional languages. It’s a winning situation for all of us!

During the intervening years, however, some docs were not explicitly licensed in this manner. We wanted to bring them in line with this practice, so we embarked on a review of all our documentation on developers.google.com this week and made sure they all have a footer displaying the license they’re subject to. The vast majority of our docs are now available under liberal terms that we hope will spur new innovation in the community. In the rare cases where a doc isn’t being freely licensed for some reason, we now clearly display “All rights reserved” so you aren’t left wondering. We’ve also tweaked our internal process for publishing new documentation so that pages yet to be written will display a license footer when they’re released. Here’s to the sharing of knowledge!


Ashleigh Rentz supports the team of technical writers who tirelessly document Google’s developer products. She can often be seen skating down the hallways between meetings.

Posted by Scott Knaster, Editor
URL: http://googledevelopers.blogspot.com/2013/06/reaffirming-our-commitment-to-open.html

[Gd] Backlinks and reconsideration requests

| More

Official Google Webmaster Central Blog: Backlinks and reconsideration requests

Webmaster level: advanced

When talking to site owners on Google Webmaster Forums we come across questions on reconsideration requests and how to handle backlink-related issues. Here are some common questions, along with our recommendations.

When should I file a reconsideration request?

If your site violates our Google Quality Guidelines or did in the past, a manual spam action may be applied to your site to prevent spam in our search results. You may learn about this violation from a notification in Google Webmaster Tools, or perhaps from someone else such as a previous owner or SEO of the site. To get this manual action revoked, first make sure that your site no longer violates the quality guidelines. After you've done that, it's time to file a reconsideration request.

Should I file a reconsideration request if I think my site is affected by an algorithmic change?

Reconsideration requests are intended for sites with manual spam actions. If your site’s visibility has been solely affected by an algorithmic change, there's no manual action to be revoked, and therefore no need to file a reconsideration request. If you're unsure if it's an algorithmic change or a manual action, and have found issues that you have resolved, then submitting a reconsideration request is fine.

How can I assess the quality of a site’s backlinks?

The links to your site section of Google Webmaster Tools is a great starting point for an investigation as it shows a significant amount of your site’s inbound links. If you know that you ran an SEO campaign during a particular period of time, downloading the latest links can come handy in slicing links created at that time. Using the links found in Google Webmaster Tools, we recommend looking for patterns that point to general issues that are worth resolving. For example, spammy blog comments, auto generated forum posts or text advertisements with links that pass PageRank are likely to be seen as unnatural links and would violate Google’s quality guidelines. For individual examples and hands-on advice we recommend getting help of peers and expert webmasters on the Google Webmaster Forum.

How do I clean a bad backlink profile?

Make sure to identify poor links first, then make a strong effort to get them either removed or nofollowed. Then use the Disavow Links Tool to deal with remaining unnatural backlinks. We recommend using domain-wide operator for sites with a complicated URL structure, very obvious spam sites, such as gibberish content sites or low quality sites with content that shows no editorial value. See our video on common mistakes when using the disavow tool for more information.

How much information do I need to provide?

Detailed documentation submitted along with a reconsideration request can contribute to its success, as it demonstrates the efforts made by the webmaster and helps Googlers with their investigation. If you are including a link to a shared document, make sure that it’s accessible to anyone with the link.

How long does it take to process reconsideration requests?

Reconsideration requests for sites affected by a manual spam action are investigated by a Googler. We strive to respond in a timely manner, normally within just a few days. However, the volume of incoming reconsideration requests can vary considerably, hence we don't provide a guaranteed turnaround time.

What are the possible outcomes of a reconsideration request?

Upon submitting a reconsideration request, you will first receive an automated confirmation in Google Webmaster Tools. After your request is processed, we'll send you another message to let you know the outcome of the request. In most cases, this message will either inform you that the manual action has been revoked or that your site still violates our quality guidelines.

Where can I get more guidance?

For more information on reconsideration requests, please visit our Help Center. And as always, the Google Webmaster Forum is a great place for further discussions as well as seeking more advice from experienced webmasters and Google guides.

Written by Kaspar Szymanski and Uli Lutz, Search Quality Team
URL: http://googlewebmastercentral.blogspot.com/2013/06/backlinks-and-reconsideration-requests.html

[Gd] Chrome Beta for Android Update

| More

Chrome Releases: Chrome Beta for Android Update

The Chrome for Android Beta channel has been updated to 28.0.1500.54 This release has a number of crash fixes as well as the following fixes:
  • 239383: Crash when typing in text box that triggers autocomplete
  • 246481: scroll getting stuck (possible with FS)
  • 159687: Save Link on authenticated sites doesn't work
  • 235673: [FS API] Zooming in and out a video that has gone FS through API, shows the background page
  • 239455: Tapping within text sometimes causes a word to become highlighted instead of inserting the text cursor
  • 249541: [RTL]New tab button displaced during QIB search in RTL language
  • 249031: Add history to the menu
Known issues:
  • 248090: Gmail - on-screen keyboard is automatically dismissed when replying tot an email
  • 243602: Page jumps up and down when loaded in landscape mode
  • 239685: White flash when creating NTP
A partial list of changes in this build is available in the SVN revision log. If you find a new issue, please let us know by filing a bug. More information about Chrome for Android is available on the Chrome site.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/06/chrome-beta-for-android-update_20.html

Thursday, June 20, 2013

[Gd] Dart: Faster Editor and more

| More

Chromium Blog: Dart: Faster Editor and more

Today's release of the Dart SDK and Editor is the first beta release, and contains performance and productivity improvements across the platform. This latest release helps Dart developers automate code evolution, produce smaller JavaScript code and deploy Dart web apps.

The Editor's analysis engine, responsible for reporting warnings and errors, is completely rewritten and is 20% faster at parsing and analyzing. Now, there’s no need to run all the unit tests just to discover a typo. The Dart Editor watches your back as you type.

In addition, Dart Editor makes it easier for developers to manage an evolving app. Some of the new features include:

  • "Rename Library" refactoring
  • "Convert Method to Getter" and "Convert Getter to Method" refactorings
  • "Import Library" quick fix
  • "Create Class" and "Create part" quick fixes

Code completion has also improved. For example, completion is now camelcase aware. Type iE and Dart Editor finds isEmpty.

Compiling Dart to JavaScript now results in smaller code. For example, some Dart programs that use reflection and HTML can compile to JavaScript that is 3.7x smaller than previous compilation sizes.

Dart VM performance has also improved. Compared against the previous release of Dart, DeltaBlue is 33% faster and Tracer is 40% faster. This release also includes full SIMD acceleration in Dart VM.

Finally, deploying a Dart web app is now easier, with the beta pub deploy command. It creates a directory with your app's code and assets and prepares it for hosting on your favorite web server. You can use this command from Dart Editor or the pub command-line utility.

That's just the highlights - there are more improvements across the platform. You can read the full release notes for more details and changes. You can download the latest version of Dart Editor, including everything you need for Dart development, from dartlang.org. We look forward to your feedback!

Dan Rubel
Productivity Enhancer, Dart Editor team

URL: http://blog.chromium.org/2013/06/dart-faster-editor-and-more.html

[Gd] Enabling Google App Engine to run in the Private Cloud with CapeDwarf

| More

Cloud Platform Blog: Enabling Google App Engine to run in the Private Cloud with CapeDwarf

We hear consistently from developers that they want to see more portability of their apps when working in the cloud.  The Google Cloud Platform team has been collaborating with the Redhat/JBoss Application Server team to help them provide an alternate implementation of Google App Engine running on top of JBoss to facilitate portability and openness.



The bulk of the collaborative work between Google and Redhat is really around the open source Test Compatibility Kit (TCK) project:

Google engineers provided many of the tests of the internal App Engine product, and RedHat engineers added many tests to verify that their implementation of App Engine is correct. These collections of tests have been tested against a local App Engine SDK, a CapeDwarf implementation, and the real Google App Engine running in the Google cloud.



In my previous life in the Java Enterprise, portability across different application servers was a very important feature. But it was never 100% achievable due to lack of some specifications (how do you specify load balancing, auto-scalability, NOSQL access or even simple APIs like caching). Compliance certification was done via a reference implementation (RI) and a Test Compatibility Kit.



Why is providing an App Engine TCK in the open source so important? A few reasons:



First reason: JBoss is one of the key leaders in the Java EE API specification and implementation: JPA, CDI, Beans validation, JAX-RS. JBoss working on implementing Google App Engine on top of their existing APIs helps customers address portability and testing concerns and helps validate our approach.



Second reason: If you are considering using App Engine but have had technical or business constraints for making the move to Google Cloud Platform, you now can when using CapeDwarf on your private cloud (or even private machine), on OpenShift or Google Compute Engine.



Third reason: If you are an existing Java EE JBoss customer, but are looking for easier and more “cloud ready” APIs than Java EE, you can start discovering the simplicity of App Engine APIs. The DNA for these APIs is not from Java EE, it is from the cloud.



Accessing the Datastore is as simple as writing:



DatastoreService ds = DatastoreServiceFactory.getDatastoreService();



No more non portable resource definition, funky XML files or command line tools, JNDI configuration and injection. An App Engine application comes with a complete runtime environment: a datastore, a user service, a mail service, a task queue system, a blob service, a chat service, and more.

An App Engine application does not need to specify load balancing parameters, autoscaling rules, failover across data center settings, replication configuration. It just works and scales automatically.



Fourth reason: If you are an App Engine customer and you love the App Engine APIs, but would like to deploy a new App Engine application on your private farm of servers, you now can with CapeDwarf.



Google has always been committed to the open web.  We are looking forward to moving these tests to open source.  But, of course, we know this is a two way street - we would love for you to provide new tests to us and the community so we can all grow together and improve our applications.  Adding such customer centric tests in the open source TCK would help provide a quick turn around (nobody wants to see a failing TCK build), and also help prevent future App Engine versions (we release the product once a month) from breaking customer tests.



Check it out for yourself: get the TCK code, run the tests and contribute new tests that match your App Engine Application, we are open!





-Posted by Ludovic Champenois, Software Engineer
URL: http://googlecloudplatform.blogspot.com/2013/06/google-app-engine-running-in-private-cloud-with-capedrawf.html

[Gd] Dart: Faster Editor and more

| More

Google Developers Blog: Dart: Faster Editor and more


By Dan Rubel, Productivity Enhancer, Dart Editor team

Cross-posted from the Chromium Blog

Today's release of the Dart SDK and Editor is the first beta release, and contains performance and productivity improvements across the platform. This latest release helps Dart developers automate code evolution, produce smaller JavaScript code and deploy Dart web apps.

The Editor's analysis engine, responsible for reporting warnings and errors, is completely rewritten and is 20% faster at parsing and analyzing. Now, there’s no need to run all the unit tests just to discover a typo. The Dart Editor watches your back as you type.

In addition, Dart Editor makes it easier for developers to manage an evolving app. Some of the new features include:

  • "Rename Library" refactoring
  • "Convert Method to Getter" and "Convert Getter to Method" refactorings
  • "Import Library" quick fix
  • "Create Class" and "Create part" quick fixes

Code completion has also improved. For example, completion is now camelcase aware. Type iE and Dart Editor finds isEmpty.

Compiling Dart to JavaScript now results in smaller code. For example, some Dart programs that use reflection and HTML can compile to JavaScript that is 3.7x smaller than previous compilation sizes.

Dart VM performance has also improved. Compared against the previous release of Dart, DeltaBlue is 33% faster and Tracer is 40% faster. This release also includes full SIMD acceleration in Dart VM.

Finally, deploying a Dart web app is now easier, with the beta pub deploy command. It creates a directory with your app's code and assets and prepares it for hosting on your favorite web server. You can use this command from Dart Editor or the pub command-line utility.

That's just the highlights - there are more improvements across the platform. You can read the full release notes for more details and changes. You can download the latest version of Dart Editor, including everything you need for Dart development, from dartlang.org. We look forward to your feedback!



Written by Dan Rubel, Dart Editor Team

Posted by Scott Knaster, Editor
URL: http://googledevelopers.blogspot.com/2013/06/dart-faster-editor-and-more.html

[Gd] Google Developers Live: our first year

| More

Google Developers Blog: Google Developers Live: our first year

Author Photo
By Louis Gray, Program Manager, Google Developers Live

One year ago, we took the magic of Google I/O and brought it home with Google Developers Live (+GDL)  - engaging with our developer community all year round, live, from our offices around the world. Nearly 1,000 videos and several million views later, we’ve seen you connect with Googlers and industry experts every day, gaining knowledge, sharing insights, and getting feedback on how to create incredible apps and leverage Google’s tools.

Thanks to the combination of Google+ Hangouts and YouTube Live, you can now see our engineers face to face and gain up to the minute insights on +Android+Google Chrome+Google Cloud Platform, and many more.

But Google Developers Live is not just all Google products, all the time. It’s an interactive platform for innovative applications, design wizards and entrepreneurs. We’ve hosted initiatives like Women Techmakers, Google Top Geek from Mexico City, Android Design In Action and Root Access, and we hear directly from the minds behind applications many of us use every day.



It was on GDL where we saw Google Fellow +Sebastian Thrun introduce a new HTML5 course on Udacity. GDL debuted the Mirror API for +Project Glass. And it was on GDL where we first demonstrated YouTube API v3, went behind the scenes with Santa Tracker, and answered questions on the Blink rendering engine.

And when we returned to I/O last month, it was Google Developers Live with wall-to-wall broadcasts, featuring exceptional guests like Megan Smith of Google[x], Bradley Horowitz of Google+ and Hiroshi Lockheimer and Hugo Barra of Android.

While we love the live interaction, Google Developers Live is more than just live. Our archives make it easy for you to watch on your own schedule - in any order, on any product.

Although GDL is only a year old, we’re now broadcasting from Mountain View, New York, Sydney, Tokyo, Milan, Moscow, Buenos Aires, and many places around the world, to bring you the latest Google tools for developers in your time zone, in your language. And we’ve got a lot more planned. So make sure you don’t miss a show, by subscribing to Google Developers on YouTube and staying tuned to https://developers.google.com/live/.


+Louis Gray is a Program Manager on Google's Developer Relations Team, running Google Developers Live. He believes life is but a (live) stream.

Posted by +Scott Knaster, Editor
URL: http://googledevelopers.blogspot.com/2013/06/google-developers-live-our-first-year.html

[Gd] Beta Channel Update for Chrome OS

| More

Chrome Releases: Beta Channel Update for Chrome OS

The Beta channel has been updated to 28.0.1500.53 (Platform version: 4100.48.0 for most platforms, 4100.49.0 for Lenovo Thinkpadfor all Chrome OS devices. This build contains a number of bug fixes, security updates and feature enhancements.

Some highlights of these changes are:
  • Pepper Flash updated to 11.8.800.68-r5
  • File app fixes/improvements
  • Stability fixes
Security fixes:
  • [249335] Medium CVE-2013-2866: Clickjacking in the Flash plug-in.
Known issues:
  • Video frames may get delayed when playing videos in normal mode. Workaround: Play videos in Full screen
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...’ in the Chrome menu (3 horizontal bars in the upper right corner of the browser).

Josafat Garcia
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/06/beta-channel-update-for-chrome-os_20.html

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

The Beta channel has been updated to 28.0.1500.52 for Windows, Mac, and Chrome Frame, and Linux.  Full details about what changes are in this build are available in the SVN revision log.

For more information about features coming to Chrome, check out the Chrome Blog.

Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Anthony Laforge
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/06/beta-channel-update_19.html

[Gd] Dev Channel Update

| More

Chrome Releases: Dev Channel Update

The Dev Channel has been updated to 29.0.1541.0 for Windows, Mac and Chrome Frame; 29.0.1541.2 for Linux. This release fixes a number of crashes, as well as other bugs. A full list of changes is available in the SVN log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/06/dev-channel-update_18.html

[Gd] Stable Channel Update for Chrome OS

| More

Chrome Releases: Stable Channel Update for Chrome OS

The Stable channel has been updated to 27.0.1453.116 (Platform version: 3912.101.0) for all Chrome OS devices. This build contains a number of  stability fixes and security improvements. 
Machines will be receiving updates over then next several days.


Release Highlights:
  • Pepper Flash updated to 11.7.700.225-r4
  • Firmware update for Chromebook Acer C7. Note: A screen with Chrome Logo and a critical update notification will be displayed
Security fixes and rewards:

Please see the Chromium security page for more information. (Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.)

  • [249335] Medium CVE-2013-2866: Clickjacking in the Flash plug-in.

Known issues:

  • File App keeps loading for small images (248235). Work around: Select multiple images to be able to open/edit
  • File App shows "File could not displayed" when moving across large images when they are still loading. (250936)

    Please see the Chromium security page for more information. (Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.)

    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...’ in the Chrome menu (3 horizontal bars in the upper right corner of the browser).

    Josafat Garcia
    Google Chrome
    URL: http://googlechromereleases.blogspot.com/2013/06/stable-channel-update-for-chrome-os.html

    [Gd] Stable Channel Update

    | More

    Chrome Releases: Stable Channel Update

    The Stable channel has been updated to 27.0.1453.116 for Windows, Macintosh and Chrome Frame platforms.

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

    This automatic update includes security fixes. We’d like to highlight the following fixes for various reasons (crediting external researchers, issuing rewards, or highlighting particularly interesting issues):

    • [249335] Medium CVE-2013-2866: Clickjacking in the Flash plug-in.

    This build also has fixes to the following issues:
    • Multiple flash movies on one page not playing [Issue: 243290]
    • Arc rendering bug in canvas [Issue: 243996]
    • Select box with Multiple option fires Onchange event on scroll [Issue: 244406]
    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.

    Karen Grunberg

    Google Chrome
    URL: http://googlechromereleases.blogspot.com/2013/06/stable-channel-update_18.html

    Wednesday, June 19, 2013

    [Gd] Optimizing Drive API calls

    | More

    Google Apps Developer Blog: Optimizing Drive API calls

    Ever look at the data returned when using the Drive API? A files.list call, even if just returning a single file, can yield upwards of 4kb of data. Drive has a rich set of metadata about files, but chances are your application only needs a small fraction of what’s available.

    One of the simplest but most effective optimizations you can make when building apps with the Drive API is limiting the amount of data returned to only those fields needed for your particular use case. The fields query parameter gives you that control, and the results can be dramatic.

    A simple example of this is using the files.list call to display a list of files to a user. The naive query, https://www.googleapis.com/drive/v2/files?maxResults=100, generated more than 380kb of data when I ran it against my own corpus. But to render this list nicely, an app only needs a few bits of information -- the document title, icon & thumbnail URLs, the mime type, and of course the file ID.

    Using the fields query parameter, the results can be trimmed to just the necessary fields and those needed for fetching subsequent pages of data. The optimized query is https://www.googleapis.com/drive/v2/files?maxResults=100&fields=items(iconLink%2Cid%2Ckind%2CmimeType%2CthumbnailLink%2Ctitle)%2CnextPageToken.

    After modifying the query the resulting data was only 30k. That’s more than a 90% reduction in data size! Besides reducing the amount of data on the wire, these hints also enable us to further optimize how queries are processed. Not only is there less data to send, but also less time spent getting it in the first place.


    Steven Bazyl   profile | twitter

    Steve is a Developer Advocate for Google Drive and enjoys helping developers build better apps.


    URL: http://googleappsdeveloper.blogspot.com/2013/06/optimizing-drive-api-calls.html

    [Gd] Requesting Google Groups in a Domain through Apps Script

    | More

    Google Apps Developer Blog: Requesting Google Groups in a Domain through Apps Script

    Editor’s Note: Guest author Niels Buekers is a Google Apps consultant at Capgemini Belgium. — Arun Nagarajan

    During a recent Google Apps migration project, we received several requests to create custom groups of contacts so that users could more easily email frequent collaborators. Before switching to Google Apps, users created their own private distribution lists — but this approach led to overlapping groups that quickly fell out of sync.

    The problem was a perfect case for Google Apps Script. We built a great solution that gives users as much power as possible with just a quick administrator review.


    The situation before: either manually adding each contact or using a private contacts group.


    Solution overview

    To start the process, a user adds a specific label to a Gmail message. A script that runs on a timed trigger then generates a request to create a group for all the addresses in the message. The script writes this data to a spreadsheet that tracks group names and administrator approval.


    /**
    * Retrieves all 'group_request' threads and creates a request.
    */
    function processInbox() {
    // Get threads that have the group_request label.
    var groupRequestLabel = GmailApp.getUserLabelByName('group_request');
    var threads = groupRequestLabel.getThreads(0, 10);

    // For each thread, retrieve all recipients and create a group request.
    for (var i = 0; i < threads.length; i++) {
    var firstMessage = threads[i].getMessages()[0];
    var sender = firstMessage.getFrom();
    var recipients = [];

    // Add sender.
    recipients.push(parseAddresses(sender));

    // Add recipients.
    if (threads[i].getMessages()[0].getTo()) {
    var toRecipients = parseAddresses(firstMessage.getTo());
    recipients.push(toRecipients);
    }

    // Add CCs.
    if (threads[i].getMessages()[0].getCc()){
    var ccRecipients = parseAddresses(firstMessage.getCc());
    recipients.push(ccRecipients);
    }

    // Write all recipients to a cell in the spreadsheet
    // and send emails to ask for group name and approval.
    createGroupRequestForRecipients(recipients,
    Session.getActiveUser().getEmail());

    // Remove label from this thread now that it has been processed.
    threads[i].removeLabel(groupRequestLabel);
    }
    };

    Handling the request

    Once the request has been processed and written to the spreadsheet, the script sends the user an email that asks her to suggest a name for the group in an Apps Script web app. A second email asks the administrator to visit the web app to approve or decline the request. The results are again stored in the spreadsheet.

    The spreadsheet contains a second script, which is triggered for each modification. Once the script confirms that the request has been approved, it uses the Apps Script Domain Service to create the new group.


    /**
    * Creates a new group in the Google Apps cPanel with the provided name
    * and members.
    */
    function createGroupWithAddresses(addresses,groupName){
    var group = GroupsManager.createGroup(groupName, groupName, groupName,
    GroupsManager.PermissionLevel.DOMAIN);
    var splitAddresses = addresses.split(',');
    for (var i = 0; i < splitAddresses.length; i++) {
    Logger.log('Adding ' + splitAddresses[i]);
    group.addMember(splitAddresses[i]);
    }
    };

    The result after successfully running the script.

    This solution provides a simple way for users to request new Google groups, without all the overhead of manually creating an admin-managed distribution list.

    Niels Buekers   profile | Twitter

    Niels is a Google Apps consultant at Capgemini Belgium, with interest in both the technical track and change management. He recently visited Google’s London office to participate in a Google Apps Script hackathon, which resulted in the above solution. Niels is a strong believer in cloud solutions and loves to spread the word about Google Apps.


    URL: http://googleappsdeveloper.blogspot.com/2013/06/requesting-google-groups-in-domain.html

    Tuesday, June 18, 2013

    [Gd] Enabling offline disk import for Google Cloud Storage

    | More

    Cloud Platform Blog: Enabling offline disk import for Google Cloud Storage



    Transferring large data sets (in the hundreds of terabytes and beyond) can be expensive and time-consuming over the public network. To help, we're beginning a limited preview of offline disk import for Google Cloud Storage, which lets you load data by sending us a physical hard disk drives (HDDs) of data that we load on your behalf. Using this option can be helpful if you’re limited to a slow, unreliable, or expensive Internet connection.



    To use offline disk import, write your data to HDDs and then ship them to a Google import center using a mail carrier. For security during shipment, the data on the HDDs must be encrypted. Upon receiving the shipment, Google uploads the data into an empty Cloud Storage bucket that you designate. Because the data is loaded directly via Google's network, this approach may be faster or less expensive than transferring data over the Internet.



    Offline disk import have a flat fee of $80 per HDD irrespective of the drive capacity or data size. During the limited preview, offline disk import is available for customers with a return address based in the United States. If you’re interested in using offline disk import, sign up for the limited preview. If you are outside the United states and are interested in offline disk import also let us know and we will follow up.



    We are pleased to add this additional option for getting your data into the cloud. If you have a moderately sized data set, aren’t in a hurry to transfer your data, or have excellent throughput over the internet, you’ll likely be best served by using gsutil tool to transfer the data over the Internet.





    - Posted by Lamia Youseff, Software Engineer
    URL: http://googlecloudplatform.blogspot.com/2013/06/enabling-offline-disk-import-for-google-cloud-storage.html

    Monday, June 17, 2013

    [Gd] Stable Channel Update

    | More

    Chrome Releases: Stable Channel Update

    The Stable channel has been updated to 28.0.1500.45 for Linux.

    The minimum requirements for Linux have also been updated:

    Ubuntu 12.04+
    Debian 7+
    OpenSuSE 12.2+
    Fedora Linux 17+

    If you find a new issue, please let us know by filing a bug.

    Anthony Laforge
    Google Chrome
    URL: http://googlechromereleases.blogspot.com/2013/06/stable-channel-update_17.html

    [Gd] Beta Channel Update for Chrome OS

    | More

    Chrome Releases: Beta Channel Update for Chrome OS

    The Beta channel has been updated to 28.0.1500.47 (Platform version: 4100.44.0) for Samsung Chromebooks. This build contains a number of bug fixes, security updates and feature enhancements.

    Some highlights of these changes are:
    • Fixed crash when on the login screen when connected to network with proxy auth (244173)
    • Added a delay between screen off & lock (246008)

    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...’ in the Chrome menu (3 horizontal bars in the upper right corner of the browser).

    Danielle Drew
    Google Chrome
    URL: http://googlechromereleases.blogspot.com/2013/06/beta-channel-update-for-chrome-os_17.html

    [Gd] Verify your site in Webmaster Tools using Google Tag Manager

    | More

    Official Google Webmaster Central Blog: Verify your site in Webmaster Tools using Google Tag Manager

    Webmaster level: Intermediate


    If you use Google Tag Manager to add and update your site tags, now you can quickly and easily verify ownership of your site in Webmaster Tools using the container snippet code.

    Here’s how it’s done:

    1. On the Webmaster Tools home page, click Manage site for the site you’d like to verify, then select Verify this site. If you haven’t added the site yet, you can click the Add a site button in the top right corner.



    To do this, you must have "View, Edit, and Manage" account level permissions in Google Tag Manager.

    2. On the Verification page, select Google Tag Manager as the verification method and follow the steps on your screen.



    3. Click Verify.

    And you’re done!

    If you’ve got any questions about this verification method, drop by the Webmaster Help Forum.


    Posted by , Webmaster Trends Analyst

    URL: http://googlewebmastercentral.blogspot.com/2013/06/verify-your-site-in-webmaster-tools.html