Hi,
I'm afraid we're a bit short on documentation, other then the source code
> it's self :)
>
OK!
> Basically Shindig is an OpenSocial spec implementation that does everything
> for you, except the database integration and the container UI work. (With
> container we mean the website that will contain the opensocial apps).
OK.
> Shindig knows 3 basic classes you need to implement (see the sample &
> partuza implementations for examples):
> - People: the profile and relationship data
OK, that's easy
>
> - Activities: activity stream ("chris ate a peanut today")
OK, that's easy too.
> - AppData: persistent application data storage, used to store small and
> simple things like highscores of games, etc
Hummmm this is a little cloudy.
What am I expected to do about this one, at server level?
Each class has a few functions defined, and the return values are not
> documented, but the 2 examples (jsondb one and partuza's) are your guide
> here,
What is JasonDB?
> just return exactly the same as those examples do (and learn how to
> parse the params you get in those functions from the examples too), and it
> should be relatively easy to implement your own version, that reads it's
> data from drupal's db :)
OK. The first two you gave me were easy. The AppData one... I am still a
little confused about.
> Also you'll need to create an iframe when viewing a gadget on a page, and
> it
> requires a security token.. best reference on how to do this magic in php
> is
> partuza:
>
> http://code.google.com/p/partuza/source/browse/trunk/Application/Views/gadget/gadget.php
OK.
>
> <http://code.google.com/p/partuza/source/browse/trunk/Application/Views/gadget/gadget.php>also
> keep in mind that gadgets know 'views' (profile, canvas), so you
> probably will have to add a 'canvas page' to drupal (profile is the small
> box format, canvas is the full page view)
OK. Just to make sure: the only difference between the views "profile" and
"canvas" is in their sizes?
> and you will need to implement a few basic RPC services (gadget to
> container
> rpc through javascript that is), see partuza's container.js for example:
> http://code.google.com/p/partuza/source/browse/trunk/html/js/container.js
Sorry, I lost you here. Can you please explain this in very simple words?
In particular, can you give me an example of this?
<http://code.google.com/p/partuza/source/browse/trunk/html/js/container.js>Add
> a gallery (browse avail gadgets), and other basic UI elements
> (preferences, remove gadget, etc) and your done :)
>
That's the _easy_ part for me...
THANK YOU!
Merc.
