Pratt 1.5.6

data/pkgs/tile-0.8.2/doc/xml/separator.tmml

@@ -0,0 +1,59 @@
+<manpage cat="cmd" id="separator" title="separator" version="0.5">
+<!-- This file was automatically generated.  DO NOT EDIT (yet)! -->
+<!--  separator.n,v 1.5 2006/11/27 05:45:02 jenglish Exp
+    
+     Copyright (c) 2004 Joe English
+ -->
+<?TROFF.TH title="separator" section="n" date="0.5" source="tile" manual="Tile Widget Set" ?>
+<namesection>
+<name>ttk::separator</name>
+<desc>Separator bar</desc>
+</namesection>
+<synopsis>
+<syntax>
+<b>ttk::separator</b> <m>pathName</m> ?<m>options</m>?
+</syntax>
+</synopsis>
+<section>
+<title>DESCRIPTION</title>
+<p>A <b>separator</b> widget displays a horizontal or vertical separator bar.
+</p>
+</section>
+<section>
+<title>STANDARD OPTIONS</title>
+<sl cat="stdopt" cols="4">
+<li>-class</li>
+<li>-cursor</li>
+<li>-state</li>
+<li>-style</li>
+<li>-takefocus</li>
+</sl>
+</section>
+<section>
+<title>OPTIONS</title>
+<optionlist>
+<optiondef>
+<name>-orient</name>
+<dbname>orient</dbname>
+<dbclass>Orient</dbclass>
+<desc>One of <b>horizontal</b> or <b>vertical</b>.
+Specifies the orientation of the separator.
+</desc>
+</optiondef>
+</optionlist>
+</section>
+<section>
+<title>WIDGET COMMAND</title>
+<p>Separator widgets support the standard 
+<b>cget</b>, <b>configure</b>, <b>instate</b>, and <b>state</b> 
+methods.  No other widget methods are used.
+</p>
+</section>
+<seealso>
+<ref>widget(n)</ref>
+</seealso>
+<keywords>
+<keyword>widget</keyword>
+<keyword>separator</keyword>
+</keywords>
+</manpage>

data/pkgs/tile-0.8.2/doc/xml/sizegrip.tmml

@@ -0,0 +1,82 @@
+<manpage cat="cmd" id="sizegrip" title="sizegrip" version="0.8">
+<!-- This file was automatically generated.  DO NOT EDIT (yet)! -->
+<!--  sizegrip.n,v 1.5 2007/10/16 00:59:23 jenglish Exp
+    
+     Copyright (c) 2006 Joe English
+ -->
+<?TROFF.TH title="sizegrip" section="n" date="0.8" source="tile" manual="Tile Widget Set" ?>
+<namesection>
+<name>ttk::sizegrip</name>
+<desc>A silly widget</desc>
+</namesection>
+<synopsis>
+<syntax>
+<b>ttk::sizegrip</b> <m>pathName</m> ?<m>options</m>?
+</syntax>
+</synopsis>
+<section>
+<title>DESCRIPTION</title>
+<p>A <b>sizegrip</b> widget (also known as a <i>grow box</i>)
+allows the user to resize the containing toplevel window
+by pressing and dragging the grip.
+</p>
+</section>
+<section>
+<title>STANDARD OPTIONS</title>
+<sl cat="stdopt" cols="4">
+<li>-class</li>
+<li>-cursor</li>
+<li>-state</li>
+<li>-style</li>
+<li>-takefocus</li>
+</sl>
+</section>
+<section>
+<title>WIDGET COMMAND</title>
+<p>Sizegrip widgets support the standard
+<b>cget</b>, <b>configure</b>, <b>instate</b>, and <b>state</b>
+methods.  No other widget methods are used.
+</p>
+</section>
+<section>
+<title>PLATFORM-SPECIFIC NOTES</title>
+<p>On Mac OSX, toplevel windows automatically include a built-in
+size grip by default.
+Adding an <b>ttk::sizegrip</b> there is harmless, since
+the built-in grip will just mask the widget.
+</p>
+</section>
+<section>
+<title>EXAMPLES</title>
+<example>
+# Using pack:
+pack [ttk::frame $top.statusbar] -side bottom -fill x
+pack [ttk::sizegrip $top.statusbar.grip] -side right -anchor se
+
+# Using grid:
+grid [ttk::sizegrip $top.statusbar.grip] \
+    -row $lastRow -column $lastColumn -sticky se
+# ... optional: add vertical scrollbar in $lastColumn,
+# ... optional: add horizontal scrollbar in $lastRow
+</example>
+</section>
+<section>
+<title>BUGS</title>
+<p>If the containing toplevel's position was specified
+relative to the right or bottom of the screen
+(e.g., <b>[wm geometry ...</b> <i>w</i><b>x</b><i>h</i><b>-</b><i>x</i><b>-</b><i>y</i><b>]</b>
+instead of <b>[wm geometry ...</b> <i>w</i><b>x</b><i>h</i><b>+</b><i>x</i><b>+</b><i>y</i><b>]</b>),
+the sizegrip widget will not resize the window.
+</p>
+<p>ttk::sizegrip widgets only support "southeast" resizing.
+</p>
+</section>
+<seealso>
+<ref>widget(n)</ref>
+</seealso>
+<keywords>
+<keyword>widget</keyword>
+<keyword>sizegrip</keyword>
+<keyword>grow box</keyword>
+</keywords>
+</manpage>

data/pkgs/tile-0.8.2/doc/xml/style.tmml

@@ -0,0 +1,171 @@
+<manpage cat="cmd" id="style" title="style" version="0.5">
+<!-- This file was automatically generated.  DO NOT EDIT (yet)! -->
+<!-- 
+     Copyright (c) 2004 Joe English
+     style.n,v 1.15 2007/12/12 15:55:15 jenglish Exp
+ -->
+<?TROFF.TH title="style" section="n" date="0.5" source="tile" manual="Tile Widget Set" ?>
+<namesection>
+<name>ttk::style</name>
+<desc>Manipulate style database</desc>
+</namesection>
+<synopsis>
+<syntax>
+<b>ttk::style</b> <m>option</m> ?<m>args</m>?
+</syntax>
+</synopsis>
+<section>
+<title>NOTES</title>
+<p>See also the Tcl'2004 conference presentation,
+available at
+<ref href="http://tktable.sourceforge.net/tile/tile-tcl2004.pdf
+">http://tktable.sourceforge.net/tile/tile-tcl2004.pdf
+</ref></p>
+</section>
+<section>
+<title>DEFINITIONS</title>
+<p>Each widget is assigned a <i>style</i>,
+which specifies the set of elements making up the widget
+and how they are arranged, along with dynamic and default
+settings for element options.
+By default, the style name is the same as the widget's class;
+this may be overridden by the <b>-style</b> option. 
+</p>
+<p>A <i>theme</i> is a collection of elements and styles 
+which controls the overall look and feel of an application.
+</p>
+</section>
+<section>
+<title>DESCRIPTION</title>
+<p>The <b>ttk::style</b> command takes the following arguments:
+</p>
+<dl>
+<dle>
+<dt><b>ttk::style configure</b> <m>style</m> ?<m>-option</m> ?<m>value option value...</m>? ?</dt>
+<dd>Sets the default value of the specified option(s) in <i>style</i>.
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style map</b> <m>style</m> ?<m>-option</m> <b>{</b> <m>statespec value...</m> <b>}</b>?</dt>
+<dd>Sets dynamic values of the specified option(s) in <i>style</i>.
+Each <i>statespec / value</i> pair is examined in order;
+the value corresponding to the first matching <i>statespec</i>
+is used.
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style lookup</b> <m>style</m> <m>-option</m> ?<m>state</m> ?<m>default</m>??</dt>
+<dd>Returns the value specified for <i>-option</i> in style <i>style</i>
+in state <i>state</i>, using the standard lookup rules for element options.
+<i>state</i> is a list of state names; if omitted, 
+it defaults to all bits off (the ``normal'' state).
+If the <i>default</i> argument is present, it is used as a fallback
+value in case no specification for <i>-option</i> is found.
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style layout</b> <m>style</m> ?<m>layoutSpec</m>?</dt>
+<dd>Define the widget layout for style <i>style</i>.  
+See <ref refid="layouts">LAYOUTS</ref> below for the format of <i>layoutSpec</i>.
+If <i>layoutSpec</i> is omitted, return the layout specification
+for style <i>style</i>.
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style element create</b> <m>elementName</m> <m>type</m> ?<m>args...</m>?</dt>
+<dd>Creates a new element in the current theme of type <i>type</i>.
+The only built-in element type is <i>image</i> (see <i>image(n)</i>),
+although themes may define other element types 
+(see <b>Ttk_RegisterElementFactory</b>).
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style element names</b></dt>
+<dd>Returns the list of elements defined in the current theme.
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style element options</b> <m>element</m></dt>
+<dd>Returns the list of <i>element</i>'s options.
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style theme create</b> <m>themeName</m> ?<b>-parent</b> <m>basedon</m>? ?<b>-settings</b> <m>script...</m> ?</dt>
+<dd>Creates a new theme.  It is an error if <i>themeName</i> already exists.
+If <b>-parent</b> is specified, the new theme will inherit
+styles, elements, and layouts from the parent theme <i>basedon</i>.
+If <b>-settings</b> is present, <i>script</i> is evaluated in the
+context of the new theme as per <b>ttk::style theme settings</b>.
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style theme settings</b> <m>themeName</m> <m>script</m></dt>
+<dd>Temporarily sets the current theme to <i>themeName</i>, 
+evaluate <i>script</i>, then restore the previous theme.
+Typically <i>script</i> simply defines styles and elements,
+though arbitrary Tcl code may appear.
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style theme names</b></dt>
+<dd>Returns a list of all known themes.
+</dd>
+</dle>
+<dle>
+<dt><b>ttk::style theme use</b> <m>themeName</m></dt>
+<dd>Sets the current theme to <i>themeName</i>, and refreshes all widgets.
+</dd>
+</dle>
+</dl>
+</section>
+<section id="layouts">
+<title>LAYOUTS</title>
+<p>A <i>layout</i> specifies a list of elements, each followed
+by one or more options specifying how to arrange the element.
+The layout mechanism uses a simplified version of the <cmd>pack</cmd>
+geometry manager: given an initial cavity,
+each element is allocated a parcel.
+Valid options are:
+</p>
+<dl>
+<dle>
+<dt><b>-side</b> <m>side</m></dt>
+<dd>Specifies which side of the cavity to place the element;
+one of <b>left</b>, <b>right</b>, <b>top</b>, or <b>bottom</b>.
+If omitted, the element occupies the entire cavity.
+</dd>
+</dle>
+<dle>
+<dt><b>-sticky</b> <b>[</b><m>nswe</m><b>]</b></dt>
+<dd>Specifies where the element is placed inside its allocated parcel.
+</dd>
+</dle>
+<dle>
+<dt><b>-children {</b> <m>sublayout...</m> <b>}</b></dt>
+<dd>Specifies a list of elements to place inside the element.
+</dd>
+</dle>
+</dl>
+<p>For example:
+</p>
+<example>
+ttk::style layout Horizontal.TScrollbar {
+    Scrollbar.trough -children {
+        Scrollbar.leftarrow -side left
+        Scrollbar.rightarrow -side right
+        Horizontal.Scrollbar.thumb -side left -sticky ew
+    }
+}
+</example>
+</section>
+<seealso>
+<ref>tile-intro</ref>
+<ref>widget</ref>
+<ref>pixmap</ref>
+</seealso>
+<keywords>
+<keyword>style</keyword>
+<keyword>theme</keyword>
+<keyword>appearance</keyword>
+</keywords>
+</manpage>

