Friday, March 8, 2013

[Gd] Fridaygram: women in tech, buzzing bees, storytelling rules

| More

Google Developers Blog: Fridaygram: women in tech, buzzing bees, storytelling rules

Author Photo
By Scott Knaster, Google Developers Blog Editor

Today is International Women’s Day, and one of the ways we’re celebrating is by being part of the Voices Global Conference. The conference includes sessions focused on women in technology, including new Women Techmakers episodes. You can watch live streams and archived videos, all available on the conference site.



Sometimes people ask the purpose of events like this. Beryl Nelson, writing in the Official Google Blog says it nicely: “A diverse workforce is critical in helping us build products that can help people change the world. That includes diversity of all life experiences, including gender.”

Now let’s turn to the uncommon combination of insects and coffee. Researchers in England were able to use caffeine found in some plants to help train the long-term memory of bees. The bees that got a hit of caffeine were far more likely to remember a particular plant than bees that received just sugar water. Coffee drinkers are probably nodding their heads knowingly at this news.

Finally, be sure to read Pixar’s 22 Rules of Storytelling, which has been making the Internet rounds again lately. And try to take the time to enjoy a great story yourself this weekend.


Fridaygram: it’s not the usual yada yada. Sure, you figured out all the hidden codes on the new Google I/O site earlier this week, but think about this: why were those particular numbers chosen? See what you can come up with, then leave a comment on our +Google Developers page.
URL: http://googledevelopers.blogspot.com/2013/03/fridaygram-women-in-tech-buzzing-bees.html

[Gd] Chrome for Android Update

| More

Chrome Releases: Chrome for Android Update

Chrome for Android Stable Channel has been updated to 25.0.1364.169. This version is currently rolling out to Google Play over the next few hours.

This update improves font clarity and includes other stability fixes. Known issues are available on the Chrome support site.

Interested in other release channels of Chrome for Android? A Beta channel is now available and can be run side by side with Stable. 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.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/03/chrome-for-android-update.html

[Gd] Python 2.5, thanks for the good times

| More

Google App Engine Blog: Python 2.5, thanks for the good times



Python 2.5 has a special place in the heart of any Google App Engine developer, as it was the first runtime we launched way back in 2008. Since then, both Python and App Engine have advanced a great deal.

A year ago we announced our support for Python 2.7, which brings syntactic and semantic improvements to the language and includes powerful features like threading and a large selection of third-party libraries.

Not only does Python 2.7 make developers’ lives easier, the runtime is extremely cost-effective. Our customers have taken advantage of features like concurrent requests to reduce their front-end instance costs by more than 70% while handling the same amount of traffic.

Not surprisingly, the Python 2.7 runtime has proven to be extremely popular. Just over a year after launch, more than 78% of active Python applications on App Engine are using the new runtime, and more are being added every minute.

As both Python and App Engine evolve, we must occasionally make hard choices about which legacy runtimes we should continue to support. Today we are announcing the deprecation of the Python 2.5 runtime. The deprecation period will follow the guidelines set in our terms of service.

What does this mean?



  • We will continue to run Python 2.5 applications throughout the deprecation period. For most customers, upgrading to Python 2.7 is trivial as most elements of Python 2.5 are forwards-compatible with Python 2.7. We’ve prepared a handy migration guide that covers the steps to migrate in detail.

  • If your application is still using the already deprecated Master/Slave Datastore, then you should first plan the migration to our more reliable High Replication Datastore, as the Master/Slave Datastore is not accessible from Python 2.7.

  • Future versions of the App Engine Python Development SDK will display warnings to developers deploying updates to a deprecated runtime.

  • Starting from January 2014, we will no longer allow new applications to be created using the Python 2.5 runtime.



We encourage all developers using Python 2.5 to consider migrating as soon as possible. We’re confident that the vast majority of our customers will find the upgrade straightforward and the benefits substantial.

If you’re considering migrating, here are some useful resources:


If you have any questions about this deprecation, we encourage you to contact us at google-appengine-python25-deprecation@googlegroups.com.

-Posted by Andrew Jessup, Product Manager
URL: http://googleappengine.blogspot.com/2013/03/python-25-thanks-for-good-times.html

