Remotely controlling Winboard.

[Matthew Molineaux]

Geschrieben von:/Posted by: Matthew Molineaux at 15. June 2004 22:44:

I'm attempting to interface a scientific testbed to WinBoard; I would like this program to be able to start, and then communicate with the program. I see how Winboard can start my program if I provide it with a command line; however, I would prefer that my program call it in similar fashion. After I start up WinBoard, however, is there any way to connect to its communication streams? Thanks for your help.
- Matt

[Richard Pijl]

Geschrieben von:/Posted by: Richard Pijl at 16 June 2004 09:35:04:
Als Antwort auf:/In reply to: Remotely controlling Winboard. geschrieben von:/posted by: Matthew Molineaux at 15. June 2004 22:44:

I'm attempting to interface a scientific testbed to WinBoard; I would like this program to be able to start, and then communicate with the program. I see how Winboard can start my program if I provide it with a command line; however, I would prefer that my program call it in similar fashion. After I start up WinBoard, however, is there any way to connect to its communication streams? Thanks for your help.
- Matt

I'm not sure what you want to accomplish. Could you elaborate?
The obvious thing that comes to my mind is to create proxy engine that will connect to your application. So:
1.Your application starts winboard
2.Winboard starts the proxy engine
3.The proxy engine contacts your application over a socket and relays winboard command/responses to your application.
I don't know whether that answers your question ..
Richard.

[Matthew Molineaux]

Geschrieben von:/Posted by: Matthew Molineaux at 16. June 2004 15:53:
Als Antwort auf:/In reply to: Re: Remotely controlling Winboard. geschrieben von:/posted by: Richard Pijl at 16 June 2004 09:35:04:

I'm not sure what you want to accomplish. Could you elaborate?
The obvious thing that comes to my mind is to create proxy engine that will connect to your application. So:
1.Your application starts winboard
2.Winboard starts the proxy engine
3.The proxy engine contacts your application over a socket and relays winboard command/responses to your application.
I don't know whether that answers your question ..
Richard.

The basic idea is that the program I am writing will perform an experiment defined by the user, which may involve starting at various states, running the program multiple times, and configuring execution. Winboard is one of several programs I intend to attempt to interface to this application, and more may be interfaced in the future. I hope this makes my aims clearer.
In order to do this, my system needs control over stopping and starting the test environment (i.e. Winboard) as well as to communicate with it.
This solution would work, but I was hoping not to incur the additional overhead of a second interface. I was hoping there might be some way to start WinBoard which created pipes to a running application. This may, however, be unrealistic.
-Matt

[Volker Annuss]

Geschrieben von:/Posted by: Volker Annuss at 16 June 2004 19:53:18:
Als Antwort auf:/In reply to: Re: Remotely controlling Winboard. geschrieben von:/posted by: Matthew Molineaux at 16. June 2004 15:53:

This solution would work, but I was hoping not to incur the additional overhead of a second interface. I was hoping there might be some way to start WinBoard which created pipes to a running application. This may, however, be unrealistic.

Winboard is open source, so you can see how winboard starts engines and creates pipes. You may even modify winboard to satisfy your needs.
Greetings,
Volker

[Josephia Carolinendo]

Geschrieben von:/Posted by: Josephia Carolinendo at 16. June 2004 21:48:
Als Antwort auf:/In reply to: Re: Remotely controlling Winboard. geschrieben von:/posted by: Matthew Molineaux at 16. June 2004 15:53:

I'm not sure what you want to accomplish. Could you elaborate?
The obvious thing that comes to my mind is to create proxy engine that will connect to your application. So:
1.Your application starts winboard
2.Winboard starts the proxy engine
3.The proxy engine contacts your application over a socket and relays winboard command/responses to your application.
I don't know whether that answers your question ..
Richard.

The basic idea is that the program I am writing will perform an experiment defined by the user, which may involve starting at various states, running the program multiple times, and configuring execution. Winboard is one of several programs I intend to attempt to interface to this application, and more may be interfaced in the future. I hope this makes my aims clearer.
In order to do this, my system needs control over stopping and starting the test environment (i.e. Winboard) as well as to communicate with it.
This solution would work, but I was hoping not to incur the additional overhead of a second interface. I was hoping there might be some way to start WinBoard which created pipes to a running application. This may, however, be unrealistic.
-Matt

[Matthew M]

Geschrieben von:/Posted by: Matthew M at 18. June 2004 15:07:
Als Antwort auf:/In reply to: Sente paranto en panioala du este vente mi oda vb? (en/t) geschrieben von:/posted by: Josephia Carolinendo at 16. June 2004 21:48: