thanks for the info! And the advice on query direction ;) duly noted.

On Jun 29, 12:08 pm, Chris Chabot <[email protected]> wrote:
> Hey Terry,
>
> On Mon, Jun 29, 2009 at 12:54 PM, terry <[email protected]> wrote:
>
> > Thanks chris thats a fair few things for me to start with. I've read
> > aboutthere being some stubs of code that I need to fill in inorder for
> > people to access information stored on my database,
>
> Ah when you wrote 'I have shindig installed' I assumed you had already done
> that., my bad :)
>
> > do you have any
> > information on where these stubs are? and the types of functionality i
> > should be providing in them for developers.
>
> The how and what depends a bit on if you're using the java or php variant of
> shindig (btw, you should be posting on the
> [email protected] list, that's where all the
> people who can give shindig support hang
> out, seehttp://incubator.apache.org/shindigfor details on how to
> subscribe).
>
> If you're using PHP Shindig (or even if you're using java it's still a nice
> example) the easiest way to see what's involved & what needs to be
> implemented is by checking out Partuza,http://code.google.com/p/partuzaand
> a live version atwww.partuza.nl
>
> Basically you need to implement the People, Activities and AppData
> interfaces (for php shindig see
> shindig/php/src/social/spi/{People,Activity,AppData}Service.php and
> partuza/Shindig/PartuzaService.php & PartuzaDbFetcher.php for a 'real'
> example on how to implement those). There are also interfaces for OAuth,
> Albums, Invalidation and Messages, but for a first deployment you should
> consider those to be optional.. the people, activities and appdata are the
> core services that gadgets use.
>
> After that you also need to implement an user preferences UI, support
> different views (profile and canvas are the two must-haves, and home and
> preview are 'optional', ie only if that makes sense on your site). Then you
> need to generate iframe's that contain the nav-params, user prefs, an
> encrypted security token, lang, country, etc..
>
> That iframe business is a bit tricky, but again Partuza has a nice example
> of how to do that which you can trace starting from
> partuza/Application/Views/gadget/gadget.php
>
> Hopefully that'll help you get started, and if (read: when :) you run into
> any issues, please feel free to ping us (but preferably on the shindig-dev
> list)
>
>    -- Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Implementing OpenSocial Containers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/opensocial-container?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to