[Gd] Stable Channel Update

| More

Chrome Releases: Stable Channel Update

The Stable channel has been updated to 25.0.1364.160 for Windows, Mac, and Linux. This release contains 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.
  • [180763] High CVE-2013-0912: Type confusion in WebKit. Credit to Nils and Jon of MWR Labs.
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/03/stable-channel-update_7.html

[Gd] New Asynchronous APIs for Dart

| More

Chromium Blog: New Asynchronous APIs for Dart

The latest Dart SDK now provides a cohesive API for asynchronous programming. Some of the new or improved classes in this release include Stream, a sequence of asynchronous events, and Future, a single asynchronous result.

The Stream class is new and delivers on a common developer request for a more unified approach to events. An event can be any Dart object, which makes Streams very flexible. Consumers of a Stream can listen for events, and streams can be piped, transformed, filtered, and more. We are working to apply them across HTML, I/O, isolates, and more. Here is an example of using streams with the HTML library, treating clicks as a stream of events:


query('#button').onClick.listen((e) => submitForm());

Here is an example of streaming the contents of a file. Notice how streams can be transformed.


Stream<<int>> stream = ...
stream
.transform(new StringDecoder())
.transform(new LineTransformer())
.listen((String line) { /* Do something with line. */ },
onDone: () { /* No more lines */ },
onError: (e) { /* Error on input. */ });

The Future class, which represents a single value available in the future, was cleaned up and is much easier to use. In many cases this allows you to write asynchronous code very similar to its synchronous counterpart:


// Synchronous code, does not use Future
bool writeFile(String data, File file) {
try {
var io = file.openSync(FileMode.WRITE);
io.writeStringSync(data);
io.closeSync();
return true;
} catch (error) {
return false;
}
}


// Asynchronous code, does use Future
Future<bool> writeFile(String data,
File file) {
return file.open(FileMode.WRITE)
.then((io) => io.writeString(data))
.then((io) => io.close())
.then((io) => true)
.catchError((error) => false);
}

Some of these changes are not backwards compatible. Luckily, you can use Dart Editor's Clean Up feature to help automatically port your code from the old API to the new API. Here is an example of Clean Up at work:

Over the following months we will continue to work on the libraries, applying the new asynchronous models. We always appreciate the feedback, please let us know what you think at dartbug.com and misc@dartlang.org.

To get started, you can download the Dart SDK, learn about the language and libraries, and follow our tutorials. If you already have Dart Editor, it can auto-update to the latest release for you.

Posted by Florian Loitsch, Software Engineer and Corelib Hacker

URL: http://blog.chromium.org/2013/03/new-asynchronous-apis-for-dart.html

[Gd] New Asynchronous APIs for Dart

| More

Chromium Blog: New Asynchronous APIs for Dart

The latest Dart SDK now provides a cohesive API for asynchronous programming. Some of the new or improved classes in this release include Stream, a sequence of asynchronous events, and Future, a single asynchronous result.

The Stream class is new and delivers on a common developer request for a more unified approach to events. An event can be any Dart object, which makes Streams very flexible. Consumers of a Stream can listen for events, and streams can be piped, transformed, filtered, and more. We are working to apply them across HTML, I/O, isolates, and more. Here is an example of using streams with the HTML library, treating clicks as a stream of events:


query('#button').onClick.listen((e) => submitForm());

Here is an example of streaming the contents of a file. Notice how streams can be transformed.


Stream<<int>> stream = ...
stream
.transform(new StringDecoder())
.transform(new LineTransformer())
.listen((String line) { /* Do something with line. */ },
onDone: () { /* No more lines */ },
onError: (e) { /* Error on input. */ });

The Future class, which represents a single value available in the future, was cleaned up and is much easier to use. In many cases this allows you to write asynchronous code very similar to its synchronous counterpart:


// Synchronous code, does not use Future
bool writeFile(String data, File file) {
try {
var io = file.openSync(FileMode.WRITE);
io.writeStringSync(data);
io.closeSync();
return true;
} catch (error) {
return false;
}
}


// Asynchronous code, does use Future
Future<bool> writeFile(String data,
File file) {
return file.open(FileMode.WRITE)
.then((io) => io.writeString(data))
.then((io) => io.close())
.then((io) => true)
.catchError((error) => false);
}

Some of these changes are not backwards compatible. Luckily, you can use Dart Editor's Clean Up feature to help automatically port your code from the old API to the new API. Here is an example of Clean Up at work:

Over the following months we will continue to work on the libraries, applying the new asynchronous models. We always appreciate the feedback, please let us know what you think at dartbug.com and misc@dartlang.org.

To get started, you can download the Dart SDK, learn about the language and libraries, and follow our tutorials. If you already have Dart Editor, it can auto-update to the latest release for you.

Posted by Florian Loitsch, Software Engineer and Corelib Hacker

URL: http://blog.chromium.org/2013/03/new-asynchronous-apis-for-dart.html

[Gd] Beta Channel Update for Chrome OS

| More

Chrome Releases: Beta Channel Update for Chrome OS

The Beta channel has been updated to 26.0.1410.28 (Platform version: 3701.42.0) for all Chromebooks. This build contains a number of stability improvements and bug fixes.

Some highlights of these changes are:
  • Pepper Flash updated to 11.6.602.177
  • GTalk updated to 3.14.17
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/03/beta-channel-update-for-chrome-os.html

Thursday, March 7, 2013

[Gd] Unlock the magic: Get ready for Google I/O 2013 registration

| More

Google Developers Blog: Unlock the magic: Get ready for Google I/O 2013 registration

Author Photo
By Katie Miller, Developer Marketing

With Google I/O 2013 registration only days away, on Wednesday, March 13, 2013 at 7:00 AM PDT (GMT-7), we want to make sure you’re as prepared as possible for the process.

First, we’re pleased to share that we’ve just added a lot of information to the Google I/O 2013 site, including information on the registration process, travel planning resources, key event details, FAQs, and (new this year) child care.
I/O 13 logo
Second, we’d like to share answers to some of the most commonly asked questions we’ve received in the last few days on +Google Developers. Complete FAQs are available on the Help page of the event site.

Optimizing your registration experience

We anticipate high demand once again, but there are steps you can take to be prepared for the process.

Before registration opens:
  • Make sure you have set up both a Google+ account and a Google Wallet account. If you’ve ever bought anything on Google Play, you already have Google Wallet.
  • Check your Google Wallet settings to make sure your postal address is complete and accurate, and your payment method is correct and up to date.
  • If this will be the first time you're making a large payment with Google Wallet, you may want to notify your bank or credit card company in advance that you plan to make a $900 (general ticket) or $300 (academic ticket) charge that will appear as GOOGLE*IORegistration. This will help ensure your payment is processed.
  • Be on the site before registration opens on Wednesday, March 13, 2013 at 7:00 AM PDT (GMT-7) so you can sign in to your Google+ account.
Once registration opens on March 13, 2013 at 7:00 AM PDT (GMT-7):
  • When you’re placed on the waiting page, don’t refresh your browser or your ticket search will restart.
  • Please don’t open multiple tabs or use multiple browsers. Each time you open a new connection, your ticket search will restart.
Details for academic attendees

To qualify as an academic attendee (and receive the $300 ticket price) you need to be an active full-time student, professor, faculty or staff at a high school or higher education institution. The academic rate is also available to anyone who graduated in 2013 prior to the event.

To verify that you are qualified to receive the special rate, we will require a current school ID, transcripts, credentials, or other forms of documentation when you check in at the conference. A couple of other important things to note:
  • Once purchased, general admission tickets can't be converted to academic tickets, and vice versa.
  • If you buy an academic ticket and can't provide academic documentation when you arrive at Google I/O, you won't be admitted or offered a refund, nor will you be able to convert your ticket to general admission.
Information on participating from afar

You can be part of Google I/O from wherever you are. You can watch live streams of the keynotes and many other sessions on Google Developers Live. Even better, be part of Google I/O by attending an I/O Extended event in your area. More details on these programs will be available soon. If you can't watch live, you can see YouTube recordings of all sessions on Google Developers Live after the conference.

We greatly appreciate your interest in coming to Google I/O, and we hope to see you there. Good luck!


