From: "T. V. Raman" <ramantv@earthlink.net>
To: blinux-list@redhat.com
Subject: software for overhead projection
Date: Tue, 21 Nov 2000 08:14:29 -0800 [thread overview]
Message-ID: <14874.40805.696226.731284@localhost.earthlink.net> (raw)
In-Reply-To: <14873.63423.923420.483347@pjr2-as.dar.csiro.au>
Prepare your slides in latex convert them to good looking
pdf and leave the button clicking to some photon-enabled
mouse-waving human.
If you really want to click the buttons yourself,
then run emacspeak under X,
and spend some time hacking your favorite window manager to
send
the next button click when you push the appropriate key.
>>>>> "RAYNER" == RAYNER Peter <ray060@dar.csiro.au> writes:
RAYNER> Help help! I'm getting powerpoint envy ... Well
RAYNER> not really. I am, though, looking for some of
RAYNER> its functionality, i.e to project overheads.
RAYNER> I'm imagining myself at front of lecture with
RAYNER> speech-enabled laptop and overhead projector
RAYNER> panel connected to video output. I have a file
RAYNER> menu (probably using something like the
RAYNER> dired-mode of emacspeak) which the members of
RAYNER> the audience can't see. "visiting" a file feeds
RAYNER> it to ghostscript or acroread or something to
RAYNER> display it on the panel. I foresee all kinds of
RAYNER> problems with this, e.g. the emacspeak session
RAYNER> (or however we do this) has to be invisible, but
RAYNER> it sounds like a task for some interestingly
RAYNER> devious hacking. Anyone done anything like
RAYNER> this? Have any ideas? cheers Peter Rayner
RAYNER> _______________________________________________
RAYNER> Blinux-list mailing list Blinux-list@redhat.com
RAYNER> https://listman.redhat.com/mailman/listinfo/blinux-list
--
Best Regards,
--raman
Email: raman@cs.cornell.edu
WWW: http://www.cs.cornell.edu/home/raman/
PGP: http://www.cs.cornell.edu/home/raman/raman.asc
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
RAYNER Peter
` T. V. Raman [this message]
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=14874.40805.696226.731284@localhost.earthlink.net \
--to=ramantv@earthlink.net \
--cc=blinux-list@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).