Re: [Zero-install-devel] Console output on Windows

[Thomas L. <ta...@gm...>]

On 9 February 2010 21:28, Bastian Eicher <ba...@ei...> wrote:
> A short summary of the Windows console application dilemma:
>
> Basically, Windows has two different types of applications:
>
> Console applications:
> These apps have the default streams (stdin, stdout, stderr). These streams
> can be redirected but no matter what you do with them, Windows always forces
> you to have a Terminal window to go with the app, even if it is unused.
> Console applications can display GUI windows in addition to using the
> standard streams.
> python.exe is an example for such an application.
>
> GUI applications:
> These apps have no default streams. They can never output to the console and
> therefore don't come with a forced Terminal window. They can only display
> GUI windows.
> pythonw.exe is an example for such an application.
>
> In my opinion this separation really sucks, especially since it can't be
> decided at runtime which of the two your app will be. Can't change anything
> about it though.
>
> I hope this clears up why I've been talking about this separation of
> 0launch.exe and 0launchw.exe.

So, to be clear, if I mark 0launch as a GUI application that doesn't
need a terminal, and I explicitly open a terminal window myself and
run "0launch --console" then what happens?

I'd expect its output to come to the existing terminal window. Are you
saying that Windows would explicitly close its streams in this case?


-- 
Dr Thomas Leonard		ROX desktop / Zero Install
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA