rb-appscript 0.5.3 → 0.6.0

data/doc/aem-manual/06_buildingandsendingevents.html

@@ -14,7 +14,7 @@
 
 <!-- top navigation -->
 <div class="navbar">
-<a href="05_targettingapplications.html">Previous</a> &bull;
+<a href="05_targetingapplications.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="07_findapp.html">Next</a>
 
@@ -168,33 +168,61 @@ KAE::KAECanSwitchLayer</code></pre>
 <pre><code>KAE::KAutoGenerateReturnID</code></pre>
 
 
-<h3>The <code>CommandError</code> class</h3>
+<h3>Exception classes</h3>
 
-<p>The <code>CommandError</code> class is raised by <code>Event#send</code> and represents an error raised by the target application or Apple Event Manager when sending an event.</p>
+<h4>The <code>EventError</code> class</h4>
 
-<pre><code>CommandError(MacOS.Error)
+<p>The <code>EventError</code> class is raised by <code>Event#send</code> and represents an error raised by the target application or Apple Event Manager when sending an event.</p>
 
-    Methods:
+<pre><code>EventError &lt; RuntimeError
 
+    Methods:
+        
         number
-            Result: integer -- error number
+            Result: integer -- Mac OS error number
 
         message
-            Result: string | nil -- error message, if any</code></pre>
-
-<!-- TO DO: MacOSError notes -->
+            Result: string | nil -- application-supplied/generic 
+                    error description
+        
+        offending_object
+            Result: anything | nil -- object that caused the error, 
+                    if given by application
+        
+        expected_type
+            Result: anything | nil -- object that caused a coercion 
+                    error, if given by application
+        
+        partial_result
+            Result: anything | nil -- part of return value constructed 
+                    before error occurred, if given by application
+        
+        to_i -- Mac OS error number
+        
+        to_s -- formatted description of error</code></pre>
+
+
+<h4><code>AE::MacOSError</code></h4>
+
+<p>The <code>AE::MacOSError</code> exception is raised by the low-level <code>AE</code> extension and represents an error raised by the Apple Event Manager. The <code>AEM</code> API usually traps these low-level errors and throws more descriptive errors in their place (e.g. <code>AEM::EventError</code>).</p>
+
+<pre><code>MacOSError &lt; StandardError
 
+    Methods:
+        number
+            Result: integer -- the Mac OS error number
+        
+        description
+            Result: string -- short generic error description</code></pre>
 
 </div>
 
 <!-- bottom navigation -->
 
 <div class="footer">
-<a href="05_targettingapplications.html">Previous</a> &bull;
+<a href="05_targetingapplications.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="07_findapp.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/aem-manual/07_findapp.html

@@ -57,8 +57,6 @@ by_creator(creator) -- Find the application with the given creator type.
 <a href="06_buildingandsendingevents.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="08_examples.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/aem-manual/08_examples.html

