Default

<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger. com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http:// www.georss.org/georss' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>ta g:blogger.com,1999:blog-2471378914199150966</id><updated>2011-12-20T16:41:36.
758 -08:00</updated><category term='linux'/><category term='native client'/><categor y term='extensions'/><category term='javascript'/><category term='googlechrome'/ ><category term='html5'/><category term='incognito'/><category term='releases'/> <category term='security'/><category term='websockets'/><category term='benchmar ks'/><category term='gdd'/><category term='webtiming'/><category term='webgl'/>< category term='beta'/><category term='dart'/><category term='accessibility'/><ca tegory term='chromeos'/><category term='webkit'/><category term='mac'/><category term='webp'/><category term='ssl'/><category term='devtools'/><category term='c hromium'/><category term='v8'/><category term='rlz'/><category term='New Feature s'/><category term='chrome web store'/><category term='chromeframe'/><category t erm='cloud print'/><category term='open web'/><title type='text'>Chromium Blog</ title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/20 05#feed' type='application/atom+xml' href='http://blog.chromium.org/feeds/posts/ default'/><link rel='self' type='application/atom+xml' href='http://www.blogger. com/feeds/2471378914199150966/posts/default'/><link rel='alternate' type='text/h tml' href='http://blog.chromium.org/'/><link rel='hub' href='http://pubsubhubbub .appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.bl ogger.com/feeds/2471378914199150966/posts/default?start-index=26&max-results =25'/><author><name>A Googler</name><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/200 5#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounde d.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger< /generator><openSearch:totalResults>188</openSearch:totalResults><openSearch:sta rtIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPe rPage><entry><id>tag:blogger.com,1999:blog-2471378914199150966.post-255947714710 1678220</id><published>2011-12-15T16:13:00.002-08:00</published><updated>2011-12 -15T16:23:06.722-08:00</updated><title type='text'>In-App Payments Expands its B orders</title><content type='html'><div>(Cross-posted on the < a href="http://googlecode.blogspot.com/2011/12/in-app-payments-expands-its-borde rs.html">Official Google Code</a> and <a href="http://googlecommerce .blogspot.com/2011/12/in-app-payments-expands-its-borders.html">Commerce</ a> Blogs)</div><div> </div><div> Since <a href="http://www.google.com/payments/payment-options/digital-goods.h tml">Google In-App Payments</a> launched in July for developers in the United States, weve received great <a href="http://googlecode.blogspot.com/201 1/09/monetizing-games-with-in-app-payments.html">feedback</a> on how ea sy it is to integrate as well as how simple it is for consumers to use. While th e API has been off to a strong start, theres been a growing demand for availabili ty outside of the United States.</div><div> </div>& lt;div>So starting today, we are opening developer enrollment for Google In-A pp Payments to 17 additional countries. In addition to the United States, develo pers from Australia, Austria, Belgium, Canada, Denmark, Finland, France, Germany , Ireland, Italy, Japan, the Netherlands, Norway, Portugal, Spain, Sweden, and t he United Kingdom can now use the Google In-App Payments API to incorporate an i n-context payment experience into applications on the <a href="http://blog.ch romium.org/2011/09/international-success-with-chrome-web.html">Chrome Web Sto re</a> and their own sites. </div><div class="separator" style="t ext-align: center;"><a href="http://1.bp.blogspot.com/-bJuHO9edrN8/Tuo-6cq _7zI/AAAAAAAAAe4/PkyRH0-LWZw/s1600/flags2.png" imageanchor="1" style="margin-lef t: 1em; margin-right: 1em;"><img border="0" src="http://1.bp.blogspot.com/ -bJuHO9edrN8/Tuo-6cq_7zI/AAAAAAAAAe4/PkyRH0-LWZw/s1600/flags2.png" /></a&g t;</div><div>Developers using In-App Payments are <a href="http:/ /www.google.com/intl/en/landing/chrome/webstore/create/success-story-graphicly.h tml">seeing strong conversions and revenue streams</a> thanks to these key features:</div><ul><li>Ease of use: the
short payment process for consumers takes place right in the developers app or s ite.</li><li>Large existing user base: there are millions of <a href="http://www.google.com/wallet/what-is-google-wallet.html" >Google Wallet</a> online users in over 140 countries.</li><li >Low fees: developers pay just 5% on all transactions.< /li></ul><div>You can get started accepting payments in your web apps by <a href="http://code.google.com/apis/inapppayments/docs/tutorial.html ">following the tutorial</a> and get answers to any questions in the &l t;a href="http://groups.google.com/group/in-app-payments/topics">forum</a& gt;. We look forward to expanding to even more countries in the future, as well as continuously working to improve the Google In-App Payments experience.</di v><div></div><div> </div><div><sp an class= post-author >Posted by Pali Bhat, Product Manager, Google Commerce Team</div><div class="blogger-post-footer"><img widt h= 1 height= 1 src= https://blogger.googleusercontent.com/tracker/247137891419 9150966-2559477147101678220?l=blog.chromium.org alt= /></div></conte nt><link rel= replies type= application/atom+xml href= http://blog.chromium.or g/feeds/2559477147101678220/comments/default title= Post Comments /><link rel= replies type= text/html href= http://www.blogger.com/comment.g?blogID=24713789 14199150966&postID=2559477147101678220 title= 4 Comments /><link rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150 966/posts/default/2559477147101678220 /><link rel= self type= application/atom+ xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/255947 7147101678220 /><link rel= alternate type= text/html href= http://blog.chromiu m.org/2011/12/in-app-payments-expands-its-borders.html title= In-App Payments E xpands its Borders /><author><name>Google Chrome Blog</name><uri>http://www.blog ger.com/profile/15781870002790872375</uri><email>noreply@blogger.com</email><gd: image xmlns:gd= http://schemas.google.com/g/2005 rel= http://schemas.google.com /g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b16rounded.gif /></author><media:thumbnail xmlns:media= http://search.yahoo.com/mrs s/ url= http://1.bp.blogspot.com/-bJuHO9edrN8/Tuo-6cq_7zI/AAAAAAAAAe4/PkyRH0-LW Zw/s72-c/flags2.png height= 72 width= 72 /><thr:total>4</thr:total></entry><en try><id>tag:blogger.com,1999:blog-2471378914199150966.post-5510317517664413195</ id><published>2011-12-09T08:58:00.000-08:00</published><updated>2011-12-14T00:44 :22.927-08:00</updated><category scheme= http://www.blogger.com/atom/ns# term= native client /><title type= text >Games, apps and runtimes come to Native Clien t</title><content type= html >Updated on December 14th with the video of the event. S ince we <a href="http://googlecode.blogspot.com/2011/08/native-client-bringssandboxed-native.html">launched</a> Native Client late last summer, our team has been working hard to make the technology more useful to developers. Ye sterday at an event held at Google we shared the progress weve made towards this goal and showcased work from some of the early adopters of the technology, inclu ding <a href="http://www.square-enix.com/">Square Enix</a>, <a hr ef="http://unity3d.com/">Unity Technologies</a>, and <a href="http:/ /www.bungie.net/">Bungie</a>. <iframe width= "560" height="315" src="http://www.youtube.com/embed/g3aBfkFbPWk" frameborder="0 " allowfullscreen></iframe> One code base for all OSs In September , we started supporting a set of core Pepper interfaces, suited for 2D graphics, audio, and compute-intensive applications. Since that release, weve shipped addi tional APIs and capabilities, providing native code with more of the capabilitie s available from JavaScript. These include hardware-accelerated 3D graphics via OpenGL ES 2.0, a mouse lock API, a full-screen API, and much more. One example o f the kind of experience Native Client can currently support is <a href="http s://chrome.google.com/webstore/detail/oohphhdkahjlioohbalmicpokoefkgid">Basti on</a>, an award-winning role-playing game from Supergiant Games. Previous ly limited to Microsoft Windows and Xbox systems, the Native Client port of Bastio n allows Supergiant to reach users on all popular desktop operating systems, wit h the safety and simplicity of the web. Easy porting of previous work If yo u have existing code bases in C, C++, or C#, Native Client now allows you to por t your existing apps to the web while maintaining just one code base. This was p articularly appealing to Spacetime Studios. They ported their multiplayer online game <a href="https://chrome.google.com/webstore/detail/chcaflnbhnoegjedbjaa mecefhglfamc">Star Legends</a> to the web in less than two weeks from a n existing code base of more than half a million lines of code. The side benefit of being able to maintain their existing development and testing infrastructure further accelerated their delivery of a shipping title. More choices of programming languages The community is actively involved in Native Client, porting some of the most popular application middleware. Ports include <a href="http ://unity3d.com/">Unity</a> and <a href="http://getmoai.com/">Moai </a> game engines, programming language environments <a href="http://ww w.mono-project.com/">Mono</a> and <a href="http://www.lua.org/">L ua</a>, audio middleware such as <a href="http://www.fmod.org/">fmod </a> and <a href="http://www.audiokinetic.com/en/products/wwise/introdu ction">Wwise</a>, as well as the <a href="http://www.bulletphysics.c om/ ">Bullet physics engine</a>. These Native Client ports make the web more accessible to hundreds of thousands of application developers. At the even t, we showcased upcoming applications from <a href="http://hwd3d.com/">Hea rtwood</a>, <a href="http://silvertreemedia.com/">Silvertree</a&g t;, <a href="http://www.exitstrategyentertainment.com/ ">Exit Strategy< /a>, and <a href="http://www.dedalord.com">Dedalord</a>, who used those tools to bring their apps to the web with very little effort. Well continu e to work with the community to get even more languages and middleware systems p orted to Native Client. We recognize that building a Nati ve Client app is only the start of a successful app. Thats why weve enabled distri bution of Native Client-based apps via the <a href="http://chrome.google.com/ webstore">Chrome Web Store</a>. The Chrome Web Store gives developers a simple, effective strategy to reach over 200 million active users of Google Chr ome. If all this sounds exciting, please visit our new do cumentation site at <a href="http://gonacl.com">gonacl.com</a>. Ther e youll find a growing collection of tutorials, examples, videos, reference docum entation, and much more. <iframe width="560" height=" 315" src="http://www.youtube.com/embed/videoseries?list=PL730404AD6E15D017&a mp;hl=en_US" frameborder="0" allowfullscreen></iframe> Questions or suggestions? Join us in the <a href="https://developers.g oogle.com/native-client/community/forums">discussion forums</a>. We loo k forward to seeing some great new apps from Native Client developers. Posted by Christian Stefansen, Pro duct Manager <div class="blogger-post-footer"><img width= 1 height= 1 src= https://blogger.googleusercontent.com/tracker/247137891419915 0966-5510317517664413195?l=blog.chromium.org alt= /></div></content> <link rel= replies type= application/atom+xml href= http://blog.chromium.org/f eeds/5510317517664413195/comments/default title= Post Comments /><link rel= rep lies type= text/html href= http://www.blogger.com/comment.g?blogID=24713789141 99150966&postID=5510317517664413195 title= 6 Comments /><link rel= edit ty pe= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966 /posts/default/5510317517664413195 /><link rel= self type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/551031751 7664413195 /><link rel= alternate type= text/html href= http://blog.chromium.o rg/2011/12/games-apps-and-runtimes-come-to-native.html title= Games, apps and r untimes come to Native Client /><author><name>Google Chrome Blog</name><uri>http ://www.blogger.com/profile/15781870002790872375</uri><email>noreply@blogger.com< /email><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://schemas .google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.c om/img/b16-rounded.gif /></author><media:thumbnail xmlns:media= http://search.ya hoo.com/mrss/ url= http://img.youtube.com/vi/g3aBfkFbPWk/default.jpg height= 7 2 width= 72 /><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:b
log-2471378914199150966.post-2368201914401052574</id><published>2011-11-28T17:20 :00.000-08:00</published><updated>2011-11-29T11:10:42.875-08:00</updated><catego ry scheme= http://www.blogger.com/atom/ns# term= webgl /><title type= text >Ope nGL ES 2.0 Certification for ANGLE</title><content type= html >In March of last year <a href="http://blog.chromium.org/2010/03/introducing-angle-project.html ">we introduced</a> ANGLE as the engine that would power Chrome s GPU r endering on Windows. At the time it was announced, <a href="http://code.googl e.com/p/angleproject/">ANGLE</a> only supported a subset of the OpenGL ES 2.0 API. Thanks to continued work from TransGaming, in collaboration with Goo gle engineers and other contributors, ANGLE has reached an important milestone: It now passes the rigorous OpenGL ES 2.0 test suite and ANGLE version 1.0 has be en certified as a compliant GL ES 2.0 implementation. This is a major step forwa rd for the project, and a major event for OpenGL ES support on Windows. Mac and Linux already enjoy solid OpenGL support, but on Windows OpenGL drivers are not sufficiently widespread to be relied upon. Using ANGLE al lows us to issue OpenGL ES commands in Chrome s graphics systems and not worry a bout the user s computer having OpenGL drivers -- ANGLE translates these command s into Direct3D 9 API calls. ANGLE helps Chrome use a si ngle, open graphics standard and remain portable across platforms. Because it s a standalone library, open-source project ANGLE can help other software projects in the same way. Firefox, for instance, is already using ANGLE to render WebGL content on Windows. ANGLE is a necessary step in our cont inued efforts to push the web platform forward. Without ANGLE, it would be impos sible to reliably run WebGL on many Windows computers, so we couldn t enable gre at applications like <a href="http://www.chromeexperiments.com/detail/mapsgl/ ">MapsGL</a>. We hope WebGL developers and implementors will continue t o join us in making ANGLE, and the open web platform, successful. &lt ;br />Posted by Vangelis Kokkevis, Software E ngineer <div class="blogger-post-footer"><img width= 1 he ight= 1 src= https://blogger.googleusercontent.com/tracker/24713789141991509662368201914401052574?l=blog.chromium.org alt= /></div></content><link rel= replies type= application/atom+xml href= http://blog.chromium.org/feeds/ 2368201914401052574/comments/default title= Post Comments /><link rel= replies type= text/html href= http://www.blogger.com/comment.g?blogID=2471378914199150 966&postID=2368201914401052574 title= 1 Comments /><link rel= edit type= a pplication/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/post s/default/2368201914401052574 /><link rel= self type= application/atom+xml hre f= http://www.blogger.com/feeds/2471378914199150966/posts/default/23682019144010 52574 /><link rel= alternate type= text/html href= http://blog.chromium.org/20 11/11/opengl-es-20-certification-for-angle.html title= OpenGL ES 2.0 Certificat ion for ANGLE /><author><name>Google Chrome Blog</name><uri>http://www.blogger.c om/profile/15781870002790872375</uri><email>noreply@blogger.com</email><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://schemas.google.com/g/20 05#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b16-round ed.gif /></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,199 9:blog-2471378914199150966.post-1329498309316059437</id><published>2011-11-21T11 :52:00.000-08:00</published><updated>2011-11-21T11:59:50.072-08:00</updated><cat egory scheme= http://www.blogger.com/atom/ns# term= v8 /><title type= text >A g ame changer for interactive performance.</title><content type= html >Today we ar e announcing the release of Chromes new <a href="http://en.wikipedia.org/wiki/ Garbage_collection_(computer_science)#Stop-the-world_vs._incremental_vs._concurr ent">incremental garbage collector</a> (GC) which dramatically improves interactive performance of web apps and HTML5 games. The V8 project has made <a href="http://blog.chromium.org/2010/12/new-crankshaft -for-v8.html">huge progress</a> improving peak performance of web apps. With the advent of technolo gies like <a href="http://blog.chromium.org/2010/12/webgl-now-in-beta-here-co mes-3d-web.html">WebGL</a> were seeing the emergence of highly interacti ve and graphically intensive apps, such as the <a href="http://blog.chromium. org/2011/10/heading-in-right-direction-with-webgl.html">new version of Google
Maps</a>, <a href="https://chrome.google.com/webstore/detail/aknpkdffa afgjchaibgeefbgmgeghloj">new games</a> and <a href="http://www.chrom eexperiments.com/webgl">demos</a>. But with these new uses comes a nee d for better interactive performance in JavaScript. Avoiding pauses is vital to achie ving good interactive performance. Previously, garbage collection pause times de pended on the amount of memory used. Therefore, large interactive apps were impa cted by pauses that caused hiccuping. V8s new GC reduces pause times dramatically while maintaining great peak performance and memory use. stress test</a> for interactive performance. In our testing the max imum time to render a frame including pause time is reduced from 272ms to 50ms.& lt;br /> The new GC in Chrome improves interactive performance and opens up new possibilities for the interactive web. If you are developing highl y interactive web apps or games, please try it out and share your experiences. I t is available now on the <a href="http://dev.chromium.org/getting-involved/d ev-channel">dev channel</a>. Posted by Vyacheslav Egorov and Erik Corry, Software Engineers <div class="blogger-post-footer"><img width= 1 height= 1 src = https://blogger.googleusercontent.com/tracker/2471378914199150966-132949830931 6059437?l=blog.chromium.org alt= /></div></content><link rel= replie s type= application/atom+xml href= http://blog.chromium.org/feeds/132949830931 6059437/comments/default title= Post Comments /><link rel= replies type= text/ html href= http://www.blogger.com/comment.g?blogID=2471378914199150966&post ID=1329498309316059437 title= 11 Comments /><link rel= edit type= application/ atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/1 329498309316059437 /><link rel= self type= application/atom+xml href= http://w ww.blogger.com/feeds/2471378914199150966/posts/default/1329498309316059437 /><li nk rel= alternate type= text/html href= http://blog.chromium.org/2011/11/gamechanger-for-interactive.html title= A game changer for interactive performance. /><author><name>Google Chrome Blog</name><uri>http://www.blogger.com/profile/15 781870002790872375</uri><email>noreply@blogger.com</email><gd:image xmlns:gd= ht tp://schemas.google.com/g/2005 rel= http://schemas.google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gif /></au thor><thr:total>11</thr:total></entry><entry><id>tag:blogger.com,1999:blog-24713 78914199150966.post-3299066394395948626</id><published>2011-11-17T22:27:00.000-0 8:00</published><updated>2011-11-18T00:04:47.144-08:00</updated><category scheme = http://www.blogger.com/atom/ns# term= webp /><title type= text >Lossless and Transparency Encoding in WebP</title><content type= html >In September 2010 we a nnounced the <a href="http://code.google.com/speed/webp/">WebP</a> i mage format with lossy compression. WebP was proposed as an alternative to JPEG, with <a href="http://code.google.com/speed/webp/docs/webp_study.html">2534 %</a> better compression compared to JPEG images at equivalent SSIM index. We received lots of feedback, and have been busy improving the format. <a hr ef="https://groups.google.com/a/webmproject.org/group/webp-discuss/browse_thread /thread/4ab76cbde89e6ade/23512e5a1ed1dab0?lnk=raot">Last month</a> we a nnounced WebP support for animation, ICC profile, XMP metadata and tiling. Today , we introduce a new mode in WebP to compress images losslessly, and support for transparency also known as alpha channel in both the lossless and lossy modes.& lt;br /> With these new modes, you can now use WebP to better comp ress all types of images on the web. Photographic images typically encoded as JP EG can be encoded in WebP lossy mode to achieve smaller file size. Icons and gra phics can be encoded better in WebP lossless mode than in PNG. WebP lossy with a lpha can be used to create transparent images that have minimal visual degradati on, yet are much smaller in file size. Animations compressed as GIFs can use ani mation support in WebP. New lossless mode</b& gt; Our main focus for lossless mode has been in compress ion density and simplicity in decoding. On average, we get a 45% reduction in si ze when starting with PNGs found on the web, and a <a href="http://code.googl
e.com/speed/webp/docs/webp_lossless_alpha_study.html#results">28% reduction&l t;/a> in size compared to PNGs that are re-compressed with pngcrush and pngou t. Smaller images on the page mean faster page loads. &lt ;b>New transparency mode Today, webmasters w ho need transparency must encode images losslessly in PNG, leading to a signific ant size bloat. WebP alpha encodes images with low bits-per-pixel and provides a n effective way to reduce the size of such images. Lossless compression of the a lpha channel adds just <a href="http://code.google.com/speed/webp/docs/webp_l ossless_alpha_study.html#results">22% bytes</a> over lossy (quality 90) WebP encoding. Smaller alpha overhead means richer images on webpages. You can find a more detailed compression study for these modes &l t;a href="http://code.google.com/speed/webp/docs/webp_lossless_alpha_study.html" >here</a> and sample images in the <a href="http://code.google.com/s peed/webp/gallery2.html">WebP-Gallery</a>. The bit stream specification has not been finalized, and the encoding and decoding implementations have not yet been optimized for processing speed. We encourage you to <a href="http:// code.google.com/speed/webp/docs/webp_lossless_alpha_study.html#reproduce">try it out</a> on your favorite set of images, check out the <a href="http s://groups.google.com/a/webmproject.org/group/webp-discuss/browse_thread/thread/ bf368050925aeb8e#">code</a>, and <a href="http://www.webmproject.org /about/discuss/#webp-discuss">provide feedback</a>. We hope WebP will n ow handle all your needs for web images, and we re working to get WebP supported in more browsers. Posted by Jyrki Alakuijala, Vikas Arora, and Urvang Joshi, Software Engineers </spa n><div class="blogger-post-footer"><img width= 1 height= 1 src= ht tps://blogger.googleusercontent.com/tracker/2471378914199150966-3299066394395948 626?l=blog.chromium.org alt= /></div></content><link rel= replies t ype= application/atom+xml href= http://blog.chromium.org/feeds/3299066394395948 626/comments/default title= Post Comments /><link rel= replies type= text/html href= http://www.blogger.com/comment.g?blogID=2471378914199150966&postID=3 299066394395948626 title= 19 Comments /><link rel= edit type= application/atom +xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/32990 66394395948626 /><link rel= self type= application/atom+xml href= http://www.b logger.com/feeds/2471378914199150966/posts/default/3299066394395948626 /><link r el= alternate type= text/html href= http://blog.chromium.org/2011/11/losslessand-transparency-encoding-in.html title= Lossless and Transparency Encoding in WebP /><author><name>Google Chrome Blog</name><uri>http://www.blogger.com/profil e/15781870002790872375</uri><email>noreply@blogger.com</email><gd:image xmlns:gd = http://schemas.google.com/g/2005 rel= http://schemas.google.com/g/2005#thumbn ail width= 16 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gif /> </author><thr:total>19</thr:total></entry><entry><id>tag:blogger.com,1999:blog-2 471378914199150966.post-9038756634660999918</id><published>2011-10-18T10:02:00.0 00-07:00</published><updated>2011-10-18T10:05:41.446-07:00</updated><category sc heme= http://www.blogger.com/atom/ns# term= extensions /><category scheme= http ://www.blogger.com/atom/ns# term= chrome web store /><title type= text >New Tex t-to-Speech API for Chrome extensions</title><content type= html >Interested in making your Chrome Extension (or <a href="http://code.google.com/chrome/webst ore/articles/apps_vs_extensions.html">packaged app</a>) talk using synt hesized speech? Chrome now includes a Text-to-Speech (TTS) API that’s simple to use, powerful, and flexible for users. Let& #8217;s start with the "simple to use" part. A few clever apps and extensions fi gured out how to talk before this API was available – typically by sen ding text to a remote server that returns an MP3 file that can be played using H TML5 audio. With the new API, you just need to add "tts" to your permissions and then write: <pre>chrome.tts.speak( Hello, world! ) ; </pre> It’s also very easy to change the rate, pitch, and volume. Here’s an example that speaks more slowly:&l t;br /> <pre>chrome.tts.speak( Can you understand me now? , {rate: 0.6}); </pre> How about powerful? To get even fancier and synchronize speech with your application, you can register to recei
ve callbacks when the speech starts and finishes. When a TTS engine supports it, you can get callbacks for individual words too. You can also get a list of poss ible voices and ask for a particular voice – more on this below. All t he details can be found in the <a href="http://code.google.com/chrome/extensi ons/tts.html">TTS API docs</a>, and we provide complete example code on the <a href="http://code.google.com/chrome/extensions/dev/samples.html#chrom e.tts">samples page</a>. In fact, the API is pow erful enough that <a href="https://chrome.google.com/webstore/detail/kgejglhp jiefppelpmljglcjbhoiplfn">ChromeVox</a>, the Chrome OS screen reader fo r visually impaired users, is built using this API. Here are three examples you can try now:   & amp;nbsp; <a href="https://chrome.google.com/webstore/detail/chhkejk kcghanjclmhhpncachhgejoel">TTS Demo</a> (app)  &amp ;nbsp;  <a href="https://chrome.google.com/webstore/detail/ happachemjeninagaojbimmpkmmeajlg">Talking Alarm Clock</a> (extension)&l t;br />    <a href="https://chrome.goo gle.com/webstore/detail/pgeolalilifpodheeocdmbhehgnkkbak">SpeakIt</a> ( extension) Finally, let s talk about flexibility for user s. One of the most important things we wanted to do with this API was to make su re that users have a great selection of voices to choose from. So we ve opened t hat up to developers, too. The <a href="http://code.g oogle.com/chrome/extensions/ttsEngine.html">TTS Engine API</a> enables you to implement a speech engine as an extension for Chrome. Essentially, you pr ovide some information about your voice in the extension manifest and then regis ter a JavaScript function that gets called when the client calls <code>chr ome.tts.speak</code>. Your extension then takes care of synthesizing and o utputting the speech – using any web technology you like, including &l t;a href="http://www.w3.org/TR/html5/video.html#audio">HTML5 Audio</a>, the new <a href="https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specific ation.html">Web Audio API</a>, or <a href="http://code.google.com/ch rome/nativeclient/">Native Client</a>. Here are two voices implemented using the TTS Engine API that you can install now:     <a href="https://chr ome.google.com/webstore/detail/jcabofbhfighebggomnamjankeaplmhn">Lois TTS - U S English</a>     <a hre f="https://chrome.google.com/webstore/detail/edimkjalobeaakbgjdeikeimmacjdppn"&g t;Flite SLT Female TTS - US English</a> These voice s both use Native Client to synthesize speech. The experience is very easy for e nd users: just click and install one of those voices, and immediately any talkin g app or extension has the ability to speak using that voice. If a user doesn t have any voices installed, Chrome automatically speaks us ing the native speech capabilities of your Windows or Mac operating system, if p ossible. Chrome OS comes with a built-in speech engine, too. For now, there s un fortunately no default voice support on Linux – but TTS is fully suppo rted once users first install a voice from the Chrome Web Store. Now it s your turn: add speech capability to your app or extension today ! We can t wait to hear what you come up with, and if you talk about it, please add the hashtag <a href="https://plus.google.com/s/%23chrometts">#chromett s</a> so we can join the conversation. If you have any feedback, direct it to the <a href="https://groups.google.com/forum/#!forum/chromium-extensions" >Chromium-extensions</a> group. Posted by Dominic Mazzoni, Software Engineer <di v class="blogger-post-footer"><img width= 1 height= 1 src= https://blogg er.googleusercontent.com/tracker/2471378914199150966-9038756634660999918?l=blog. chromium.org alt= /></div></content><link rel= replies type= applic ation/atom+xml href= http://blog.chromium.org/feeds/9038756634660999918/comment s/default title= Post Comments /><link rel= replies type= text/html href= htt p://www.blogger.com/comment.g?blogID=2471378914199150966&postID=903875663466 0999918 title= 1 Comments /><link rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/90387566346609999
18 /><link rel= self type= application/atom+xml href= http://www.blogger.com/f eeds/2471378914199150966/posts/default/9038756634660999918 /><link rel= alternat e type= text/html href= http://blog.chromium.org/2011/10/new-text-to-speech-ap i-for-chrome.html title= New Text-to-Speech API for Chrome extensions /><author ><name>Google Chrome Blog</name><uri>http://www.blogger.com/profile/157818700027 90872375</uri><email>noreply@blogger.com</email><gd:image xmlns:gd= http://schem as.google.com/g/2005 rel= http://schemas.google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gif /></author><thr: total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-2471378914199150 966.post-5105768751586874992</id><published>2011-10-12T06:58:00.000-07:00</publi shed><updated>2011-10-13T07:21:45.125-07:00</updated><category scheme= http://ww w.blogger.com/atom/ns# term= webgl /><title type= text >Heading in the right di rection with WebGL</title><content type= html >Editor s note: The Chromium WebGL team worked closely with the Maps team t o help make MapsGL a reality. We invited a member of the Maps team to talk about their experience with MapsGL in the hope that it would help inform others who are interested in deploying a large scale WebGL app. &lt ;br />At this point it s almost hard to remember, but when Google Maps was &l t;a href="http://googleblog.blogspot.com/2005/02/mapping-your-way.html">first released</a> in 2005, it was one of the first web applications to demonst rate what was possible with AJAX and the web platform. This project was a challe nge technically but wed like to think that it helped to fire the imaginations of web developers around the world. Today, the Maps team is launching a beta of a brand new experience we call <a href="http://maps.googl e.com/gl">MapsGL</a>. MapsGL is one of the first large scale applicatio ns to be built on top of <a href="http://blog.chromium.org/2010/12/webgl-nowin-beta-here-comes-3d-web.html">WebGL</a>. MapsGL makes use of 3D rende ring and hardware graphics acceleration to provide an experience that is seamles s, smooth, and runs directly in the browser. Technically, MapsGL brings significant changes to how map and image tiles are rendered on th e client and server. Rather than loading pre-rendered image tiles from servers, vector data for the map is sent to the browser and rendered on the fly using Web GL. This generally means that less data needs to be sent to the browser, but als o that every aspect of the map needs to be rendered on the order of ~20ms per fr ame in order to achieve a reasonable frame rate. Imagery transitions in Maps are also enhanced by loading 3D metadata along with image tiles, allowing Maps to p rovide rich 3D transitions between different levels and angles of imagery. While developing MapsGL, we found that WebGL draws from both n ative and web app backgrounds. For those used to working on web applications, We bGL adds a lot of functionality, but also increases the complexity of what you n eed to build and test. Even though WebGL is cross platform, performance varies d ramatically across graphics hardware and operating systems - and what improves p erformance on one may hurt performance elsewhere - so testing across a wide arra y of setups is critical. We also found that performance dependent Javascript and WebGL optimizations were needed in order for MapsGL to run properly on slower hardware. For example, there are a number of users with g raphics cards that can t currently run WebGL content. In these cases, we dont gi ve the user the ability to opt-in and they can continue with the current Maps ex perience. Other graphics cards have somewhat poor performance for some key opera tions, which we measure with a small benchmark when the user first opts-in. In t hese cases, MapsGL falls back on a hybrid approach where we use pre-rendered ras ter tiles for the background of the map and only dynamically render labels on to p of these. We hope that MapsGL makes you excited to use WebGL in your own app. WebGL enables 3D graphics and immersive experiences in th e browser that were formerly impossible. As WebGL becomes more robust and graphi cs card drivers improve, we can t wait to see what web developers will create wi th it. Check out the <a href="http://www.khronos.org/webgl/">WebGL documen tation</a> and get started! Posted by Jennifer Maurer, Software Engineer on the MapsGL team </sp an><div class="blogger-post-footer"><img width= 1 height= 1 src= h
ttps://blogger.googleusercontent.com/tracker/2471378914199150966-510576875158687 4992?l=blog.chromium.org alt= /></div></content><link rel= replies type= application/atom+xml href= http://blog.chromium.org/feeds/510576875158687 4992/comments/default title= Post Comments /><link rel= replies type= text/htm l href= http://www.blogger.com/comment.g?blogID=2471378914199150966&postID= 5105768751586874992 title= 6 Comments /><link rel= edit type= application/atom +xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/51057 68751586874992 /><link rel= self type= application/atom+xml href= http://www.b logger.com/feeds/2471378914199150966/posts/default/5105768751586874992 /><link r el= alternate type= text/html href= http://blog.chromium.org/2011/10/heading-i n-right-direction-with-webgl.html title= Heading in the right direction with We bGL /><author><name>Google Chrome Blog</name><uri>http://www.blogger.com/profile /15781870002790872375</uri><email>noreply@blogger.com</email><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://schemas.google.com/g/2005#thumbna il width= 16 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gif />< /author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-247 1378914199150966.post-6840372560635420793</id><published>2011-10-10T00:12:00.000 -07:00</published><updated>2011-10-10T11:13:13.433-07:00</updated><category sche me= http://www.blogger.com/atom/ns# term= dart /><title type= text >Dart: A lan guage for structured web programming</title><content type= html >Cross -posted on the <a href="http://googlecode.blogspot.com/2011/10/dart-languagefor-structured-web.html">Google Code Blog</a> &lt ;br />Today we are introducing an early preview of <a href="http://dartlan g.org/">Dart</a>, a class-based optionally typed programming language f or building web applications. Darts design goals are: < li>Create a structured yet flexible language for web progr amming.</li> <li>Make Dart feel familiar and nat ural to programmers and thus easy to learn.</li> < li>Ensure that Dart delivers high performance on all moder n web browsers and environments ranging from small handheld devices to server-si de execution.</li> Dart targets a wide range of development sce narios: from a one-person project without much structure to a large-scale projec t needing formal types in the code to state programmer intent. To support this w ide range of projects, Dart has optional types; this means you can start coding without types and add them later as needed. We believe Dart will be great for wr iting large web applications. Dart code can be executed i n two different ways: either on a native <a href="http://en.wikipedia.org/wik i/Virtual_machine">virtual machine</a> or on top of a JavaScript engine by using a <a href="http://en.wikipedia.org/wiki/Compiler">compiler</a > that translates Dart code to JavaScript. This means you can write a web app lication in Dart and have it compiled and run on any modern browser. The Dart VM is not currently integrated in Chrome but we plan to explore this option. The language comes with a set of basic libraries and tools fo r checking, compiling, and running Dart code, all of which will evolve further w ith your participation. We ve made the language and preliminary tools available as open source on <a href="http://dartlang.org/">dartlang.org</a>. C heck out the site to give feedback, learn more about Dart, and participate in it s development. We look forward to rapidly evolving Dart i nto a solid platform for structured web programming. Posted by Lars Bak, Software Engineer & lt;div class="blogger-post-footer"><img width= 1 height= 1 src= https:// blogger.googleusercontent.com/tracker/2471378914199150966-6840372560635420793?l= blog.chromium.org alt= /></div></content><link rel= replies type= a pplication/atom+xml href= http://blog.chromium.org/feeds/6840372560635420793/co mments/default title= Post Comments /><link rel= replies type= text/html href = http://www.blogger.com/comment.g?blogID=2471378914199150966&postID=6840372 560635420793 title= 38 Comments /><link rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/68403725606 35420793 /><link rel= self type= application/atom+xml href= http://www.blogger .com/feeds/2471378914199150966/posts/default/6840372560635420793 /><link rel= al
ternate type= text/html href= http://blog.chromium.org/2011/10/dart-language-f or-structured.html title= Dart: A language for structured web programming /><au thor><name>Google Chrome Blog</name><uri>http://www.blogger.com/profile/15781870 002790872375</uri><email>noreply@blogger.com</email><gd:image xmlns:gd= http://s chemas.google.com/g/2005 rel= http://schemas.google.com/g/2005#thumbnail width = 16 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gif /></author>< thr:total>38</thr:total></entry><entry><id>tag:blogger.com,1999:blog-24713789141 99150966.post-4598767724665064392</id><published>2011-10-03T10:57:00.000-07:00</ published><updated>2011-10-04T09:17:38.962-07:00</updated><category scheme= http ://www.blogger.com/atom/ns# term= extensions /><category scheme= http://www.blo gger.com/atom/ns# term= devtools /><title type= text >New developer tools exper imental APIs for Chrome extensions</title><content type= html >Are you already a happy user of <a href="http://code.google.com/chrome/devtools/">Chrome De veloper Tools</a> but always wanted that particular feature added to make you even more productive? Then we have some exciting news for you: our developer tools are now extensible! You can now add new panels and sidebar section panes, retrieve network requests data, evaluate scripts on the page being inspected, and add custom audit rules. <a h ref="http://1.bp.blogspot.com/-p93QYl1mroM/Ton4XNRR-jI/AAAAAAAAAUk/Jq0dIP1SQJQ/s 1600/Screen%2Bshot%2B2011-10-03%2Bat%2B11.00.37%2BAM.png" onblur="try {parent.de selectBloggerImageGracefully();} catch(e) {}"><img style="display:block; m argin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 167px;" src="http://1.bp.blogspot.com/-p93QYl1mroM/Ton4XNRR-jI/AAAAAAAA AUk/Jq0dIP1SQJQ/s400/Screen%2Bshot%2B2011-10-03%2Bat%2B11.00.37%2BAM.png" border ="0" alt="" id="BLOGGER_PHOTO_ID_5659327484350560818" /></a> The extension support is still experimental, but we wanted to let y ou know early, so we can incorporate <a href="http://groups.google.com/group/ google-chrome-developer-tools/topics">your feedback</a> before releasin g the APIs. Heres how to get started with writing extensio ns for Chrome Developer Tools: <ul><li>Use the <a href ="http://www.chromium.org/getting-involved/dev-channel">dev channel</a> of Chrome as the APIs are still under development;</li><li>Enable e xperimental extension APIs using the <a href="chrome://flags">chrome://fla gs</a> page;</li><li>List in the permissions list of your extension;</li&g t;<li>Add a devtools_page</span& gt; field to your extensions manifest, e.g:</li></ul><div style="t ext-align: left;"> { </div><div style="text-align: left;">&l t;span class="Apple-style-span" style="color: rgb(0, 102, 0); "> "name": ...&lt ;/div><div style="text-align: left;"> "minimum_chrome_version": "14.0",</sp an></div><div style="text-align: left;"> "devtools_page": "devtools.html ",</div><div style="text-align: left;"> "permissions": [ "expe rimental" ... ],</div><div style="text-align: left;">&l t;span class="Apple-style-span" style="font-size:85%;color:#006600;"><sp an class="Apple-tab-span" style="white-space:pre"> ...</div><div style="text-align: left;"> }</div> The developer tools extension pages get access to the chrome.experimenta
l.devtools.* APIs which are described further in our <a href="http://code.goo gle.com/chrome/extensions/dev/experimental.devtools.html">docs</a>. Be sure to check out the <a href="http://code.google.com/chrome/extensions/trunk /samples.html#devtools">sample extensions</a>, which include extensions for jQuery and FirePHP users and a simple audit extension that finds broken lin ks. For a richer example, you can also check out <a hr ef="http://code.google.com/speed/page-speed/docs/using_chrome.html">Page Spee d for Chromium</a>, which uses the extensions API to provide Page Speed su ggestions right in the Chrome Devtools UI. Were looking fo rward to seeing your feedback on the APIs and, of course, cool extensions coming to life! Posted by Andre y Kosyakov, Software Engineer <div class="blogger-post-footer"&g t;<img width= 1 height= 1 src= https://blogger.googleusercontent.com/tracke r/2471378914199150966-4598767724665064392?l=blog.chromium.org alt= /></ div></content><link rel= replies type= application/atom+xml href= http://bl og.chromium.org/feeds/4598767724665064392/comments/default title= Post Comments /><link rel= replies type= text/html href= http://www.blogger.com/comment.g?b logID=2471378914199150966&postID=4598767724665064392 title= 8 Comments /><l ink rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/24 71378914199150966/posts/default/4598767724665064392 /><link rel= self type= app lication/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/ default/4598767724665064392 /><link rel= alternate type= text/html href= http: //blog.chromium.org/2011/10/new-developer-tools-experimental-apis.html title= N ew developer tools experimental APIs for Chrome extensions /><author><name>Googl e Chrome Blog</name><uri>http://www.blogger.com/profile/15781870002790872375</ur i><email>noreply@blogger.com</email><gd:image xmlns:gd= http://schemas.google.co m/g/2005 rel= http://schemas.google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gif /></author><media:thumbnail xmlns:media= http://search.yahoo.com/mrss/ url= http://1.bp.blogspot.com/-p93QY l1mroM/Ton4XNRR-jI/AAAAAAAAAUk/Jq0dIP1SQJQ/s72-c/Screen%2Bshot%2B2011-10-03%2Bat %2B11.00.37%2BAM.png height= 72 width= 72 /><thr:total>8</thr:total></entry><e ntry><id>tag:blogger.com,1999:blog-2471378914199150966.post-7035928655072703670< /id><published>2011-09-26T09:10:00.000-07:00</published><updated>2011-09-26T09:1 7:41.201-07:00</updated><category scheme= http://www.blogger.com/atom/ns# term= chrome web store /><title type= text >International Success with the Chrome Web Store</title><content type= html >We recently <a href="http://chrome.blogspo t.com/2011/09/chrome-web-store-expands-its-borders.html">expanded the reach&l t;/a> of the Chrome Web Store from the U.S. to 24 more countries. Developers from around the world have already launched successful apps in the Chrome Web S tore to US users. Now all developers can reach a global user base. What makes this global reach even more interesting is the global pay ments infrastructure that goes along with it. The store allows developers from & lt;a href="http://code.google.com/chrome/webstore/docs/pricing.html">20 count ries</a> to sell apps in the store, and users to buy apps in their local c urrency. We also recently launched the <a href="https://checkout.google.com/i napppayments/">In-App Payments API</a>, which allows developers (U.S.-o nly for now; international soon) to sell virtual goods in their apps. Integratio n is easy and transaction fees are only 5%. <a href="https://chrome.google.co m/webstore/detail/bfahkchgjncmgadmplfkeancoeljcmhp">Graphicly</a>, an e arly user of in-app payments, saw its net revenues double after starting to use the API and experienced an even bigger rise in profit margins due to increased c onversions and lower transaction fees. In keeping with ou r international theme, wed like to highlight a few developers from different part s of the world who have utilized Chromes global reach to find success in the stor e: <ul><li><a href="https://chrome.google.com/webstore /detail/bkgoccjhfjgjedhkiefaclppgbmoobnk">Audiotool</a> is an online mu sic production app that was built by a team of German developers. They saw the C hrome Web Store as a way to present their app to an international audience. Audi otools traffic increased by 20% after launching in the store, and this motivated the team to release <a href="https://chrome.google.com/webstore/detail/jodaom
flkhombighfoeldofifjkpldej">another app</a> in the store.</li>&lt ;/ul><ul><li><a href="https://chrome.google.com/webstore/detai l/pgjchkcfmigkkhedgjedmffdepgmpfil">Psykopaint</a> is the brainchild of French developer Mathieu Gosselin. The Chrome Web Store provided Mathieu an op portunity to get his photo painting app noticed outside of France. Traffic to Ps ykopaint has jumped by 700% since it launched in the store and Mathieu has found that Chrome Web Store users tend to be more engaged than other users.</li&gt ;</ul><ul><li>Finally, Nulab, a Japanese company, launched its online diagramming app, <a href="https://chrome.google.com/webstore/detail/p cflmbddgcmomcfngehfhlajjapabojh">Cacoo</a>, in the store to expand its user base outside Japan. In just a few months after Cacoo was released in multip le languages in the Chrome Web Store, the app already accounts for 20% of Cacoos user base.</li></ul> The experience of Audiotool, Psykopa int and Nulab shows that no matter where youre located, you can always find a glo bal audience for your applications in the Chrome Web Store. To learn more about the stories of these and other successful Chrome Web Store developers, read our <a href="http://www.google.com/intl/en/landing/chrome/webstore/create/success -stories.html">case studies</a>. And if you want to find out more about posting your app in the store, visit our documentation at <a href="http://co de.google.com/chrome/webstore/">code.google.com/chrome/webstore</a>. &l t;br /> Posted by Alexandra Levich , Product Manager<div class="blogger-post-footer"><img wid th= 1 height= 1 src= https://blogger.googleusercontent.com/tracker/24713789141 99150966-7035928655072703670?l=blog.chromium.org alt= /></div></cont ent><link rel= replies type= application/atom+xml href= http://blog.chromium.o rg/feeds/7035928655072703670/comments/default title= Post Comments /><link rel= replies type= text/html href= http://www.blogger.com/comment.g?blogID=2471378 914199150966&postID=7035928655072703670 title= 0 Comments /><link rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/247137891419915 0966/posts/default/7035928655072703670 /><link rel= self type= application/atom +xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/70359 28655072703670 /><link rel= alternate type= text/html href= http://blog.chromi um.org/2011/09/international-success-with-chrome-web.html title= International Success with the Chrome Web Store /><author><name>Google Chrome Blog</name><uri> http://www.blogger.com/profile/15781870002790872375</uri><email>noreply@blogger. com</email><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://sch emas.google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogbl og.com/img/b16-rounded.gif /></author><thr:total>0</thr:total></entry><entry><id >tag:blogger.com,1999:blog-2471378914199150966.post-7191078757942424335</id><pub lished>2011-08-31T13:16:00.000-07:00</published><updated>2011-08-31T13:19:48.638 -07:00</updated><category scheme= http://www.blogger.com/atom/ns# term= native client /><category scheme= http://www.blogger.com/atom/ns# term= chrome web sto re /><title type= text >Google @ GDC Online Oct. 10th-12th</title><content type= html >Cross posted at the <a href="ht tp://googlecode.blogspot.com/2011/08/google-gdc-online-oct-10th-12th.html">Go ogle Code blog</a> />This year at the <a href="http://www.gdconline.com/">Game Deve lopers Conference</a> (GDC) Online we have organized a <a href="http:// www.google.com/events/gdc/2011/agenda.html">Developer Day</a> on Oct. 1 0th full of Google information for game developers. It will feature hardcore tec hnical information on Google products and platforms delivered by Google <a hr ef="http://www.google.com/events/gdc/2011/speakers.html">engineers and develo per advocates</a>. Well discuss the latest projects were working on and how our online technologies can help you better create, distribute, and monetize gam es that reach a larger audience than ever before. Well present everything from h ow developers can build hardware accelerated 3D games for the browser with WebGL framework used to bring Angry Birds to the Web. to the/><div style="margin-left: 1em; margin-right: 1em;"><a href=" game http://code.google.com/" style="clear: left; float: left; margin-bottom: 1em; ma rgin-right: 1em;"><img src="http://1.bp.blogspot.com/-HJG7ixTCixU/Tl563iFu jpI/AAAAAAAAAww/vrfkRx2HY5A/s1600/GDC.png" style="border-bottom-style: none; bor der-color: initial; border-left-style: none; border-right-style: none; border-to
p-style: none; border-width: initial; text-align: left;" width="177" /></a ></div>In addition to the Developer Day, we will also have a booth on t he Expo floor on Oct. 11th-12th where well have representatives from the <a hr ef="http://code.google.com/chrome/webstore/">Chrome Web Store</a>, < a href="http://code.google.com/chrome/nativeclient/">Native Client</a>, WebGL, <a href="http://code.google.com/appengine/">App Engine</a>, Google+, <a href="http://code.google.com/apis/inapppayments/">In-App Payme nts</a>, <a href="http://code.google.com/tv/">Google TV</a>, a nd <a href="http://code.google.com/apis/adsense/">AdSense</a>/<a href="http://code.google.com/mobile/ads/">AdMob</a> demoing technologie s and platforms for game developers. Come by booth 503 to try out Google product s and ask questions, or hang out in our Google TVat <a href="http://schedule. />For more information on presence lounge. gdconline.com/session/5977/%28106%29_Google_Developer_Day_%28Presented_by_Google %29">GDC Online</a>, including session and speaker details, please visi t <a href="http://www.google.com/events/gdc/2011/">http://www.google.com/e vents/gdc/2011</a>. Hope to see you in Austin!href="http://code.google.com />Not able to attend GDC? Check out <a /games/">Google Game Developer Central</a> to get an overview of Google services that are particularly relevant Amygame developers. products and />Posted by to Walgenbach, Developer Marketing <div class="blogger-post-footer"><img width= 1 height= 1 src= https://blogger.googleusercontent.com/tracker/247137891419915096 6-7191078757942424335?l=blog.chromium.org alt= /></div></content><li nk rel= replies type= application/atom+xml href= http://blog.chromium.org/feed s/7191078757942424335/comments/default title= Post Comments /><link rel= replie s type= text/html href= http://www.blogger.com/comment.g?blogID=24713789141991 50966&postID=7191078757942424335 title= 1 Comments /><link rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/po sts/default/7191078757942424335 /><link rel= self type= application/atom+xml h ref= http://www.blogger.com/feeds/2471378914199150966/posts/default/719107875794 2424335 /><link rel= alternate type= text/html href= http://blog.chromium.org/ 2011/08/google-gdc-online-oct-10th-12th.html title= Google @ GDC Online Oct. 10 th-12th /><author><name>Google Chrome Blog</name><uri>http://www.blogger.com/pro file/15781870002790872375</uri><email>noreply@blogger.com</email><gd:image xmlns :gd= http://schemas.google.com/g/2005 rel= http://schemas.google.com/g/2005#thu mbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gif /></author><media:thumbnail xmlns:media= http://search.yahoo.com/mrss/ url= ht tp://1.bp.blogspot.com/-HJG7ixTCixU/Tl563iFujpI/AAAAAAAAAww/vrfkRx2HY5A/s72-c/GD C.png height= 72 width= 72 /><thr:total>1</thr:total></entry><entry><id>tag:bl ogger.com,1999:blog-2471378914199150966.post-2003043805642505231</id><published> 2011-08-30T18:41:00.000-07:00</published><updated>2011-08-30T18:47:11.727-07:00< /updated><category scheme= http://www.blogger.com/atom/ns# term= chromeframe /> <title type= text >Non-Admin Chrome Frame Reaches Stable Channel</title><content type= html >A few months ago, we <a href="http://blog.chromium.org/2011/06/i ntroducing-non-admin-chrome-frame.html">introduced</a> Non-Admin Google Chrome Frame on the developer channel for testing. We deployed it to the beta c hannel two weeks ago and we are now bringing Non-Admin to the stable channel. He ad over <a href="http://www.google.com/chromeframe/eula.html?user=true">he re</a> toyou have it and letthe know how it goes. channel version and wish />If install installed us developer or beta to switch to the stable version, you ll need to uninstall Chrome Frame and then install via the above link. Note that the uninstall experience is smoothest if addition to Non-Admin Chrome Frame moving to the stable channel, you close all Internet Explorer windows prior to uninstalling Chrome Frame. />In we are rolling out a change to the default Chrome Frame installer; it will now r un at Admin level by default and will fall back to Non-Admin mode if the user do es not have the necessary permissions on their machine. This will allow all user s to download a single installer that just works. This installer is available at the Chrome Frame <a href="http://www.google.com/chromeframe/">download pa ge</a>. always, we welcome discussions in the Chrome Frame <a href="ht />As tps://groups.google.com/group/google-chrome-frame?pli=1">Google group</a&g t; and bug reports on Chromiums <a href="http://code.google.com/p/chromium/iss ues/entry?template=ChromeFrame%20Issue">issue tracker</a>. Software En />Posted by Greg Thompson, gineer <div class="blogger-post-footer"><img width= 1 hei
ght= 1 src= https://blogger.googleusercontent.com/tracker/2471378914199150966-2 003043805642505231?l=blog.chromium.org alt= /></div></content><link rel= replies type= application/atom+xml href= http://blog.chromium.org/feeds/2 003043805642505231/comments/default title= Post Comments /><link rel= replies type= text/html href= http://www.blogger.com/comment.g?blogID=24713789141991509 66&postID=2003043805642505231 title= 4 Comments /><link rel= edit type= ap plication/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts /default/2003043805642505231 /><link rel= self type= application/atom+xml href = http://www.blogger.com/feeds/2471378914199150966/posts/default/200304380564250 5231 /><link rel= alternate type= text/html href= http://blog.chromium.org/201 1/08/non-admin-chrome-frame-reaches-stable.html title= Non-Admin Chrome Frame R eaches Stable Channel /><author><name>Google Chrome Blog</name><uri>http://www.b logger.com/profile/15781870002790872375</uri><email>noreply@blogger.com</email>< gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://schemas.google. com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b 16-rounded.gif /></author><thr:total>4</thr:total></entry><entry><id>tag:blogger .com,1999:blog-2471378914199150966.post-3385064935817182213</id><published>201108-25T13:25:00.000-07:00</published><updated>2011-08-25T13:34:03.798-07:00</upda ted><category scheme= http://www.blogger.com/atom/ns# term= chrome web store /> <title type= text >Getting your app discovered in the Chrome Web Store with new promotional assets.</title><content type= html >Yesterday we made a small change in Chrome Web Stores app upload flow: when you upload new apps and extensions to the <a href="http://chrome.google.com/webstore">Chrome Web Store</a&gt ;, or edit one of your existing items, you ll be prompted to provide us with new promotional image assets. We are asking you for these assets so that we can hig hlight your apps and extensions in a brand new store layout that our team is wor king on. /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e ) {}" href="http://2.bp.blogspot.com/-7ftSqNg06qU/TlaxUBKFzUI/AAAAAAAAAR4/Naz6MY 2cT-c/s1600/dev-new-ui-screengrab.png"><img style="display:block; margin:0 px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height : 220px;" src="http://2.bp.blogspot.com/-7ftSqNg06qU/TlaxUBKFzUI/AAAAAAAAAR4/Naz 6MY2cT-c/s400/dev-new-ui-screengrab.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5 <ul><li>(Required) Youll need to provide us with a large 644894140421754178"new: />What s /></a> rectangular image to identify your app, in addition to assets you already provid e - your app icon and at least one screenshot.</li><li>(Optional) Yo u can provide us with an even larger rectangular image format as well.</li&gt What s different ;</ul> /><ul><li>The screenshot dimensions have grown larger with a wider aspect ratio.</li><li>The (optional) marquee image dimensio <ul><li>The specification and dimensions for the icon fi ns have/>What s the same also grown larger.</li></ul> To make things le</li></ul> easier, we only require screenshots in the new dimens ions going forward -- we ll automatically scale them as needed to make them visi ble in the current store layout. You can read the details about the new requirem ents on our <a href="http://code.google.com/chrome/webstore/docs/images.html" >image guidelines page</a>. If you have any questions on these changes , feel free to reach us at our <a href="http://groups.google.com/a/chromium.o rg/group/chromium-apps/topics">discussion group</a>. Guymon, Product Ma />Posted by Shannon nager </div></div><div class="blogger-post-footer"&g t;<img width= 1 height= 1 src= https://blogger.googleusercontent.com/tracke r/2471378914199150966-3385064935817182213?l=blog.chromium.org alt= /></ div></content><link rel= replies type= application/atom+xml href= http://bl og.chromium.org/feeds/3385064935817182213/comments/default title= Post Comments /><link rel= replies type= text/html href= http://www.blogger.com/comment.g?b logID=2471378914199150966&postID=3385064935817182213 title= 4 Comments /><l ink rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/24 71378914199150966/posts/default/3385064935817182213 /><link rel= self type= app lication/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/ default/3385064935817182213 /><link rel= alternate type= text/html href= http: //blog.chromium.org/2011/08/getting-your-app-discovered-in-chrome.html title= G etting your app discovered in the Chrome Web Store with new promotional assets. /><author><name>Google Chrome Blog</name><uri>http://www.blogger.com/profile/157
81870002790872375</uri><email>noreply@blogger.com</email><gd:image xmlns:gd= htt p://schemas.google.com/g/2005 rel= http://schemas.google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gif /></aut hor><media:thumbnail xmlns:media= http://search.yahoo.com/mrss/ url= http://2.b p.blogspot.com/-7ftSqNg06qU/TlaxUBKFzUI/AAAAAAAAAR4/Naz6MY2cT-c/s72-c/dev-new-ui -screengrab.png height= 72 width= 72 /><thr:total>4</thr:total></entry><entry> <id>tag:blogger.com,1999:blog-2471378914199150966.post-7900756314373110311</id>< published>2011-08-25T09:38:00.000-07:00</published><updated>2011-08-25T09:42:11. 115-07:00</updated><category scheme= http://www.blogger.com/atom/ns# term= html 5 /><title type= text >Register now for New Game, the conference for HTML5 game developers</title><content type= html >Cr oss posted at the <a href="http://googlecode.blogspot.com/2011/08/register-no w-for-new-game-conference.html">Google Code blog</a> games s />Ive been a bit wasnt playing />This post almosttoo busywritten. and testing new browser-based uch as <a href="https://chrome.google.com/webstore/detail/cknghehebaconkajgio bncfleofebcog">Monster Dash</a>, <a href="https://chrome.google.com/ webstore/detail/aknpkdffaafgjchaibgeefbgmgeghloj">Angry Birds</a>, and the newly released <a href="https://chrome.google.com/webstore/detail/bnnkhdi odblfknjkjcifnpcmbkckmiaf">SONAR</a>. Bigger and better games are comin g to the browser rapidly (and just wait until <a href="http://blog.chromium.o rg/2011/08/native-client-brings-sandboxed-native.html">Native Client with 3D lands in Chrome</a>), and its hard to keep up with the technology and scene . So what better way to bring everyone together to share stories and keep up to date than to hold a conference dedicated1em;HTML5 game development? /><div style="margin-left: to margin-right: 1em;"><a href=" http://www.newgameconf.com/" style="clear: left; float: left; margin-bottom: 1em ; margin-right: 1em;"><img height="200" src="http://1.bp.blogspot.com/-N7M gGnjVnBc/TlXJ0iYnKLI/AAAAAAAAAvw/0ym77mvTRro/s200/image02.png" style="border-bot tom-style: none; border-color: initial; border-left-style: none; border-right-st yle: none; border-top-style: none; border-width: initial; text-align: center;" w idth="193" /></a></div><a href="http://www.newgameconf.com/"&g t;New Game</a>, the first North American conference for HTML5 game develop ers, is now open for <a href="http://newgame.eventbrite.com/">registration </a>. You are invited to join hundreds of HTML5 game developers for two da ys of technical sessions and case studies from developers and publishers who bro ught their games to the open web platform. The event will take place November 1 This year, New Game looks at what is possible in the browser <i&g 2, 2011/> beautiful Yerba Buena Center for the Arts in San Francisco, CA. at the t;today. Sessions will focus on the technologies that have elevated th e browser-based gaming experience, such as WebGL, Canvas, and JavaScript perform ance techniques. In addition, the conference will feature sessions exploring and analyzing lessons-learned from recent HTML5 game launches. Chief Creative Officer />New Game is honored to have Rich Hilleman, EAs , keynote the event. The <a href="http://www.newgameconf.com/#speakers">sc hedule</a> also includes sessions from Mozilla, Spil, Opera, Google, Bocou p, GameSalad, Moblyng, and others. After the first day, well network with our col leagues and share high scores at the New Game party, open to all registered atte <div style="margin-left: 1em; margin-right: 1em;"><a href=" ndees. /> http://www.newgameconf.com/" style="clear: right; float: right; margin-bottom: 1 em; margin-left: 1em;"><img height="172" src="http://3.bp.blogspot.com/-bW CXPBiA1OU/TlXKH9_MLsI/AAAAAAAAAv4/R59BDjYBQfM/s200/image00.png" style="border-bo ttom-style: none; border-color: initial; border-left-style: none; border-right-s tyle: none; border-top-style: none; border-width: initial; text-align: center;" width="200" /></a></div>For more information on New Game, includi ng session and speaker details, please visit <a href="http://www.newgameconf. com/">www.newgameconf.com</a> and follow <a href="http://twitter.com /#!/newgameconf">@newgameconf</a> for the latest news. Google, the prem ier sponsor, and conference director <a href="http://weblog.bocoup.com/new-ga me-tickets-on-sale">Bocoup</a> invite you to take advantage of <a hr ef="http://newgame.eventbrite.com/">early bird registration pricing</a> , available for a limited time. is in your browser, so Ill see you at New Game! />The future of gaming Now if youll excuse me, its time to get back to my <a href="https://chrome.goo gle.com/webstore/detail/bnnkhdiodblfknjkjcifnpcmbkckmiaf">SONAR</a> tab Posted by Seth Ladd, Developer Advoc .lt;br /> &
ate <div class="blogger-post-footer"><img width= 1 height = 1 src= https://blogger.googleusercontent.com/tracker/2471378914199150966-7900 756314373110311?l=blog.chromium.org alt= /></div></content><link rel = replies type= application/atom+xml href= http://blog.chromium.org/feeds/7900 756314373110311/comments/default title= Post Comments /><link rel= replies typ e= text/html href= http://www.blogger.com/comment.g?blogID=2471378914199150966& amp;postID=7900756314373110311 title= 0 Comments /><link rel= edit type= appli cation/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/de fault/7900756314373110311 /><link rel= self type= application/atom+xml href= h ttp://www.blogger.com/feeds/2471378914199150966/posts/default/790075631437311031 1 /><link rel= alternate type= text/html href= http://blog.chromium.org/2011/0 8/register-now-for-new-game-conference.html title= Register now for New Game, t he conference for HTML5 game developers /><author><name>Google Chrome Blog</name ><uri>http://www.blogger.com/profile/15781870002790872375</uri><email>noreply@bl ogger.com</email><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http ://schemas.google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2. blogblog.com/img/b16-rounded.gif /></author><media:thumbnail xmlns:media= http:/ /search.yahoo.com/mrss/ url= http://1.bp.blogspot.com/-N7MgGnjVnBc/TlXJ0iYnKLI/ AAAAAAAAAvw/0ym77mvTRro/s72-c/image02.png height= 72 width= 72 /><thr:total>0< /thr:total></entry><entry><id>tag:blogger.com,1999:blog-2471378914199150966.post -2155416952482419090</id><published>2011-08-18T09:27:00.000-07:00</published><up dated>2011-08-18T09:50:04.194-07:00</updated><category scheme= http://www.blogge r.com/atom/ns# term= native client /><title type= text >Native Client Brings Sa ndboxed Native Code to Chrome Web Store Apps</title><content type= html >Wouldnt it be great if you could create web apps using your existing C and C++ code? &lt ;a href="http://code.google.com/chrome/nativeclient/">Native Client</a> lets you do just that, and it is now enabled for Chrome Web Store apps in Googl e Chromes <a href="http://www.google.com/intl/en/landing/chrome/beta/">beta channel</a>.Client apps live on the web platform, so you dont need to crea />Native te separate versions of your app for each operating system. Rather than relying on OS-specific APIs, Native Client apps use Pepper, a set of interfaces that pro vide C and C++ bindings to the capabilities of HTML5. This means that once youve ported your code to Native Client, it will work across different operating syste Today Native Client supports the Pepper APIs for 2D graphics, stereo ms, and/>only need to maintain one code base. you audio, URL fetching, sandboxed local file access (<a href="http://dev.w3.org /2009/dap/file-system/file-dir-sys.html">File API</a>), and asynchronou s message passing to and from JavaScript. In future releases we will be adding s upport for hardware accelerated 3D graphics (OpenGL ES 2.0), fullscreen mode, ne tworking (<a href="http://www.w3.org/TR/websockets/">WebSockets</a> and peer-to-peer connections), and much more. As new capabilities are added to H TML5 and Pepper, they will become available to Native Client. security. To ensu />This functionality does not come at the expense of re that Native Client is as safe as JavaScript, Native Client code is isolated f rom the operating system by two nested security sandboxes: the <a href="http: //www.chromium.org/nativeclient/reference/research-papers">Native Client sand box</a> and the <a href="http://seclab.stanford.edu/websec/chromium/chr omium-security-architecture.pdf">Chrome sandbox</a>. And unlike NPAPI p lugins or ActiveX controls, Native Client apps do not have access to the underly ing OS APIs. encourage you to start developing apps with Native Client. You ca />We n download the SDK and find tutorials, examples, API documentation, and our < a href="http://code.google.com/chrome/nativeclient/faq.html">FAQ</a> on the <a href="http://code.google.com/chrome/nativeclient/">Native Client s ite</a>. Once version 14 of Chrome hits stable channel, youll be able to up load your Native Client apps to the Chrome Web Store, where you can reach Chromes users. milestone for Native Client is architecture independence: & 160 million />The next lt;a href="http://nativeclient.googlecode.com/svn/data/site/pnacl.pdf">Portab le Native Client</a> (PNaCl) will achieve this by using <a href="http:/ /llvm.org/docs/BitCodeFormat.html">LLVM</a> bitcode as the basis for th e distribution format for Native Client content, translating it to the actual ta rget instruction set before running. Until then the Chrome Web Store will be the only distribution channel for Native Client apps. This will help us ensure that
all Native Client apps are updated to PNaCl when its ready and in the meantime a void the spread of instruction set architecture dependent apps on the web. Well b e providing updates on the progress of PNaCl on this blog. />Posted by Christian Stefansen, Produ ct Manager <div class="blogger-post-footer"><img width= 1 height= 1 src= https://blogger.googleusercontent.com/tracker/24713789141991509 66-2155416952482419090?l=blog.chromium.org alt= /></div></content><l ink rel= replies type= application/atom+xml href= http://blog.chromium.org/fee ds/2155416952482419090/comments/default title= Post Comments /><link rel= repli es type= text/html href= http://www.blogger.com/comment.g?blogID=2471378914199 150966&postID=2155416952482419090 title= 9 Comments /><link rel= edit type = application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/p osts/default/2155416952482419090 /><link rel= self type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/21554169524 82419090 /><link rel= alternate type= text/html href= http://blog.chromium.org /2011/08/native-client-brings-sandboxed-native.html title= Native Client Brings Sandboxed Native Code to Chrome Web Store Apps /><author><name>Google Chrome Bl og</name><uri>http://www.blogger.com/profile/15781870002790872375</uri><email>no reply@blogger.com</email><gd:image xmlns:gd= http://schemas.google.com/g/2005 r el= http://schemas.google.com/g/2005#thumbnail width= 16 height= 16 src= http ://img2.blogblog.com/img/b16-rounded.gif /></author><thr:total>9</thr:total></en try><entry><id>tag:blogger.com,1999:blog-2471378914199150966.post-29461272322469 41337</id><published>2011-08-04T09:15:00.000-07:00</published><updated>2011-08-0 4T09:15:01.931-07:00</updated><title type= text >Connecting Web Apps with Web In tents</title><content type= html >In todays browser ecosystem, web apps are compl etely disconnected or require the use of complicated APIs in order to make use o f a third-party service, e.g., posting a comment to Twitter from your custom pub lishing domain. What if we could give sites the ability to leverage these servi ces without any knowledge of the chosen service, except that it provides some se t of predefined functionality? Android OS addresses this problem with Intents, a facility for late run-time binding between components in the same or different applications. In the Intents system, the client applicat ion requests a generic action, e.g. share, and specifies the data to pass to the selected service application. The user is given a list of applications which h ave registered that they can handle the requested intent. The user-selected app lication is created in a new context and passed the data sent from the client, t he format of which is predefined for each specific intent type. We are hard at work designing an analogous system for the web: Web Intent s. This web platform API will provide the same benefits of Android Intents, but better suited for web applications. When designing the system, we have first a nd foremost been interested in creating a simple, easy-to-use API. With Web Int ents, you will be able to connect your web app to a service with as little as tw o lines of code! Chrome will perform the heavy lifting for you. As with Androi d, Web Intents documents an initial set of intent actions (edit, view, share, et c.) that likely cover the majority of use cases on the web today; however, as th e web grows and sites provide more functionality, new intent actions will be add ed by services that document these intents, some more popular than others. To f oster development and use of intents, we plan to create a site to browse existin g intents and add new intents. Consider an online photo s torage site run by a cash-strapped startup: the developers dont have the resource s to add image editing abilities to their app, but they feel the site wont be a h it without it. The Web Intent system will make it easy for them to offer this w ith little effort. w indow.navigator.startActivity(intent, loadEditedImage); / / This callback will be called when the service replies with the edited function loadEditedImage(data) { var im age = document.getElementById(image); setImageData(image, data); } When the user visits her favorite me megen service, the site will request registration to handle the EDIT intent for files of type image/* using the following declaration: &lt
;span style="font-family:courier"> <intent a ction=http://webintents.org/edit  type=ima ge/*  /></span&gt ; When the user initiates the EDIT action, this service i s presented to the user, along with other registered image editors. Once the us er selects Meme Generator, the referenced site is opened in a new context and is able to load the image data from the intent payload: &lt ;span style="font-family:courier">var intent = window.intent; meme Img.src = intent.data; memegenForm.onsubmit = function() { // Transform the image - meme it. addMemeTaglines(me meImg, memeTopText, memeBottomText); // Send the genera ted meme back to the client. intent.postResult(getImageData(memeImg )); }; Once postResult() is called, the Meme Generator conte xt is closed and the output data is sent back to the client via the callback pas sed to startActivity(). Mozilla is also actively <a href="http://mozillalabs.com/ blog/2011/07/web-apps-update-experiments-in-web-activities-app-discovery/">ex ploring</a> this problem space. In fact were working closely with Mozilla engineers to unify our two proposals into one simple, useful API. Visit the &lt ;a href="http://examples.webintents.org/">examples</a> page to try out the feature in any current browser. To explore using the API in your site, chec k out out the <a href="https://github.com/PaulKinlan/webintents">JavaScrip t shim</a>, which provides an implementation of the API for browsers that have not implemented this feature. We are rapidly prototyping this feature, so check back soon for an announcement when Web Intents is available behind a flag in Chrome. Posted by Jame s Hawkins, Software Engineer<div class="blogger-post-footer"> <img width= 1 height= 1 src= https://blogger.googleusercontent.com/tracker/ 2471378914199150966-2946127232246941337?l=blog.chromium.org alt= /></di v></content><link rel= replies type= application/atom+xml href= http://blog .chromium.org/feeds/2946127232246941337/comments/default title= Post Comments / ><link rel= replies type= text/html href= http://www.blogger.com/comment.g?blo gID=2471378914199150966&postID=2946127232246941337 title= 13 Comments /><li nk rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/247 1378914199150966/posts/default/2946127232246941337 /><link rel= self type= appl ication/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/d efault/2946127232246941337 /><link rel= alternate type= text/html href= http:/ /blog.chromium.org/2011/08/connecting-web-apps-with-web-intents.html title= Con necting Web Apps with Web Intents /><author><name>Google Chrome Blog</name><uri> http://www.blogger.com/profile/05118170181302314891</uri><email>noreply@blogger. com</email><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://sch emas.google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogbl og.com/img/b16-rounded.gif /></author><thr:total>13</thr:total></entry><entry>tag:blogger.com,1999:blog-2471378914199150966.post-6516722701933321402</id><pu blished>2011-08-01T17:59:00.000-07:00</published><updated>2011-08-01T18:06:05.14 6-07:00</updated><category scheme= http://www.blogger.com/atom/ns# term= websoc kets /><title type= text >New WebSocket Protocol: Secure and Extensible</title>< content type= html ><div>The WebSocket protocol specification is now large ly stable, having solved previous <a href="http://www.ietf.org/mail-archive/w eb/hybi/current/msg04744.html">security concerns</a>. As such, weve upda ted Chromium to support the latest version (<a href="http://tools.ietf.org/ht ml/draft-ietf-hybi-thewebsocketprotocol-10">draft-ietf-hybi-thewebsocketproto col-10</a>) on the dev channel (14.0.835.2). Given that the specification is now in last-call and and no further breaking changes are expected, it should no w be safe to use WebSockets for production application development.</div>& lt;div> </div><div>Please note that the new protocol i s incompatible with one which Chromium previously supported (<a href="http:// tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-00">draft-ietf-hybithewebsocketprotocol-00</a>), so existing WebSocket-based services may bre
ak. Please upgrade your servers to ones which support HyBi 10. Existing JavaScri pt code still works once the protocol version used by the browser and server mat ch.</div><div> </div><div>The new protocol in troduces some exciting new features like binary message support and compression support, but these are not quite ready yet in Chrome and will come shortly - han g tight!</div><div> </div><div>See the specs and discussion at W3C and WHATWG (<a href="http://dev.w3.org/html5/websockets /">spec</a>, <a href="http://www.whatwg.org/mailing-list">whatwg list</a>) and IETF (<a href="http://tools.ietf.org/html/draft-ietf-hybi -thewebsocketprotocol">spec</a>, <a href="https://www.ietf.org/mailm an/listinfo/hybi">HyBi list</a>) for more detail about the new protocol .</div><div> </div><div>Were more than happy t o hear your feedback, and encourage you to file any bugs you find on our <a h ref="http://code.google.com/p/chromium/issues/list">issue tracker</a>.& lt;/div> Posted by Takeshi Yoshino , Software Engineer<div class="blogger-post-footer"><img w idth= 1 height= 1 src= https://blogger.googleusercontent.com/tracker/247137891 4199150966-6516722701933321402?l=blog.chromium.org alt= /></div></co ntent><link rel= replies type= application/atom+xml href= http://blog.chromium .org/feeds/6516722701933321402/comments/default title= Post Comments /><link re l= replies type= text/html href= http://www.blogger.com/comment.g?blogID=24713 78914199150966&postID=6516722701933321402 title= 6 Comments /><link rel= ed it type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199 150966/posts/default/6516722701933321402 /><link rel= self type= application/at om+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/651 6722701933321402 /><link rel= alternate type= text/html href= http://blog.chro mium.org/2011/08/new-websocket-protocol-secure-and.html title= New WebSocket Pr otocol: Secure and Extensible /><author><name>Ian Fette</name><uri>http://www.bl ogger.com/profile/03671498484855623325</uri><email>noreply@blogger.com</email><g d:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://schemas.google.c om/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b1 6-rounded.gif /></author><thr:total>6</thr:total></entry><entry><id>tag:blogger. com,1999:blog-2471378914199150966.post-9192367780081314346</id><published>2011-0 8-01T17:21:00.000-07:00</published><updated>2011-08-01T17:23:47.216-07:00</updat ed><title type= text >Chrome Web Store: Now with more international support and with In-App Payments</title><content type= html >Since Google I/O, weve been work ing hard to make the Chrome Web Store available to <a href="http://blog.chrom ium.org/2011/02/chrome-web-store-international-support.html" target=_blank>mo re users around the world</a> as well as to provide <a href="http://blo g.chromium.org/2011/05/chrome-web-store-in-41-languages-and-in.html" target=_bla nk>additional monetization opportunities</a> for developers. Today, we re happy to share progress in both of these areas. We &lt ;a href="http://googlecommerce.blogspot.com/2011/07/make-money-with-in-app-payme nts-for-web.html" target=_blank>recently launched</a> the much awaited <a href="https://checkout.google.com/inapppayments/" target=_blank>In App Payments API</a> in the US. This API provides a simple and effective way t o monetize your apps in the Chrome Web Store, allowing you to complete transacti ons with buyers from 140 countries. Integration is simple - all you need is to d o is to insert a few lines of code. An even more exciting feature of the API is the 5% flat transaction fee pricing. To learn more about In-App Payments, check out our <a href="http://code.google.com/apis/inapppayments/" target=_blank&gt ;docs</a> and a <a href="http://iap-hello-world.appspot.com/" target=_b lank>sample app complete with source code</a> or watch <a href="http ://www.youtube.com/watch?v=9EEOWbIqQdE" target=_blank>our short video</a&g t;. We look forward to expanding this service to additional developer locations as quickly as possible. <center><iframe width="5 00" height="314" src="http://www.youtube.com/embed/9EEOWbIqQdE?rel=0" frameborde r="0" allowfullscreen></iframe></center> With our in-s tore payments, developers in Australia, Austria, Belgium, Canada, Denmark, Finla nd, France, Germany, Hong Kong, Italy, Japan, Netherlands, New Zealand, Norway,
Portugal, Singapore, Spain, Sweden, Switzerland, United Kingdom can now complete merchant account sign up and start adding their paid apps to the Chrome Web Sto re. Paid apps will be published to international users later this year. In the m eantime, you can <a href="http://code.google.com/chrome/extensions/i18n.html" target=_blank>localize your app listing</a> to make it accessible to m ore people and be eligible for promotion in local store fronts. Weve also added the ability to target or exclude specific markets. In thi s launch, Chrome Web Store developers can publish their apps to the following re gions: Argentina, Australia, Austria (new), Belgium (new), Brazil, Canada, Czech Republic (new), Denmark (new), Finland (new), France, Germany, Hong Kong (new), India, Indonesia (new), Israel (new), Italy, Japan, Mexico, Netherlands, New Ze aland (new), Norway (new), Philippines (new), Poland, Portugal, Russia (new), Si ngapore (new), Spain, Sweden (new), Switzerland (new), United Kingdom and United States. Our users will only see apps that were published for their market. We a lso added support for our various featured lists to be targeted by market, allow ing users to see the best apps for their market. If you h ave additional questions, please join our <a href="https://groups.google.com/ a/chromium.org/group/chromium-apps/topics" target=_blank>developer discussion group</a>. Posted by Elvin Lee, Software Engineer<div class="blogger-post-footer"& gt;<img width= 1 height= 1 src= https://blogger.googleusercontent.com/track er/2471378914199150966-9192367780081314346?l=blog.chromium.org alt= />< /div></content><link rel= replies type= application/atom+xml href= http://b log.chromium.org/feeds/9192367780081314346/comments/default title= Post Comment s /><link rel= replies type= text/html href= http://www.blogger.com/comment.g? blogID=2471378914199150966&postID=9192367780081314346 title= 6 Comments />< link rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/2 471378914199150966/posts/default/9192367780081314346 /><link rel= self type= ap plication/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts /default/9192367780081314346 /><link rel= alternate type= text/html href= http ://blog.chromium.org/2011/08/chrome-web-store-now-with-more.html title= Chrome Web Store: Now with more international support and with In-App Payments /><autho r><name>Google Chrome Blog</name><uri>http://www.blogger.com/profile/15781870002 790872375</uri><email>noreply@blogger.com</email><gd:image xmlns:gd= http://sche mas.google.com/g/2005 rel= http://schemas.google.com/g/2005#thumbnail width= 1 6 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gif /></author><med ia:thumbnail xmlns:media= http://search.yahoo.com/mrss/ url= http://img.youtube .com/vi/9EEOWbIqQdE/default.jpg height= 72 width= 72 /><thr:total>6</thr:total ></entry><entry><id>tag:blogger.com,1999:blog-2471378914199150966.post-151812535 9438141713</id><published>2011-07-22T09:15:00.000-07:00</published><updated>2011 -07-22T09:27:49.774-07:00</updated><title type= text >Writing Extensions More Se curely</title><content type= html >Extensions are powerful pieces of software in modern browsers, and as such, you should help ensure that your extensions are n ot susceptible to security exploits. If an attacker manages to exploit a vulnera bility in an extension, its serious business because they may gain access to the same privileges that the extension has. The Chrome extens ions system has a number of <a href="http://blog.chromium.org/2009/12/securit y-in-depth-extension-system.html">built-in protections</a> to make it m ore difficult to introduce exploitable code, but certain coding patterns can sti ll open up the risk of exploits like a cross-site scripting (XSS) attack. Many of these mistakes are common to web programming in general, so it wouldnt be a ba d idea to check out one of the <a href="https://www.owasp.org/index.php/XSS_( Cross_Site_Scripting)_Prevention_Cheat_Sheet">many</a> good <a href= "http://en.wikipedia.org/wiki/Cross-site_scripting">articles</a> on the net about XSS bugs. Here are some of our recommendations for writing healthier extensions. Minimize your permissions The most important thing to consider is whethe r youre declaring the minimal set of permissions that you need to function. That way, if you do have a security bug in your code, the amount of permissions youre exposing to the attacker is minimal as well. Avoid requesting <all_urls> (
*/*) permissions for hosts if you only need to access a couple, and dont copy and paste your manifest from example code blindly. Review your manifest to make sur e youre only declaring what you need. This applies to permissions like tabs, hist ory, cookies, etc. in addition to host permissions. For example, if all youre us ing is <a href="http://code.google.com/chrome/extensions/tabs.html#method-cre ate">chrome.tabs.create</a>, you dont actually need the tabs permission. Use content_security_policy in your manife st Starting in Chrome 14, we will begin su pporting <a href="http://dvcs.w3.org/hg/content-security-policy/raw-file/tip/ csp-specification.dev.html">Content Security Policy</a> in extensions v ia the <a href="http://code.google.com/chrome/extensions/trunk/manifest.html# content_security_policy">content_security_policy</a> manifest field. Th is allows you to control where scripts can be executed, and it can be used to he lp reduce your exposure to cross-site scripting vulnerabilities. For example, to specify that your extension loads resources only from its own package, use the following policy: If you need to include scripts from specific hosts, you can add those hosts to this property. Dont use <script s rc> with an HTTP URL When you inclu de javascript into your pages using an HTTP URL, youre opening your extension up to man-in-the-middle (MITM) attacks. When you do so in a content script, you hav e a similar effect on the pages youre injected into. An attacker on the same net work as one of your users could replace the contents of the script with content that they control. If that happens, they could do anything that your page can do . If you need to fetch a remote script, always use HTTPS from a trusted source. Dont use eval()</s trong> The eval() function is very powerful and you sh ould refrain from using it unless absolutely necessary. Where did the code come from that you passed into eval()? If it came from an HTTP URL, youre vulnerable t o the same issue as the previously mentioned <script> tag. If any of the content that you passed into eval() is based on content from a random web page the user visits, youre vulnerable to escaping bugs. For example, lets say th at you have some code that looks like this: function displayAddress(address) { // address was det ected and grabbed from the current page eval("alert( " + address + " )"); } If it turned out that you had a bug in your parsing code, the address might wind up looking something like this: ); dosome thingevil(); Theres almost always a better al ternative to using eval(). For example, you can use JSON.parse if you want to pa rse JSON (with the added benefit that it runs faster). Its worth the extra effor t to use alternatives like this. Dont use in nerHTML or document.write() Its really temp ting to use innerHTML because its much simpler to generate markup dynamically tha n to create DOM nodes one at a time. However, this again sets you up for bugs in escaping your content. For example: function displayAddress(address) { // address was detected a nd grabbed from the current page myDiv.innerHTML = " " + address + ""); } This would allow an attacker to make an address like the following and onc e again run some script in your page: <script>dosomethingevil();</script&amp ;gt; Instead of innerHTML, you can manually create DOM nodes and use innerText to insert dynamic content. Beware external content <br /&gt ;In general, if youre generating dynamic content based on data from outside of yo ur extension (such as something you fetched from the network, something you pars ed from a page, or a message you received from another extension, etc.), you sho uld be extremely careful about how you use it. If you use this data to generate
content within your extension, you might be opening your users up to increased r isk. You can also read a <a href="http://code.google.c om/chrome/extensions/content_scripts.html#security-considerations">few more&l t;/a> examples of the issues discussed here in our extension docs. We hope th ese recommendations help you create better and safer extensions for everyone.&lt ;br /> Posted by Erik Kay, Softwar e Engineer </all_urls><div class="blogger-post-footer"> <img width= 1 height= 1 src= https://blogger.googleusercontent.com/tracker/ 2471378914199150966-1518125359438141713?l=blog.chromium.org alt= /></di v></content><link rel= replies type= application/atom+xml href= http://blog .chromium.org/feeds/1518125359438141713/comments/default title= Post Comments / ><link rel= replies type= text/html href= http://www.blogger.com/comment.g?blo gID=2471378914199150966&postID=1518125359438141713 title= 5 Comments /><lin k rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/2471 378914199150966/posts/default/1518125359438141713 /><link rel= self type= appli cation/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/de fault/1518125359438141713 /><link rel= alternate type= text/html href= http:// blog.chromium.org/2011/07/writing-extensions-more-securely.html title= Writing Extensions More Securely /><author><name>Google Chrome Blog</name><uri>http://ww w.blogger.com/profile/05118170181302314891</uri><email>noreply@blogger.com</emai l><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://schemas.goog le.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/im g/b16-rounded.gif /></author><thr:total>5</thr:total></entry><entry><id>tag:blog ger.com,1999:blog-2471378914199150966.post-7641044569018855631</id><published>20 11-07-13T09:26:00.000-07:00</published><updated>2011-07-13T11:37:42.375-07:00<category scheme= http://www.blogger.com/atom/ns# term= extensions /><ti tle type= text >Chrome Extensions: Now with more powerful scripts and improved p roxy management.</title><content type= html >In Chrome 13, we added some new cap abilities to content scripts and proxy management. First, you can now make cross-origin XMLHttpRequest calls with the privileges of the e xtension directly from your content script. You will no longer need to relay th ese requests through a background page; this should simplify your code. In some cases, it may even eliminate your need to use a background page. Heres a <a hr ef="http://code.google.com/chrome/extensions/samples.html#6871d09f4a96bf9d4b6cc7 24d00e909cee0f3902">sample extension</a> which demonstrates the old way a content script could make a cross domain request. As you can see, the extensi on required a <a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome /common/extensions/docs/examples/howto/contentscript_xhr/background.html?view=ma rkup&pathrev=91622">background page</a> to route the cross-origin c alls through a chrome.extension.onReques t listener. Using the new content script cross-origin capabilities, we were able to successfully <a href="http://src.chromium.org/viewvc/chrome? view=rev&revision=91623">rewrite the extension</a> to completely el iminate the background page requirement. This reduces the memory required to run the extension, and reduces code complexity as well. This also means that Grease monkey scripts that use GM_xmlhttpReques t - such as the classic <a href="http://userscripts.org/scripts/ show/1859">Book Burro</a> - will now work in Chrome. Second, we improved how <a href="http://code.google.com/chrome/extension s/trunk/content_scripts.html#match-patterns-globs">match patterns</a> w ork. Until this release you could specify a matches array for your content script - the URLs over which it should operate. In Chrome 13 you can now also specify an exclude_matches array, where you can indicate the pages in which your content scripts should not work. This should allow more prec ise targeting of your content script. Finally, we added s upport for the <a href="http://wiki.greasespot.net/Talk:Metadata_Block">@r un-at</a> command for imported Greasemonkey scripts, so you can control wh en your script is loaded in the same way youve been able to do for content script s. Running scripts at different points in a page s lifecycle can enable additio
nal functionality. For example, we ve written <a href="http://src.chromium.o rg/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/howto/userscri pt-runat/runat.user.js?view=markup">a script</a> which runs at "documen t-start" and lists all of the HTTP resources included in the current page. In addition to these improvements to scripts, weve been working hard to allow extensions to manage Chromes proxy settings using different config uration options. With the <a href="http://code.google.com/chrome/extensions/t runk/proxy.html">Proxy Extension API</a>, you can now configure proxy s ettings by choosing from several options including auto detection, the host OSs s ystem default, PAC scripts or fixed <a href="http://code.google.com/chrome/ex tensions/trunk/proxy.html#proxy_rules">ProxyRules</a>. These new configuration options allow for more fine grained proxy control s, which we invite you to try out. There are already several 3rd party extension s available in the Chrome Web Store that showcase the API and its new capabiliti es, including <a href="https://chrome.google.com/webstore/detail/eejcbegfnjfj nmdikkplhbhnemddchbn">Proxy Anywhere</a> and <a href="https://chrome .google.com/webstore/detail/ipidcfpkiejdjjibecbippcokfipcfad">Proxy SwitchyPl us</a>. Let us know what you think of these new f eatures and what else you might like to see us do by joining the discussion at c hromium-extensions@chromium.org. Posted by Tessa MacDuff and Mihai Parparita, Software Engineers </sp an><div class="blogger-post-footer"><img width= 1 height= 1 src= h ttps://blogger.googleusercontent.com/tracker/2471378914199150966-764104456901885 5631?l=blog.chromium.org alt= /></div></content><link rel= replies type= application/atom+xml href= http://blog.chromium.org/feeds/764104456901885 5631/comments/default title= Post Comments /><link rel= replies type= text/htm l href= http://www.blogger.com/comment.g?blogID=2471378914199150966&postID= 7641044569018855631 title= 4 Comments /><link rel= edit type= application/atom +xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/76410 44569018855631 /><link rel= self type= application/atom+xml href= http://www.b logger.com/feeds/2471378914199150966/posts/default/7641044569018855631 /><link r el= alternate type= text/html href= http://blog.chromium.org/2011/07/chrome-ex tensions-now-with-more.html title= Chrome Extensions: Now with more powerful sc ripts and improved proxy management. /><author><name>Google Chrome Blog</name>http://www.blogger.com/profile/15781870002790872375</uri><email>noreply@blogg er.com</email><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http:// schemas.google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blo gblog.com/img/b16-rounded.gif /></author><thr:total>4</thr:total></entry><entry> <id>tag:blogger.com,1999:blog-2471378914199150966.post-1342684305552804657</id>< published>2011-07-06T14:15:00.000-07:00</published><updated>2011-07-07T16:24:37. 151-07:00</updated><category scheme= http://www.blogger.com/atom/ns# term= webg l /><title type= text >Using Cross-domain images in WebGL and Chrome 13</title>< content type= html >A few weeks ago, we became aware of a <a href="http://www .khronos.org/webgl/public-mailing-list/archives/1010/msg00034.html">security issue</a> with WebGL: <a href="http://www.contextis.co.uk/resources/blo g/webgl/poc/index.html">shaders could be used</a> to indirectly deduce the contents of textures uploaded to the GPU. As a result, the WebGL specificati on was <a href="http://www.khronos.org/registry/webgl/specs/latest/#4.2">u pdated</a> to be more restrictive when it comes to using cross-domain imag es and videos as WebGL textures. As a result, Chrome 13 ( and Firefox 5) will no longer allow cross-domain media as a WebGL texture. The d efault behavior will be a DOM_SECURITY_ERR. However, applications may still util ize images and videos from another domain with the cooperation of the server hos ting the media, otherwise known as <a href="http://www.w3.org/TR/cors/">CO RS</a>. <a href="http://www.whatwg.org/specs/web -apps/current-work/multipage/urls.html#cors-settings-attribute">CORS support& lt;/a> for MediaElements has also been fully implemented in WebKit by setting a new .crossOrigin attribu te. This means that sophisticated applications that were using cross-origin text ures before, can continue to do so, assuming the hosting image server grants the
necessary cross-origin permission using CORS. If you want to enable CORS reques t on an image, all you have to do is add one line of code: var img = document.createElement( img ); img.onload = function(e) { }; img.crossOrigin = ; // no credentials flag. Same as img.crossOrigin= anonymous img.src = h ttp://other-domain.com/image.jpg ; Another n ice property that we gain from this new setting is the ability to read cross-dom ain image data set on a 2D canvas. Normally, filling a canvas with a remote imag e (e.g. ctx.drawImage()) fl ips the <a href="http://dev.w3.org/html5/spec/Overview.html#security-with-ca nvas-elements">origin-clean flag</a> to false. Attempting to read back the pixels using ctx.toDataURL()</spa n> or ctx.getImageData() throws a SECURITY_ERR. This is to prevent information leakage. However, when &l t;span style="font-family:courier">.crossOrigin is set (and the remote server supports CORS), the read is possible. For example: var img = document.createElement ( img ); img.onload = function(e) { ctx.drawImage(img, 0, 0, canvas.width, canvas.height); }; img.crossOrigin = ; img.src = http: //other-domain.com/image.jpg ; Unfortunately , this new restriction in WebGL means that some existing content will break. Weve already started working with external image and video hosting services like Fli ckr to evangelize the <a href="http://enable-cors.org/">use of CORS</a& gt; on their images. You can test this new behavior today using images from Picasa, which already sends a CORS header allowing cross-orig in requests, and the <a href="http://www.chromium.org/getting-involved/dev-ch annel">Chrome dev channel</a>. Posted by Eric Bidelman, Developer Advocate <div class="blogger-post-footer"><img width= 1 height= 1 src= https://blogger .googleusercontent.com/tracker/2471378914199150966-1342684305552804657?l=blog.ch romium.org alt= /></div></content><link rel= replies type= applicat ion/atom+xml href= http://blog.chromium.org/feeds/1342684305552804657/comments/ default title= Post Comments /><link rel= replies type= text/html href= http: //www.blogger.com/comment.g?blogID=2471378914199150966&postID=13426843055528 04657 title= 4 Comments /><link rel= edit type= application/atom+xml href= ht tp://www.blogger.com/feeds/2471378914199150966/posts/default/1342684305552804657 /><link rel= self type= application/atom+xml href= http://www.blogger.com/fee ds/2471378914199150966/posts/default/1342684305552804657 /><link rel= alternate type= text/html href= http://blog.chromium.org/2011/07/using-cross-domain-imag es-in-webgl-and.html title= Using Cross-domain images in WebGL and Chrome 13 /> <author><name>Christos</name><uri>http://www.blogger.com/profile/153118783332177 71150</uri><email>noreply@blogger.com</email><gd:image xmlns:gd= http://schemas. google.com/g/2005 rel= http://schemas.google.com/g/2005#thumbnail width= 16 h eight= 16 src= http://img2.blogblog.com/img/b16-rounded.gif /></author><thr:tot al>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-2471378914199150966 .post-7212866542901969050</id><published>2011-06-29T07:59:00.000-07:00</publishe d><updated>2011-06-29T10:24:14.337-07:00</updated><category scheme= http://www.b logger.com/atom/ns# term= chrome web store /><title type= text >Cloud Coding an d Beyond: Web Development Apps in the Chrome Web Store</title><content type= htm l >When we talk <a href="http://www.google.com/chromebook/">Chromebooks&lt ;/a> with our developer friends, a common reaction we get is I can see why my [insert-relative-here] would use it, but I need my PC for coding. Over the last few years, browser-based coding has grown from a research topic to a viable prac tice. You can already find many development apps on the <a href="chrome.googl e.com/webstore">Chrome Web Store</a> today. Some are conventional code editors and IDEs, built right into the browser. Others are oriented more around prototyping and design. There are also many tools for project management. First up, IDEs. You can now code, debug, and deploy real progra
ms from the browser. A popular example at Google IO was <a href="https://chro me.google.com/webstore/detail/nbdmccoknlfggadpfkmcpnamfnbkmkcp">Cloud9</a& gt;, an IDE for JavaScript, Python, PHP, and Ruby. Cloud9 uses the HTML5 <a h ref="http://www.html5rocks.com/en/tutorials/file/filesystem/">FileSystem</ a> capability and AppCache to sync files, so you can even code offline. There are many other IDEs in the web store too, such as <a href="https://chrome.go ogle.com/webstore/detail/fgbjpbdfegnodokpoejnbhnblcojccal">Kodingen</a> , <a href="https://chrome.google.com/webstore/detail/lbalghnpcjmlpmmocijdfogh ihgocakd">Codey</a>, <a href="https://chrome.google.com/webstore/det ail/igajdgcflbbkkjamijjpjadkcncjloog">Akshell</a>, <a href="https:// chrome.google.com/webstore/detail/lefigjbiimiemfhjmibbgemkpenelmag?hl=en-US"> eXo Cloud IDE</a>, and <a href="https://chrome.google.com/webstore/deta il/ncblfioagpfcaojcjlocnakemfjdcdhh">PHPAnywhere</a>. <a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-Yxgj2Xvjros/TgtexL7igpI/AAAAAAAAAFI/-tJaAsfn0tg/ s1600/Screen%2Bshot%2B2011-06-29%2Bat%2B9.04.18%2BAM.png"><img style="disp lay:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;w idth: 400px; height: 187px;" src="http://4.bp.blogspot.com/-Yxgj2Xvjros/TgtexL7i gpI/AAAAAAAAAFI/-tJaAsfn0tg/s400/Screen%2Bshot%2B2011-06-29%2Bat%2B9.04.18%2BAM. png" border="0" alt=""id="BLOGGER_PHOTO_ID_5623692758811312786" /></a>& lt;br />Its not all about coding though. There are also apps focusing on web d esign, for people who want to make a web page without coding or perhaps experime nt with a few concepts early on. Being able to edit and design web pages inside the tool that will display them is a very powerful concept. <a href="https:// chrome.google.com/webstore/detail/ofkbkdeephpnfkfkflgigmoojnghgeph">BuildorLi te</a> and <a href="https://chrome.google.com/webstore/detail/kapbhjlif fabbcegjdkoknpmmohhdepg">BuildorPro</a> let you construct a web page vi a a graphical user interface, and publish it straight on their servers. <a hr ef="https://chrome.google.com/webstore/detail/kgpklhhhiiafnocfiikcpffkogjkdmki"& gt;Handcraft</a> and <a href="https://chrome.google.com/webstore/detail /mglnbanmebacbohplmcogiompoijbhnm?hl=en-US">Mockingbird</a> are two app s aimed at design and prototyping. And if you want a scratchpad to try a few cod ing experiments, check out <a href="https://chrome.google.com/webstore/detail /hiigmadmngbpbmacbkfngpkjfmmpagfk">JSFiddle</a>. <br /&gt ;<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href= "http://4.bp.blogspot.com/-LcvsmHy888M/TgtfF-jjJ1I/AAAAAAAAAFQ/THGPtkseWhg/s1600 /Screen%2Bshot%2B2011-06-29%2Bat%2B10.20.46%2BAM.png"><img style="display: block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width : 400px; height: 184px;" src="http://4.bp.blogspot.com/-LcvsmHy888M/TgtfF-jjJ1I/ AAAAAAAAAFQ/THGPtkseWhg/s400/Screen%2Bshot%2B2011-06-29%2Bat%2B10.20.46%2BAM.png " border="0" alt=""id="BLOGGER_PHOTO_ID_5623693115998283602" /></a> Launching software isnt just about designing and coding your apps; its als o about managing the entire workflow, from planning release schedules to triagin g bug reports. One example is <a href="https://chrome.google.com/webstore/det ail/oaianekphgmiibhdffnoimngeolnailp?hl=en-US">GitHub Issues</a>, provi ding a quick, app-like, way to track project issues. Another is <a href="http s://chrome.google.com/webstore/detail/cfjmekcoebepooldamlampienojfjljf?hl=en-US" >Launchlist Pro</a>, a checklist you can use to launch your website.&lt ;br /> <a onblur="try {parent.deselectBloggerImageGracefully(); } catch(e) {}" href="http://2.bp.blogspot.com/-wyOgwft9VyM/TgtfMgpiZdI/AAAAAAAAA FY/M3rVtJgdHls/s1600/Screen%2Bshot%2B2011-06-29%2Bat%2B10.21.01%2BAM.png">&lt ;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointe r; cursor:hand;width: 400px; height: 279px;" src="http://2.bp.blogspot.com/-wyOg wft9VyM/TgtfMgpiZdI/AAAAAAAAAFY/M3rVtJgdHls/s400/Screen%2Bshot%2B2011-06-29%2Bat %2B10.21.01%2BAM.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5623693228229420498" /></a> Chrome aims to bring simplicity, speed, and security to all users, and that includes developers. Being cloud-based means these tools are always up to date, and running inside the browsers sandbox minimises the sec urity risk to your machine. Theres no complicated install process and the only de pendency is Chrome itself, which is automatically kept up to date. Just install
the app and get coding. Were especially excited about what this means for new developers, as programming tools have never been more access ible to everyone. So whether youre a seasoned veteran or just looking to get star ted, visit the <a href="http://chrome.google.com/webstore">Chrome Web Stor e</a> today and build something awesome in your browser! Posted by Michael Mahemoff and Paul Kinlan , Chrome Developer Relations <div class="blogger-post-footer"&gt ;<img width= 1 height= 1 src= https://blogger.googleusercontent.com/tracker /2471378914199150966-7212866542901969050?l=blog.chromium.org alt= /></d iv></content><link rel= replies type= application/atom+xml href= http://blo g.chromium.org/feeds/7212866542901969050/comments/default title= Post Comments /><link rel= replies type= text/html href= http://www.blogger.com/comment.g?bl ogID=2471378914199150966&postID=7212866542901969050 title= 8 Comments /><li nk rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/247 1378914199150966/posts/default/7212866542901969050 /><link rel= self type= appl ication/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/d efault/7212866542901969050 /><link rel= alternate type= text/html href= http:/ /blog.chromium.org/2011/06/cloud-coding-and-beyond-web-development.html title= Cloud Coding and Beyond: Web Development Apps in the Chrome Web Store /><author> <name>Christos</name><uri>http://www.blogger.com/profile/15311878333217771150<email>noreply@blogger.com</email><gd:image xmlns:gd= http://schemas.google.c om/g/2005 rel= http://schemas.google.com/g/2005#thumbnail width= 16 height= 1 6 src= http://img2.blogblog.com/img/b16-rounded.gif /></author><media:thumbnail xmlns:media= http://search.yahoo.com/mrss/ url= http://4.bp.blogspot.com/-Yxgj 2Xvjros/TgtexL7igpI/AAAAAAAAAFI/-tJaAsfn0tg/s72-c/Screen%2Bshot%2B2011-06-29%2Ba t%2B9.04.18%2BAM.png height= 72 width= 72 /><thr:total>8</thr:total></entry><e ntry><id>tag:blogger.com,1999:blog-2471378914199150966.post-7665878471236738548< /id><published>2011-06-20T08:19:00.000-07:00</published><updated>2011-06-20T08:2 5:29.212-07:00</updated><category scheme= http://www.blogger.com/atom/ns# term= chromeframe /><title type= text >Introducing Non-Admin Chrome Frame</title><con tent type= html >We <a href="http://blog.chromium.org/2009/09/introducing-goo gle-chrome-frame.html">released</a> Google Chrome Frame in September 20 09 to expand the reach of modern web technologies and help developers take advan tage of HTML5 s capabilities. Since then, we ve seen great adoption of the plugin by end users and developers. Even more exciting, weve heard from developers th at Google Chrome Frame is enabling them to create legacy-free apps that are easi er to build, maintain, and optimize. However, there was o ne remaining obstacle to making Chrome Frame accessible to users of older browse rs - users needed to have administrative privileges on their machines to install Chrome Frame. At this year s Google I/O we <a href="http://www.google.com/ev ents/io/2011/sessions/html5-today-with-google-chrome-frame.html">announced&lt ;/a> this obstacle has finally been removed. Non-Admin Chrome Frame runs a helper process at startup to assist with loading the Chrome Frame plug-in into Internet Explorer. The helper process is designed to consume almost no system resources while running. Once installed, non-admin users will have the same no-friction experience that admin users of Chrome Frame have today . You can try it yourself by installing the new non-admin version of Chrome Frame <a href="http://www.google.com/chromeframe/eula.html ?user=true">here</a>. This is now available in our developer channel an d is coming to stable channel very soon. For more technic al details, please see the <a href="http://www.chromium.org/developers/how-to s/chrome-frame-getting-started/chrome-frame-faq">Chrome Frame FAQ</a>. Please share your feedback in our <a href="https://groups.google.com/group/go ogle-chrome-frame?pli=1">discussion group</a> and if you encounter any bugs while using Chrome Frame, please file them on Chromium s <a href="http:/ /code.google.com/p/chromium/issues/entry?template=ChromeFrame%20Issue">issue tracker</a>. Well be working hard to bring Non-Admin Chrome Frame up to the beta and stable channels over the coming weeks. You can help us move this up to stable as quickly as possible by trying out the current release and sending us your feedback! Posted by
Robert Shield, Software Engineer <div class="blogger-post-footer "><img width= 1 height= 1 src= https://blogger.googleusercontent.com/tra cker/2471378914199150966-7665878471236738548?l=blog.chromium.org alt= />&l t;/div></content><link rel= replies type= application/atom+xml href= http:/ /blog.chromium.org/feeds/7665878471236738548/comments/default title= Post Comme nts /><link rel= replies type= text/html href= http://www.blogger.com/comment. g?blogID=2471378914199150966&postID=7665878471236738548 title= 7 Comments / ><link rel= edit type= application/atom+xml href= http://www.blogger.com/feeds /2471378914199150966/posts/default/7665878471236738548 /><link rel= self type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/pos ts/default/7665878471236738548 /><link rel= alternate type= text/html href= ht tp://blog.chromium.org/2011/06/introducing-non-admin-chrome-frame.html title= I ntroducing Non-Admin Chrome Frame /><author><name>Christos</name><uri>http://www .blogger.com/profile/15311878333217771150</uri><email>noreply@blogger.com</email ><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://schemas.googl e.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog.com/img /b16-rounded.gif /></author><thr:total>7</thr:total></entry><entry><id>tag:blogg er.com,1999:blog-2471378914199150966.post-5886492252609542755</id><published>201 1-06-15T14:04:00.000-07:00</published><updated>2011-06-15T14:18:07.318-07:00</up dated><title type= text >Testing Chromium: AddressSanitizer, a fast memory error detector.</title><content type= html ><a href="http://valgrind.org/">Valg rind</a> is a great tool for detecting memory errors. We are running many Chromium tests under Valgrind and it has helped us find <a href="http://code. google.com/p/chromium/issues/list?can=1&q=Stability%3DValgrind&colspec=I D+Stars+Pri+Area+Feature+Type+Status+Summary+Modified+Owner+Mstone+OS&x=msto ne&y=area&cells=tiles">hundreds of significant bugs</a>. Howeve r, when we run binaries under Valgrind, testing becomes at least 10 times slower . This huge slowdown costs us more than just machine time; our trybots and build bots cant provide fast feedback and some tests fail due to timeouts. & lt;br />A month ago we released <a href="http://code.google.com/p/addresssanitizer/wiki/AddressSanitizer">AddressSanitizer</a> (aka ASan), a new testing tool. ASan consists of two parts: <ul><li>A comp iler which performs instrumentation - currently we use a modified <a href="ht tp://llvm.org/">LLVM</a>/<a href="http://clang.llvm.org/">Clang&l t;/a> and we re trying to contribute our code to the core LLVM package.</l i><li>A run-time library that replaces malloc(), free()&lt ;/span>and friends. </li></ul> The custom malloc() allocates more bytes than requ ested and poisons the redzones around the region returned to the caller. The custo m free() poisons the entire r egion and puts it into quarantine for some time. The instrumented code produced by the compiler checks if the address being accessed is poisoned and if so, repo rts an error. The compiler also inserts poisoned redzones between objects on sta ck to catch stack buffer overrun/underrun. ASan helps us find a subset of bugs that are detectable by Valgrind like heap buffer overrun/u nderrun (out-of-bounds access) and Use after free. It can also detect bugs that Va lgrind can not find, such as stack buffer overrun/underrun. Last month alone, AS an helped us find more than 20 bugs in Chromium including some that could have p otentially led to security vulnerabilities. What makes AS an even more powerful than other comparable tools is its speed. On <a href="h ttp://www.spec.org/cpu2006/">SPEC CPU2006</a> benchmarks the <a href ="http://code.google.com/p/address-sanitizer/wiki/PerformanceNumbers">average slowdown</a> is about 2x. On Chromiums browser_tests, the slowdown is about 20%. If you are curious to learn why ASan is faster than comparable tools read t his <a href="http://code.google.com/p/address-sanitizer/wiki/AddressSanitizer Algorithm">article</a>. Today ASan works only on Linux (x86 and x86_64) and ChromiumOS, but we re planning to port it to other p latforms in the near future. In the coming months we also plan to setup various ASan buildbots and trybots for Chromium. The <a href=
"http://code.google.com/p/address-sanitizer/wiki/AddressSanitizer">AddressSan itizer home page</a> has the instructions for running it with your favorit e project outside of Chromium. If you are working on Chromium, refer to this &lt ;a href="https://sites.google.com/a/chromium.org/dev/developers/testing/addresss anitizer">page</a> for instructions. If you have any questions or sugge stions, feel free to contact address-sanitizer@googlegroups.com Posted by Kostya Serebryany, Software Eng ineer <div class="blogger-post-footer"><img width= 1 heig ht= 1 src= https://blogger.googleusercontent.com/tracker/2471378914199150966-58 86492252609542755?l=blog.chromium.org alt= /></div></content><link r el= replies type= application/atom+xml href= http://blog.chromium.org/feeds/58 86492252609542755/comments/default title= Post Comments /><link rel= replies t ype= text/html href= http://www.blogger.com/comment.g?blogID=247137891419915096 6&postID=5886492252609542755 title= 2 Comments /><link rel= edit type= app lication/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/ default/5886492252609542755 /><link rel= self type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/posts/default/5886492252609542 755 /><link rel= alternate type= text/html href= http://blog.chromium.org/2011 /06/testing-chromium-addresssanitizer-fast.html title= Testing Chromium: Addres sSanitizer, a fast memory error detector. /><author><name>Christos</name><uri>ht tp://www.blogger.com/profile/15311878333217771150</uri><email>noreply@blogger.co m</email><gd:image xmlns:gd= http://schemas.google.com/g/2005 rel= http://schem as.google.com/g/2005#thumbnail width= 16 height= 16 src= http://img2.blogblog .com/img/b16-rounded.gif /></author><thr:total>2</thr:total></entry><entry><id>t ag:blogger.com,1999:blog-2471378914199150966.post-6963395838232395757</id><publi shed>2011-06-14T15:00:00.000-07:00</published><updated>2011-06-14T15:21:40.933-0 7:00</updated><category scheme= http://www.blogger.com/atom/ns# term= security /><title type= text >New Chromium security features, June 2011</title><content t ype= html >When the Google Chrome Security Team isnt busy giving prompt attention to finding and fixing bugs, were always looking for new security features to add and hardening tweaks to apply. There are some changes worth highlighting in our current and near-future Chromium versions: Chromium 11: strong random numbers for the web We added a new Javascript API for getting access to a good sourc e of system entropy from a web page. The new API is window.crypto.getRandomValues. Web pages should not curre ntly be using Math.random for anything sensitive. Instead of making a round-trip to the server to generate strong random numbers, web sites can now generate str ong random numbers entirely on the client. Chromium 12: user-specified HSTS preloads and certificat e pins Advanced users can enable stronger security for s ome web sites by visiting the network internals page: chrome://net-internals/#hs ts <a onblur="try {parent.deselectBloggerImageGraceful ly();} catch(e) {}" href="http://3.bp.blogspot.com/-s70rejSpThk/TffcXzAO17I/AAAA AAAAAFA/bX2hwmYzmNk/s1600/hsts.png"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 2 38px;" src="http://3.bp.blogspot.com/-s70rejSpThk/TffcXzAO17I/AAAAAAAAAFA/bX2hwm YzmNk/s400/hsts.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5618201361554266034" /></a> You can now force HTTPS for any domain you want, and even pin that domain so that only a more trusted subset of CAs are permitted to id entify that domain. .&l t;br /> Chromium 13: blockin g HTTP auth for subresource loads Theres an unfortunate c onflict between a browsers HTTP basic auth dialog, the location bar, and the load ing of subresources (such as attacker-provided <img&gt tag references ). Its possible for a basic auth dialog to pop up for a different origin from the origin shown in the URL bar. Although the basic auth dialog identifies its orig in, the user might reasonably look to the URL bar for trust guidance. To resolve this, weve blocked HTTP basic auth for subresource loads where the resource origin is different to the top-level URL bar origin. We also added the command line flag switch --allow-cross-origin-auth-prompt in case anyo ne has legacy applications which require the old behavior. Chromium 13: Content-Security-Policy sup port We added an initial implementation of <a href="h ttp://people.mozilla.com/~bsterne/content-security-policy/ ">Content Security Policy</a>, which was first introduced in Firefox 4. You can use the X-We bKit-CSP header to experiment with our implementation. Were working with Mozilla and others through the W3C to finish the standard. Once thats done, well remove su pport for the X-WebKit-CSP header and add support for the final header name. Ple ase feel encouraged to kick the tires and let us know how we can improve this fe ature! Chromium 13: built-in certificate pinning and HSTS Were experimenting with ways to improve the security of HTTPS. One of the sites were collaborating with to try new security measures is Gmail. As of Chromiu m 13, all connections to Gmail will be over HTTPS. This includes the initial nav igation even if the user types gmail.com or mail.google.com into the URL bar without an https:// prefix, which defends against <a href="http://www.thoughtcrime.o rg/software/sslstrip/">sslstrip-type</a> attacks. <br /&g t;The same HSTS technology also prevents users from clicking through SSL warning s for things such as a self-signed certificate. These attacks have been seen in the wild, and users have been known to fall for such attacks. Now theres a mechan ism to prevent them from doing so on sensitive domains. I n addition in Chromium 13, only a very small subset of CAs have the authority to vouch for Gmail (and the Google Accounts login page). This can protect against <a href="http://googleonlinesecurity.blogspot.com/2011/04/improving-ssl-certi ficate-security.html">recent incidents</a> where a CA has its authority abused, and generally protects against the proliferation of signing authority.& lt;br /> Chromium 13: defens es for self-XSS via javascript URLs Working together wit h Facebook and other browser vendors, were trialing a self-XSS defense that makes it harder for users to shoot themselves in the foot when they are tricked into pasting javascript: URLs into the omnibox. This is an int eresting area because its hard to know what detail of instruction it is possible to trick a user into following. It is also hard to measure success until a large percentage of installed browsers have the defense (thus forcing the attackers t o adapt their approach). Still hiring! We are always looking to expand the Google Chrome Security Team, and were looking for a wide range of talents for bot h Chrome and ChromeOS. We can promise exciting and varied work, working to prote ct hundreds of millions of users and working alongside the best in the industry. Why not have a look at our <a href="http://www.google.com/intl/mn/jobs/usloc ations/mountain-view/swe/information-security-engineer-chrome-mountain-view/inde x.html">job posting</a>? Posted by Chris Evans of the Google Chrome Security Team. With thanks t o Adam Barth, Adam Langley, Cris Neckar and Tom Sepez for implementing the above features.<div class="blogger-post-footer"><img width= 1 height= 1 src= https://blogger.googleusercontent.com/tracker/247137891419915096 6-6963395838232395757?l=blog.chromium.org alt= /></div></content><li nk rel= replies type= application/atom+xml href= http://blog.chromium.org/feed s/6963395838232395757/comments/default title= Post Comments /><link rel= replie s type= text/html href= http://www.blogger.com/comment.g?blogID=24713789141991 50966&postID=6963395838232395757 title= 8 Comments /><link rel= edit type= application/atom+xml href= http://www.blogger.com/feeds/2471378914199150966/po sts/default/6963395838232395757 /><link rel= self type= application/atom+xml h ref= http://www.blogger.com/feeds/2471378914199150966/posts/default/696339583823 2395757 /><link rel= alternate type= text/html href= http://blog.chromium.org/ 2011/06/new-chromium-security-features-june.html title= New Chromium security f eatures, June 2011 /><author><name>Christos</name><uri>http://www.blogger.com/pr
ofile/15311878333217771150</uri><email>noreply@blogger.com</email><gd:image xmln s:gd= http://schemas.google.com/g/2005 rel= http://schemas.google.com/g/2005#th umbnail width= 16 height= 16 src= http://img2.blogblog.com/img/b16-rounded.gi f /></author><media:thumbnail xmlns:media= http://search.yahoo.com/mrss/ url= h ttp://3.bp.blogspot.com/-s70rejSpThk/TffcXzAO17I/AAAAAAAAAFA/bX2hwmYzmNk/s72-c/h sts.png height= 72 width= 72 /><thr:total>8</thr:total></entry></feed>

Default

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Default

Transféré par

Droits d'auteur :

Formats disponibles

Vous aimerez peut-être aussi