Hey Chris,
What you're calling "views" are going to be officially called
"surfaces" for OpenSocial. This is going to be an extensible system,
so different containers may have different numbers of surfaces, each
with different properties and use cases. We're adding API calls to
query for the current container's available surfaces, as well as some
metadata about each surface.
@wkdown - There's a couple different solutions for this, but the
easiest may be to use CSS to make the image a background of a page
element, like a header DIV. If the image is then too wide for the
current surface, the application iframe won't scroll (the image will
just be cut off).
Hope this helps,
~Arne
On Nov 14, 10:43 am, Chris Waterson <[EMAIL PROTECTED]> wrote:
> On Nov 14, 2007, at 9:28 AM, Simon Willison wrote:
>
> > I couldn't find anything in the OpenSocial documentation about the
> > dimensions of a gadget. Are these dimensions entirely up to the
> > container site? If they are, this could make designing gadgets that
> > could be run in several different containers quite challenging. Are
> > there any suggested techniques for dealing with this?
>
> Along those lines, are there particular *views* that a gadget is
> expected to provide? Looking at the Hi5 container, for example, I
> saw "preview", "profile", and "canvas". Are there others? Is this
> scheme extensible?
>
> thanks!
> chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenSocial API Definition" 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
-~----------~----~----~----~------~----~------~--~---
