screendumps of example programs

InterViews Glyph objects provide the usual user interface widgets like buttons, scrollbars, pulldown menus, string editors, etc. (They also provide a limited graphical capability; since they don't have a general editing framework the glyph graphics are mostly useful for static pictures, e.g. a graphic inside a button.) We use glyphs to implement layout, look-and-feel, and controls/displays for application programs.

The main technical advantages of glyphs are:

The ultimate reference for glyphs is the "InterViews Reference Manual Version 3.1" (no frames) dated December 14, 1992. It is included in the InterViews source tree under iv/src/man/refman/refman.PS. Here we will provide supplementary information and more practical hints.

Some of the more important glyph classes are:

The basic glyph demo program is idemo, included in the InterViews source tree under iv/src/bin/idemo/. It features pulldown menus, text labels (normal and rotated), push buttons, check boxes, radio buttons, palette buttons, field (text) editors, scrollbars and a panner. By using the flags -openlook, -motif or -sgimotif at program startup you can see the same glyphs under each different look-and-feel discipline.

We also have a few other glyph-based derived classes and example programs in the ivtools package. These are examples of glyph usage and/or subclasses that extend the basic glyph functionality in some way. Most of these are contained in the IVGlyph library within ivtools.

Glyphs are compiled with different options and namespace than Unidraw objects. See the different rules used in the Imakefiles. This can lead to conflicts but we have developed ways of integrating glyphs with Unidraw that work in our examples.

The layout model for glyphs is based on the TeX boxes and glue model. ...

back to ivtools technical info