From: rob@plan9.research.att.com
To: <sam-fans@hawkwind.utcs.toronto.edu>
Date: Mon, 21 Mar 1994 10:29:20 -0500 [thread overview]
Message-ID: <94Mar21.102932est.24186@hawkwind.utcs.toronto.edu> (raw)
sam on the blit had scrolling menus because someone
else implemented them in the library that sam linked
with. i found them unusably fussy to navigate so when
sam moved off the blit scrolling menus were left
behind. a good implementation might save the idea
but that is harder than most realize.
the simpler solution, the one we apply here, is to keep
the list of files manageable. this means the menu works
equally well for all files all the time.
of course, this is a matter of taste. you have the
source.
-rob
reply other threads:[~1994-03-21 15:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=94Mar21.102932est.24186@hawkwind.utcs.toronto.edu \
--to=rob@plan9.research.att.com \
--cc=sam-fans@hawkwind.utcs.toronto.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).