W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

RE: [widgets] window modes in P&C, was Re: Small question about latestversion of "P&C specs" (11th Mar 2009)

From: <ivan.demarino@orange-ftgroup.com>
Date: Mon, 11 May 2009 13:14:40 +0200
Message-ID: <B877D90AB2240C4D84DF56169F1EAFED06327981@ftrdmel3>
To: <marcosc@opera.com>, <arveb@opera.com>
Cc: <public-webapps@w3.org>
Hello.

Better late then never: I sent this email 2 months ago :D
But I see the flux of emails everyday on this mailing list, and I
totally understand!

Anyway, funny enough, just this morning I was saying to some colleagues
that there is no current support in the config.xml for "declaring
supported modes".
Well, now we have one.

About the "widget requesting a resize", I sent in the past an email to
Arve about something similar but not quite the same: a sort of "request
mode change" or something. This would allow widgets to ASK the WUA for
"mode change".
Any news about that?

Regards


---
Ivan De Marino
Orange Labs
Mobile and Web Software Engineer, R&D UK
tel. +44 20 8849 5806
mob. +44 7515 955 861
mob. +44 7974 156 216
ivan.demarino@orange-ftgroup.com


This e-mail, and any files transmitted with it, is intended only for the
use of the person/s or entity to whom it is addressed. If you are not
the intended recipient (or authorised to receive information for the
intended recipient) you must not use, disclose, copy, print or rely on
this e-mail. If an addressing or transmission error has misdirected this
e-mail, please notify the author by replying to this e-mail and delete
all copies of this e-mail.  Thank you.

France Telecom R&D UK Ltd is a company registered in England and Wales
with company number 4193379. Our registered office is Minerva House,
Montague Close, London, SE1 9BB.

-----Original Message-----
From: Marcos Caceres [mailto:marcosc@opera.com] 
Sent: 08 May 2009 15:29
To: DE MARINO Ivan RD-ILAB-LON; Arve Bersvendsen
Cc: public-webapps@w3.org
Subject: [widgets] window modes in P&C, was Re: Small question about
latestversion of "P&C specs" (11th Mar 2009)



On 3/12/09 12:25 PM, ivan.demarino@orange-ftgroup.com wrote:
> Mmmm.
> And how we define more than one viewmode?
> I mean, apart from the "default one" for the content, was not decided
to give to the developer the possibility of declaring what modes the
widget supports and how (in terms of size)?
>
> Am I missing something?
>

Right. Finally got around to this!

Here is my attempt at a redefinition:

viewmodes
Optional. A (space separated) keyword list attribute that denotes the
view modes supported the widget. The value SHOULD be one or more of the
following valid window modes as defined in [Widgets-WM]: application,
floating, fullscreen, mini, or all. The default value, which is used
when the attribute is omitted or has a value other than one of the valid
window modes, is 'floating'. The first item in the list represents the
author's preferred view mode, followed by the next most preferred view
mode, and so forth.

Usage example
<widget xmlns="http://www.w3.org/ns/widgets"
         id="http://example.org/exampleWidget"
         version="2.0 Beta"
         height="200"
         width="200"
         viewmodes="floating application">
   <description>
    An example of the possibilities.
   </description>
</widget>

Some thoughts:

The width and height attributes only act as sizing hints for the view
port in floating and application mode. They are irrelevant for
fullscreen, and possibly mini mode. In mini mode, the widget is shoved
into a cramped space of an undefined size that is likely smaller then
all of the other modes. In application mode, the user agent MAY ignore
the width and height attribute (and in some cases, I imagine,
application mode will behave like fullscreen, in which case the width
and height will again be ignored by the UA).

For context where the author wants to resize, they should use
window.resizeBy() and window.resizeTo(). _HOWEVER_ those methods are not
standardized in HTML5 (even though every browser supports them). We need
to formally request they be standardized in HTML5 by presenting the
appropriate use cases.

Kind regards,
Marcos
Received on Monday, 11 May 2009 11:16:32 GMT

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