Friday, January 15, 2010

[Gd] App Engine at a Conference Near You this Winter!

| More

Google App Engine Blog: App Engine at a Conference Near You this Winter!

Happy New Year Everyone!


We're excited to be kicking off a new year, and you can expect to find many new exciting features coming to App Engine in the coming months. In addition to Google I/O 2010 coming up in May -- more on this below -- members of the App Engine team may be visiting a conference near you this quarter. Here is the full list:


2010 Jan 24-30 - Snow Sprint 2010 - B├╝rserberg - Nick Johnson
2010 Jan 26-27 - Jfokus - Stockholm - Patrick Chanezon
2010 Jan 28 - PROSA - Copenhagen - Patrick Chanezon
2010 Feb 17-21 - PyCon 2010 - Atlanta - Guido van Rossum, Wesley Chun, Joe Gregorio, Brett Slatkin, Andy Smith
2010 Feb 27 - Dare 2B Digital - Los Altos Hills - Wesley Chun
2010 Mar 10-12 - ConFoo.ca 2010 - Montreal - Patrick Chanezon
2010 Mar 12-16 - SXSW Interactive - Austin - Patrick Chanezon, Brett Slatkin, Sean Lynch
2010 Mar 15-18 - Cloud Connect - Santa Clara - Chris Schalk, Wesley Chun, Ikai Lan


Although not happening until next quarter, save a place in your calendar and book your travel for May 19-20 to San Francisco for Google I/O 2010. This year will be a blockbuster, featuring your favorite Google technologies and product announcements! There are at least 6 App Engine sessions planned. Register NOW!!


In addition to I/O, Google will be hosting a variety of DevFests in Asia late this winter. Keep an eye out for specific dates and locations on the Google Developer Events Calendar.


We would love to meet with App Engine developers at any of these events! Also be sure to follow @app_engine on Twitter for ongoing announcements as well as our Reddit tag for any relevant App Engine news.


Posted by Wesley Chun, App Engine team
URL: http://googleappengine.blogspot.com/2010/01/app-engine-at-conference-near-you-this.html

[Gd] My Extension Wish: A Joint Jukebox

| More

Google Wave Developer Blog: My Extension Wish: A Joint Jukebox

In the API corner of the Google Wave cubicles, we're often digressing into energetic discussions about an awesome extension that we want to see, and scheming about how we can encourage developers to implement these fantasy extensions. Since none of us are very good at inserting subliminal messages into forum posts, we figured we'd share our ideas on this blog instead, in a series of posts from various members of the Google Wave team.


To start off the series, I want to sell you on the idea of the "Joint Jukebox". First, some background. Sometimes I find myself in situations where friends put me in charge of playing music during a party, and I am constantly reminded by said people that I have one of the "worst" tastes in music ever. So, I have experimented with various ways of giving people a way to influence the stream of music. When I was a lab assistant in college, I wrote an app that used Google Spreadsheets to power a Youtube player, and invited everyone in the lab to edit the spreadsheet. They could add Youtube video IDs to the spreadsheet, and then change the number in the "rank" column to get the video to play sooner. I'd then project that player onto the screen. That worked alright, but the voting mechanism (the "rank" column) was too easy to hack, and it wasn't really that fun to use. I always envisioned writing a digg-like interface for it, and since I never got the chance, I'm putting you up to the challenge of doing it... but Wave-ified!



The Joint Jukebox would let users search for songs (using any one of the various music APIs on the web), and then submit play requests (or skip requests for the haters) on each submitted song. A highly intelligent algorithm would be constantly analyzing the current rankings and play history of all the songs, and use that information to select the next song to play. A group could use this as their DJ for a party or joint working space, just by hooking up a computer displaying the Wave to their audio system. Or, a couple in a long-distance relationship could use it across oceans, to feel like they're aurally connected. The Jukebox could also support playing music videos, or even playing karaoke versions of songs with lyrics displayed. No more listening to lame slow songs by the one depressed dude at Karaoke — you'll just vote him down!


The diagram below — made using a cool UI mockup app called Mockingbird (which would also make a great extension to Google Wave) — shows what the main screen and stats dialog could look like for the gadget. The jukebox shows the currently playing songs, the songs slated to play next, and then tabs to browse other songs users can rate. Users can suggest new songs, of course, when they want to listen to the latest from their favorite pop star or musical TV drama. :)




So, that's my wish — making music listening into a collaborative experience. If you want to help fulfill my wish — or if you're inspired to take it in a different direction — pop by the forum and share your ideas. Thanks, in advance!



Posted by Pamela Fox, Developer Relations
URL: http://googlewavedev.blogspot.com/2010/01/my-extension-wish-joint-jukebox.html

Thursday, January 14, 2010

[Gd] YouTube's APIs and Refresher on our Terms of Service

| More

YouTube API Blog: YouTube's APIs and Refresher on our Terms of Service

It's been a busy 2009 and we're excited to be back in 2010 to work on all the cool features we have planned for the YouTube APIs in the coming months.

Opening up our API has led to some really cool and fun commercial applications, far beyond what anyone here at YouTube could ever have imagined. Tens of thousands of developers have created great apps and websites that not only entertain and delight users in creative ways but give our content partners more choice and reach in distributing their videos. For example, we recently announced YouTube Direct, an open-source video uploading platform that is built entirely on top of the YouTube APIs and is available to any commercial website that wants to solicit video submissions from their users.

We thought it would be a good idea to start the year by revisiting a subject that many of you have had questions about since the APIs were born: the API Terms of Service.

