On Fri, 5 May 2017, at 15:00, David Matthews wrote:
On 03/05/2017 09:23, Chris Cannam wrote:
(I'd love to see a console-only build as an alternative .exe in the official Windows distributions.)
That's certainly possible. Why exactly are you using a console application? My feeling has always been that Windows users expect a Windows-style GUI.
Maybe because I'm not a very authentic Windows user. I usually use Linux and I like to do things from a command line, so I like tools that work similarly when invoked within Powershell or cmd.exe to how they work on other platforms.
(But I don't really like to use cygwin or other Unix tools on Windows -- partly because I'm used to having to build systems that can be used by people who don't have them installed, and partly because I find it all a bit uncanny-valley. Besides, I rather like Powershell.)
Earlier you said that the existing Windows distribution should be usable without GUI if the I/O streams are redirected. If I try something like this:
echo 'print "hello, world\n";' | & 'C:\Program Files\Poly ML\PolyML.exe'
the GUI window appears for a moment then disappears, and no output goes to the Powershell window. If I do this instead:
echo 'print "hello, world\n";' | & 'C:\Program Files\Poly ML\
PolyML.exe' > output.txt
then the GUI window doesn't appear, but output.txt is empty. Is this expected?
(With the console build I made following your guidance in this thread, these print to console and output file respectively.)
Chris