From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, "Federico G. Benavento" <benavento@gmail.com>
Subject: [9fans] abaco's UI
Date: Thu, 10 Nov 2005 20:46:11 -0600 [thread overview]
Message-ID: <20051111024611.A143222E2@dexter-peak.quanstro.net> (raw)
In-Reply-To: <25913419de36b904890aa0747e7eab6d@yourdomain.dom>
great!
on a related note, it's been mentioned that adding graphics to acme
isn't too hard. has anybody done this? i haven't even taken a look.
my todo list grows at twice the rate as the done list. ;-)
erik
"Federico G. Benavento" <benavento@gmail.com> writes
|
| Hi,
|
| I'm planning a major rewrite of abaco, to fix some bugs and change the
| UI.
|
| This is what I have in mind:
|
| Two bars on the top the first one with commands(Snarf, Download, Exit
| and, maybe in a not so distant future, Look), and the second with the
| current url, their would be frame(2)s, so you can edit them like in
| acme. A third bar would be at the bottom showing the url under the
| mouse pointer.
|
| Also would have scrollbars, because they are needed to render framed
| pages. Mouse's button 1 would open the url in the same window, 2
| would drag the page and 3 would plumb the link.
|
| Some of this changes were sujested by Kenji Okamoto and by Russ Cox.
|
| So, what do you think?
|
| Federico G.Benavento
|
| PS: /n/sources/contrib/fgb/abaco_tables.tgz, is the current
| state of abaco, notice that the rendering process is very, very slow and
| this will be fixed in the rewrite.
next prev parent reply other threads:[~2005-11-11 2:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 2:37 Federico G. Benavento
2005-11-11 2:46 ` erik quanstrom [this message]
2005-11-11 3:04 ` andrey mirtchovski
2005-11-11 3:17 ` Paul Lalonde
[not found] <000001c5e669$f1f5f5b0$14aaa8c0@utelsystems.local>
2005-11-11 9:00 ` Nils O. Selåsdal
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=20051111024611.A143222E2@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=benavento@gmail.com \
/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).