[fpc-pascal] Lazarus: graphical interface using code only?

[Ryan Mann]

Hello.  To answer your question about screen readers, basically, a  
screen reader reads in synthesized speech what a sighted person would  
read on their monitor.  The way it works is that the program gets  
information from the operating system about what is on the screen.   
This means that on Windows, applications that use common Windows  
controls usually work well with screen readers.  If an application  
doesn't use the common Windows controls, it probably won't work  
because the screen reader can't get the information that it needs from  
the operating system.  On Mac OS 10, graphical applications need to  
use the Coco interface in order for Voiceover, Mac OS 10's built-in  
screen reader to work properly with the application.
I hope this is a good explanation.
On Dec 4, 2008, at 2:20 AM, Graeme Geldenhuys wrote:

> On Thu, Dec 4, 2008 at 8:35 AM, Ryan Mann <ryan_mann at mac.com> wrote:
>> Actually, I tried to compile FPGUI using build.bat on Windows  
>> earlier today
>> and I got an error.
>
> It should now be fixed in revision 1051. Please get a svn update and
> try again. The windows build.bat file did not try and create the lib
> output directory, if it didn't exist. The unix shell script did. The
> build.batch has one limitation, it always assumes the
> ..\lib\i386-win32\ output directory, so if you run a 64bit FPC
> compiler, you will have to manually create the ..\lib\i386-win64\
> directory before running the batch file.
>
> Anybody know how I can store the output of a program into a variable
> in windows batch files? I'm trying to capture the following output
> like I have done in the unix shell script.
>   fpctarget=`fpc -iTP`-`fpc -iTO`
>
>
>> By the way, does FPGUI use Windows API on Windows?  If it does
>> that's good because the GUIs it creates are probably accessible to  
>> screen
>> readers.
>
> If you mean, does it use the Windows common controls, then the answer
> is No. fpGUI is a custom drawn toolkit. All components are drawn by
> the toolkit itself. That is how it accomplished a uniform look & feel
> across platforms.  fpGUI's GDI backend does obviously use the Windows
> API for drawing etc, but doesn't use the common controls.
>
> I'm curious... How do you manage to create a GUI or use a GUI program
> if you are blind? Sorry, I don't know how screen readers work?
>
>
> Regards,
>  - Graeme -
>
>
> _______________________________________________
> fpGUI - a cross-platform Free Pascal GUI toolkit
> http://opensoft.homeip.net/fpgui/
> _______________________________________________
> fpc-pascal maillist  -  fpc-pascal at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Ryan Mann
ryan_mann at mac.com
Break The Matrix
http://www.breakthematrix.com