Launched back in 2007, the YouTube APIs provide access to some of YouTube's core features (uploading, searching and playing videos, organizing playlists, etc.) for your websites and apps. Before using the API, we ask that you do one thing: carefully read through our Terms of Service (TOS). Here are a few things contained in our TOS that you should be aware of.
  • Videos belong to their owners - YouTube is a hosting platform. The videos themselves belong to the content owner (anyone from a major studio to a mother recording her son's graduation). In all cases, the content owner decides how and where their YouTube videos are distributed. Sometimes, video owners don't want others to profit from their work, or sometimes they may want to restrict where their videos are shown. While you may disagree with this decision, we need to respect the content owners' wishes.
  • Standard YouTube video player is key - Consistency in terms of quick video loads and playbacks is a hallmark of the YouTube experience. We therefore ask that you don't enable videos for download, modify a video in any way, or enable playback through means other than other official embeddable players.
  • Don't serve or strip ads from the video - Serving your own ads against a video without sharing revenue with the content creator, or YouTube, is against the TOS. So is using technology that strips out the ads we're serving on videos. Doing this deprives the uploader from legitimate earnings from his or her work. If you want to learn more about monetizing your YouTube apps, check out our API monetization guide.
  • It's ok to charge customers to access your application - Creating a subscription, or a one-time access/download fee to use your website or app is fine. But if you do, make it clear that it's you who's charging for access to the video, not YouTube. If you don't make this clear, you're very likely violating the TOS.
Occasionally, we update our TOS to make things even clearer, or to evolve as new features become available on the Web. But rest assured that the core guidelines in our TOS related to advertising, downloading videos, and using an official player have been there since the TOS's inception.

Our hope is that this post can serve as a reference point to clear up any confusions you might have surrounding our TOS. We're always looking to do more to make the API better for our developers and we are eager to hear your ideas and feedback. If you haven't already, do drop by our YouTube APIs Developer Forum and get in touch with us.

Posted by Kuan Yong, YouTube APIs and Tools Team
URL: http://apiblog.youtube.com/2010/01/youtubes-apis-and-refresher-on-our.html

[Gd] Google Chrome Frame has been updated to version 4.0.295.0. All

| More

Google Chrome Releases: Google Chrome Frame has been updated to version 4.0.295.0. All

Google Chrome Frame has been updated to version 4.0.295.0. All users should be updated automatically.

This release fixes several of the most common crashes and the following issues:

    • Network related fixes (Issue: 30149, 30203, 30355)
    • Enable UMA data upload in ChromeFrame (Issue: 30508)
    • Authorization headers set using XHR with ChromeFrame were stripped in the outgoing HTTP (Issue: 23103)
    • CF Full Mode display webpage when "Open link in new window" opened in ChromeFrame via the Open in New window operation (Issue: 30013)
    • Delete cookies with JavaScript and chromeframe (Issue: 30786, 30786)

    If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry.

    -- Orit Mazor, Google Chrome Team
    URL: http://googlechromereleases.blogspot.com/2010/01/google-chrome-frame-has-been-updated-to.html

    [Gd] [Libraries][Update] jQuery 1.4.0

    | More

    Google AJAX API Alerts: [Libraries][Update] jQuery 1.4.0

    jQuery was updated to 1.4.0
    URL: http://ajax-api-alerts.blogspot.com/2010/01/librariesupdate-jquery-140.html

    [Gd] [Libraries][Update] ext-core 3.1.0

    | More

    Google AJAX API Alerts: [Libraries][Update] ext-core 3.1.0

    ext-core was updated to version 3.1.0
    URL: http://ajax-api-alerts.blogspot.com/2010/01/librariesupdate-ext-core-310.html

    [Gd] Dev Channel Update

    | More

    Google Chrome Releases: Dev Channel Update

    The Dev channel has been updated to 4.0.295.0 for All platforms

    All Platforms
    • See full list

    Windows
    • See full list

    Mac
    • Several crash fixes.
    • [r35546 , r35826] Add a rudimentary bookmark manager (Issue: 13149, 31844)
    • [r35678] Fix stuck hover states on tab close buttons (Issue: 31279)
    • [r35576] Make devtools window dockable. (Issue: 17368)
    • [r35512] Implement the cookie manager (Issue: 15360)
    • [r35440] Cmd-three finger swipe opens prev/next page in new tab. (Issue: 29804)


    Linux
    • [r35441] We no longer show "exe" in process listings for helper processes. (Issue: 29118)
    • [r35536] Work around LAHF crash bug in Flash. (Issue: 29789)


    Known issues:
    - [OS-MAC] Bookmark manager for Mac is not finished yet. No need to file bugs at this point. (Implemented so far: moving, deleting and renaming bookmarks; drag/drop and copy/paste to and from Safari; creating folders.)
    - [OS-MAC] Close button on download shelf is semi-visible (Issue: 31785)
    - [OS-MAC] A few crashes within the Inspector (Issue: 32035, 32037, 32066, 32002)

    More details about additional changes are available in the svn log of all revisions.

    You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel.

    If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry.

    Orit Mazor, Google Chrome
    URL: http://googlechromereleases.blogspot.com/2010/01/dev-channel-update_14.html

    [Gd] Answering your December Grab Bag questions

    | More

    Official Google Webmaster Central Blog: Answering your December Grab Bag questions

    Webmaster Level: All

    You asked and Matt Cutts answered. It's time to answer the latest round of Grab Bag questions! Here's the first answer, complete with Matt's new hairstyle:


    We have a lot of videos ready to share, so we're not currently taking new questions for the Grab Bag. If you have a question that you would like answered, your best bet as always is to head to our Webmaster Help Forum, where you'll find plenty of knowledgeable webmasters, including some Bionic Posters!

    To be kept up-to-date on our latest video releases, you can follow @googlewmc on Twitter, where we'll announce new videos and blog posts as they're published.

    Posted by Michael Wyszomierski, Search Quality Team
    URL: http://googlewebmastercentral.blogspot.com/2010/01/answering-your-december-grab-bag.html

    Wednesday, January 13, 2010

    [Gd] Google Chrome Extension Internationalization

    | More

    Chromium Blog: Google Chrome Extension Internationalization

    Starting with Google Chrome developer channel release 4.0.288.1 and beta channel release 4.0.249.64 for Windows, an internationalization (i18n) framework for Google Chrome Extensions is available and enabled by default. This framework lets extension developers translate user-visible parts of the extension manifest — such as the name and description, and localize messages using simple JavaScript calls to the chrome.i18n.getMessage() method. We've implemented this feature as described in the design docs for Chromium.

    The following screenshots show a browser action's tooltip that has been translated into English, Spanish, Serbian, and Korean.



    To localize the extension manifest, extract all user-visible strings into message catalogs, and define the default locale.

    {
    "name": "__MSG_name__",
    "description": "__MSG_description__",
    ...
    "default_locale": "en",
    ...
    }

    To get translated messages in JavaScript code, including extension code and content scripts, invoke one of the following forms of chrome.i18n.getMessage().

    chrome.i18n.getMessage("messagename")
    chrome.i18n.getMessage("messagename", "one parameter")
    chrome.i18n.getMessage("messagename", ["one", "to", "nine", "parameters"])

    For more details, see the documentation.

    We're more than happy to hear your feedback, not only on our implementation and documentation, but also on the API design. You can reach us at the chromium-extensions group.

    Posted by Nebojsa Ciric, Software Engineer
    URL: http://blog.chromium.org/2010/01/google-chrome-extension.html

    [Gd] 100 days until major v13 sunset

    | More

    AdWords API Blog: 100 days until major v13 sunset

    In October of last year we launched the v200909 API and shared with you that the majority of v13 services would be turned off on April 22 of this year. This is a reminder to our developers that less than 100 days are left before most v13 services will be turned off.

    As of April 22, 2010, the following v13 services will no longer be accessible:
    CampaignService
    AdGroupService
    CriterionService
    AdService
    InfoService
    KeywordToolService
    SiteSuggestionService

    The AccountService, TrafficEstimatorService, and ReportService v13 services will continue to be accessible because they are not yet available in the v2009 API. In the coming months, we'll announce the launch dates for these services in the v2009 API and corresponding sunset dates for the v13 services.

    Want to learn more about migrating your application to the v2009 API? Review the side-by-side differences between v13 and v2009. Try out the code examples in these client libraries: Java, .NET, Python, Ruby, and PHP. You can also learn more from our Discover v2009 series of blog posts.

    As we go into the last 100 days before migration to v2009, please continue to ask us your questions and share your feedback on the AdWords API Developer Forum.

    –- Jason Shafton, Product Marketing Manager

    URL: http://adwordsapi.blogspot.com/2010/01/100-days-until-major-v13-sunset.html

    [Gd] GWT Developers: Hope to see you at Google I/O

    | More

    Google Web Toolkit Blog: GWT Developers: Hope to see you at Google I/O

    As you may have heard from our announcement this morning, registration for Google I/O is now open. In addition to publishing access to registration, we've also included event details on the I/O website.


    We already have quite a few Google Web Toolkit I/O sessions and Developer Sandbox demos lined up, and we expect this number to grow over the coming months. Here's a partial list of the GWT sessions that are already listed on the I/O website:








    Over the next couple of months, we'll be adding new GWT sessions and more GWT Developer Sandbox participants to the I/O website. For updates on when new content is added, follow @googleio on Twitter.




    Registration for Google I/O (at the early bird rate of $400) is open as of today. We hope you'll be as excited about this year's I/O as we are, and we look forward to seeing everyone in May.

    URL: http://googlewebtoolkit.blogspot.com/2010/01/gwt-developers-hope-to-see-you-at.html

    Tuesday, January 12, 2010

    [Gd] Documents List API: Upload any file type and more!

    | More

    Google Code Blog: ​Documents List API: Upload any file type and more!

    As just announced over on the Enterprise blog, Google Docs now allows users to upload any type of file! Over the next couple of weeks we’ll be rolling out the same feature in the Documents List Data API. For now, uploading arbitrary files via the API will be restricted to Google Apps Premier domains. For starters, each user gets 1GB of storage with a maximum size of 250 MB per file.

    Combined with the shared folders feature of Google Docs, we think this new feature is a great way to build collaborative applications for exchanging files with coworkers and external parties. No more email attachments!

    In addition to arbitrary file upload, we’re launching several top features requested by developers:
    Look for resumable upload support in the Java, Python, and Objective-C client libraries in the near future. As always, if you have any questions, please visit us in our new developer forum.

    Issues resolved in this release: 72, 1040, 1675, 1260, 1741, 1127

    By ​Eric Bidelman, Google Docs Team
    URL: http://googlecode.blogspot.com/2010/01/documents-list-api-upload-any-file-type.html

    [Gd] Google I/O 2010: Now open for registration

    | More

    Google Code Blog: Google I/O 2010: Now open for registration

    I'm excited to announce that registration for Google I/O is now open at code.google.com/io. Our third annual developer conference will return to Moscone West in San Francisco on May 19-20, 2010. We expect thousands of web, mobile, and enterprise developers to be in attendance.

    I/O 2010 will be focused on building the next generation of applications in the cloud and will feature the latest on Google products and technologies like Android, Google Chrome, App Engine, Google Web Toolkit, Google APIs, and more. Members of our engineering teams and other web development experts will lead more than 80 technical sessions. We'll also bring back the Developer Sandbox, which we introduced at I/O 2009, where developers from more than 100 companies will be on hand to demo their apps, answer questions and exchange ideas.

    We'll be regularly adding more sessions, speakers and companies on the event website, and today we're happy to give you a preview of what's to come. Over half of all sessions are already listed, covering a range of products and technologies, as well as speaker bios. We've also included a short list of companies that will be participating in the Developer Sandbox. For the latest I/O updates, follow us (@googleio) on Twitter.

    Today's registration opens with an early bird rate of $400, which applies through April 16 ($500 after April 16). Faculty and students can register at the discounted Academia rate of $100 (this discounted rate is limited and available on a first come, first serve basis).

    Last year's I/O sold out before the start of the conference, so we encourage you to sign up in advance.

    Google I/O
    May 19-20, 2010
    Moscone West, San Francisco

    To learn more and sign up, visit code.google.com/io.

    We hope to see you in May!

    By David Glazer, Engineering Director
    URL: http://googlecode.blogspot.com/2010/01/google-io-2010-now-open-for.html

    Monday, January 11, 2010

    [Gd] Beta Channel Update

    | More

    Google Chrome Releases: Beta Channel Update

    The Beta channel has been updated to 4.0.249.64 for Windows.

    This release adds additional functionality to extensions:

    • The addition of internationalization support for extensions http://code.google.com/chrome/extensions/trunk/i18n.html.
    • [r34858] Adds a right-click context menu for Browser Actions and Page Actions. (Issue: 29538)
    • [r35233] Disables content scripts in Incognito mode. (Issue: 21392)
    • [r35663] Prevents extension popups from being dismissed when the focus changes from a child window of the popup, as it is the case with select popups. (Issue: 28110)
    • [r35681] Enforces minimum version from the extension manifest. (Issue: 24737)

    More details about additional changes are available in the svn log of all revisions.

    Anthony Laforge
    Google Chrome Program Manager
    URL: http://googlechromereleases.blogspot.com/2010/01/beta-channel-update_11.html

    [Gd] Android 2.1 SDK

    | More

    Android Developers Blog: Android 2.1 SDK

    Today, we are releasing the SDK component for Android 2.1, so that developers can take advantage of the new features introduced in Android 2.1. Please read the Android 2.1 release notes for more details. You can download the Android 2.1 component through the SDK Manager.

    In addition to the new SDK, a new USB driver that supports Nexus One is also available today through the SDK Manager. The USB driver page contains more information.

    URL: http://android-developers.blogspot.com/2010/01/android-21-sdk.html