On Thursday 05 June 2003 04:04 am, Mike Hearn wrote:
> > We have that, this is what MESSAGE is meant to do.
>
> OK, cool, I guess routing that into a GUI should be on somebodies mental
> if not marked up todo list.
just another note (hmm, by speaking on this, I fear I am getting dangerously
close
On June 5, 2003 01:40 am, Gregory M. Turner wrote:
> Really... I didn't know that. Then, should we slap a gui into this as
> discussed previously?
Sure... We just need a volunteer to do it! :)
--
Dimi.
On Wednesday 04 June 2003 09:59 pm, Dimitrie O. Paun wrote:
> On June 4, 2003 05:16 am, Mike Hearn wrote:
> > I would also propose a new class of logging message, or logging macro,
> > USERMSG, which is *only* to be used for things that directly help or
> > inform the user, as opposed to developers
Mike Hearn writes:
> Basically I think the Wine output should be hidden by default as it's
> essentially meaningless to anybody but developers (and often, anybody
> but wine developers).
PMFJI, I'm basically a Wine newbie as of 11/01/02 and a Linux newbie as of a
year before that, but it was pre
On June 4, 2003 05:16 am, Mike Hearn wrote:
> I would also propose a new class of logging message, or logging macro,
> USERMSG, which is *only* to be used for things that directly help or
> inform the user, as opposed to developers.
We have that, this is what MESSAGE is meant to do.
--
Dimi.