Katie Miller leads marketing for Google I/O and other developer marketing initiatives at Google. Outside of work, Katie spends her time running (both road races and after a very active toddler) and memorizing Dr. Seuss rhymes.

Posted by Scott Knaster, Editor
URL: http://googledevelopers.blogspot.com/2013/03/unlock-magic-get-ready-for-google-io.html

[Gd] Chrome OS Management Console Update

| More

Chrome Releases: Chrome OS Management Console Update


The Chrome OS Management Console in the administrator control panel has been updated. This update brings new user policies including:
  • Malicious Sites
  • Allow Cookies for URL Patterns
  • Block Cookies for URL Patterns
  • Allow Session-Only Cookies for URL Patterns
  • Third-Party Cookie Blocking
  • Plugin Authorization
  • Outdated Plugins
  • Bookmark Bar
Known issues are available here. Enterprise customers can report an issue by contacting support.

Lawrence Lui
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/03/chrome-os-management-console-update.html

Wednesday, March 6, 2013

[Gd] Announcing the GTAC 2013 Agenda

| More

Google Testing Blog: Announcing the GTAC 2013 Agenda


by The GTAC Committee

We have completed selection and confirmation of all speakers for GTAC 2013. You can find the detailed agenda at:
  developers.google.com/gtac/schedule

Thank you to all who submitted proposals! It was very hard to make selections from so many fantastic submissions.

If you were not extended an invitation, don’t forget that you can join us via YouTube live streaming. We’ll be setting up Google Moderator, so remote attendees can get involved in Q&A after each talk. Information about live streaming, Moderator, and other details will be posted on the GTAC site soon and announced here.

URL: http://googletesting.blogspot.com/2013/03/announcing-gtac-2013-agenda.html

[Gd] Chrome Beta for Android Update

| More

Chrome Releases: Chrome Beta for Android Update

Chrome Beta for Android has been updated to 26.0.1410.28. This release contains a few new fixes including:
  • 180205 - Short flings decelerate too quickly
  • 180396 - Allow Nexus 7 to update to Chrome 26
  • 180403 - Fix password sync for users upgrading from Chrome 25 (This fix will roll out over the next few days)
Key issues:
  • 180540:'Aw, Snap!' help content is not Android-specific
  • 179833 - Keyboard reappears after being dismissed whilst text is underlined
  • 179188 - On signing in to Chrome with a new account, Chrome to Mobile seeks authentication
  • 176399: Swype keyboard commits text after every setComposition()
  • Occasional crashes and ANRs
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/03/chrome-beta-for-android-update_6.html

[Gd] Dev Channel Update for Chrome OS

| More

Chrome Releases: Dev Channel Update for Chrome OS

The Dev channel has been updated to 27.0.1430.0 (Platform version: 3797.0.0) for all Chrome OS devices. This build contains a number of stability fixes and feature enhancements.

Some highlights of these changes are:


  • New UI improvements
  • Pepper Flash updated to 11.6.602.177

Known Issues:

  • Switch window key (F5) not working. (174035)
  • Brightness keys not working on new Samsung Chromebook (180100)
  • Hangout not working on the new Samsung Chromebook from active conversation. Workaround: Start from camera icon next to the contact name in the list  or from G+
  • Video playback plays stutteringly sometimes on new Samsung Chromeboox (175638)

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/03/dev-channel-update-for-chrome-os.html

[Gd] Modern Social Application Development Demands Leaner and More Streamlined JavaScript Libraries

| More

OpenSocial API Blog: Modern Social Application Development Demands Leaner and More Streamlined JavaScript Libraries


HANNOVER, Germany – March 6, 2013 – The OpenSocial Foundation today announced here at CeBIT, the world’s leading high-tech event showcasing digital IT and telecommunications solutions, the launch of a new effort to define, design and release a next generation social application tool kit.  This project will include an evolution of the OpenSocial specification and a new open source effort focused on streamlining and simplifying the approach to tightly integrated collaboration across social applications for both enterprises and consumers.

“We have seen a significant evolution in the use cases and underlying technology of social enabled applications over the past 10 years,” says Matt Tucker, chief technology officer and co-founder of Jive Software.  “It is time that the standards driving the interoperability between social applications evolve along the lines of a leaner, more agile approach.”

