Re: On working with consoles/terminals in Sodbeans

Marlon, try using "dir /d", that might be what you are looking for in
windows command prompt.

Andreas, I have a couple comments.

A command prompt/terminal all comes down to review of screen output to me.

<dream>
I think it would be great to be able to review output in different ways,
pertaining to its presentation.  So if the output is representing a
table/grid.  Then in addition to being able to review the entire line
from left to right.  It would be great to navigate by cell.  Much like
some of the screen readers read a table in Microsoft Word or an HTML
table.  You can navigate by row/column/cell.  Navigating by cell would
just read the cell contents as you come down row by row.

So the console would know the output is representing a table, and you
would have review commands to navigate that table efficiently and logically.
</dream>

-Rodney



Marlon Brandão de Sousa wrote:
> Hello,
> 1- One thing that is needed is to stop the screen and enter in a
> review mode where you can use the arrows to read, spell or do other
> reviewing operations with data currently displayed on the screen. The
> screen should not scroll while this reviewing is being made, so that
> when the normal mode is actived again, the information can continue to
> be presented.
> 2- One thing that helps in a text mode based is do not showing
> graphical stuff like several iphens and other characters that compose
> a somehow graphical presentation. A typical screen reader will
> consider these characters as part of the text to be reviewed making
> the important information hard to be accessed.
>
> Another thing that should be considered is context. For example, if I
> use the dir command in the DOS prompt and use the JAWS cursor (also
> called the review cursor or review mode in other assistive
> technologies), I will hear a bunch of numbers (the date and time plus
> perhaps some other information) before hearing the file name. If my
> goal is hearing the files list, having to hear all dates plus time
> plus other information before hearing the file names will make the
> command unaccessible in practical terms for me, even with JAWS being
> perfectly able to read the results of the command in the screen.
> Thanks,
> Marlon
>
> 2009/11/3, Andreas Stefik <stefika@xxxxxxxxx>:
>   
>> Folks,
>>
>> Work is proceeding steadily on the sodbeans project. We are "nearly"
>> complete with our debugger windows and are steadily finishing up the OOP
>> implementation of our custom programming language. While there's quite a bit
>> of work to do, my team is now looking for some ideas on what would make
>> working with "consoles" easier (e.g., the command line).
>>
>> One of the ideas that we are going to implement, for sure, is making our
>> console reversible, so you can always back up what was output to a previous
>> point, just like the rest of sodbeans. We're also looking carefully at what
>> kind of audio should be output and are integrating this console directly
>> into netbeans. A few questions though:
>>
>> 1. When using a terminal, is there anything about it that makes interacting
>> with it difficult?
>>
>> 2. What kind of features would you like to see in the terminal that you
>> think would help alleviate the problems?
>>
>> As always, everything we are working on is open source and freely available.
>> We're highly open to ideas, suggestions, and feedback. Of course --- if you
>> want to submit a patch or get more involved; we're open to that too.
>>
>> Andreas Stefik, Ph.D.
>> Southern Illinois University Edwardsville
>> Assistant Professor
>> Department of Computer Science
>>
>>     
>
>
>

Other related posts: