W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2009

Re: [widgets] Widget modes

From: Jon Ferraiolo <jferrai@us.ibm.com>
Date: Thu, 29 Jan 2009 09:11:58 -0800
To: SUZANNE Benoit RD-SIRP-ISS <benoit.suzanne@orange-ftgroup.com>
Cc: public-webapps <public-webapps@w3.org>
Message-ID: <OFF7BBA006.82B90A06-ON8825754D.005D0AF7-8825754D.005E7B13@us.ibm.com>
Hi everyone,
It would be good if the Widgets spec was careful to study potential
conflicts with similar attributes in Google/OpenSocial Gadgets and OpenAjax
Metadata. Google Gadgets has:

OpenSocial/Google Gadgets:
  <content view="canvas|profile|home|preview">
* http://code.google.com/apis/gadgets/docs/ui.html#views


  <content view="default|edit|help|insert">

Over at OpenAjax Alliance, we are in the process of examining our spec for
web widgets  to align better with Google Gadgets. There is a good chance we
will change our 'view' attribute to re-use the same keywords as
OpenSocial/Google Gadgets when used for the same purpose. The W3C doesn't
have to do that since there are different namespaces for the different XML
vocabularies anyway, but at least it makes sense to spend a little time
studying what's happening at OpenSocial and OpenAjax to see if it makes
sense to attempt to share the same markup.


             SUZANNE Benoit                                                
             <benoit.suzanne@o                                          To 
             range-ftgroup.com         public-webapps                      
             >                         <public-webapps@w3.org>             
             Sent by:                                                   cc 
             quest@w3.org                                          Subject 
                                       [widgets] Widget modes              
             01/29/2009 08:34                                              

Hi all, about the widget windows modes, I wanted to share the following

*** Wording ***
In the wordings of the modes, I think that the wording used in some of the
modes are too specific to existing platforms, therefore I propose the
following names:
      Icon: I’m not sure this one is really a mode as it is already dealt
      with in the rest of the spec in the right manner with a static image
      Iconized: this mode will allow to define an icon that can be adapted
      to the content status, for example a weather icon will display the
      right cloud or sun based on the real time information. This is
      possible using the svg, but I believe this is one of the modes of
      displaying information in a widget.
      Expanded: this is the reference to the existing floating mode in the
      spec or the undocked mode for vista
      Minimized: this is the reference to the existing docked mode in the
      spec but is too restrictive in the wordings
      Full screen: now for this one my worry is more the fact that there
      are other attributes that should be available for this mode as the
      display can be specific to the orientation (landscape or portrait)
      and to the size of the screen’s device (vga, qvga, ...)
      Hidden: I like the proposition from mark to allow a widget to run as
      a background task that can awaken an action, so you would probably
      need to add this as a mode as well.
      Settings: I would also like to add the settings of the widget as a
      specific mode as this will largely simplify the coding of the widget
      where all the various screens to display will all be defined as

The way I see this implemented is that based on the platform actions (drag
on a widget bar for example) the platform would switch from one view to the
other. Or based on a code input in the hidden mode, a widget would be able
to call it’s Minimized mode through the code. In this context the one thing
that needs to be included is how to pass parameters from one mode to the
other, but that could be resolved using some kind of parametered

I do not see the mode as an element, but as an item of the content element,
see examples below.

***Code example***
In the format to use the modes I propose the following as a bases for
<content src="miniview.html" mode=”minimized”/>
<content src="index.html" mode=”expanded” default=”true” flying=”true”/>
<content src="fullscreen-vga.html" mode=”fullscreen” width=”640”
<content src="fullscreen-wvga.html" mode=”fullscreen” width=”854”
height=”480” orientation=”landscape”/>
<content src="fullscreen-wvga.html" mode=”fullscreen” width=”854”
height=”480” orientation=”portrait”/>
<content src="minimumbackgroundaction.js" mode=”idden”/>
<content src="settings.html" mode=”settings”/>

What do you think?

Best Regards, Benoit

      Benoit  Suzanne
      Widget Factory Project Manager - Orange Labs - FT/RD/SIRP/SOL/SLAM
      t. +33 (0)145 298  198 - m. +33 (0)680 287 553

(image/gif attachment: graycol.gif)

(image/gif attachment: pic00638.gif)

(image/gif attachment: ecblank.gif)

(image/gif attachment: 10957882.gif)

(image/gif attachment: 10652444.gif)

Received on Thursday, 29 January 2009 17:13:11 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:13 UTC