To support the project launch, OpenSocial Foundation board members including Mark Weitzel, foundation president, will represent the foundation during the CeBIT conference in Germany as well as participate in a panel on the future of social business.

The OpenSocial Foundation was established in 2008 with the charter to provide the leading and most mature standards-based component model for SaaS-delivered social business applications.  As an industry recognized standards body, the OpenSocial Foundation provides the forum for social business application companies like IBM, Jive and SugarCRM as well as industry leading consulting companies including the Dachis Group to jointly define the interoperability standards for today’s rapidly growing social applications market.  "We have OpenSocial support on the SAP Jam roadmap as an integral way to integrate enterprise applications in today's social workplace," says Sameer Patel, general manager of Enterprise Social Software for SAP.  

In the past five years, the foundation has led the social collaboration industry with efforts in defining groundbreaking new technology developments like the Embedded Experience and Social Feeds.

"Great adoption is driven by culture and technology. Embedding social capabilities into business process and applications drives higher engagement and adoption in any organization -- and those are the core elements of achieving strong ROI,” says Sandy Carter, vice president of Social Business Evangelism and Sales at IBM  “IBM continues our leadership of OpenSocial to accelerate market value while maximizing existing IT investments"

With the launch of this new effort, the OpenSocial Foundation is setting the strategic direction for the OpenSocial community on the path of defining and implementing a new approach to the underlying components of an interconnected set of socially-aware applications.

“There is no better implementation of an open standard than through an open source project,” remarks Clint Oram, chief technology officer and co-founder of SugarCRM Inc.  “By committing to both an evolution of the specification and the surrounding open source projects incorporating the latest developments in HTML5, modern browser technologies and JavaScript libraries like node.js and jQuery, the OpenSocial Foundation is responding to the demands of its community.”

To participate in the definition of the next generation of open social technology standards, please contact the foundation at president@opensocial.org

About the OpenSocial Foundation
The OpenSocial Foundation is an industry-recognized standards body dedicated to advancing the social web through community innovation and open source.  Widely supported by a majority of leading consumer and enterprise social platforms, such as IBM, Jive, and SugarCRM, the OpenSocial specification fosters the development of a growing set of socially aware off-the-shelf applications.  Through open source projects such as Apache Rave and Shindig, it provides a well-defined way for 3rd-party applications to richly interact with users directly in their activity stream.
URL: http://blog.opensocial.org/2013/03/modern-social-application-development.html

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

The Beta channel has been updated to 26.0.1410.28 for Windows, Mac, Linux, and Chrome Frame. This build contains the following:
  • Updated Flash to new beta version of Flash 11.6.602.177, includes ActionScript Workers feature.
  • Fixed the way apps appear in new tab page. [Issue: 175377]
  • Fixed a crash while clicking "Install to play offline" button. [Issue: 178036]
  • Fixed prerender of a page when a original prerender was cancelled. [Issue: 178755]
  • Fixed an issue where some avatar icons are shown mirrored in tab strip. [Issue: 178397]
  • Fixed ~60% regression in Cookie.TimeLoadDBQueueWait on Mac and Windows. [Issue: 175415]
  • [Windows] Fixed a crash when installing the app launcher (and the first packaged app). [Issue: 178487]
  • [Chrome Frame] Fixed a crash when trying to process a target="_blank" link. [Issue: 178415]
  • Fixed stability crashes [Issues: 167510165952, 177659, 177843]
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/2013/03/beta-channel-update.html

[Gd] Google Drive Hackathon in Mountain View, CA

| More

Google Apps Developer Blog: Google Drive Hackathon in Mountain View, CA

Hey Silicon Valley developers,

We are organizing a Google Drive hackathon next week. If you’d like to learn more about the Google Drive SDK, meet with Google Drive engineers and have fun developing your first Google Drive application or integrating your existing application, join us.

The event will take place at the Googleplex in Mountain View, CA. We’ll start with an introduction to the Google Drive SDK at 4:00 p.m. on Wednesday March 13th 2013 and the hackathon will run through the next day at 3:00 p.m. See the detailed agenda of this event, don’t forget to RSVP and tell your friends about it.

Also there will be some exciting Google prizes for the best apps.

