From: pac7@post.cz
To: 9fans@cse.psu.edu
Subject: [9fans] Re: Evolving rio / GUI development
Date: Thu, 24 Mar 2005 06:58:18 +0100 [thread overview]
Message-ID: <384299dc7960de58a71fae1736546185@www2.mail.post.cz> (raw)
Hi!
As an everyday user of Acme (since 2000, or so) I would like to
share some ideas I would like to see in Acme's UI, which I,
nevertheless, like much. Here they are:
-No taglines
-Processes win shows running processes started from Acme (like
uppermost tagline does now) -Special command win shows guide file
with predefined commands; this win is special in that command
2-clicked in this win acts in the last focused win, not in this
one; otherwise, it is a normal window ( perhaps could be also
permanently visible) -Two columns: first contains Command win and
+List win
-Rows instead of columns
-Just a single win visible in the row, others are hidden
-Command ListWin lists open windows in +List win, 3-click on win
name brings it to front, as usually -Moving between wins
(bringing win to the front) using +List win
-No win handle: instead, dirtiness indicator of any win resizes
both width (of column) and heigth (of individual win, as usually)
-New win created in the row with last win in focus
It could look something like this:
hget http://www.gli.cas.cz/home/cejchan/newacme.pdf | page
One problem: should there be a list of window-specific commands,
e.g. for mail, or so? [No. Guide file should suffice] If we could
get rid of menus in rio, too, wouldn't that be nice?? Perhaps,
having a command-window somewhere [no taglines, please] (Nextstep
had a single menu for all apps; doesn't Mac have it, too? Not
familiar with Mac)
Hope it does not hurt anybody.
Regards,
++pac.
--
! NOVINKA ! -- SURVIVAL L-Carnitin+Chrom -- Zbav se kil a dej se
do formy! http://www.sportwave.cz
next reply other threads:[~2005-03-24 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 5:58 pac7 [this message]
2005-03-24 6:08 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 13:39 pac7
2005-03-04 13:44 ` C H Forsyth
2005-03-04 13:46 ` Brantley Coile
2005-02-23 7:22 tapique
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=384299dc7960de58a71fae1736546185@www2.mail.post.cz \
--to=pac7@post.cz \
--cc=9fans@cse.psu.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.
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).