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

[widgets] Widget modes

From: SUZANNE Benoit RD-SIRP-ISS <benoit.suzanne@orange-ftgroup.com>
Date: Thu, 29 Jan 2009 17:34:34 +0100
To: public-webapps <public-webapps@w3.org>
Message-ID: <C5A7992A.1BEC3%benoit.suzanne@orange-ftgroup.com>
Hi all, about the widget windows modes, I wanted to share the following
points:

*** 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 format
* 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 modes.

***Context***
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
declaration.

***Usage***
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
discussions:
<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²
height=²480²/>
<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
> benoit.suzanne@orange-ftgroup.com
> 
 







image.gif
(image/gif attachment: image.gif)

image.gif
(image/gif attachment: 02-image.gif)

Received on Thursday, 29 January 2009 16:35:24 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:29 GMT