See you there!

Nicolas Garnier Google+ | Twitter

Nicolas Garnier joined Google’s Developer Relations in 2008 and lives in Zurich. He is a Developer Advocate for Google Drive and Google Apps. Nicolas is also the lead engineer for the OAuth 2.0 Playground.

URL: http://googleappsdeveloper.blogspot.com/2013/03/google-drive-hackathon-in-mountain-view.html

[Gd] Stable Channel Update for Mac

| More

Chrome Releases: Stable Channel Update for Mac

The Stable channel has been updated to 25.0.1364.155 for Mac. This release fixes a crash when typing in the Omnibox. 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/03/stable-channel-update-for-mac.html

Tuesday, March 5, 2013

[Gd] Dev Channel Update

| More

Chrome Releases: Dev Channel Update

The Dev channel has been updated to 27.0.1430.0 for Mac, Windows, Linux, and Chrome Frame


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/03/dev-channel-update.html

[Gd] Data Compression in Chrome Beta for Android

| More

Chromium Blog: Data Compression in Chrome Beta for Android

Today’s Chrome Beta for Android update brings your saved passwords and autofill entries from your desktop to your phone and tablet. This release also introduces an experimental data compression feature that will yield substantial bandwidth savings. This feature is powered by a connection to a SPDY proxy running on Google’s servers, paired with content optimization performed by our open-source PageSpeed libraries, specifically tuned for Chrome Beta on Android.

