Hi Anand,
Yes we only need to submit one URL, even though we are talking about 2
views. These views are coded in the gadget code.

This is how things work
1. You can have multiple Content sections. Refer the link below
    http://code.google.com/p/opensocial-resources/wiki/MultipleContentSections


2. You have no such distinction in XML, but you distinguish between
views in the javascript code. We use APIs to figure out which view we
are in and
    choose to display appropriate things and provide appropriate
functionality. Please refer to the link below

    http://code.google.com/apis/opensocial/docs/0.7/devguide.html#Nav

Also, refer to the following link to know how to navigate between
views
http://code.google.com/p/opensocial-resources/wiki/NavigationBetweenViews

Hope this helps you,
Rohit

On May 7, 12:10 am, Anand <[EMAIL PROTECTED]> wrote:
> Thanks for the reply Rohit..Was very explanatory. My developer is
> still confused on one part : When teh application is submitted, we
> only provide one URL to be added. How do I write two codes here (one
> corresponding to the canvas view and another to the profile view).
> Sorry if the questions sound mundane, but since the whole concept is
> new, I am a bit confused.
>
> About the message board, I was referring to the comments that users
> enter about the application which is normally seen before the 'Add
> Application' button. I presume this is a default window provided by
> orkut and does not require coding from our end.
>
> Thanks again,
> Anand
>
> Rohit Ghatol (Google) wrote:
> > Hi Anand,
>
> > Typically another user can see an OpenSocial application that you have
> > installed in two ways
> > 1. On your Profile view, along side other OpenSocial Apps you have
> > installed. Here the application has limited real estate.
> > 2. On the Canvas view where the Application occupies complete space.
> > Here the application has much more real estate.
>
> > A user who visits your profile page would see number of applications
> > that you have installed. Each of this applications should show limited
> > but useful information to the user (owing to the limited real estate).
> > If this user finds some thing useful in an application he/she would
> > interact with the application. As a result of this interaction (say
> > clicking a button or a link), the application can move to the Canvas
> > View, to show user much richer content.
>
> > Hence, if you have a application which has very rich content,
> > typically you would like to code differently for two views. One
> > version of your code would show less richer and concise contents for
> > Profile page and another code would show much richer content for the
> > Canvas page. But, if there is no such need to distinguish between the
> > richness of your application, you can just have one code for both the
> > views.
>
> > About the "message board" related query, I am not very clear, Do you
> > mean activity stream (updates)? If you meant activity streams, this is
> > another way to make other users aware, what you did with a particular
> > application. It is a good way of communicating with other users who do
> > not visit directly visited your application.
>
> > I am using Orkut as a container to explain things here.
>
> > regards,
> > Rohit
>
> > On May 5, 11:57 pm, Anand <[EMAIL PROTECTED]> wrote:
> > > While coding for an app, should I only write code for the application
> > > page alone, or should I also write code for the message board that
> > > appears below the 'add app' page for the apps that currently exist?
> > > Should I also write the code for what appears on the user profile
> > > page?
>
> > > Sorry, I am a bit confused about this.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenSocial Application Development" 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-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to