RE: View modes and sizes, was Re: Application window state and size

Very informative! It looks better if we could conform to W3C standard. Thanks!

> -----Original Message-----
> From: Marcos Caceres [mailto:w3c@marcosc.com]
> Sent: Thursday, April 25, 2013 11:10 PM
> To: Min, Hongbo
> Cc: Christiansen, Kenneth R; public-sysapps@w3.org
> Subject: View modes and sizes, was Re: Application window state and size
> 
> (Sorry for top posting … but this is more of a summary…)
> 
> Ok, so it sounds like we are having the old "view modes" discussion:) Thankfully,
> we already have a W3C Rec for that [1], which supports windowed | floating |
> fullscreen | maximized | minimized.
> 
> The current manifest supports "fullscreen": true | false.
> 
> If people are really serious about supporting other view modes, then we can
> change the manifest to allow the various view mode values. Something like:
> 
> {
> …
> "viewModes": ["fullscreen", "maximized"] ...
> }
> 
> Where viewMode is: A list that denotes the author's preferred view mode,
> followed by the next most preferred view mode and so forth. When the value is
> missing, or is left empty, it implies that the author expects the user agent to
> select an appropriate viewmode for the application.
> 
> With regards to width and height, we will need those for the "floating" case.
> But they only serve as a *hint* for the preferred width and height when the app
> starts up.  I don't think we should add other window positioning information
> (leave that to the window manager).
> 
> [1] http://www.w3.org/TR/view-mode/

> 
> --
> Marcos Caceres
> 
> 
> On Monday, April 22, 2013 at 3:24 PM, Min, Hongbo wrote:
> 
> > Thanks for your explanation. I agree with you about the notes about window
> size, max width/height and window state.
> >
> > Regarding to topleft corner position, it may be useless for an app, as you said,
> the visual effect depends on the desktop window size.
> >
> > From: kenneth.christiansen@gmail.com
> > [mailto:kenneth.christiansen@gmail.com] On Behalf Of Kenneth Rohde
> > Christiansen
> > Sent: Monday, April 22, 2013 8:48 PM
> > To: Min, Hongbo
> > Cc: Marcos Caceres; public-sysapps@w3.org
> > (mailto:public-sysapps@w3.org)
> > Subject: Re: Application window state and size
> >
> > Hi there,
> >
> > On Mon, Apr 22, 2013 at 2:39 PM, Min, Hongbo <hongbo.min@intel.com
> (mailto:hongbo.min@intel.com)> wrote:
> > That is fine.
> >
> > Moreover, if desktop application is taken into consideration. More items
> should be counted into manifest:
> >
> > * window size (width, height)
> >
> >
> > That would be initial I guess, as you probably want to launch the app given
> the previously used size. That is common behavior on desktop.
> >
> >
> > > * max width and height
> >
> >
> > Should be optional.
> >
> >
> > > * window state (fullscreen, always on top, maximized, minimized)
> >
> >
> > Is always on top really honored on all platforms? I guess fullscreen should be
> default if no initial window size is given.
> >
> >
> > > * top-left corner (x, y position)
> >
> >
> > There is an issue here as we define sizes and positions in CSS pixel units which
> might be not the same as the desktop position. Do you have an actual use-case
> for this? Isn't it enough that the runtime restarts the app as the last used
> position instead?
> 
> >
> >
> > Kenneth
>

Received on Saturday, 27 April 2013 04:49:05 UTC