Re: Wine isn't GUI user friendly

2004-07-31 Thread Mike Hearn
On Fri, 30 Jul 2004 16:39:36 -0400, Scott W Gifford wrote: > isatty(STDOUT_FILENO) is probably pretty close to the right way to do > this. > Thanks but I suspect we'd need to use the Windows API at that point in the code.

Re: Wine isn't GUI user friendly

2004-07-30 Thread Scott W Gifford
Mike Hearn <[EMAIL PROTECTED]> writes: [...] > I don't know how to tell if a console is available or not though. isatty(STDOUT_FILENO) is probably pretty close to the right way to do this. -ScottG.

Re: Wine isn't GUI user friendly

2004-07-26 Thread Vincent Béron
Le lun 26/07/2004 à 10:56, Mike Hearn a écrit : > On Mon, 26 Jul 2004 15:44:02 +0200, Fabian Cenedese wrote: > > Well, the parsing was just an idea. The main intent for the GUI-app > > was that the user could at least see something as opposed to the > > messages vanishing on the non-existent consol

Re: Wine isn't GUI user friendly

2004-07-26 Thread Vitaly Lipatov
On Monday 26 July 2004 13:04, Fabian Cenedese wrote: > What about a simple GUI-application which would call wine and > capture (and maybe parse?) the output? This would be called if If it is fatal error we can use error code returned by wine process. -- Lav Vitaly Lipatov Saint-Petersburg GNU! A

Re: Wine isn't GUI user friendly

2004-07-26 Thread Mike Hearn
On Mon, 26 Jul 2004 15:44:02 +0200, Fabian Cenedese wrote: > Well, the parsing was just an idea. The main intent for the GUI-app > was that the user could at least see something as opposed to the > messages vanishing on the non-existent console or the ever popping > up error dialogs. I guess GUI d

Re: Wine isn't GUI user friendly

2004-07-26 Thread Fabian Cenedese
At 13:31 26.07.2004 +0100, Mike Hearn wrote: >On Mon, 26 Jul 2004 11:04:38 +0200, Fabian Cenedese wrote: >> What about a simple GUI-application which would call wine and capture >> (and maybe parse?) the output? This would be called if a program is >> started with a shortcut (no console). For the c

Re: Wine isn't GUI user friendly

2004-07-26 Thread Mike Hearn
On Mon, 26 Jul 2004 11:04:38 +0200, Fabian Cenedese wrote: > What about a simple GUI-application which would call wine and capture > (and maybe parse?) the output? This would be called if a program is > started with a shortcut (no console). For the console you can still use > the normal wine. Like

Re: Wine isn't GUI user friendly

2004-07-26 Thread Fabian Cenedese
>> Also, maybe we need a new debug level for that (above ERR and FIXME), >> which is "Human readable messages". The message as it is is perfectly >> understandable to programmers, but not to users. Even if it was, these >> messages are usually surrounded by hundred of messages that the user >>

Re: Wine isn't GUI user friendly

2004-07-25 Thread Shachar Shemesh
Mike Hearn wrote: Christian Neumair <[EMAIL PROTECTED]> writes: That reminds me of asking for nicer, GUI-driven error handling: touch mustardandwiener.exe && wine mustardandwiener.exe returns wine: cannot determine executable type for L"H:\\Desktop\\test.exe" which is neither verbose enough nor

Re: Wine isn't GUI user friendly

2004-07-25 Thread Mike Hearn
On Sun, 2004-07-25 at 19:02 +0300, Shachar Shemesh wrote: > Also, maybe we need a new debug level for that (above ERR and FIXME), > which is "Human readable messages". The message as it is is perfectly > understandable to programmers, but not to users. Even if it was, these > messages are usuall

Re: Wine isn't GUI user friendly

2004-07-25 Thread Mike Hearn
Christian Neumair <[EMAIL PROTECTED]> writes: > That reminds me of asking for nicer, GUI-driven error handling: > touch mustardandwiener.exe && > wine mustardandwiener.exe > returns > wine: cannot determine executable type for L"H:\\Desktop\\test.exe" > which is neither verbose enough nor user fri