From: Paul Donnelly <paul-donnelly@sbcglobal.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Why does Acme only show text?
Date: Wed, 15 Jul 2009 09:25:51 +0000 [thread overview]
Message-ID: <87r5wivc8s.fsf@plap.localdomain> (raw)
In-Reply-To: <d50d7d460907141858j7eb10c06yf095d70c138374a7@mail.gmail.com>
jason.catena@gmail.com (Jason Catena) writes:
> I've been wondering for years now why Acme (and Wily, which I used
> first) only display text files.
>
> It seems to me that the content of an Acme window could be anything: a
> picture, a postscript or PDF file, a star chart, a web page. Keeping
> with the spirit of small parts brought together, Acme could outsource
> the displaying of the content to another program, place its output in
> the Acme window, and operate on it by sending commands from the tag to
> the rendering program.
Hi, I don't know anything about anything, but it seems to me that it's
more productive to look at the question the other way around: why not
modify Rio to tile windows like Acme does? Acme is a text editor, so
it's no surprise that it handles text only. If you want tiled windows
you can display arbitrary graphics in... well, there's already an API
for graphics (and input).
If you wrote up a general API for sending commands to windows, then you
could write a window system that tiled windows and provided tags to
execute commands from. I think that would be a very good thing,
FWIW. Not that there aren't other issues to consider to make the system
as usable as Acme, for example how the “applets” in this system are
going to interoperate with each other.
next prev parent reply other threads:[~2009-07-15 9:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 1:58 Jason Catena
2009-07-15 4:36 ` Rob Pike
2009-07-15 5:02 ` David Leimbach
2009-07-15 13:11 ` Charles Forsyth
2009-07-16 9:58 ` cej
2009-07-16 10:41 ` mattmobile
2009-07-16 12:11 ` michael block
2009-07-16 12:29 ` cej
2009-07-15 9:25 ` Paul Donnelly [this message]
2009-07-15 12:22 ` Ethan Grammatikidis
2009-07-15 15:32 ` cej
2009-07-15 15:44 ` Ethan Grammatikidis
2009-07-15 17:00 ` John Floren
2009-07-15 18:24 ` Francisco J Ballesteros
2009-07-15 18:26 ` Steve Simon
2009-07-15 18:59 ` David Leimbach
2009-07-15 19:07 ` John Floren
2009-07-15 19:27 ` David Leimbach
2009-07-15 20:58 ` Chad Brown
2009-07-15 21:07 ` John Floren
2009-07-15 19:54 ` Jason Catena
2009-07-15 19:59 ` erik quanstrom
2009-07-15 20:05 ` andrey mirtchovski
2009-07-15 20:14 ` Devon H. O'Dell
2009-07-15 20:29 ` Jason Catena
2009-07-15 20:42 ` Noah Evans
2009-07-15 20:51 ` David Leimbach
2009-07-15 21:27 ` Ethan Grammatikidis
2009-07-15 23:31 ` Jason Catena
2009-07-15 21:07 ` Ethan Grammatikidis
2009-07-15 21:12 ` erik quanstrom
2009-07-15 21:32 ` Ethan Grammatikidis
2009-07-15 20:41 ` Lyndon Nerenberg
2009-07-15 21:00 ` Federico G. Benavento
2009-07-15 21:14 ` David Leimbach
2009-07-16 8:51 ` Paul Donnelly
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=87r5wivc8s.fsf@plap.localdomain \
--to=paul-donnelly@sbcglobal.net \
--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).