]>
A viewset describes which views should be placed where in the window.
Which viewset is used for an equation is defined by the two options
viewset
and defaultViewset
. If viewset is
not set at all or is set to auto
, then the option
defaultViewset
is used to find out which viewset should
be used. Because options can also be set locally to an equaiton, it is
possible to choose a certain viewset for only one equaiton. You can
either set these options directly, or use the
dedicated
command for choosing viewsets from the editMode.
A viewset is described using XML. Currently, the viewset
descriptions are only to be found in editor.xul
itself.
While Gemse is running, there is a userfriendly way to edit viewsets. Changes made like this are however lost when Gemse is closed.
The edit mode provides a command to open the configuraiton window. You can keep it open during your Gemse session. It allows you to remove and add views to a viewset. In order to place the views, you can also insert XUL box elements. Attributes of all elements and options of views can be set as well.
First of all, note that every change you make takes effect immediately. Keep in mind that the changes also take effect for all other equations using the same viewset. If you don't want that, you first have to save the viewset under anoter name and then make the changes.
On the top of the configuration window you see an input box which allows you to change the name of the viewset and one which allows you to change its description. Below, you see a preview of the viewset using boxes. Every box represents an element of the viewset description. You can click on a box to select it. Below the preview you have a list of all attributes and options of the currently selected element of the viewset. Open the context menu on this list if you want delete or add an entry. Below the list, you find buttons which allow you to insert a view, a box before, after or into the selected element or remove the selected element. At the bottom you can save a copy of the current viewset under a new name, load another viewset. The last button at the very bottom allows you to use this viewset for all equations (except for the ones that are locally configured to use a certain viewset).
Just shows the equation using Mozilla's rendering engine. This works excellent for Presentation MathML. However, Mozilla's rendering engine does not show Content MathML and OpenMath.
Shows errors, warnings and other messages
Uses nested boxes to depict the tree structore of the equation's XML code.
Shows the XML source code of the current equation. The cursor is shown here as well. The appearance can be configured in various ways. (Note, not a real serializer is used, therefore the output of this view might not be usable as XML document directly.)
Options:
SourceView.foldingDepth
-1
causes
the source view to show all elements from the starting point to
the leaves.SourceView.foldingStart
0
, the source view starts at the
element under the cursor. That is, it only shows this element and
its descendants (how deep is defined by
SourceView.foldingDepth
).
If set to -n
, it starts at the n-th
ancestor of the element under the cursor. If set to
1
, the view starts at the root element of the
equation.SourceView.foldingKeepIndentation
SourceView.indentation
SourceView.showAttributes
SourceView.syntaxHighlighting
gemse.css
.A more advanced version of the DirectView. It also shows Content MathML in a non-rendered form.
Shows the attributes of the current element.
Shows information from the opterator dictionary for a MathML
mo
element.
Shows a list of the other loaded equations.
Shows a status bar indicating the current mode and other things.
If you work with Content MathML, this view renders your formula as
Presentation MathML in real time. It is part of the viewset
content
. It uses
JOMDoc, which is written in Java. Because of this, you have to
make some preparations. When you are ready,
you can start Gemse and switch to viewset content
by entering
:viewset content&enter;.
By default, only the notation definitions bundled with JOMDoc are used. However, notation sources can be configured manually. If the formula originates from an OMDoc document, notations can be collected from there as well as from its imports.
It is also possible to render another equation loaded in Gemse and use the current equation as notation source. Like this it is possible to edit a notation definition and see the effect on an equation immediately.
The following options can be set to customize the behaviour:
NTNView.notations
B
. Notations from notation sources that turn up
sooner in the list have higher priority.
B
without any arguments denotes the notations
bundled with JOMDoc.C
without any arguments causes content
dictionaries to be searched for notations. That is, if a symbol with
cdbase http://example.com/somedir
, cd foo
and name
bar
, the document
http://example.com/somedir/foo
is fetched and searched
for notation definitions for foo
and for references to
such notation definitions. (This might not yet work as you expect it.
There is a problem with the default cdbase.)F
loads from the URL given as argument.D
looks in the document at the given URL for
notation definition and also searches all its imports. If the URL is
omitted, the value of the option NTNView.theoryName
is
used.I
is useful when you load the equation from an
OMDoc document. In this case, the options
NTNView.documentURI
and NTNView.theoryName
are set automatically to the right value should they not already have
been set. (Note that this is at the moment the same as D
with NTNView.documentURI
set to the URL for the document
the formula is part of and NTNView.theoryName
set to the
name of the innermost theory the formula is located in.E
uses an equation currently loaded in Gemse as
a notation definition. The argument is the number of the equation. If
the argument is missing, the current equation is used.NTNView.documentURI
NTNView.theoryName
NTNView.equation
Only file and http URLs are supported for notation sources. Contexts and tags are not yet supported.