<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
making more progress on some of the tools I need for speech or
programming. Got a friend working with me on the variable management
tool. Could use a few bits to help project along.<br>
<br>
1)<br>
"Where am I." used to help resolve which transformation of an
English name is used in a given context. Specifically, I'm looking
for files/class/method information. Next variation of this "where am
I." context is if I have an instance, what names are visible from
that class defining that instance. Yes, yes I know all about
ducktyping and how it has made people's lives completely miserable
(mine at least. I really love a good strong type signature). I'm
perfectly content to do my own transformation between instance and
class and then ask about what's visible in the class. which raises
the question of how does an external application query Emacs for
data.<br>
<br>
2)<br>
(Jump to|push to|get|change) [next | last]
(instance|method|argument #|index|single [double] quotes|triple
[double] quotes)<br>
<br>
These are the kind of operations and data types I need to
manipulate. Some of these imply selection at the same time (get,
change).<br>
<br>
3)<br>
Something that would be really really nice would be navigation plus
selection. If you navigate piece of code like this, you would
highlight (and automatically select) in the following sequence<br>
<br>
if unit is "carbs":<br>
<br>
<br>
<font color="#ff0000">if unit is "carbs":</font> (statements)<br>
<br>
<font color="#ff0000"><font color="#000000">if </font>unit is
"carbs"<font color="#000000">: (predicate)</font><br>
</font><br>
<font color="#ff0000"><font color="#000000">if unit</font> is <font
color="#000000">"carbs": (comparison)<br>
<br>
</font></font><font color="#ff0000"><font color="#000000">if </font>unit
<font color="#000000">is "carbs": <br>
<br>
</font></font><font color="#ff0000"><font color="#000000">if unit
is</font> "carbs"<font color="#000000">:</font></font><br>
<br>
<font color="#ff0000"><font color="#000000">if unit is "carbs"</font>:</font><br>
<font color="#ff0000"><br>
</font>as you can see, navigation involves traversing the language
structure. The reason for this is each point is highlighted in red
has a name and I should also be able to navigate it by name. I've
put in the few that I can think of that makes sense and yes, if you
have multiple terms it's going get a little ugly naming them but I'm
sure something useful will evolve.<br>
For right now though simply navigating and selection would make
things much easier because I don't have to coordinate hands,
fingers, mouse to select an element. I just get a chunk and it will
most likely be the chunk I want.<br>
<br>
I think I did warn you that speech user interfaces and specifically
programming by speech does get a little weird at times if all you're
used to his keyboard and mouse. :-)<br>
<br>
<br>
</body>
</html>