From: Jeff Kowalczyk <jtk@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode screencasts
Date: Sun, 26 Sep 2010 18:41:36 +0000 (UTC) [thread overview]
Message-ID: <loom.20100926T195501-235@post.gmane.org> (raw)
In-Reply-To: 87tylfvnte.fsf@ericabrahamsen.net
Eric Abrahamsen <eric <at> ericabrahamsen.net> writes:
>
> One thing that would be really excellent is to show keystrokes as you do
> the tutorial. I don't know what system you're using, but this link:
>
> http://screencasters.heathenx.org/blog/2009/04/06/smaller-key-status-monitor/
>
>
> Rustom Mody wrote:
>
> mwe-log-commands may be particularly useful for an emacs related
> screencast http://www.foldr.org/~michaelw/emacs/mwe-log-commands.el
It would be extremely nice for screencasting Emacs to have a configurable input
and prompt display similar to the calc trail.
Wish list:
- stack view of the keystream from view-lossage
- annotations (i.e. an overlay) when a binding dispatches a command
using the mechanism from mwe-log-commands.
- annotations of minibuffer prompts
- annotations of keybinding hints
The view-lossage stream doesn't use the format one would want for user
documentation:
C-x b f o o <return> <return> <menu> v i e w - l o s s a g e <return>
Something like the following would be more like documentation:
C-x b [switch-to-buffer]
f o o RET [minibuffer input]
RET [minibuffer prompt confirm]
[visiting buffer] foo
M-x [<menu>]
v i e w - l o s s a g e RET [minibuffer input]
[visiting buffer] *Help*
The parts in [brackets] are intended to indicate some kind of face overlay. As
uncolored plaintext the information is just distracting.
Another tool, http://www.emacswiki.org/emacs/ScreencastMode has good ideas for
keybinding hints and one-key stepthrough. I don't think the typed-text narration
style is a good fit for these particular screencasts and their target audience,
however.
Jeff
next prev parent reply other threads:[~2010-09-26 18:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 15:12 Org-mode screencasts Richard Moreland
2010-09-23 15:22 ` Russell Adams
2010-09-23 15:27 ` Eric Schulte
2010-09-23 16:31 ` John Hendy
2010-09-23 15:56 ` Erik Iverson
2010-09-23 16:21 ` Richard Moreland
2010-09-23 16:49 ` Bastien
2010-11-05 13:11 ` Russell Adams
2010-09-23 18:16 ` Sebastian Rose
2010-09-23 22:47 ` Charles Cave
2010-09-24 0:45 ` Richard Moreland
2010-09-24 2:54 ` Erik Iverson
2010-09-24 3:09 ` John Hendy
2010-09-24 3:34 ` Richard Moreland
2010-09-24 3:46 ` Shelagh Manton
2010-09-24 20:17 ` Stefan Vollmar
2010-09-24 3:50 ` Erik Iverson
2010-09-25 23:34 ` Richard Moreland
2010-09-24 2:58 ` Erik Iverson
2010-09-24 8:45 ` Memnon Anon
2010-09-24 3:10 ` Eric Abrahamsen
2010-09-26 15:03 ` Olivier Berger
2010-09-26 18:41 ` Jeff Kowalczyk [this message]
2010-09-28 10:23 ` Scot Becker
2010-09-28 10:35 ` Richard Riley
2010-09-28 12:06 ` Sebastian Rose
-- strict thread matches above, loose matches on Subject: below --
2010-09-23 16:34 Rustom Mody
[not found] <201009241600.o8OG0swV023247@hormel6.ieee.org>
2010-09-24 18:01 ` Raymond Zeitler
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20100926T195501-235@post.gmane.org \
--to=jtk@yahoo.com \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).