Re: minibuffer design problems

2002-07-15 Thread John Levon
On Tue, Jul 16, 2002 at 04:54:11PM +1000, Allan Rae wrote: > While I agree with the separate implementation you suggest I don't > like the waste of screenspace experienced with KDE/Gnome/Mozilla > because they are afraid of having two separate widgets share the same > space -- especially when the

Re: minibuffer design problems

2002-07-15 Thread Allan Rae
On Mon, 15 Jul 2002, John Levon wrote: > On Mon, Jul 15, 2002 at 09:00:09AM +0200, Juergen Vigna wrote: > > > I don't think they are visible at once. There is or the message bar or > > the input buffer visible (well they have the same design so you won't > > notice. But they use the same space. D

Re: minibuffer design problems

2002-07-15 Thread John Levon
On Mon, Jul 15, 2002 at 09:00:09AM +0200, Juergen Vigna wrote: > I don't think they are visible at once. There is or the message bar or > the input buffer visible (well they have the same design so you won't > notice. But they use the same space. Do you say you want to make that > part higher and

Re: minibuffer design problems

2002-07-14 Thread Juergen Vigna
John Levon wrote: > I don't think you understand: they are two entirely separate UI objects, > both visible at once. I don't think they are visible at once. There is or the message bar or the input buffer visible (well they have the same design so you won't notice. But they use the same space. Do

Re: minibuffer design problems

2002-07-12 Thread John Levon
On Fri, Jul 12, 2002 at 09:28:56AM +0200, Juergen Vigna wrote: > I don't understand really what problems you have with this? > Why do you need two different objects? Mainly because commingling (oooh yeah) two different purposes into the one buffer is really bad UI > Isn't it possible to > do th

Re: minibuffer design problems

2002-07-12 Thread Juergen Vigna
John Levon wrote: > I guess we also need something to get the "information" string > (I assume this is the keyboard shortcut list string ?) > > It's quite wrong IMHO for the core code to push /anything/ to the > MiniBuffer: it should only push to the StatusBar > > Note such a scheme still alllo

minibuffer design problems

2002-07-11 Thread John Levon
There are two main problems: the commingling (I love that word) of a status bar with a command buffer, and the push/pull mixup thereof. For xforms, fine, but for Qt there must be a separation. I propose : a StatusBar instance with one method show_message(string const & msg, int timeout