From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Fred Stratton <fredstratton@imap.cc>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Field Report on CeroWrt 3.10.24-1
Date: Sun, 15 Dec 2013 12:46:25 +0000 [thread overview]
Message-ID: <871u1e1dum.fsf@toke.dk> (raw)
In-Reply-To: <52AD9F16.8080802@imap.cc> (Fred Stratton's message of "Sun, 15 Dec 2013 12:22:46 +0000")
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
Fred Stratton <fredstratton@imap.cc> writes:
> Such as user, I argue, is capable of reading a wiki.
Sure, put the long explanations in the wiki. But the whole point of
having a GUI (IMHO) is discoverability of options, and to contain enough
of a reference that it's not necessary to look at the documentation
every time, even for a seldomly used feature.
That being said, I agree that the GUI should not contain pages of
explanation. But a very terse explanation with a link to the wiki for
more information would work, I think. I.e. enough text to jog one's
memory after having read the wiki the first time around. :)
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-12-15 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 5:16 Rich Brown
2013-12-15 11:33 ` Sebastian Moeller
2013-12-15 11:55 ` Fred Stratton
2013-12-15 12:09 ` Sebastian Moeller
2013-12-15 12:22 ` Fred Stratton
2013-12-15 12:46 ` Toke Høiland-Jørgensen [this message]
2013-12-15 14:04 ` [Cerowrt-devel] Field Report on CeroWrt 3.10.24-1/AQM GUI Rich Brown
2013-12-15 15:04 ` [Cerowrt-devel] CeroWrt 3.10.24-1/Wifi problems Rich Brown
2013-12-15 18:16 ` [Cerowrt-devel] Field Report on CeroWrt 3.10.24-1 Dave Taht
2013-12-15 19:25 ` Sebastian Moeller
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://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871u1e1dum.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=fredstratton@imap.cc \
/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