Re: Auditory interface ideas, what would help?

  • From: "qubit" <lauraeaves@xxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Tue, 1 Sep 2009 19:16:32 -0500

Hi Andreas --
Is your dissertation available online?
What languages did you work with?
I remember many battles with scope management back when I worked on C++ 
compiler and tools.  There were a number of people working on components of 
early IDEs for C++, which was difficult to manage as the language was still 
evolving and changing.  But scope was one thing that received a lot of 
attention, especially in the front end where it influenced parsing and typing 
and beyond.
It is interesting now to see how things have evolved.  I worked on it back in 
the stone age (hmm, maybe the stone age through the bronze age).
I would love to read about your work. Was it on java?
Happy hacking.
--le

  ----- Original Message ----- 
  From: Andreas Stefik 
  To: programmingblind@xxxxxxxxxxxxx 
  Sent: Monday, August 31, 2009 10:27 PM
  Subject: Re: Auditory interface ideas, what would help?


  Vladyslav,

  Thanks for pointing this out. Ironically, my dissertation was done, in part, 
on this very topic. We've got a whole army of techniques for handling it and 
have put in several hundred hours of user testing on it. 

  So, yaa, in short, I couldn't agree more, virtually anything related to 
scoping is a real pain in audio. In our current version of the tool, we get 
pretty good results with helping folks identify things related to scope, but I 
think there's some improvements that can be made to our design as well. 

  Anyway, good point,

  Stefik


  On Mon, Aug 31, 2009 at 4:35 PM, Vladyslav Kutsenko <kutsenko@xxxxxxxxx> 
wrote:

    Hello Andreas,

    Andreas Stefik schrieb:

      I've got an overwhelming number of ideas about what could help, but I 
can't implement them all and would like to get some feedback from the 
community. Specifically, we're looking for some ideas in two main areas, code 
completion and auditory navigation.


      2. Auditory navigation --- I have a graduate student currently working on 
a blind code navigation system. Right now, the system allows you to jump around 
the source window and find variable declarations, method declarations, and 
other similar things, but we want to expand the navigation to make things 
easier.


    I think it is very important to get information on the context the code is 
in. So for example, it is sometimes quite time consuming to read code which 
contains  numerous into each other embedded variable scopes. In my experience, 
maintaining of such code, often results in algorithm errors. The information 
about the level of scope recursion which could also contain additional 
information about the scope properties, e.g. "if block", "for loop ...) would 
be in my opinion of huge importance.



    Thank you for your work!

    Vladyslav


    __________
    View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

Other related posts:

  1. Home
  2. programmingblind
  3. Archive
  4. 09-2009