Re: Putting A GUI Onto A Command Line Program With AutoIt3
- From: Tyler Littlefield <tyler@xxxxxxxxxxxxx>
- To: programmingblind@xxxxxxxxxxxxx
- Date: Mon, 30 Nov 2009 11:00:45 -0700
Hello james,
AutoIt sounds fine. what you'll have to do is retrieve the handles and write to
the stin and read from the program's stdout. You can send more than one command
through stdin, and that would be the same as typing it at a console.
HTH,
On Nov 30, 2009, at 10:50 AM, Homme, James wrote:
> Hi Tyler,
> Thanks for saying this. Now I’m remembering that languages like Perl can run
> another program and read their output that normally would go to the screen.
> To interpret what you say, then, it sounds like I’d want to find a similar
> function in AutoIt.
>
> If I’m right, my next question is that if the program is still running, would
> I need to figure out a way to send it more commands? If so, how would my
> program find where to send them? Is it possible to do that without displaying
> the input to the screen?
>
> Let me explain what I’m up to here. I found a chess playing engine called
> Crafty, which is one of the best free chess engines, as far as I have read.
> Anyway, I’d like to see if I can make an accessible GUI and use that to
> control the chess engine. I know about Winboard for JAWS. I’m not a C
> programmer at all, and I thought that maybe I could make a GUI using AutoIt3.
> If this isn’t the best way to go, I’d entertain doing it in some other
> language, but I had to pick something, so I picked AutoIt.
>
> Thanks.
>
> Jim
>
> Highmark recipients, Read my accessibility blog
>
> "If a green on green tree falls in the forest and you're there, can you see
> it?"
> "Not unless you have a screen reader." :)
>
> From: programmingblind-bounce@xxxxxxxxxxxxx
> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Tyler Littlefield
> Sent: Monday, November 30, 2009 11:40 AM
> To: programmingblind@xxxxxxxxxxxxx
> Subject: Re: Putting A GUI Onto A Command Line Program With AutoIt3
>
> hello jim,
> What you'll have to do is capture the stdin and stdout handles, and possibly
> stderr to monitor for input and allow for writing to the program.
> HTH,
>
> On Nov 30, 2009, at 9:05 AM, Homme, James wrote:
>
>
> Hi,
> I don't understand how this kind of thing works in the first place, so I'm
> not sure what to ask. I'll just start at the beginning.
>
> When any program runs another one in Windows, and it wants to see its output,
> where does it look?
>
> Thanks.
>
> Jim
>
> Highmark recipients, Read my accessibility blog
>
> "If a green on green tree falls in the forest and you're there, can you see
> it?"
> "Not unless you have a screen reader." :)
>
>
> This e-mail and any attachments to it are confidential and are intended
> solely for use of the individual or entity to whom they are addressed. If you
> have received this e-mail in error, please notify the sender immediately and
> then delete it. If you are not the intended recipient, you must not keep,
> use, disclose, copy or distribute this e-mail without the author's prior
> permission. The views expressed in this e-mail message do not necessarily
> represent the views of Highmark Inc., its subsidiaries, or affiliates.
>
Other related posts:
