From: pac7@post.cz
To: 9fans@cse.psu.edu
Subject: [9fans] Re: Evolving rio / GUI development
Date: Fri, 4 Mar 2005 14:39:43 +0100 [thread overview]
Message-ID: <b0f4e6e2f677edcd7a242194a4dcb532@www2.mail.post.cz> (raw)
>i think the right thing to do is eliminate the menus
> entirely.
Yes! Menus are just crap compared to acme UI. Don't give me
anything I can't change!
>what i'd really like is to be able to move
>windows between rio and acme, not just make them look
> similar.
How about to make everything, incl. graphics, go to Acme ?? No
joke, really.... Old Oberon had it, until it downgraded to a
Windozish UI.
(out of topic): BTW, mee too is running proudly two machines
(lap- + desktop) natively -- and, hopefully, will ever do so.
++pac
--
Akcni unorova nabidka "3 za cenu 1"! Ziskejte
VOLNY ADSL 512/128 3GB za cenu 1GB!
http://adsl.volny.cz
next reply other threads:[~2005-03-04 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 13:39 pac7 [this message]
2005-03-04 13:44 ` C H Forsyth
2005-03-04 13:46 ` Brantley Coile
-- strict thread matches above, loose matches on Subject: below --
2005-03-24 5:58 pac7
2005-03-24 6:08 ` Russ Cox
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=b0f4e6e2f677edcd7a242194a4dcb532@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).