Yep works for me, keep in mind that this is a container feature, and  
not a 'shindig' feature.

What you need to do is create some javascript for your container site,  
that registers 'i can handle the requestNagivateTo rpc, with this  
function', see http://partuza.us.chabotc.com/js/container.js for  
example.

Also when your setting up your server, and you support more then the  
'profile' and 'canvas' view, don't forget to edit your shindig/config/ 
container.js, and add your other view(s) to the "views" section (for  
instance partuza supports the home view so i added:
     "home" : {
       "isOnlyVisible" : false,
       "aliases": []
     },

to views.

ps i did double check by whiping up a quick navigate gadget: 
http://chabotc.com/navigate.xml 
  when i add that to my site, and click the navigate links, it's  
working fine and dandy for me

        -- Chris

On Jun 27, 2008, at 10:21 AM, tuhin.barua wrote:

>
> hey chris
>
> is this working currently in php server?
>
> this is my app javascript which works in orkut
>
> function nav(view,data){
>       var supported_views = gadgets.views.getSupportedViews();
>       d={
>               q: data
>       }
>       gadgets.views.requestNavigateTo(supported_views[view],d);
> }
>
> here view = 'canvas' and data is appdata
> ir orkut i call this function from profile view... and then it gets
> redirected to application canvas view with app params.... which works
> fine
> but in my php server its not working.... i can see rpc_relay.html
> getting called asynchronously in the firebug when i call this function
> same like orkut....
>
> - Tuhin
>
> 

--~--~---------~--~----~------------~-------~--~----~
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