unity-design team mailing list archive

[Frederik Nnaji <frederik.nnaji@xxxxxxxxx>]

Hi Siegfried,

On Mon, Jun 28, 2010 at 13:39, Siegfried Gevatter <rainct@xxxxxxxxxx> wrote:

> FYI, If I remember correctly, GNOME's keybinding app lets you choose a
> keyboard combination to switch any window to fullscreen (even if it
> doesn't nativelly support it).
>

yeah, Compiz can do that to a window.

On Mon, Jun 28, 2010 at 04:09, Frederik Nnaji <frederik.nnaji@xxxxxxxxx>wrote:
>
> Fortunately, Compiz has "window rules" which can allow for toggling of
> fullscreen mode for any app.
> Unfortunately, this feature is buggy, as gnome-panel will sometimes cover a
> fullscreen app, instead of disappearing behind it or autohiding.
>

i think a fullscreen mode is different from the ordinary window mode.
The worst example for how to design a fullscreen mode was what i found in
the current Epiphany release. Epiphany rocks, really, i love it, even if it
has some rough corners. But i have a mouse way of getting into fullscreen,
and NO mouse way of leaving it. That's a problem.

What is fullscreen?
Fullscreen is a way of using all the screen pixels to focus mainly the
content an application is trying to communicate to a user.
Every application should decide by itself, what content is relevant while in
this special mode of window focus. Some apps might even request FUSA/MeMenu
to set itself to busy automatically, which definitely should be optional if
implemented as a feature.
Back to Epiphany, while in fullscreen mode, it still shows a navigation bar
and doesn't autohide the tabs toolbar.. this totally misses the point of
fullscreen mode.
In fullscreen mode, an app should display content only, perhaps a few
controls where appropriate, no redundancy at all concerning window chrome or
anything decoration-wise..

or what is the meaning of fullscreen in your opinion?