Closed (fixed)
Project:
MySite
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Mar 2007 at 10:03 UTC
Updated:
16 Apr 2007 at 18:05 UTC
I was follwing the discussion at and seeing your comment
1) MySite does not duplicate PageCreator. It duplicates http://www.google.com/ig?hl=en.
was interested in trying it out. So, I tried adding the 'Current moon Phase' widget
http://www.google.com/ig/directory?hl=en&root=/ig&dpos=top&num=24&url=http://www.calculatorcat.com/gmodules/current_moon.xml&q=&start=0
I figured I needed to drop the parameters so tried adding
http://www.calculatorcat.com/gmodules/current_moon.xml
to MySite web feed - but it doesn't seem to work.
I just get a blank page and the looking in the aggregator feed listing it doesn't seem to update?
Comments
Comment #1
csc4 commentedSorry - the discussion at bit should say http://drupal.org/node/117764#comment-208830
Comment #2
agentrickardAh. By 'duplicates' I mean "It duplicates the ability to create and store such widgets within the Drupal framework."
It does not respect the use of Google widgets on Drupal-powered pages, as I suspect there are both technical and legal reasons not to do so.
Looking at that XML file, it might be possible to replicate the widget -- you'd likely need to include the
<script>that would generate the content. See http://www.google.com/apis/gadgets/publish.html#SyndicationThere are security concerns about applying 3rd-party JavaScript to any site, so we'd have to look carefully at adding actual Google widgets.
Can you take a look at the license and terms of use for Google widgets and report back?
Comment #3
agentrickardSee http://www.google.com/webmasters/gadgets/terms.html
Comment #4
agentrickardMore accurate title. Moving to v5, since v4.7 is closed to feature development.
Comment #5
agentrickardApparently, we'd select content from: http://www.google.com/ig/directory?synd=open&source=gghp.
Writing an include that would allow site admins to select which gadgets to offer on their sites would work. There are two things that need to be done first:
1) Extend the data API to include a 'content' element of the array. In the case where 'content' exists, it would be printed in addition to 'title' or instead of 'teaser'. This would allow widgets to guarentee that they get seen in all layouts and formats.
2) Create a menu callback that allows the Add/Remove content page to be separated into distinct pages per content type. This would allow us to display a gadget grid and make finding gadgets easier.
MySite probably should support this. It would be left to administrators to select and test the gadgets they want available to users.
Comment #6
agentrickardThe Google Terms of Service may prohibit using these gadgets. http://www.google.com/terms_of_service.html
However, that may be up to the site developer; not to me.
Comment #7
agentrickardSee also: http://www.google.com/personalized_homepage_dmca.html
These types of restrictions, plus the fact that Google reserves the right to ad content to the gadgets sugget to me that we may be better off replicating the framework but not the gadgets themselves.
Comment #8
csc4 commentedWow - thanks for all of that!!
Replicating the framework sounds great - it looks like we need the iframing from
as the rest is just the XML feed?
As to licencing - there's stuff specfiically about adding to your page and providing you keep the branding (and don't hold Google responsible for anything!) they seem very happy - there's a whole suite of stuff specficailly about adding to your webpage - http://www.google.com/ig/directory?num=24&synd=open and onwards.
T&Cs at Syndicated Google Gadgets Terms of Service for Webmasters
I can get them to work in blocks but it would be so great if I could offer them as Mysite components...
Comment #9
agentrickardOK, here's where I think we stand.
1) Google Gadgets will be 'supported' just like any arbitrary code that an admin might want to add to MySite.
2) Special code for handling Google Gadgets will _not_ be provided by MySite. This means that no automated search/retrieval of Google Gadgets will fo into the source code. Admins will have to search/copy/paste on their own. This is due to the non-commercial license elements of Google's T & C.
There are two ways that we might solve that issue.
1) Create Block support in MySite. I've historically been against this, but am warming to it.
2) Follow the http://drupal.org/node/127661#comment-213262 plan.
For the time being, you might try to write a block.inc file. It would need to leverage the {mysite_content} table. The refine.inc plugin available in the 4.7 tarball gives some examples. You need to use {mysite_content} because Block identifiers are not integers. They are {module_name}-{delta} strings.
Comment #10
agentrickardSee http://drupal.org/node/128185 for block progress
Comment #11
agentrickardCommitted to HEAD.