[graphic-forms-cvs] r338 - trunk/docs/manual
junrue at common-lisp.net
junrue at common-lisp.net
Tue Oct 17 06:22:42 UTC 2006
Author: junrue
Date: Tue Oct 17 02:22:41 2006
New Revision: 338
Added:
trunk/docs/manual/glossary.xml
Modified:
trunk/docs/manual/graphic-forms.css
trunk/docs/manual/graphic-forms.xml
trunk/docs/manual/image-data-plugins.xml
Log:
restored glossary
Added: trunk/docs/manual/glossary.xml
==============================================================================
--- (empty file)
+++ trunk/docs/manual/glossary.xml Tue Oct 17 02:22:41 2006
@@ -0,0 +1,210 @@
+<!--
+ glossary.xml
+
+ Copyright (c) 2006, Jack D. Unrue
+-->
+<glossary><title>Glossary</title>
+
+<glossdiv><title>A</title>
+
+ <glossentry id="accelerator"><glossterm>accelerator</glossterm>
+ <glossdef>
+ <para>
+ An accelerator is a key sequence assigned to an application
+ function allowing a user to bypass navigation of the menu or control
+ hierarchy normally required to invoke the function. Some accelerators
+ are established by Windows style guidelines, such as control-c for
+ the clipboard copy operation from an Edit menu. Applications may define
+ other accelerators as appropriate. Accelerators are generally intended
+ for more knowledgeable users and should not be the sole mechanism for
+ invoking functionality.
+ </para>
+ <glossseealso otherterm="mnemonic"/>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="auto-scrolling"><glossterm>auto-scrolling</glossterm>
+ <glossdef>
+ <para>
+ Auto-scrolling is a feature whereby scrolling occurs as a side
+ effect of user input so content can remain visible, thus avoiding
+ the need to explicitly manipulate scrollbars to achieve the same result.
+ </para>
+ </glossdef>
+ </glossentry>
+
+</glossdiv>
+
+<glossdiv><title>B</title>
+</glossdiv>
+
+<glossdiv><title>C</title>
+
+ <glossentry id="control"><glossterm>control</glossterm>
+ <glossdef>
+ <para>
+ A control is a system-defined window class whose role is to accept
+ user input and possibly generate notification events based on such
+ input.
+ </para>
+ </glossdef>
+ </glossentry>
+
+</glossdiv>
+
+<glossdiv><title>D</title>
+
+ <glossentry id="default action"><glossterm>default action</glossterm>
+ <glossdef>
+ <para>
+ Conceptually, a default action is a secondary event initiated by
+ user input that is a logical follow-up to a previous event. Examples
+ of such user gestures include double-clicking an item in a list box
+ control, or pressing enter when an edit control has the keyboard focus.
+ The response to a default action makes use of context established by
+ the preceding event (e.g., the selection set by an initial click
+ becomes the context for the double-click response).
+ </para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="dialog"><glossterm>dialog</glossterm>
+ <glossdef>
+ <para>
+ A dialog is a mechanism for collecting user input or showing
+ information. The system defines common dialogs for tasks like
+ choosing files, fonts, or colors. Custom dialogs can be defined
+ by application code.
+ </para>
+ </glossdef>
+ </glossentry>
+
+</glossdiv>
+
+<glossdiv><title>E</title>
+
+ <glossentry id="extension"><glossterm>extension</glossterm>
+ <glossdef>
+ <para>
+ An extension is code providing additional functionality beyond the
+ original scope of a system. An extension framework encourages
+ modularity. More importantly, it is a conscious design choice to
+ allow a system to be stretched beyond what the original designers may
+ have anticipated.
+ </para>
+ <glossseealso otherterm="plugin"/>
+ </glossdef>
+ </glossentry>
+
+</glossdiv>
+
+<glossdiv><title>F</title>
+</glossdiv>
+
+<glossdiv><title>G</title>
+</glossdiv>
+
+<glossdiv><title>H</title>
+</glossdiv>
+
+<glossdiv><title>I</title>
+</glossdiv>
+
+<glossdiv><title>J</title>
+</glossdiv>
+
+<glossdiv><title>K</title>
+</glossdiv>
+
+<glossdiv><title>L</title>
+</glossdiv>
+
+<glossdiv><title>M</title>
+
+ <glossentry id="menu"><glossterm>menu</glossterm>
+ <glossdef>
+ <para>
+ A collection of menu items presented within a single rectangular
+ region. Menus are often anchored to a menu bar, but may also be
+ invoked in a context-sensitive manner via the mouse or an
+ <glossseealso otherterm="accelerator"/>.
+ </para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="mix-in class"><glossterm>mix-in class</glossterm>
+ <glossdef>
+ <para>
+ A mix-in class represents a specific abstraction that complements
+ the role(s) of other class(es) in a class hierarchy.
+ </para>
+ </glossdef>
+ </glossentry>
+
+ <glossentry id="mnemonic"><glossterm>mnemonic</glossterm>
+ <glossdef>
+ <para>
+ A mnemonic is a key sequence (usually a single character modified
+ by the <Alt> key) enabling mouse-free navigation of a menu or
+ control hierarchy to invoke an application function. Depending on
+ the user's system settings, mnemonic characters may be hidden until
+ the user presses the <Alt> key.
+ </para>
+ <glossseealso otherterm="accelerator"/>
+ </glossdef>
+ </glossentry>
+</glossdiv>
+
+<glossdiv><title>N</title>
+</glossdiv>
+
+<glossdiv><title>O</title>
+</glossdiv>
+
+<glossdiv><title>P</title>
+
+ <glossentry id="plugin"><glossterm>plugin</glossterm>
+ <glossdef>
+ <para>
+ A plugin is a unit of code integrated into a larger system in order
+ to implement a specific instance of an established category of
+ services. A plugin framework encourages modularity within a
+ defined scope of functionality.
+ </para>
+ <glossseealso otherterm="extension"/>
+ </glossdef>
+ </glossentry>
+
+</glossdiv>
+
+<glossdiv><title>Q</title>
+</glossdiv>
+
+<glossdiv><title>R</title>
+</glossdiv>
+
+<glossdiv><title>S</title>
+</glossdiv>
+
+<glossdiv><title>T</title>
+</glossdiv>
+
+<glossdiv><title>U</title>
+</glossdiv>
+
+<glossdiv><title>V</title>
+</glossdiv>
+
+<glossdiv><title>W</title>
+</glossdiv>
+
+<glossdiv><title>X</title>
+</glossdiv>
+
+<glossdiv><title>Y</title>
+</glossdiv>
+
+<glossdiv><title>Z</title>
+</glossdiv>
+
+</glossary>
Modified: trunk/docs/manual/graphic-forms.css
==============================================================================
--- trunk/docs/manual/graphic-forms.css (original)
+++ trunk/docs/manual/graphic-forms.css Tue Oct 17 02:22:41 2006
@@ -27,7 +27,7 @@
font-family: { Arial, Helvetica, sans-serif; }
}
-a, p.normal, span.productname {
+a, dd, dt, p.normal, span.productname {
font-size: 12;
font-family: { Arial, Helvetica, sans-serif; }
}
Modified: trunk/docs/manual/graphic-forms.xml
==============================================================================
--- trunk/docs/manual/graphic-forms.xml (original)
+++ trunk/docs/manual/graphic-forms.xml Tue Oct 17 02:22:41 2006
@@ -10,6 +10,7 @@
<!ENTITY introduction SYSTEM "introduction.xml">
<!ENTITY misctopics SYSTEM "miscellaneous-topics.xml">
<!ENTITY imdataplugins SYSTEM "image-data-plugins.xml">
+ <!ENTITY glossary SYSTEM "glossary.xml">
]>
<book>
@@ -24,6 +25,7 @@
&legal;
&introduction;
&misctopics;
+ &glossary;
<index id="index"/>
</book>
Modified: trunk/docs/manual/image-data-plugins.xml
==============================================================================
--- trunk/docs/manual/image-data-plugins.xml (original)
+++ trunk/docs/manual/image-data-plugins.xml Tue Oct 17 02:22:41 2006
@@ -16,7 +16,7 @@
<para role="small">
Nowadays, the Windows platform offers alternatives, such as GDI+
which adds among other features native support for additional image
- formats. Graphic-Forms sticks with plain-old gdi to avoid the
+ formats. Graphic-Forms sticks with plain-old GDI to avoid the
possibility of these alternatives not being installed.
</para>
</footnote>
More information about the Graphic-forms-cvs
mailing list