Live.com to Support Google Universal Gadgets

By Donavon | Posted November 13, 2006 4 comments

Is the Live.com team working on support for Google’s universal gadget manifest format? You can’t load a Google gadget manifest yet, but there are signs that it’s not far off. If I’m right (and I’m sensing that I am) you should be able to use any of the plethora of gadgets available at http://www.google.com/ig/directory?synd=open on your Live.com or Windows Live Spaces page not too far down the road.

Actually, we’ve known for a while that running Google gadgets on Live.com was possible. I wrote a proof of concept about a year ago in which I was able to load and execute the Google “Eyes” gadget (back then Google called them “modules”). I never released an actual product of this, as it was just an exercise for myself. Since then, I have wondered whether the guys at Microsoft were working on a way to do this too, and it looks like they are.

But what’s behind the decision to add this functionality to Live.com and why now? I believe it is because Microsoft has fallen behind Google in the number of gadgets available for their respective formats (less than 300 compared to Google’s nearly 2000 gadgets). Its a battle for users that reminds me of the VHS/Betamax war in the early ’80s. As we all know, Sony’s Betamax lost out to JVC’s VHS format even though Betamax was technically superior. VHS won out with consumers because there were simply more VHS videos on the shelf.

Microsoft doesn’t want to be the Betamax of the gadget world. Like Sony, Microsoft’s format is technically superior to the competition. When writing a Microsoft gadgets, the developer must abide by the Atlas framework; meaning JavaScript classes, initialize and dispose methods, bindings, inheritance and interfaces. Google went with a flexible format more like a traditional web page and therefore more familiar to web developers. For the most part, if you can write a web page, you can make a Google gadget; not so with Microsoft’s. There is only a small school of Atlas savvy fish swimming in an overwhelming sea of web developers. Therefore it’s simple: fewer Atlas developers means fewer Microsoft gadgets.

Microsoft prides itself on bringing new, better and more sophisticated platforms and tools to the development community. I defend and applaud the Live.com platform but some developers have been vocal about this “sophistication” on MicrosoftGadgets.com (a developer community site). In response to a posting titled “Building a simple gadget for Live.com“, one developer commented “I’ve just finished writing a Google Personal Homepage module. Then I thought: “what the heck, let’s write one for live.com also”. Adding a gadget to live.com is much more complex then it should be…“. To which another developer responded “I agree… creating a Gadget is very complex and relies on age old web dev skills like JScript (gosh!) – there should be an easier + better way to develop gadgets if live.com is to succeed“.

Does this mean the death of the Live.com format gadget? Not at all. Speaking as a developer, it’s not going away, it is just being used by a smaller proportion of the community. I’ve written more Microsoft gadgets than I can count, compared to only a handful of the Google variety.

When will this supposed new functionality be rolled out? Only the Live.com team can say for sure. I would expect that we should see Google gadgets running natively on Live.com within the next one or two Live.com releases cycles.

*** Update ***

While I can’t get the Live.com user interface to accept a manifest to a Google gadget, I can force the Microsoft gadget engine to run a Google gadget directly. For example, click the link below to run Google’s clock. Note that all of the work to read the manifest and render this Google gadget is being done by Microsoft code.

http://gadgets.start.com/gadget.aspx?manifestUrl=http://www.google.com/ig/modules/datetime.xml

You can substitute a different manifest URL to run any Google gadget as long as the gadget’s manifest is not set to render_inline=”required in the <ModulePrefs> tag (as is the case with the Google Eyes gadget).

Posted November 13th, 2006 at 1:20 pm
Category: Developer
Tags: Gadgets
  • http://khristopherr.spaces.live.com Khristopher

    ya i love gadgets but i’m so unimpressed with what MS is offering right now. not to mention i have the rss feed for gadgets in my reader and it’s constantly bombarded with utter CRAP. some italian crap constantly! real annoying.

    but if this happens it could be very cool!

  • bf1977

    Very good It takes that when the Sight to arrive can also use gadget of other sites. This demonstrates that the Microsoft so is not interested in closing the doors for compatibility with other companies of software and services.

  • toddos

    Phunky, the Gallery team is aware of the gadget spam problem (I’d hope so, as I’ve brought it to their attention enough times) and is actively working on a solution that’s fair to all gadget authors.

    I’m of mixed opinion about this. On the one hand, getting 2000 gadgets for “free” is a huge win, but I can’t help wonder, “Is it worth it?” Those “free” gadgets have look & feel that was designed explicitly for the Google page and may look completely out of place on live.com or Spaces. As well, by using Google’s gadget manifest, Microsoft is completely at the mercy of Google. If they change, Microsoft will have to scramble to change with them or risk broken gadgets. Being reactionary is never a good position.

    So long as the Atlas framework-based gadget interface is around, that’s what I’ll be using. Aside from being more powerful, it’s just plain more interesting. Since I write gadgets to entertain myself, I’ll use whatever framework is the most fun to work with.

  • http://www.chrisabraham.com chrisabraham

    I was so excited when I read that google gadgets render in MSN properties; unfortunately, I jumped the gun here. When do you think that this might become implemented. Strangely enough, making a very simple, integrated, inline HTML gadget from what I learned in the Web Gadget SDK isn’t so easy.