data/pkgs/tile-0.8.2/doc/xml/tile-intro.tmml

@@ -0,0 +1,192 @@
+<manpage cat="misc" id="tile-intro" title="intro" version="0.2">
+<!-- This file was automatically generated.  DO NOT EDIT (yet)! -->
+<!-- 
+     Copyright (c) 2004 Joe English
+ -->
+<?TROFF.TH title="intro" section="n" date="0.2" source="tile" manual="Tile Widget Set" ?>
+<namesection>
+<name>tile_intro</name>
+<desc>Introduction to the Tile theme engine</desc>
+</namesection>
+<section>
+<title>OVERVIEW</title>
+<p>The tile widget set is based on a revised and enhanced version
+of the 
+<ref href="http://purl.org/tcl/tip/48">TIP #48
+</ref>style engine.
+The main concepts are described below.
+The basic idea is to separate, to the extent possible,
+the code implementing a widget's behavior from
+the code implementing its appearance.
+Widget class bindings are primarily responsible for
+maintaining the widget state and invoking callbacks;
+all aspects of the widgets appearance is
+</p>
+</section>
+<section>
+<title>THEMES</title>
+<p>A <i>theme</i> is a collection of elements and styles 
+that determine the look and feel of the widget set.
+Themes can be used to:
+</p>
+<ul>
+<li>Isolate platform differences (X11 vs. classic Windows vs. XP vs. Aqua ...)
+</li>
+<li>Adapt to display limitations (low-color, grayscale, monochrome, tiny screens)
+</li>
+<li>Accessibility (high contrast, large type)
+</li>
+<li>Application suite branding
+</li>
+<li>Blend in with the rest of the desktop (Gnome, KDE, Java)
+</li>
+<li>And, of course: eye candy.
+</li>
+</ul>
+</section>
+<section>
+<title>ELEMENTS</title>
+<p>An <i>element</i> displays an individual part of a widget.
+For example, a vertical scrollbar widget contains <b>uparrow</b>,
+<b>downarrow</b>, <b>trough</b> and <b>slider</b> elements.
+</p>
+<p>Element names use a recursive dotted notation.
+For example, <b>uparrow</b> identifies a generic arrow element,
+and <b>Scrollbar.uparrow</b> and <b>Combobox.uparrow</b> identify 
+widget-specific elements.
+When looking for an element, the style engine looks for
+the specific name first, and if an element of that name is
+not found it looks for generic elements by stripping off
+successive leading components of the element name.
+</p>
+<p>Like widgets, elements have <i>options</i> which
+specify what to display and how to display it.
+For example, the <b cat="AMBIGUOUS widget canvasitemtype cmd">text</b> element 
+(which displays a text string) has
+<b>-text</b>, <b>-font</b>, <b>-foreground</b>, <b>-background</b>, 
+<b>-underline</b>, and <b>-width</b> options.
+The value of an element option is taken from:
+</p>
+<ul>
+<li>An option of the same name and type in the widget containing the element;
+</li>
+<li>A dynamic setting specified by <b>style map</b> and the current state;
+</li>
+<li>The default setting specified by <b>style configure</b>; or
+</li>
+<li>The element's built-in default value for the option.
+</li>
+</ul>
+</section>
+<section>
+<title>LAYOUTS</title>
+<p>A <i>layout</i> specifies which elements make up a widget
+and how they are arranged.
+The layout engine uses a simplified version of the <cmd>pack</cmd>
+algorithm: starting with an initial cavity equal to the size
+of the widget, elements are allocated a parcel within the cavity along
+the side specified by the <b>-side</b> option,
+and placed within the parcel according to the <b>-sticky</b>
+option.
+For example, the layout for a horizontal scrollbar 
+</p>
+<example>
+ttk::style layout Horizontal.TScrollbar {
+    Scrollbar.trough -children {
+	Scrollbar.leftarrow -side left -sticky w
+	Scrollbar.rightarrow -side right -sticky e
+	Scrollbar.thumb -side left -expand true -sticky ew
+    }
+}
+</example>
+<p>By default, the layout for a widget is the same as its class name.
+Some widgets may override this (for example, the <b>ttk::scrollbar</b>
+widget chooses different layouts based on the <b>-orient</b> option).
+</p>
+</section>
+<section>
+<title>STATES</title>
+<p>In standard Tk, many widgets have a <b>-state</b> option
+which (in most cases) is either <b>normal</b> or <b>disabled</b>.
+Some widgets support additional states, such
+as the <b cat="AMBIGUOUS widget cmd">entry</b> widget which has a <b>readonly</b> state
+and the various flavors of buttons which have <b>active</b> state.
+</p>
+<p>The Tile widget set generalizes this idea:
+every widget has a bitmap of independent state flags.
+Widget state flags include <b>active</b>, <b>disabled</b>,
+<b>pressed</b>, <cmd>focus</cmd>, etc., 
+(see <i>widget(n)</i> for the full list of state flags).
+</p>
+<p>Instead of a <b>-state</b> option, every widget now has 
+a <b>state</b> widget command which is used to set or query
+the state.
+A <i>state specification</i> is a list of symbolic state names
+indicating which bits are set, each optionally prefixed with an 
+exclamation point indicating that the bit is cleared instead.
+</p>
+<p>For example, the class bindings for the <b>ttk::button</b>
+widget are:
+</p>
+<example>
+bind TButton &lt;Enter&gt;		{ %W state active }
+bind TButton &lt;Leave&gt;		{ %W state !active }
+bind TButton &lt;ButtonPress-1&gt;	{ %W state pressed }
+bind TButton &lt;Button1-Leave&gt;	{ %W state !pressed }
+bind TButton &lt;Button1-Enter&gt;	{ %W state pressed }
+bind TButton &lt;ButtonRelease-1&gt;	\
+    { %W instate {pressed} { %W state !pressed ; %W invoke } }
+</example>
+<p>This specifies that the widget becomes <b>active</b> when
+the pointer enters the widget, and inactive when it leaves.
+Similarly it becomes <b>pressed</b> when the mouse button is pressed,
+and <b>!pressed</b> on the ButtonRelease event.
+In addition, the button unpresses if 
+pointer is dragged outside the widget while Button-1 is held down,
+and represses if it's dragged back in.
+Finally, when the mouse button is released, the widget's
+<b>-command</b> is invoked, but only if the button is currently
+in the <b>pressed</b> state.
+(The actual bindings are a little more complicated than the above,
+but not by much).
+</p>
+<p><i>Note to self: rewrite that paragraph.  It's horrible.</i>
+</p>
+</section>
+<section>
+<title>STYLES</title>
+<p>Each widget is associated with a <i>style</i>, 
+which specifies values for element options.
+Style names use a recursive dotted notation like layouts and elements;
+by default, widgets use the class name to look up a style in the current theme.
+For example:
+</p>
+<example>
+ttk::style configure TButton \
+	-background #d9d9d9 \
+	-foreground black \
+	-relief raised \
+	;
+</example>
+<p>Many elements are displayed differently depending on the widget state.  
+For example, buttons have a different background when they are active,
+a different foreground when disabled, and a different relief when pressed.
+The <b>style map</b> command specifies dynamic option settings
+for a particular style:
+</p>
+<example>
+ttk::style map TButton \
+	-background [list disabled #d9d9d9  active #ececec] \
+	-foreground [list disabled #a3a3a3] \
+	-relief [list {pressed !disabled} sunken] \
+	;
+</example>
+</section>
+<seealso>
+<ref>widget(n)</ref>
+<ref>style(n)</ref>
+<ref></ref>
+<ref href="http://purl.org/tcl/tip/48">TIP #48
+</ref>
+</seealso>
+</manpage>