From: <cej@gli.cas.cz>
To: <9fans@9fans.net>
Subject: Re: [9fans] Small program "PlanKey" (paraphrase of DOSKey)
Date: Thu, 29 Jan 2009 14:53:03 +0100 [thread overview]
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17DD660E8@XMAIL.asuch.cas.cz> (raw)
In-Reply-To: <509071940901290350w103904c6rea469880f7dac12e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
>> How about turning acme to universal UI, in the style of old Oberon?
>>From a UI design perspective, it's not clear what it ought to look
>like. More strongly, I'm not really convinced there *is* a good way
>for a UI like that to work. You'd have all the problems the X11 tiled
>window managers have, and if you don't separately provide for either
>"floating" windows (as some of them do) or horribly throw tiles
>around, things like viewing large postscript documents is going to be
>hella disruptive.
What about adding a hide/unhide column functionality? And, perhaps, HideAll (tiles except the current one)?
>I love acme, but I think rio's the right starting place for GUI
>things. Maybe just move the menu into a pre-populated tag, similar to
>Acme's.
I agree. Maybe I am to much Acme-biased.
++pac
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3455 bytes --]
next prev parent reply other threads:[~2009-01-29 13:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 10:03 pavel.klinkovsky
2009-01-23 10:50 ` Francisco J Ballesteros
2009-01-23 11:27 ` Pietro Gagliardi
2009-01-23 11:35 ` Pietro Gagliardi
2009-01-23 12:56 ` roger peppe
2009-01-23 14:14 ` erik quanstrom
2009-01-26 12:41 ` cej
2009-01-26 10:31 ` pavel.klinkovsky
2009-01-27 3:29 ` Roman Shaposhnik
2009-01-27 3:42 ` erik quanstrom
2009-01-27 4:43 ` Roman Shaposhnik
2009-01-27 6:35 ` Akshat Kumar
2009-01-27 6:44 ` Akshat Kumar
2009-01-27 20:01 ` Roman V. Shaposhnik
2009-01-27 20:10 ` erik quanstrom
2009-01-27 22:01 ` Roman V. Shaposhnik
2009-01-27 22:26 ` erik quanstrom
2009-01-27 22:58 ` sqweek
2009-01-27 23:42 ` erik quanstrom
2009-01-28 0:35 ` Anthony Sorace
2009-01-28 5:59 ` lucio
2009-01-28 19:00 ` erik quanstrom
2009-01-28 22:19 ` Joel C. Salomon
2009-01-28 22:51 ` Francisco J Ballesteros
2009-01-29 0:26 ` Akshat Kumar
2009-01-29 2:09 ` erik quanstrom
2009-01-29 8:49 ` cej
2009-01-29 11:50 ` Anthony Sorace
2009-01-29 13:04 ` roger peppe
2009-01-29 13:53 ` cej [this message]
2009-01-29 16:14 ` jimmy brisson
2009-01-29 13:53 ` erik quanstrom
2009-01-29 15:20 ` Akshat Kumar
2009-01-29 16:40 ` Roman V. Shaposhnik
2009-01-29 16:52 ` erik quanstrom
2009-01-29 17:03 ` Akshat Kumar
2009-01-29 17:09 ` Brian L. Stuart
2009-01-27 7:09 ` Russ Cox
2009-01-27 22:12 ` Roman V. Shaposhnik
2009-01-27 22:25 ` Christopher Nielsen
2009-01-27 22:31 ` Roman V. Shaposhnik
2009-01-27 22:43 ` Christopher Nielsen
2009-01-27 22:50 ` Roman V. Shaposhnik
2009-01-27 23:11 ` Christopher Nielsen
2009-01-27 23:40 ` Roman V. Shaposhnik
2009-01-28 3:15 ` Christopher Nielsen
2009-01-28 7:22 ` Eris Discordia
2009-01-27 23:01 ` sqweek
2009-01-26 10:31 ` pavel.klinkovsky
2009-01-27 3:21 ` Roman Shaposhnik
2009-01-27 9:37 ` Pavel Klinkovsky
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=ACCF003CBA3D09458207DB0CB86AD17DD660E8@XMAIL.asuch.cas.cz \
--to=cej@gli.cas.cz \
--cc=9fans@9fans.net \
/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).