On 2/7/2011 7:06 PM, Stephen J. Turnbull wrote:
Mats Lidell writes:
> almost half a developer! This might be a path worth taking for you
> until we have the time to look into getting all these install issues
> into place.
Remember, Eric can't type (or at best it's very painful for him), and
as I understand his situation one reason for his interest in XEmacs is
that voice control is almost as difficult for him at present. He's
looking for a way to gain more control over his environment through
XEmacs. While he's willing to put in a lot of effort, he says, he
still needs our help. This is good for us too IMO.
Like most RSI injured developers, it's painful all the time ranging from
moderate to severe depending on level of use. What may take you (collectively) a
small number of hours to type will take me a half a day to type or a small
number of hours to speak if and only if accessibility features are present.
Control means there is a task specific interface in place. For example,
something like trace route would need some way of incrementally building the
commands, memorizing it with a specific name and then an argument which
translates a name to a hostname. So I could say something like
Trace numeric Harvey which would generate
traceroute -n
harvee.org
But if I did something like
Trace route raw
(Display UI for selecting options)
Remember as something simple
after the command is built, saying "trace something simple truly free Emacs"
should generate the right command. Haven't figured it all out but I think this
is the way it can work.
How much any given developer wants to help is a personal matter, of
course, but I hope people will keep in mind that the returns to making
it easier for Eric to get these "trivial" "startup" tasks done are
more than just helping him; it will be a much smoother XEmacs
experience for all new users.
There are two levels of help I need. Obviously there is the "let's get things
running better and this startup problem I'm having I'm trying to keep notes so I
can put it into the documentation. The second level is starting to do
"interesting" things. I don't know whether to do them completely independent
of
Emacs because I do need a particular edit control if I'm going to edit using
speech recognition. The concept I'm trying to exploit is putting a
transformation filter between the environment holding non-speakable data and a
speakable editing environment. Outbound, it translates to an English like format
and the return is the inverse (Idemopotent transform)
There are multiple contexts where this would be useful. In theory, we could do
everything inside of Emacs as long as I could write the code in Python. :-)
although we would need the core of the vr-mode working.
I need to go back over these concepts and think about what does it mean when the
editing environment is on a remote machine and the speech recognition
environment is local. I'd like to be able to run a remote Emacs so that things
like Shell and other tools could be used with whatever accessibility features
are developed.
I'll close with, if we can make some serious headway with incorporating
something like Select-and-Say within Emacs, and other accessibility features, it
would be greatly appreciated by a number of developers and a great example to
show nuance that they can't do what we need for accessibility and should support
independent efforts.
BTW, I try not to think of people as *being* users or *being*
developers. Rather at any given time a person *acts as* a user or as
a developer. Of course some people are most visible on this list in
their developer role, and others as users. But *everybody* is a
contributor, and everybody uses XEmacs or is interested in it for some
reason.
But but but, I'm a really destructive user. :-)
---eric
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta