unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-devel@gnu.org
Subject: Re: Proposal for a new API to fullscreen
Date: Tue, 19 Aug 2008 12:25:00 +0200	[thread overview]
Message-ID: <200808191225.00543.tassilo@member.fsf.org> (raw)
In-Reply-To: <jebpzpqq94.fsf@sykes.suse.de>

On Tuesday 19 August 2008 11:59:51 Andreas Schwab wrote:

Hi Andreas,

> >> By fullscreen I mean no taskbar, emacs take all the screen estate.
> >
> > Isn't fullscreen display of some application window something the
> > window manager should deal with, not the application itself?  For
> > example in KDE or stumpwm you can make any window fullscreen (via a
> > window menu or a keybinding), and I'm sure it's the same for GNOME
> > and most/all other windowmanagers.
>
> That's not fullscreen, but maximize.

No, it's fullscreen.  In KDE (4.1) it's rightklick on window decoration
-> Advanced -> [X] at Fullscreen.  In stumpwm (a tiling window manager,
where all windows are maximized anyway) it's the `fullscreen' command.

> The difference is that the latter still shows things like the taskbar
> and window decoration.

Nope, there are no such things anymore.

> The fullscreen mode has to be requested by the application.

So how do those commands achive that?  Fake that request?  And who
serves it?  I've thought the window manager, but in that case there's no
reason that the application has to request the fullscreen mode.

Bye,
Tassilo





  reply	other threads:[~2008-08-19 10:25 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19  7:46 Proposal for a new API to fullscreen Ivan Kanis
2008-08-19  9:31 ` Tassilo Horn
2008-08-19  9:58   ` René Kyllingstad
2008-08-19 10:26     ` Tassilo Horn
2008-08-19 11:11       ` René Kyllingstad
2008-08-19 11:36         ` Tassilo Horn
2008-08-19 11:59           ` Ivan Kanis
2008-08-19 12:13             ` Lennart Borgman (gmail)
2008-08-19 13:31               ` Ivan Kanis
2008-08-19 13:40                 ` Lennart Borgman (gmail)
2008-08-19 13:42                 ` Lennart Borgman (gmail)
2008-08-19 12:47             ` Tassilo Horn
2008-08-19 13:49               ` Jan Djärv
2008-08-19 14:00                 ` Tassilo Horn
2008-08-19 15:11             ` Tom Tromey
2008-08-19 18:52               ` Jan Djärv
2008-08-19  9:59   ` Andreas Schwab
2008-08-19 10:25     ` Tassilo Horn [this message]
2008-08-19 10:56       ` Andreas Schwab
2008-08-19 13:08 ` Jason Rumney
2008-08-19 13:42   ` Ivan Kanis
2008-08-19 16:53     ` Jason Rumney
2008-08-19 17:52       ` Tassilo Horn
2008-08-19 17:57         ` Lennart Borgman (gmail)
2008-08-19 18:14           ` Jason Rumney
2008-08-19 18:32             ` Lennart Borgman (gmail)
2008-08-19 18:33             ` Lennart Borgman (gmail)
2008-08-19 18:14           ` Tassilo Horn
2008-08-20  9:42         ` Ivan Kanis
2008-08-20 12:16           ` Jason Rumney
2008-08-20 13:06             ` Tassilo Horn
2008-08-20 13:46               ` Jason Rumney
2008-08-20 15:21               ` [PATCH] " Ivan Kanis
2008-08-19 15:08 ` Tom Tromey
2008-08-21  5:59   ` Ivan Kanis
2008-08-23  8:03   ` [PATCH] adding maximize to fullscreen frame parameters Ivan Kanis
2008-08-23 18:09     ` Eli Zaretskii
2008-08-24  8:23       ` Ivan Kanis
2008-08-24 18:12         ` Eli Zaretskii
2008-08-26  6:57           ` Ivan Kanis
2008-09-19 11:35             ` Lennart Borgman (gmail)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200808191225.00543.tassilo@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).