From: Csaba Henk <csaba@..._for_avoiding_spam.org>
Date: 2005-02-19T11:24:45+09:00
Subject: Re: [OT] Creating Effective Demo Movies

On 2005-02-18, James G. Britt <ruby.talk.list@gmail.com> wrote:
> On Sat, 19 Feb 2005 05:28:06 +0900, Bill Guindon <agorilla@gmail.com> wrote:
>> ...
>> If the entire setup can be done using a shell script, it probably
>> wouldn't take much to run that script through another script to add
>> appropriate delays - to make it "appear" as if it's being typed.
>> 
>> Just a thought.
>
>
> A very good thought.  Even without adding any typing delays (though
> that's a nice touch), a good general approach might be to script as
> much as possible, then record your script in action.

Yes, fine, but why a *shell* scripts, for Heaven's sake? We do know some
language named ruby, don't we? ;)

I think the best way of doing it would be writing directly to the
pseudoterminal device used by the editor. Than you have a programmable
control of what you are doing, without having to do anything manually.

What it doesn't solve is the interaction with gui. But that's neither a
problem, as there are a hatful window managers with some kind of
scripting or "remote control" support (ie., you write simple action
names [possibly with parameters] to a named pipe or socket, and the wm
executes those).  Maybe there are some which are macroable as well, that
is, you do some interaction with the wm and it records your actions to a
script with which you can replay what you've been doing.

Csaba