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 alllows the xforms-style commingling
>
> Does anybody have any comments / objections ? Jug ? Asger ?
I don't understand really what problems you have with this?
Why do you need two different objects? Isn't it possible to
do this internal to the Minibuffer-Object? Why should the core
care to change between a StatusBar and a Minibuffer. What real
problem do you have to make this internal to the object?
You just have to define a Input object and a display object and
change between them when needed. That shouldn't be that big of
a problem (just show/hide calls to the objects which have the same
size/position). IMO that for the core it should be just one object
to not complicate the stuff to much and for the frontend it should
be really easy to implement this as such. But obviously you are
the qt expert (I only made such small projects as
<publicity>
KSendFax, KGoodStuff
</publicity>
which I recently ported to qt3 ;)
Jug
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED]
Mitterstrich 151/A Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39050 Steinegg Web: http://www.lyx.org/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
