Displaying the output of another program
-
This needs to be removed
-
This needs to be removed
-
Not heard of that, and I cannot see what use it is. Why not just run the original in a command window to start with?
This calling program (that I have not yet found), does not necessarily need to understand graphics. And the simpler the code, the better. But this program will very much need to understand text. As a matter of fact it will really like text and it really won't like graphics. It's just funny that way. This program will be submitting a Bash shell script and displaying that script's output. Or, it might be submitting a Bourne shell script and displaying that script's output. Or, it might be submitting a Korne shell script and displaying that script's output. Or, it might be submitting a C-Shell shell script and displaying that script's output. Or, it might be submitting a Perl script and displaying that script's output. Or, it might be submitting a very fundamental Java application and displaying that program's output. Or, it might be submitting a very fundamental C executable and displaying that program's output. Or, it might be submitting a very fundamental C++ executable and displaying that program's output. I don't think that *it* even knows what it will be submitting yet. Oh, wait. *It* hasn't been identified yet. Whatever that calling program is (which is hasn't been identified yet), it MUST be command-line and text-based. The why of it isn't really important. What's important is whether or not there is an open-source C++ example of this type of program available to the general public.
-
This calling program (that I have not yet found), does not necessarily need to understand graphics. And the simpler the code, the better. But this program will very much need to understand text. As a matter of fact it will really like text and it really won't like graphics. It's just funny that way. This program will be submitting a Bash shell script and displaying that script's output. Or, it might be submitting a Bourne shell script and displaying that script's output. Or, it might be submitting a Korne shell script and displaying that script's output. Or, it might be submitting a C-Shell shell script and displaying that script's output. Or, it might be submitting a Perl script and displaying that script's output. Or, it might be submitting a very fundamental Java application and displaying that program's output. Or, it might be submitting a very fundamental C executable and displaying that program's output. Or, it might be submitting a very fundamental C++ executable and displaying that program's output. I don't think that *it* even knows what it will be submitting yet. Oh, wait. *It* hasn't been identified yet. Whatever that calling program is (which is hasn't been identified yet), it MUST be command-line and text-based. The why of it isn't really important. What's important is whether or not there is an open-source C++ example of this type of program available to the general public.