26385f2866
the terminology a bit. In particular, the term "gui" has started
to mean different things in different contexts, so I've defined
some more specific names for the parts of the user interface, and
updated comments and some variable names to reflect it. See
siminterface.h for a more complete description of all of these.
VGAW: VGA display window and toolbar buttons, the traditional Bochs
display which is ported to X, win32, MacOS X, etc. Implemented
in gui/gui.* and platform dependent gui/*.cc files.
CI: configuration interface that lets the user change settings such
as floppy disk image, ne2k settings, log options. The CI consists
of two parts: configuration user interface (CUI) which does the
actual rendering to the screen and handles key/mouse/menu events,
and the siminterface object.
CUI: configuration user interface. This handles the user interactions
that allow the user to configure Bochs. To actually change any
values it talks to the siminterface object. One implementation of
the CUI is the text-mode menus in gui/control.cc. Another
implementation is (will be) the wxWindows menus and dialogs in
gui/wxmain.cc.
siminterface: the glue between the CUI and the simulation code,
accessible throughout the code by the global variable
bx_simulator_interface_c *SIM;
Among other things, siminterface methods allow the simulator to ask the
CUI to display things or ask for user input, and allows the CUI
to query and modify variables in the simulation code.
GUI: Literally, "graphical user interface". Until the configuration menus
and wxWindows came along, everyone understood that "gui" referred to the
VGA display window and the toolbar buttons because that's all there
was. Now that we have the wxWindows code, which implements both the VGAW
and the CUI, while all other platforms implement only the VGAW, it's not
so clear. So, I'm trying to use VGAW, CI, and CUI consistently since
they are more specific.
control panel: This has been used as another name for the configuration
interface. "control panel" is also somewhat unspecific and it sounds
like it would be graphical with buttons and sliders, but our text-mode
thing is not graphical at all. I've replaced "control panel" with
"configuration interface" wherever I could find it. In configure script,
the --disable-control-panel option is still supported, but it politely
suggests that you use --disable-config-interface instead.
- clean up comments in siminterface,wx* code
- add comments and examples for bx_param_* and BxEvents
- remove some obsolete stuff: notify_*_args,
bx_simulator_interface_c::[sg]et_enabled() methods
- in siminterface.cc, move a few bx_real_sim_c methods to where they belong,
with the rest of the methods. No changes to the actual methods.
- remove some DOS ^M's which crept in and confused my editor.
22 lines
566 B
C
22 lines
566 B
C
/////////////////////////////////////////////////////////////////////////
|
|
// $Id: control.h,v 1.7 2002-08-26 15:31:20 bdenney Exp $
|
|
/////////////////////////////////////////////////////////////////////////
|
|
//
|
|
enum {
|
|
BX_CI_INIT,
|
|
BX_CI_START_MENU,
|
|
BX_CI_START_OPTS,
|
|
BX_CI_START_OPTS_MEM,
|
|
BX_CI_START_OPTS_INTERFACE,
|
|
BX_CI_START_OPTS_DISK,
|
|
BX_CI_START_OPTS_SOUND,
|
|
BX_CI_START_OPTS_MISC,
|
|
BX_CI_RUNTIME,
|
|
BX_CI_N_MENUS
|
|
};
|
|
|
|
/* special return value from bx_config_interface */
|
|
#define BX_DISABLE_CONFIG_INTERFACE 10
|
|
|
|
int bx_config_interface (int menu);
|