@@ -88,8 +88,6 @@ textedit.event('corecrel', {
 <div class="footer">
 <a href="07_findapp.html">Previous</a> &bull;
 <a href="index.html">Up</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/aem-manual/index.html

@@ -36,7 +36,7 @@
 	<li><a href="02_apioverview.html">API overview</a></li>
 	<li><a href="03_packingandunpackingdata.html">Packing and unpacking data</a></li>
 	<li><a href="04_references.html">References</a></li>
-	<li><a href="05_targettingapplications.html">Targetting applications</a></li>
+	<li><a href="05_targetingapplications.html">Targeting applications</a></li>
 	<li><a href="06_buildingandsendingevents.html">Building and sending events</a></li>
 	<li><a href="07_findapp.html">Locating applications</a></li>
 	<li><a href="08_examples.html">Examples</a></li>
@@ -50,8 +50,6 @@
 <a href="../index.html">Previous</a> &bull;
 <a href="../index.html">Up</a> &bull;
 <a href="01_introduction.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/appscript-manual/01_introduction.html

@@ -88,8 +88,6 @@ app('TextEdit').documents.end.make(
 <a href="index.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="02_aboutappscripting.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/appscript-manual/02_aboutappscripting.html

@@ -191,14 +191,14 @@ app('TextEdit').documents[1].text.paragraphs</code></pre>
 <p>Appscript is a high-level Ruby-to-Apple Event Manager bridge, intended for use by both developers and end-users. The appscript architecture consists of three layers:</p>
 
 <dl>
-<dt><code>ae</code></dt><dd>A low-level, mostly procedural Ruby wrapper around Mac OS X's Apple Event Manager API.</dd>
+<dt><code>AE</code></dt><dd>A low-level, mostly procedural Ruby wrapper around Mac OS X's Apple Event Manager API.</dd>
 
-<dt><code>aem</code></dt><dd>A mid-level wrapper around <code>AE</code>, providing an object-oriented API for building relational AEOM queries and dispatching events.</dd>
+<dt><code>AEM</code></dt><dd>A mid-level wrapper around <code>AE</code>, providing an object-oriented API for building relational AEOM queries and dispatching events.</dd>
 
-<dt><code>appscript</code></dt><dd>A high-level wrapper around <code>aem</code>, providing automatic translation between human-readable application terminology and corresponding four-letter codes, and representing relational AEOM queries in an OO-like syntax for ease of use.</dd>
+<dt><code>Appscript</code></dt><dd>A high-level wrapper around <code>AEM</code>, providing automatic translation between human-readable application terminology and corresponding four-letter codes, and representing relational AEOM queries in an OO-like syntax for ease of use.</dd>
 </dl>
 
-<p>The <code>ae</code> extension primarily serves as a foundation for higher-level libraries to build on; it's rarely used directly as it takes a significant amount of code to perform all but the most trivial of tasks. The <code>aem</code> package is largely intended for use by higher-level libraries and developers, though may also be used by end-users in cases where an application lacks terminology, or bugs within its terminology prevent its use by appscript. The <code>appscript</code> package is intended for use by both developers and end-users, though developers may prefer aem for certain tasks as appscript doesn't expose all aspects of the aem API (such as the ability to do asynchronous messaging) and terminology translation imposes additional overheads and dependencies on client code.</p>
+<p>The <code>AE</code> extension primarily serves as a foundation for higher-level libraries to build on; it's rarely used directly as it takes a significant amount of code to perform all but the most trivial of tasks. The <code>AEM</code> module is largely intended for use by higher-level libraries and developers, though may also be used by end-users in cases where an application lacks terminology, or bugs within its terminology prevent its use by appscript. The <code>Appscript</code> module is intended for use by both developers and end-users, though developers may prefer aem for certain tasks as appscript doesn't expose all aspects of the aem API (such as the ability to do asynchronous messaging) and terminology translation imposes additional overheads and dependencies on client code.</p>
 
 <p>For example, to set the size of the first character of every non-empty paragraph in every document of TextEdit to 24 pt:</p>
 
@@ -241,8 +241,6 @@ app('TextEdit').documents[1].text.paragraphs</code></pre>
 <a href="01_introduction.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="03_quicktutorial.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/appscript-manual/03_quicktutorial.html

@@ -53,7 +53,7 @@ irb(main):001:0&gt;</code></pre>
 irb&gt; include Appscript
 =&gt; Object</code></pre>
 
-<p>Once appscript is imported, the first thing to do is to create new <code>app</code> object, identifying the application to be manipulated, and assign it to a variable, <code>te</code>, for easy reuse:</p>
+<p>Once appscript is imported, create new <code>app</code> object, identifying the application to be manipulated, and assign it to a variable, <code>te</code>, for easy reuse:</p>
 
 <pre><code>irb&gt; te = app('TextEdit')
 =&gt; app("/Applications/TextEdit.app")</code></pre>
@@ -161,8 +161,6 @@ irb&gt; te.documents.text.get
 <a href="02_aboutappscripting.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="04_gettinghelp.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/appscript-manual/04_gettinghelp.html

@@ -31,7 +31,7 @@
 
 <h2>4. Getting Help</h2>
 
-<p>When developing appscript-based scripts, there are several ways to get information about applications' scripting interfaces: the ASDictionary application and its bundled <code>asdict</code> command-line tool, appscript's powerful built-in <code>help</code> method, and introspection.</p>
+<p>When developing appscript-based scripts, there are several ways to get information about applications' scripting interfaces: the ASDictionary application, appscript's powerful built-in <code>help</code> method, and introspection.</p>
 
 
 
@@ -39,8 +39,6 @@
 
 <p>ASDictionary, available from the appscript website's <a href="http://appscript.sourceforge.net/tools.html">Tools page</a>, provides a convenient GUI interface for exporting application terminology resources in plain text and HTML formats. ASDictionary can export HTML dictionaries in both single-file format and a frame-based format similar to rdoc's.</p>
 
-<p>In addition, the <code>asdict</code> tool bundled with ASDictionary can be used to export application dictionaries in HTML format, or browse them interactively from the command line. See ASDictionary's documentation for more information.</p>
-
 
 
 <h3>Built-in <code>help</code> method</h3>
@@ -139,6 +137,25 @@ p te.parameters('make')
 # ["at", "new", "with_data", "with_properties"]</code></pre>
 
 
+
+<h3>ASTranslate</h3>
+
+<p>ASTranslate, available from the appscript website's <a href="http://appscript.sourceforge.net/tools.html">tools page</a>, provides a simple tool for translating application commands from AppleScript to Ruby syntax - useful when help is needed in converting existing AppleScript code to Ruby. For example, the following AppleScript selects every file in the Home folder:</p>
+
+<pre><code>tell application "Finder"
+	select (every file of home whose name extension is in {"htm", "html"})
+end tell</code></pre>
+
+<p>To obtain the appscript equivalent, paste this script into ASTranslate and select <code>Execute</code> from the <code>Document</code> menu. ASTranslate will intercept any Apple events sent by AppleScript and display them appscript format:</p>
+
+<pre><code>app("Finder").home.files[its.name_extension.is_in(["htm", "html"])].select
+
+OK</code></pre>
+
+<p>See ASTranslate's documentation for more information.</p>
+
+
+
 <h3>Notes</h3>
 
 <p>While appscript's documentation systems try to be reasonably forgiving of flawed or faulty terminology resources, there may be a few particularly problematic applications on which they fail. Should this happen, use ASDictionary to export the application's terminology in plain text format instead.</p>
@@ -153,8 +170,6 @@ p te.parameters('make')
 
 <li>Look for third-party scripts that provide examples of use (though many of these scripts will be written in AppleScript rather than Ruby).</li>
 
-<li>The <a href="http://appscript.sourceforge.net/tools.html">ASTranslate</a> tool can be used to convert application commands from AppleScript to Ruby syntax.</li>
-
 <li>The <a href="http://appscript.sourceforge.net">appscript website</a> has links to mailing lists and other general resources.</li>
 </ul>
 
@@ -167,8 +182,6 @@ p te.parameters('make')
 <a href="03_quicktutorial.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="05_keywordconversion.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/appscript-manual/05_keywordconversion.html

@@ -86,18 +86,20 @@ hash                          to_s
 help                          type
 ID                            untaint
 id                            wait_reply</code></pre>
-</div>
 </li>
+
+<li>Appscript provides default terminology for standard type classes such as <code>integer</code> and <code>unicode_text</code>, and standard commands such as <code>open</code> and <code>quit</code>. If an application-defined name matches a built-in name but has a different Apple event code, appscript will append an underscore to the application-defined name.</li>
 </ul>
 
+<p class="hilitebox">You can use ASDictionary or appscript's built-in <code>help</code> method to export or view application terminology in appscript format. See the <a href="04_gettinghelp.html">Getting Help</a> chapter for more information.</p>
+</div>
+
 <!-- bottom navigation -->
 
 <div class="footer">
 <a href="04_gettinghelp.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="06_classesandenums.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/appscript-manual/06_classesandenums.html

@@ -50,12 +50,15 @@
 :no
 :ask</code></pre>
 
-<p>Occasionally an application dictionary defines a type or enumerator without providing it with a corresponding name name. In these cases, the value will be represented as a raw <code>AEM::AEType</code> or <code>AEM::AEEnum</code> object instead of a symbol, e.g.: <!--The aem package's documentation provides more information on these lower-level objects, should you need to use them.--></p>
+<p>Occasionally an application dictionary defines a type or enumerator without providing it with a corresponding name name. In these cases, the value will be represented as a raw <code>AEM::AEType</code> or <code>AEM::AEEnum</code> object instead of a symbol, e.g.:</p>
 
 <pre><code>AEM::AEType.new('abcd')
 
 AEM::AEEnum.new('xyz ')</code></pre>
 
+<p>See the aem manual for more information on these lower-level objects, should you need to use them.</p>
+
+
 <h3>Common AE types</h3>
 
 <table width="100%" summary="AE-Ruby type mappings">
@@ -98,23 +101,46 @@ AEM::AEEnum.new('xyz ')</code></pre>
 <p>When packing a <code>Bignum</code>, appscript will pack it either as a 32-bit integer (most preferred), 64-bit integer, or 64-bit float (least preferred), depending on the value's size.</p>
 
 
-<h4>Strings</h4>
+<h4>Strings (Ruby 1.8)</h4>
 
-<p>Because Ruby lacks a native Unicode class, appscript unpacks all text-related AE types (<code>typeChar</code>, <code>typeUnicodeText</code>, etc.) as UTF8-encoded Ruby strings.</p>
+<p>Because Ruby 1.8 lacks native Unicode support, appscript unpacks all text-related AE types (<code>typeChar</code>, <code>typeUnicodeText</code>, etc.) as String instances containing UTF8-encoded data.</p>
 
-<p>Appscript packs UTF8-encoded Ruby strings as the <code>typeUnicodeText</code> AE type. If the string does not contain valid UTF8 data, a TypeError will be raised.</p>
+<p>Appscript packs String instances containing UTF8-encoded data as the <code>typeUnicodeText</code> AE type. If the string does not contain valid UTF-8 data, a TypeError will be raised.</p>
 
 <div class="hilitebox">
-<p>You can enable a degree of UTF8 support in Ruby's <code>String</code> class via the Jcode module (included in Ruby's standard library). To use Jcode, add the following lines to the start of your Ruby scripts, irb sessions, etc.:</p>
+<p>You can enable a degree of UTF-8 support in Ruby's <code>String</code> class via the Jcode module (included in Ruby's standard library). To use Jcode, add the following lines to the start of your Ruby scripts, irb sessions, etc.:</p>
 <pre><code>require "jcode"
 $KCODE = "UTF8"</code></pre>
 
 <p>This will improve the display of non-ASCII characters in irb, amongst other things.</p>
 
 </div>
+
 <p>Note that while <code>typeUnicodeText</code> is formally deprecated in Mac OS X 10.4+ in favour of <code>typeUTF8Text</code> and <code>typeUTF16ExternalRepresentation</code>, it is still in common usage so appscript continues to use it to ensure the broadest compatibility with existing scriptable applications.</p>
 
 
+<h4>Strings (Ruby 1.9+)</h4>
+
+<p>Each String instance in Ruby 1.9+ contains an <code>Encoding</code> instance that identifies the character set used. By default, appscript unpacks a text descriptors as a String instance containing UTF-8 encoded data and a UTF-8 Encoding, and encodes a string as UTF-8 prior to packing its data into a text descriptor. To disable this behavior for individual <code>Application</code> instances:</p>
+
+<pre><code>some_app = Appscript.app('SomeApp')
+some_app.AS_app_data.use_ascii_8bit
+# Send commands here...</code></pre>
+
+<p>Once invoked, Strings will be treated as UTF-8 encoded data with ASCII-8BIT Encoding; this is equivalent to the Ruby 1.8 behavior.</p>
+
+
+<h4>Dates and Times</h4>
+
+<p>Appscript packs Ruby <code>Time</code>, <code>Date</code> and <code>DateTime</code> instances as <code>typeLongDateTime</code> descriptors. (Note that AE dates does not include locale information.)</p>
+
+<p>By default, <code>typeLongDateTime</code> descriptors are unpacked as Ruby <code>Time</code> instances. This is sufficient for most purposes; however, where the AEDesc contains a date value below or above the range supported by Ruby's <code>Time</code> class, an error will occur. To unpack dates as <code>DateTime</code> instances for individual <code>Application</code> instances:</p>
+
+<pre><code>some_app = Appscript.app('SomeApp')
+some_app.AS_app_data.use_datetime
+# Send commands here...</code></pre>
+
+
 <h4>Filesystem references</h4>
 
 <p>The <code>typeAlias</code> AE type represents a filesystem object, and will continue to point to that object even if it's renamed or moved to another location on the same disk. The <code>typeFSRef</code> and <code>typeFileURL</code> types represent a filesystem location. Both can represent existing locations; the <code>typeFileURL</code> type can also be used to specify locations that don't already exist.</p>
@@ -139,7 +165,7 @@ $KCODE = "UTF8"</code></pre>
 
 <h4>Types and enumerators</h4>
 
-<p>The <code>typeType</code> and <code>typeEnumerated</code> AE types are unpacked as Ruby symbols when the corresponding terminology is available, otherwise they are unpacked as <code>AEM::AEType</code> and <code>AEM::AEEnum</code> respectively.</td></tr>
+<p>The <code>typeType</code> and <code>typeEnumerated</code> AE types are unpacked as Ruby symbols when the corresponding terminology is available, otherwise they are unpacked as <code>AEM::AEType</code> and <code>AEM::AEEnum</code> respectively.</p>
 
 
 <h4>Unit types</h4>
@@ -160,8 +186,6 @@ $KCODE = "UTF8"</code></pre>
 <a href="05_keywordconversion.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="07_applicationobjects.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/appscript-manual/07_applicationobjects.html

@@ -34,47 +34,34 @@
 <h3>Creating application objects</h3>
 
 
-<p>Before you can communicate with a scriptable application you must call one of the following methods to create an application object:</p>
+<p>Before you can communicate with a scriptable application you must create an <code>Application</code> object, for example:</p>
 
-<pre><code>app.by_name(name) # name or POSIX path of local application
+<pre><code>textedit = app.by_id('com.apple.textedit')</code></pre>
 
-app.by_id(id) # bundle ID for a local application
 
-app.by_creator(creator) # 4-character creator type for a local application
-
-app.by_pid(pid) # Unix process id for a local process
-
-app.by_url(url) # eppc URL for a remote process
-
-app.by_aem_app(aem_app) # AEM::Application instance
-
-app.current # the host process</code></pre>
-
-<p>For convenience, the most commonly used form, <code>app.by_name(name)</code>, can be shortened to:</p>
-
-<pre><code>app(name)</code></pre>
-
-
-<p>To target an application you must supply one of the following arguments:</p>
+<p>To target an application you must call one of the <code>app</code> object's <code>by_*</code> methods with the appropriate argument:</p>
 
 <dl>
-<dt><code>name</code></dt>
+<dt><code>app.by_name(<var>name</var>)</code> / <code>app(<var>name</var>)</code></dt>
 <dd>The application's filename or POSIX path, e.g. <code>'TextEdit'</code>, <code>'TextEdit.app'</code>, <code>'/Applications/TextEdit.app'</code>. Where a filename is provided, appscript uses LaunchServices to locate the application. An <code>.app</code> suffix is optional. e.g. Given the name <code>'TextEdit'</code>, appscript first searches for an application with that exact filename; if none is found, it automatically adds an <code>.app</code> suffix (<code>'TextEdit.app'</code>) and tries again.</dd>
 
-<dt><code>id</code></dt>
+<dt><code>app.by_id(<var>id</var>)</code></dt>
 <dd>The application's bundle id, e.g. <code>'com.apple.textedit'</code>. Cocoa applications often have unique bundle ids.</dd> 
 
-<dt><code>creator</code></dt>
+<dt><code>app.by_creator(<var>creator</var>)</code></dt>
 <dd>A four-character string containing the application's creator type, e.g. <code>'ttxt'</code>. Older Carbon-based applications and some Cocoa-based applications have unique creator types.</dd>
 
-<dt><code>pid</code></dt>
+<dt><code>app.by_pid(<var>pid</var>)</code></dt>
 <dd>A valid Unix process id, e.g. <code>5687</code>.</dd>
 
-<dt><code>url</code></dt>
+<dt><code>app.by_url(<var>url</var>)</code></dt>
 <dd>A URL of form <code>eppc://[user[:password]@host/Application%20Name[?[uid=#]&amp;[pid=#]</code>, e.g. <code>eppc://johnsmith:foobar@office-mac.local/TextEdit?uid=501</code>. The host name/IP address and the process name (case-sensitive) are required. The username and password are optional: if omitted, the OS will obtain this information from the user's keychain or display a dialog asking the user to input one or both values. The user id and process id are also optional; if the process id is given, the process name will be ignored.</dd>
 
-<dt><code>aem_app</code></dt>
+<dt><code>app.by_aem_app(<var>aem_app</var>)</code></dt>
 <dd>An <code>AEM::Application</code> instance.</dd>
+
+<dt><code>app.current</code></dt>
+<dd>The host application.</dd>
 </dl>
 
 
@@ -102,25 +89,29 @@ itunes = app.by_url('eppc://Jan%20Smith@G4.local/iTunes')</code></pre>
 
 <p>All applications should respond to the following commands:</p>
 
-<pre><code>run -- Run an application.
-        Most applications will open an empty, untitled window.
+<pre><code>run -- Run an application. Most applications will open an empty, 
+          untitled window.
 
-launch -- Launch an application without sending it a 'run' event. [1]
-        Applications that normally open a new, empty document upon launch won't.
+launch -- Launch an application without sending it a 'run' event.
+          Applications that normally open a new, empty document 
+          upon launch won't. [1]
 
 activate -- Bring the application to the front.
 
-reopen -- Reactivate a running application.
-        Some applications will open a new untitled window if no window is open.
+reopen -- Reactivate a running application. Some applications 
+          will open a new untitled window if no window is open.
 
-open(directarg) -- Open the specified object(s).
-    directarg : anything -- list of objects to open, typically a list of MacFile::Alias
+open(<var>value</var>) -- Open the specified object(s).
+    anything -- list of objects to open, typically a list of 
+                MacTypes::Alias
 
-print(directarg) -- Print the specified object(s).
-    directarg : anything -- list of objects to print, typically a list of MacFile::Alias
+print(<var>value</var>) -- Print the specified object(s).
+    anything -- list of objects to print, typically a list of 
+                MacTypes::Alias
 
-quit(saving) -- Quit an application.
-    saving : :yes | :ask | :no -- specifies whether to save currently open documents
+quit(saving => <var>value</var>) -- Quit an application.
+    saving : :yes | :ask | :no -- specifies whether to save 
+                                  currently open documents
 </code></pre>
 
 <p><small>[1] The <code>launch</code> command should be used before constructing references or sending other commands, otherwise appscript will run the application normally.</small></p>
@@ -129,11 +120,11 @@ quit(saving) -- Quit an application.
 
 <p>Appscript also defines <code>get</code> and <code>set</code> commands for any scriptable application that doesn't supply its own definitions:</p>
 
-<pre><code>get(reference) -- Get the data for an object.
+<pre><code>get(<var>value</var>) -- Get the data for an object.
     reference -- the object for the command
     Result: anything -- the reply for the command
 
-set(reference, :to =&gt; value) -- Set an object's data.
+set(<var>value</var>, :to =&gt; <var>value</var>) -- Set an object's data.
     reference -- the object for the command
     to : anything -- The new value.</code></pre>
 
@@ -214,8 +205,6 @@ te.launch
 <a href="06_classesandenums.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="08_realvsgenericreferences.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>