I was thinking of an even more simple approach: tag any local mashup with
"show-me-on-my-shindig-page" and then that mashup will show up as a gadget
in the shindig page.
I guess the challenge is to tell the diff between Paul tagging it with
that tag and my tagging it .. just because Paul tags a mashup m1 with that
ugly tag I don't want it to show on my page.
We can tell who has applied a tag right? So is it abuse of the tagging
model to see who applied the tag and only show the gadget if the person
has tagged it themselves? Also, if the tag has been applied by the
"system" user then it can show up in everyone's shindig page.
Will that work?
Sanjiva.
Paul Fremantle wrote:
I *love* the idea of using tags to associate gadgets.... very cool. How
about a scheme like "gadget-xxxx" where xxxx is the gadget name.
Paul
Sanjiva Weerawarana wrote:
+1 .. how about using a simple tag to select the gadgets to show by
default? Then users can tag their stuff too and it'll show up.
We should also include some gadgets from iGoogle and include 'em too
(I'm assuming that's possible?).
Sanjiva.
Jonathan Marsh wrote:
+1 to all except putting all gadgets in the container at startup - this
could be pretty overwhelming to start off and I'd like to have it
more of a
self-demo than a random jumble. We could tag a few of the sample
services
for inclusion at startup so it's a nice clean and somewhat useful
default
display (e.g. the upgradeChecker). Perhaps we can also write a
gadget that
can be used to easily add new mashup gadgets without leaving the page...
Jonathan Marsh - http://www.wso2.com -
http://auburnmarshes.spaces.live.com
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Keith Chapman
Sent: Tuesday, May 27, 2008 7:21 AM
To: [EMAIL PROTECTED]; [email protected]
Subject: Re: [mashup-dev] Shindig Integration
>~ 1. Create the gadget container page for Shindig and store the
artifacts
in the Mashup SVN
+1
~ 2. Add a new build target to the existing build, which will
integrate
the gadget container page and shindig infrastructure to the Mashup
Server.
+1
~ 3. Post an article in OT highlighting the steps involved in
converting
a Mashup Server instance to a Google Gadget Container.
+1
The initial container page will probably retrieve all Mashups from
the
registry and display them as gadgets (/services/mashup-name?gadget).
Also may be we can allow the user to add a new mashup server url (So
that the client can talk to that server and get all the gadgets from
there)
Thanks,
Keith.
A
user can then customize this query, just as one does in the main home
page. This will allow a user to search and store a customized query,
which will display a subset of mashups in the container page.
Thoughts?
Tyrell
- --
Tyrell Perera
Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
email: [EMAIL PROTECTED]; cell: +94 77 302 2505
"Oxygenating the Web Service Platform."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIO30YehFdPcgGx7oRAmWQAKDrlkzYPIsIXIT95qlyKk61/3HuxwCgh3YC
LuyNLacRrWvMS6DtG4KxXa8=
=IloW
-----END PGP SIGNATURE-----
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
email: [EMAIL PROTECTED]; cell: +1 650 265 8311 | +94 77 787 6880
"Oxygenating the Web Service Platform."
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
