-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A shindig based dashboard (alpha) is now available for the Mashup Server. Building the Mashup Server with the optional -Dbuild-dashboard parameter will integrate the dashboard to the final build. ie: mvn clean install -Dbuild-dashboard Once the server is started, pointing the browser to http://localhost:7762/dashboard will launch the UI with a pre-determined set of gadgets. The user login will be the same used for the Mashup Server UI. Logged in users get to add/remove gadgets from the default view. The new view will be stored in their profile. The 'Add Widgets' link will allow a user to either select gadgets ( of mashups) from the local server or import (mashup or iGoogle compatible) gadgets from remote locations, by giving their URLs. An article can be written if required. Although it will essentially say the above :) Tyrell Tyrell Perera wrote: | How about if we have an 'Add Stuff' page instead of the configuration | gadget? | | It can be the place where a user can either select from all the mashups | available in the local server or provide URLs to fetch gadgets from | remote locations. | | When a user selects/adds a gadget, the related meta-data necessary to | render that in the gadget container page will be stored under that | user's profile (ie: users/jonathan/gadgets/) as a resource. | | This will allow us to pre-populate the gadget container page and the | user to remove or add gadgets as and when required. | | | Tyrell | | Sanjiva Weerawarana wrote: | | +1 .. maybe we can have a special tag which is only applied by the | | system user as a way to bring in some default mashups to show on the | | shindig page. That way we can pre-populate that with some stuff we think | | is cool/useful but whatever the user does overrides that. Later we can | | do something like what igoogle does- have tabs or something and then | | pick a few auto based on the tab name. | | | | Sanjiva. | | | | Jonathan Marsh wrote: | |> To me this problem is similar to the problem of showing a user's | personal | |> queries on the home page. We store that information in the user | |> profile at | |> present, and we probably should keep shindig layout there as well. | |> Tagging | |> is appealing because it's "clever", but does have the problems you note | |> below. I'd rather have a gadget right on the shindig page which can | |> be used | |> to select which gadgets you show. That way the cause-effect | |> relationship is | |> simple and immediate. | |> | |> Jonathan Marsh - http://www.wso2.com - | |> http://auburnmarshes.spaces.live.com | |> | |>> -----Original Message----- | |>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] | |>> On Behalf Of Sanjiva Weerawarana | |>> Sent: Friday, May 30, 2008 8:28 AM | |>> To: [email protected] | |>> Subject: Re: [mashup-dev] Shindig Integration | |>> | |>> 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:mashup-dev- | |>> [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." | |>>>>>>> _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev - -- 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 iD8DBQFISTH9ehFdPcgGx7oRAnhnAKChEY252Fuo/dpihab/q8Og7kqRPwCg3VvY HuvXxzIoDQb6oI0R+Yga0YU= =X0mm -----END PGP SIGNATURE----- _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
