It would allow Aardvark users who are in a hub together to see and interact with each other's gadgets. Aardvark already supports this. What is missing is the code that figures out who a user is in a hub with and shares that with Aardvark.
Who would use this gadget?
Anybody using both hubs and Aardvark. It would also make it more likely that users of one would start using the other.
Assuming that you're on the team, what other skillsets would you need to make this project happen over a couple days of hacking?
I may not have time during the hackathon to work on this because I'll be helping all the teams.
Mainly this project needs programmers. Javascript savvy folks to figure out how to tease this information out of Hubs. Server-side folks to bring up a quick and dirty service that shares the gadget information.
What will be the toughest part of building this gadget?
Getting Hubs to share this information. That could be accomplished with actual hubs client code changes (since it's open-source), or by wrapping hubs in an IFrame and reaching directly into the Javascript state of the hubs IFrame to pull out what we need.
What would this gadget do?
It would allow Aardvark users who are in a hub together to see and interact with each other's gadgets. Aardvark already supports this. What is missing is the code that figures out who a user is in a hub with and shares that with Aardvark.
Who would use this gadget?
Anybody using both hubs and Aardvark. It would also make it more likely that users of one would start using the other.
Assuming that you're on the team, what other skillsets would you need to make this project happen over a couple days of hacking?
I may not have time during the hackathon to work on this because I'll be helping all the teams.
Mainly this project needs programmers. Javascript savvy folks to figure out how to tease this information out of Hubs. Server-side folks to bring up a quick and dirty service that shares the gadget information.
What will be the toughest part of building this gadget?
Getting Hubs to share this information. That could be accomplished with actual hubs client code changes (since it's open-source), or by wrapping hubs in an IFrame and reaching directly into the Javascript state of the hubs IFrame to pull out what we need.