class Clipboard;
class FontLoader;
-class Gui;
-class LyXView;
class Selection;
/// The main application class
Application (this is the frontend really, should probably be renamed).
|
- LyXView-1 (one or more in case of split-view mode).
+ GuiView-1 (one or more in case of split-view mode).
| |
| <tab-widget-1-1>
| | |
| |
| <tab-widget-1-2>
|
- LyXView-2 (one or more in case of split-view mode).
+ GuiView-2 (one or more in case of split-view mode).
| |
| <tab-widget-2-1>
| | |
- etc.
- 4) The Window: \c LyXView (and its qt4 specialisation \c GuiView)
+ 4) The Window: \c GuiView
This is a full window containing a menubar, toolbars and a central
- widget. A LyXView is in charge of creating and closing a View for a
+ widget. A GuiView is in charge of creating and closing a View for a
given Buffer.
In the qt4 specialisation, \c GuiView, the central widget is a tab
widget. Each tab is reverved to the visualisation of one Buffer and
- contains one WorkArea. In the qt4 frontend, one LyXView thus contains
+ contains one WorkArea. In the qt4 frontend, one GuiView thus contains
multiple WorkAreas but this number can limited to one for another
frontend. The idea is that the kernel should not know how a Buffer
is displayed on screen; it's the frontend business.
Application() {}
///
virtual ~Application() {}
- ///
- virtual LyXView * currentWindow() = 0;
/// LyX dispatcher: executes lyx actions and does necessary
/// screen updates depending on results.
///
virtual FuncStatus getStatus(FuncRequest const & cmd) const = 0;
- ///
- virtual void resetGui() = 0;
-
/// Load files and restore GUI Session.
virtual void restoreGuiSession() = 0;
- ///
- virtual void hideDialogs(std::string const & name, Inset * inset) const = 0;
///
virtual Buffer const * updateInset(Inset const * inset) const = 0;