RE: code window

I'll even go a little further than that.  For everything to work
properly using the G.U.I. every blind person using a computer ought to
be a master mouse clicker too.  Yet one screen reader doesn't even track
the real mouse so that's not possible.  From a time management
perspective though the mouse issue and unnecessary use of G.U.I. both
have adverse time impacts.  The time impacts for the mouse use are
already well documented in time and motion studies done by production
operations management types and are available on the internet.  The hit
on time usage for the G.U.I. can be anecdotally described in the amount
of time given over to getting productive with the G.U.I. interface used
by blind people as opposed to use by their sighted counterparts.  Issues
we run into and deal with that are unique to our population and the time
costs of each should provide some pretty good clues.
 


Rot47: <;F56]52D9:6==@?2GJ]>:=>
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of DaShiell,
Jude T. CIV NAVAIR 1490, 1, 26
Sent: Monday, October 26, 2009 11:47
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: code window
Importance: Low

The G.U.I. was designed for the sighted culture, not the rest of the
population.  Those who choose to use a G.U.I. at all costs are the same
kind of people who enjoy repeatedly walking into airplane propellers
spinning at take off speed.  For myself, that kind of pain even once
just doesn't turn me on.
 


Rot47: <;F56]52D9:6==@?2GJ]>:=>
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Bryan Schulz
Sent: Monday, October 26, 2009 11:32
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: code window

come on,
what's the point of trying to produce apps like anyone else if you are 
afraid of the gui / what employer will say that's ok johnny you don't
have 
to deal with the ide problems.

Bryan Schulz

----- Original Message ----- 
From: "DaShiell, Jude T. CIV NAVAIR 1490, 1, 26"
<jude.dashiell@xxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Monday, October 26, 2009 10:14 AM
Subject: Re: code window


Actually, in the visual studio 2008 tools folder, there's a visual basic
command prompt if I'm not much mistaken.  It can be used to build any
valid visualbasic code.  You need to be in the directory with your
source files and run vbc source.vb >source.err <cr> at that prompt and
what then happens is you may or may not get a good compile, but you will
get a source.err file which you can then view with more < source.err
again at the visual studio command prompt.  Doing it this way makes the
code window superfluous.


Rot47: <;F56]52D9:6==@?2GJ]>:=>
__________
View the list's information and change your settings at
http://www.freelists.org/list/programmingblind

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

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

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

Other related posts: