Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: ... and now for something completely different: User Friendliness
Date: Thu, 02 Jan 2003 20:29:23 +0100	[thread overview]
Message-ID: <ilufzsb4agc.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3znqkhuj3.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 02 Jan 2003 08:37:20 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> So we come back to these questions: What language should these
> configuration santas be written in, and what should be used to render
> the user interface?
>
> Now, the most obvious thing to do is to just write them in Lisp, and
> I definitely don't want to do that.
>
> (if (string= (getenv "NNTPSERVER") "")
>     (if (query "You don't seem to have set a news server,
> so do you want to use Gnus to read news or mail?")
>          (setq news-server (quert "Ok, then gimme the
> name of the news server"))))
>
> Eek.  It's a readability nightmare.
>
> The same is the case with anything that looks like HTML with embedded
> program statements.  If you write PHP with lots of strings and stuff
> in between, it soon just gets too ugly to be fun.
>
> So -- any good ideas?  Surely somebody must have come up with a nice
> solution here...
>
> The other question is -- how to render the user interface?  Again,
> Customize has lots of stuff for that, and might be a likely
> contender.  The other is HTML and w3.  Any other ideas?

Doesn't GTK have wizards?  If so, then one idea is to use them if they
become accesible from elisp once the core C level GTK support in Emacs
is finished (which are working quite nicely here).

If the user is a newbie, she probably do not want to learn another
wizards GUI first, and considering the widget elisp API available I
fear implementing one now will be rather ugly even after lots of work.
(Compare speedbar and the diff frames, which are nice but rather
non-standardly crafted GUI widgets and at least confused me when I
first tried them.)




  parent reply	other threads:[~2003-01-02 19:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02  7:37 Lars Magne Ingebrigtsen
2003-01-02 10:11 ` Frank Schmitt
2003-01-02 18:19   ` Lars Magne Ingebrigtsen
2003-01-02 19:29 ` Simon Josefsson [this message]
2003-01-02 19:37   ` Lars Magne Ingebrigtsen
2003-01-02 22:10     ` Simon Josefsson
2003-01-06 16:05 ` Wes Hardaker
2003-01-07  5:23   ` Lars Magne Ingebrigtsen
2003-01-07 15:27     ` Wes Hardaker
2003-01-08  4:45       ` Lars Magne Ingebrigtsen
2003-01-08  6:31         ` Wes Hardaker
2003-01-08 15:18         ` Ted Zlatanov
2003-01-11 20:10           ` Lars Magne Ingebrigtsen
2003-01-13  0:44             ` Wes Hardaker
2003-01-13 18:24               ` Lars Magne Ingebrigtsen
2003-01-13 19:22             ` Ted Zlatanov

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

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

  git send-email \
    --in-reply-to=ilufzsb4agc.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    /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.
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 NNTP newsgroup(s).