path: root/doc/mdk_gmixvm.texi

@node gmixvm, mixasm, mixvm, Top
@comment  node-name,  next,  previous,  up
@chapter gmixvm
@cindex @code{gmixvm}
@cindex GUI
@cindex GTK+

@menu
* Invoking @code{gmixvm}::      Invoking the GTK+ interface.
* MIXVM console::               Using @code{mixvm} commands.
* MIX virtual machine::         The MIX virtual machine window.
* MIXAL source view::           Viewing the MIXAL source code.
* MIX devices view::            Device output.
* Menu and status bars::        Available menu commands.
@end menu

@node Invoking @code{gmixvm}, MIXVM console, gmixvm, gmixvm
@comment  node-name,  next,  previous,  up
@section Invoking @code{gmixvm}

If you have built @sc{mdk} with GTK+ support (@pxref{Installing MDK}), a
graphical front-end for the MIX virtual machine will be available in
your system. You can invoke it by typing

@example
gmixvm @kbd{RET}
@end example

@noindent
at your command prompt. The @code{gmixvm} main window will appear,
offering you a graphical interface to run and debug your MIX programs.

@image{img/ss_mix}

Apart from the menu and status bars, we can distinguish two zones (or
halves) in this main window. In the upper half of @code{gmixvm}'s main
window there is a notebook with three pages, namely,

@itemize
@item
a MIX virtual machine view, which shows you the registers, flags, memory
contents and time statistics of the virtual machine;
@item
a MIXAL source view, which shows the MIXAL file and lets you manage
breakpoints;
@item
a Devices view, which shows you the output to character based MIX block
devices.
@end itemize

@noindent
On the other hand, the main window's lower half presents you a
@code{mixvm} command prompt and a logging area where results of the
issued commands are presented. These widgets implement a @code{mixvm}
console which offers almost the same functionality as its @acronym{CLI}
counterpart. 

When @code{gmixvm} is run, it creates a directory named @file{.gmixvm}
in your home directory (if it does not already exist). The
@file{.gmixvm} directory contains the program settings and the device
files used by your MIX programs (@pxref{Devices}).

The following sections describe the above mentioned components of
@code{gmixvm}. 

@node MIXVM console, MIX virtual machine, Invoking @code{gmixvm}, gmixvm
@comment  node-name,  next,  previous,  up
@section MIXVM console

In the lower half of the @code{gmixvm} main window, you will find a
command text entry and, above it, an echo area. These widgets offer you
the same functionality as its @acronym{CLI} counterpart, @code{mixvm}
(@pxref{mixvm}). You can issue almost all @code{mixmv} commands at the
@code{gmixvm}'s command prompt in order to manipulate the MIX virtual
machine. Please, refer to @xref{mixvm}, for a description of these
commands, and to @xref{Getting started}, for a tutorial on using the MIX
virtual machine. The command prompt offers command line completion for
partially typed commands using the @kbd{RET} key; e.g., if you type

@example
lo @kbd{RET}
@end example
@noindent
the command is automatically completed to @code{load}. If multiple
completions are available, they will be shown in the echo area. Thus,
typing

@example
p @kbd{RET}
@end example
@noindent
will produce the following output on the echo area:

@example
Completions:
pc     psym     preg     pflags     pall     
pmem  
@end example
@noindent
which lists all the available commands starting with @code{p}.

You can change the font used to display the issued commands and the
messages in the echo area using the @w{Settings->Change font->Command
prompt} and @w{Settings->Change font->Command log} menu commands.

@node MIX virtual machine, MIXAL source view, MIXVM console, gmixvm
@comment  node-name,  next,  previous,  up
@section MIX virtual machine

The first notebook's page displays the current status of the virtual
machine. There you can find the registers' contents, the value of the
comparison and overflow flags, the location pointer, a list with all MIX
memory cells and their contents, and the time statistics (including
total uptime, elapsed time since the last run command and total
execution time for the currently loaded MIX program).

Clicking any register entry, you will be prompted for a new register's
contents.

@ifnotinfo
The next figure shows the enter word dialog.
@image{img/ss_worddlg, 400pt}
@end ifnotinfo

In the same manner, click on any address of the memory cells list to be
prompted for the new contents of the clicked cell. If you click the
address column's title, a dialog asking you for a memory address will
appear; if you introduce a valid address, this will be the first cell
displayed in the scrollable list after you click the OK button.

@ifnotinfo
The next figure shows the enter address dialog.
@image{img/ss_goto}
@end ifnotinfo


The register contents are shown as a list of MIX bytes plus sign. If you
place the mouse pointer over any of them, the decimal value of this MIX
word will appear inside a tooltip.

You can change the font used to display the MIX virtual machine contents
using the @w{Settings->Change font->MIX} menu command.

@node MIXAL source view, MIX devices view, MIX virtual machine, gmixvm
@comment  node-name,  next,  previous,  up
@section MIXAL source view

The second notebook's page, dubbed MIXAL, shows you the MIXAL source of
the currently loaded MIX file. As shown in the next figure, the
information is presented in two columns.

@image{img/ss_mixal, 400pt}

The first column shows the address and memory contents of the compiled
MIX instruction, while the second one displays its corresponding MIXAL
representation, together with the source file line number. The current
location of the location counter is highlighted in grey, while any set
breakpoint is marked in red. You can set/unset breakpoints by clicking
on any line in this view which has an associated memory address.

The colors used to mark the location pointer line and the breakpoints
can be customized with the @w{Settings->Colors...} menu command. When you
click on this menu item, a dialog showing the current line colors will
appear. 

@ifnotinfo
The following figure shows the change color dialog.
@image{img/ss_colors}
@end ifnotinfo

Clicking on any of the colors will produce a color selection dialog for
choosing a new color for the given element. In this way, you can change
the foreground and background colors used for drawing the current line,
the lines where breakpoints have been set and plain MIXAL code lines.

You can change the font used to display the MIXAL source code
using the @w{Settings->Change font->MIXAL} menu command.


@node MIX devices view, Menu and status bars, MIXAL source view, gmixvm
@comment  node-name,  next,  previous,  up
@section MIX devices view

The last notebook page, dubbed Devices, shows you the output/input
to/from MIX block devices (the console, line printer, paper tape,
disks, card and tapes @pxref{Devices}) produced by the running
program. 

@ifnotinfo
@image{img/ss_devices, 400pt}
@end ifnotinfo

Input device contents is read from files located in the
@file{~/.gmivm} directory, and the output is also written in files
at the same location. Note that device tabs will appear as they are used
by the program being run, and that loading a new MIX program will close
all previously open devices.

You can change the font used to display the devices content
using the @w{Settings->Change font->Devices} menu command.

@node Menu and status bars,  , MIX devices view, gmixvm
@comment  node-name,  next,  previous,  up
@section Menu and status bars

The menu bar gives you access to the following commands:

@deffn File Load...
Opens a file dialog that lets you specify a binary MIX file to be loaded
in the virtual machine's memory. It is equivalent to the @code{mixvm}'s
@code{load} command (@pxref{File commands}).
@end deffn

@deffn File Exit
Exits the application.
@end deffn

@deffn Debug Run
Runs the currently loaded MIX program, up to the next breakpoint. It is
equivalent to the @code{mixvm}'s @code{run} command (@pxref{Debug
commands}). 
@end deffn

@deffn Debug Next
Executes the next MIX instruction. It is equivalent to the
@code{mixvm}'s @code{next} command (@pxref{Debug commands}).
@end deffn

@deffn Debug Clear breakpoints
Clears all currently set breakpoints. It is equivalent to the
@code{mixvm}'s @code{cabp} command.
@end deffn

@deffn Settings Colors...
Lets you change the colors used to mark the current and breakpoint lines
in the MIXAL tab, as well as the colors used for plain source lines.
@end deffn

@deffn Settings Change font
Lets you change the font used in the various @code{gmixv} widgets
(i.e. commad prompt, command log, MIX, MIXAL and devices).
@end deffn

@deffn Settings Save
Saves the current settings (colors and fonts).
@end deffn

@deffn Settins Save on exit
Mark this checkbox if you want @code{gmixvm} to save its settings
(colors and fonts) every time you quit the program.
@end deffn

@deffn Help About...
Shows information about @code{gmixvm}'s version and copyright.
@end deffn

On the other hand, the status bar displays the name of the last loaded
MIX file.