John Levon wrote:
> On Thu, Apr 08, 2004 at 05:25:10PM +0100, Angus Leeming wrote:
>
>> Now, personally, I think that it should be there, but leaving that
>> to one side, why don't we have a minibuffer that 'appears' when I
>> type 'M-x' and 'disappears' when I subsequently hit return? That
>> way, its behaviour is analogous to the math and table toolbars in
>> the Qt frontend, I retain the functionality I'm looking for *and* I
>> don't pay for what I don't use in terms of screen real estate.
>
> I'd planned to do this but never got round to it
Well, toolbars are already turned on and off so it should be a case
of extending what's already there rather than starting afresh.
Would the toolbar code still benefit from an MCV-split analogous to
the Dialogs code:
struct Toolbar {
struct View {};
Toolbar(View * view) : view_(view) {}
boost::scoped_ptr<View> view_;
};
struct Toolbars {
void show(string const & name);
void hide(string const & name);
private:
void build(string const & name);
map<string, Toolbar> toolbars;
};
struct QToolbarView : public Toolbar::View {};
struct FormToolbarView : public Toolbar::View {};
struct GToolbarView : public Toolbar::View {};
My guess is yes, but I've avoided the temptation to dabble until I
finished the Dialogs.
--
Angus
