From: David Kastrup <dak@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Phil Sung <psung@MIT.EDU>, emacs-devel@gnu.org
Subject: Re: guided tour suggestions
Date: Thu, 28 Jun 2007 10:36:58 +0200 [thread overview]
Message-ID: <86hcosxyol.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <18051.28495.761758.288770@kahikatea.snap.net.nz> (Nick Roberts's message of "Thu\, 28 Jun 2007 20\:20\:31 +1200")
Nick Roberts <nickrob@snap.net.nz> writes:
> > > Would it be possible to make the screenshots with emacs -Q so
> > > that people see what they get out of the box ... ?
> >
> > Good idea.
> >
> > > The guided tour ... shows an Emacs a) compiled without a modern
> > > toolkit (Gtk+, Windows or Mac) b) without menus c) without
> > > toolbars d) without scrollbars (for heaven's sake!) e) without
> > > font diversity. The only thing hinting at fonts is a man-page
> > > f) without file dialogs g) without tooltips h) without any
> > > non-ASCII character
> >
> > When I get a chance, I will make some screenshots with the
> > default UI setup, and with more complex formatting/characters.
>
> Remember, however, that GTK is _not_ the default toolkit for Emacs
> 22.1 so that won't be what people see out of the box.
Depends on the box. I should hope that at least GNOME-centric
distributions with X11 would offer the Gtk+ version (Debian offers a
choice IIRC of what to install). Anyway, if we wanted to go for "most
common case", we would need to show a Windows Emacs. That is not
really what we want, either (though a single screenshot for each of
the major platforms for comparison would perhaps be nice: I find that
Emacs' visual integration into various desktops is a selling point
against XEmacs which shows quite the same quaint look everywhere), but
I suppose it pretty much depends on who is going to spend the effort
of creating the screenshots.
> Currently it won't be the default for Emacs 22.2 either.
I think there is still a difference between using configure without
options, and using no run-time options. However, I would also
consider my compilation (using --without-toolkit-scroll-bars since
anything but Athena toolkit semantics is somewhat dysfunctional) unfit
for screen shots since it uses _special_ configure options resulting
in a look that won't likely be available "out of the box" for _any_
distribution. It would be too complicated explaining that my look
does not result from a deficiency of Emacs, but a deficiency of Gtk+
and my way around it (with a little bit of help from Emacs).
--
David Kastrup
next prev parent reply other threads:[~2007-06-28 8:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 18:03 guided tour suggestions Karl Berry
2007-05-03 20:34 ` Phil Sung
2007-06-02 20:52 ` Chong Yidong
2007-06-02 21:04 ` David Kastrup
2007-06-02 22:08 ` Drew Adams
2007-06-03 8:23 ` Mathias Dahl
2007-06-03 15:32 ` David House
2007-06-11 20:01 ` Phil Sung
2007-06-11 20:19 ` Drew Adams
2007-06-27 1:16 ` Phil Sung
2007-06-27 4:28 ` Drew Adams
2007-06-27 5:45 ` David Kastrup
2007-06-27 6:04 ` Nick Roberts
2007-06-27 7:37 ` David Kastrup
2007-06-28 7:02 ` Phil Sung
2007-06-28 7:20 ` David Kastrup
2007-06-28 9:54 ` David House
2007-06-28 10:25 ` David Kastrup
2007-08-09 7:15 ` Phil Sung
2007-08-09 7:36 ` David Kastrup
2007-08-13 8:09 ` Phil Sung
2007-06-28 8:20 ` Nick Roberts
2007-06-28 8:36 ` David Kastrup [this message]
2007-06-29 16:41 ` Juri Linkov
2007-06-30 1:16 ` Nick Roberts
2007-06-30 10:03 ` David House
2007-07-22 10:59 ` Dieter Wilhelm
2007-05-03 22:30 ` David Koppelman
2007-05-03 22:41 ` Daniel Brockman
2007-05-04 5:09 ` Dieter Wilhelm
2007-05-04 7:32 ` Eli Zaretskii
2007-05-05 14:39 ` Randal L. Schwartz
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=86hcosxyol.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
--cc=psung@MIT.EDU \
/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).