By using SPDY, the proxy is able to multiplex multiple request and response streams in parallel over a single TCP connection to your phone or tablet. When this new feature is enabled (enable the “Experimental Data Compression Proxy” under chrome://flags) the browser-to-proxy connection is over SSL, for a more secure browsing experience. In addition, only HTTP traffic is routed through and optimized by the proxy, so secure (HTTPS) requests will bypass the proxy and continue to connect directly to the destination. Furthermore, DNS lookups are performed by the proxy, instead of on the mobile device. Turning on this experimental feature also enables Safe Browsing.

For an average web page, over 60% of the transferred bytes are images. The proxy optimizes and transcodes all images to the WebP format, which requires fewer bytes than other popular formats, such as JPEG and PNG. The proxy also performs intelligent compression and minification of HTML, JavaScript and CSS resources, which removes unnecessary whitespace, comments, and other metadata which are not essential to render the page. These optimizations, combined with mandatory gzip compression for all resources, can result in substantial bandwidth savings.

For a deeper dive into the technical details, check out our whitepaper in Chrome for Android’s developer documentation. The latest version of Chrome Beta for Android is available on Google Play (use the link, you won't find it in search)! We look forward to your early feedback.

Posted by Matt Welsh, Software Engineer & Mobile Web Performance Gearhead
URL: http://blog.chromium.org/2013/03/data-compression-in-chrome-beta-for.html

[Gd] Chrome Beta for Android Update

| More

Chrome Releases: Chrome Beta for Android Update

The Chrome team is excited to announce the promotion of Chrome 26 to the Beta channel for Android. Chrome 26.0.1410.26 contains a number of fixes and enhancements, along with these new features:
  • Password Sync 
    • This will be enabled over the coming days. We will only sync with other clients that are based on Chrome 26 or higher.
  • Autofill Sync
Known Issues:
  • 180205 - Short flings decelerate too quickly
  • 179833 - Keyboard reappears after being dismissed whilst text is underlined
  • 179188 - On signing in to Chrome with a new account, Chrome to Mobile seeks authentication
  • 176399: Swype keyboard commits text after every setComposition()
  • Occasional crashes and hangs
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/03/chrome-beta-for-android-update.html

Monday, March 4, 2013

[Gd] Chrome for iOS Update

| More

Chrome Releases: Chrome for iOS Update

The Chrome team is happy to announce Chrome 25 for iPhone and iPad. Chrome 25.0.1364.86 contains a number of improvements including:
  • Long press on the back button to quickly access any page in your tab history 
  • Share a web page via Messages 
Along with these new features, over the coming days we will make searching on Google even easier:
  • See your search term right in the omnibox, instead of the search query URL 
  • Easily refine your search queries and view more results on the search results page
The update will be rolling out in the App Store over the next few hours. Known issues are available on the Chrome support site. If you find a new issue, please let us know by filing a bug.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/03/chrome-for-ios-update.html

[Gd] Stable Channel Update

| More

Chrome Releases: Stable Channel Update

The Stable channel has been updated to 25.0.1364.152 for Windows and Linux. Note: these release notes also apply to the same version for Mac that was released last Friday. This release contains security and stability improvements along with a number of bug 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.
  • [$1000] [176882] High CVE-2013-0902: Use-after-free in frame loader. Credit to Chamal de Silva.
  • [$1000] [176252] High CVE-2013-0903: Use-after-free in browser navigation handling. Credit to “chromium.khalil”.
  • [$2000] [172926] [172331] High CVE-2013-0904: Memory corruption in Web Audio. Credit to Atte Kettunen of OUSPG.
  • [$1000] [168982] High CVE-2013-0905: Use-after-free with SVG animations. Credit to Atte Kettunen of OUSPG.
  • [174895] High CVE-2013-0906: Memory corruption in Indexed DB. Credit to Google Chrome Security Team (Jüri Aedla).
  • [174150] Medium CVE-2013-0907: Race condition in media thread handling. Credit to Andrew Scherkus of the Chromium development community.
  • [174059] Medium CVE-2013-0908: Incorrect handling of bindings for extension processes.
  • [173906] Low CVE-2013-0909: Referer leakage with XSS Auditor. Credit to Egor Homakov.
  • [172573] Medium CVE-2013-0910: Mediate renderer -> browser plug-in loads more strictly. Credit to Google Chrome Security Team (Chris Evans).
  • [172264] High CVE-2013-0911: Possible path traversal in database handling. Credit to Google Chrome Security Team (Jüri Aedla).
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.

Jason Kersey
Google Chrome
URL: http://googlechromereleases.blogspot.com/2013/03/stable-channel-update_4.html

[Gd] Native RTL support in Android 4.2

| More

Android Developers Blog: Native RTL support in Android 4.2

Posted by Fabrice Di Meglio, Android Frameworks Team

Android 4.1 (Jelly Bean) introduced limited support for bidirectional text in TextView and EditText elements, allowing apps to display and edit text in both left-to-right (LTR) and right-to-left (RTL) scripts. Android 4.2 added full native support for RTL layouts, including layout mirroring, allowing you to deliver the same great app experience to all of your users, whether their language uses a script that reads right-to-left or one that reads left-to-right.



If you do nothing, your app will not change — it will continue to appear as it currently does. However, with a few simple changes, your app will be automatically mirrored when the user switches the system language to a right-to-left script (such as Arabic, Hebrew, or Persian). For example, see the following screenshots of the Settings app:





To take advantage of RTL layout mirroring, simply make the following changes to your app:




  1. Declare in your app manifest that your app supports RTL mirroring.

    Specifically, add android:supportsRtl="true" to the <application> element in your manifest file.



  2. Change all of your app's "left/right" layout properties to new "start/end" equivalents.


    • If you are targeting your app to Android 4.2 (the app's targetSdkVersion or minSdkVersion is 17 or higher), then you should use “start” and “end” instead of “left” and “right”. For example, android:paddingLeft should become android:paddingStart.

    • If you want your app to work with versions earlier than Android 4.2 (the app's targetSdkVersion or minSdkVersion is 16 or less), then you should add “start” and end” in addition to “left” and “right”. For example, you’d use both android:paddingLeft and android:paddingStart.




For more precise control over your app UI in both LTR and RTL mode, Android 4.2 includes the following new APIs to help manage View components:





You can even create custom versions of layout, drawables, and other resources for display when a right-to-left script is in use. Simply use the resource qualifier "ldrtl" to tag your resources, meaning “layout direction right-to-left”. To debug and optimize custom right-to-left layouts, HierarchyViewer now lets you see start/end properties, layout direction, text direction, and text alignment for all the Views in the hierarchy.



It's now easy to create beautiful Android apps for all your users, whether they use a right-to-left or left-to-right language. We look forward to seeing some great apps!


URL: http://android-developers.blogspot.com/2013/03/native-rtl-support-in-android-42.html