April 27th, 2010 | by Mike Marchak | published in Google Code, iGoogle
Not everyone likes to start their day with just a search box and logo (no matter how cool it is!). Many users want email, videos, news, weather, games, and other information to be at their fingertips each time they open up a browser window. We launched…
Sometimes blue text just isn’t enough
April 22nd, 2010 | by Rob Russell (Google) | published in iGoogle
Nearly every iGoogle user has an RSS feed or two on their homepage – from top news to celebrity gossip, recipes, and much much more. In true Google fashion, we originally launched RSS support with a simple headline-only presentation. However, we all know the power of pictures, and so, we’re happy to announce the addition of image support to our standard RSS gadget.
With this new feature, users have three different display views.
Headline only
SlideshowHeadline and lead story
When users go to iGoogle today, they’ll notice that not all feeds have the same view. We default each feed to what we believe is the optimal display based on the images currently available in the feed. Of course, users can change the display setting by choosing “edit settings” in the drop down menu for each feed.
These new views not only create a better experience for users, but also give publishers an opportunity to more easily expose rich content, often already present in their RSS feeds. To take advantage of this new feature, publishers simply need to add images and associated Media RSS and/or enclosure elements to their existing RSS feeds. We’ll then grab the images, resize them down as necessary, and provide hosting/caching. Additionally, we’ll make the images clickable and display a 150 character snippet in the “Headline and lead story” view.
Here are a sampling of feeds to try out:
- CNN
- NYTimes
- BBC
- The Economist
- Time.com
- People Magazine
- Entertainment Weekly
- Wikihow
-
National Geographic (try it in slideshow mode)
-
Simply Recipes (try it in slideshow mode)
This feature is launching in the US over the next day with full international support coming soon. Please see our feed publisher instructions for more information.
Posted by James Lee, iGoogle Engineer
Sometimes blue text just isn’t enough
April 22nd, 2010 | by Rob Russell (Google) | published in iGoogle
Nearly every iGoogle user has an RSS feed or two on their homepage – from top news to celebrity gossip, recipes, and much much more. In true Google fashion, we originally launched RSS support with a simple headline-only presentation. However, we all kn…
April 20th, 2010 | by Rob Russell (Google) | published in iGoogle
There’s been a change in the way we send parameters to gadgets which use Content type=”url”. In short, we started sending the user prefs parameters after a # – the URL fragment identifier. As it turns out, this change caused problems for developers who…
April 20th, 2010 | by Rob Russell (Google) | published in iGoogle
There’s been a change in the way we send parameters to gadgets which use Content type=”url”. In short, we started sending the user prefs parameters after a # – the URL fragment identifier. As it turns out, this change caused problems for developers who…
Migration made easier
March 25th, 2010 | by Dan Holevoet | published in iGoogle
Last year we released a legacy migration guide for converting legacy gadgets to gadgets.* by hand. At the time, we promised a migration tool to help perform these migrations automatically.Today, I’m happy to announce the legacy gadget migration tool,…
March 25th, 2010 | by Dan Holevoet | published in iGoogle
Last year we released a legacy migration guide for converting legacy gadgets to gadgets.* by hand. At the time, we promised a migration tool to help perform these migrations automatically.
Today, I’m happy to announce the legacy gadget migration tool, which will convert existing XML and JavaScript code to use the gadgets.* API. The tool will accept raw XML and JavaScript to convert, or a publicly visible URL, read the code, and replace references to the legacy API with their gadgets.* equivalents. In the rare case where a migration cannot be automatically performed, it will output per-line warnings indicating what changes developers must make by hand, along with a relevant link to the migration guide.
Of course, please test migrated code before deploying to all of your users.
If you have any questions, please inquire in the iGoogle Developer Forum.
Posted by Dan Holevoet, Developer Programs
The forums, they are a-changin’
March 4th, 2010 | by Rob Russell (Google) | published in iGoogle
iGoogle developers, your lives are about to get a bit easier. For the last few years, the iGoogle Developer Forum has been the place for gadget developers to discuss development of gadgets for iGoogle. Despite the name, the forum only provided help and…
The forums, they are a-changin’
March 4th, 2010 | by Rob Russell (Google) | published in iGoogle
iGoogle developers, your lives are about to get a bit easier. For the last few years, the iGoogle Developer Forum has been the place for gadget developers to discuss development of gadgets for iGoogle. Despite the name, the forum only provided help and…
February 16th, 2010 | by Dan Holevoet | published in iGoogle
Last November we launched the iGoogle Gadget Dashboard, a tool to give our gadget developers more insight into how their gadget is used in the wild. For starters, we gave developers the ability to track their user count, pageviews, canvas views all ove…
February 16th, 2010 | by Dan Holevoet | published in iGoogle
Last November we launched the iGoogle Gadget Dashboard, a tool to give our gadget developers more insight into how their gadget is used in the wild. For starters, we gave developers the ability to track their user count, pageviews, canvas views all ove…
Last phase of inlined gadget deprecation
January 22nd, 2010 | by Dan Holevoet | published in iGoogle
The deprecation of inlined gadgets which began in November 2007 is ready to enter its final phase. Over the next 30 days, we will be disabling the remaining inlined gadgets on iGoogle, starting immediately with those that are broken or have zero use…
Last phase of inlined gadget deprecation
January 22nd, 2010 | by Dan Holevoet | published in iGoogle
The deprecation of inlined gadgets which began in November 2007 is ready to enter its final phase. Over the next 30 days, we will be disabling the remaining inlined gadgets on iGoogle, starting immediately with those that are broken or have zero users. If you’d like operation of your gadget to continue, please follow the instructions in the gadgets.* migration guide.
If you have any questions on the deprecation, please visit the iGoogle Developer Forum.
Posted by Dan Holevoet, Developer Programs
December 17th, 2009 | by Dan Holevoet | published in iGoogle
Three months ago we announced the deprecation of the legacy gadgets API. Since then we’ve released a legacy migration guide for converting legacy gadgets to “gadgets.*” by hand, and we’re continuing to work on a migration tool to help perform this conv…
December 17th, 2009 | by Dan Holevoet | published in iGoogle
Three months ago we announced the deprecation of the legacy gadgets API. Since then we’ve released a legacy migration guide for converting legacy gadgets to “gadgets.*” by hand, and we’re continuing to work on a migration tool to help perform this conv…