Robin Berjon wrote:
On Nov 9, 2009, at 13:05 , Marcos Caceres wrote:
On Mon, Nov 9, 2009 at 12:26 PM, Robin Berjon <[email protected]> wrote:
On Nov 1, 2009, at 18:06 , Marcos Caceres wrote:
2009/10/5 Robin Berjon <[email protected]>:
it seems to me that there's a missing distinction in our list of view
modes: the difference between maximised and fullscreen (or perhaps
fullscreen and all-screen).
Maximised is the case in which the application takes up the entire
available screen space minus a little bit of chrome either for
itself (a
window bar with a title and perhaps some buttons) or for the system
(task
bar, menu clock, etc.); whereas fullscreen is when the viewport is
the same
size as the screen (e.g. for video playback).
Both desktops and phones tend to have this distinction in one way or
another, so it sounds to me as something that we should expose as
well.
I think application mode already covers this if the application is
maximized as you defined it.
If application is maximised, then what is the keyword that describes a
window that has chrome but isn't occupying the entirety of the space
that
windows can?
That would be 'application', but not maximized.
Uh, but those can be two different windowing modes, with the chrome
subtly different and different behaviour (e.g. the window can't be
dragged if maximised).
That's UA/OS dependent.
Or are you thinking about this in terms of the broken OSX UI that can't
tell the difference? If so, I strongly object — it's a usability nightmare.
Exactly, so stop imposing your dirty Vi command-line view of the world
on the rest of us, Robin! :)
But seriously, I don't think we need to get to the level where we are
specifying behavior. It should just be enough to say chrome off, chrome
on. If chrome on, do as you do in your OS. If chrome off and fullscreen,
then you _may_ do as we say - fullscreen is bla bla.
