RubyGems - rb-appscript - Versions diffs - 0.5.1 → 0.5.2 - Mend

rb-appscript 0.5.1 → 0.5.2

Files changed (61) hide show

data/CHANGES +30 -0
data/LICENSE +1 -1
data/README +7 -3
data/TODO +7 -1
data/doc/aem-manual/01_introduction.html +23 -9
data/doc/aem-manual/02_apioverview.html +25 -11
data/doc/aem-manual/03_packingandunpackingdata.html +22 -17
data/doc/aem-manual/04_references.html +49 -36
data/doc/aem-manual/05_targettingapplications.html +25 -14
data/doc/aem-manual/06_buildingandsendingevents.html +47 -21
data/doc/aem-manual/07_findapp.html +22 -11
data/doc/aem-manual/08_examples.html +21 -10
data/doc/aem-manual/index.html +28 -12
data/doc/appscript-manual/01_introduction.html +40 -27
data/doc/appscript-manual/02_aboutappscripting.html +28 -15
data/doc/appscript-manual/03_quicktutorial.html +29 -16
data/doc/appscript-manual/04_gettinghelp.html +31 -16
data/doc/appscript-manual/05_keywordconversion.html +23 -10
data/doc/appscript-manual/06_classesandenums.html +32 -19
data/doc/appscript-manual/07_applicationobjects.html +31 -18
data/doc/appscript-manual/08_realvsgenericreferences.html +23 -11
data/doc/appscript-manual/09_referenceforms.html +33 -20
data/doc/appscript-manual/10_referenceexamples.html +30 -17
data/doc/appscript-manual/11_applicationcommands.html +25 -13
data/doc/appscript-manual/12_commandexamples.html +26 -15
data/doc/appscript-manual/13_performanceissues.html +46 -20
data/doc/appscript-manual/14_notes.html +29 -19
data/doc/appscript-manual/index.html +27 -11
data/doc/full.css +95 -9
data/doc/index.html +27 -10
data/doc/mactypes-manual/01_introduction.html +56 -0
data/doc/mactypes-manual/02_aliasclass.html +134 -0
data/doc/mactypes-manual/03_fileurlclass.html +136 -0
data/doc/mactypes-manual/04_unitsclass.html +102 -0
data/doc/mactypes-manual/index.html +26 -227
data/doc/osax-manual/01_introduction.html +69 -0
data/doc/osax-manual/02_interface.html +149 -0
data/doc/osax-manual/03_examples.html +75 -0
data/doc/osax-manual/04_notes.html +80 -0
data/doc/osax-manual/index.html +26 -195
data/doc/rb-appscript-logo.png +0 -0
data/rb-appscript.gemspec +2 -2
data/sample/TextEdit_demo.rb +1 -1
data/src/lib/_aem/aemreference.rb +1 -1
data/src/lib/_aem/codecs.rb +42 -8
data/src/lib/_aem/connect.rb +3 -1
data/src/lib/_aem/findapp.rb +1 -1
data/src/lib/_aem/mactypes.rb +1 -1
data/src/lib/_aem/send.rb +162 -142
data/src/lib/_aem/typewrappers.rb +2 -2
data/src/lib/_appscript/defaultterminology.rb +76 -46
data/src/lib/_appscript/referencerenderer.rb +1 -1
data/src/lib/_appscript/reservedkeywords.rb +2 -2
data/src/lib/_appscript/safeobject.rb +1 -1
data/src/lib/_appscript/terminology.rb +30 -19
data/src/lib/aem.rb +1 -6
data/src/lib/appscript.rb +65 -20
data/src/lib/osax.rb +21 -18
data/src/rbae.c +1 -1
data/test/test_appscriptcommands.rb +1 -1
metadata +12 -3

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

@@ -2,7 +2,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
-<title>appscript | 2. About Application Scripting</title>
+<title>rb-appscript manual | 2. About Application Scripting</title>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <style type="text/css" media="all"><!--@import url(../full.css);--></style>
@@ -10,19 +10,30 @@
 </head>
 <body>
-<h1>2. About Application Scripting</h1>
+<h1><img src="../rb-appscript-logo.png" alt="rb-appscript" title="rb-appscript" /></h1>
 <!-- top navigation -->
 <div class="navbar">
-	<a href="01_introduction.html">Previous</a> | <a href="index.html">Up</a> | <a href="03_quicktutorial.html">Next</a>
+<a href="01_introduction.html">Previous</a> &bull;
+<a href="index.html">Up</a> &bull;
+<a href="03_quicktutorial.html">Next</a>
+<span>
+<strong><a href="../appscript-manual/index.html">appscript</a></strong> /
+<a href="../mactypes-manual/index.html">mactypes</a> /
+<a href="../osax-manual/index.html">osax</a> /
+<a href="../aem-manual/index.html">aem</a>
+</span>
 </div>
 <!-- content -->
 <div id="content">
+<h2>2. About Application Scripting</h2>
 <p>This chapter introduces the main concepts behind Apple event-based application scripting. However, if you just can't wait to begin using appscript, you can skip to the tutorial in <a href="03_quicktutorial.html">chapter 3</a> and return to this chapter later on.</p>
-<h2>What are Apple events?</h2>
+<h3>What are Apple events?</h3>
 <p>Apple events are a high-level message-based form of Interprocess Communication (IPC; also known as Interapplication Communication, or IAC), used to communicate between local or remote application processes (and, in some cases, within the same process).</p>
@@ -59,7 +70,7 @@
 <p>Applications may respond to an incoming Apple event by sending a reply event back to the client application. The reply event may contain either a return value, if there is one, or an error description if it was unable to handle the event as requested. For example, executing the command <code>app('TextEdit').name.get</code> in a Ruby interpreter sends TextEdit a <code>code/getd</code> event containing an object specifier identifying the <code>name</code> property of its root <code>application</code> object. TextEdit processes this event, then sends a reply event containing the string '<tt>TextEdit</tt>' back to the Ruby interpreter, where it is displayed as the command's result. This exchange is usually performed synchronously, appearing to the user as a simple remote procedure call. Asynchronous messaging is also supported, though is not normally used in application scripting.</p>
-<h2>What is a scriptable application?</h2>
+<h3>What is a scriptable application?</h3>
 <p>A scriptable (or 'AppleScriptable') application is an application that provides an Apple event interface intended for third-party (e.g. end-user) use. The application implements one or more event handlers that respond to corresponding events, and may also support the Apple Event Object Model. While this interface may be regarded as an API, the emphasis is on providing a high-level <em>user interface</em> that is peer to other users interfaces the application may have (GUI, CLI, web, etc.) and accessible to end-users as much as developers.</p>
@@ -78,7 +89,7 @@
 <p>(Note that the <code>aete</code> and <code>sdef</code> formats do not provide an exhaustive description of the application's scripting interface, and additional documentation is usually required - if not always provided - to form a complete understanding of that interface and how to use it effectively.)</p>
-<h2>What is the Apple Event Object Model?</h2>
+<h3>What is the Apple Event Object Model?</h3>
 <p>The Apple Event Object Model (AEOM) is an idealised, user-oriented representation of the application's internal data model, allowing clients to identify and manipulate parts of that structure via Apple events. An incoming Apple event representing a particular command (get, set, move, etc.) is unpacked, and any object specifiers in its parameter list are evaluated against the application's AEOM to identify the user-level object(s) upon which the command should act. The command is then applied these objects, with the AEOM translating this into operations upon the application's implementation-level objects. These implementation-level objects are mostly user-data objects in the application's Model layer, plus a few GUI objects of interest to scripters (such as those representing document windows). The internal architecture of a typical scriptable desktop application might look something like this:</p>
@@ -99,7 +110,7 @@
 </div>
-<h2>How does the AEOM work?</h2>
+<h3>How does the AEOM work?</h3>
 <p>The AEOM is a tree structure made up of objects. These objects may have attributes (descriptive values such as class, name, id, size, bounds; usually primitive AE types but occasionally other application objects), e.g.:</p>
@@ -175,7 +186,7 @@ app('TextEdit').documents[1].text.paragraphs</code></pre>
 </div>
-<h2>What is appscript?</h2>
+<h3>What is appscript?</h3>
 <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>
@@ -212,7 +223,7 @@ app('TextEdit').documents[1].text.paragraphs</code></pre>
-<h2>Additional resources</h2>
+<h3>Additional resources</h3>
 <p>Background information links can be found on the <a href="http://rb-appscript.rubyforge.org">rb-appscript website</a>.</p>
@@ -225,12 +236,14 @@ app('TextEdit').documents[1].text.paragraphs</code></pre>
 </div>
 <!-- bottom navigation -->
-<div class="navbar">
-	<a href="01_introduction.html">Previous</a> | <a href="index.html">Up</a> | <a href="03_quicktutorial.html">Next</a>
+<div class="footer">
+<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>
-<!--footer-->
-<p class="footer">&copy; 2006-2008 HAS</p>
 </body>
 </html>

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

@@ -2,7 +2,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
-<title>appscript | 3. Quick Tutorial</title>
+<title>rb-appscript manual | 3. Quick Tutorial</title>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <style type="text/css" media="all"><!--@import url(../full.css);--></style>
@@ -10,19 +10,30 @@
 </head>
 <body>
-<h1>3. Quick Tutorial</h1>
+<h1><img src="../rb-appscript-logo.png" alt="rb-appscript" title="rb-appscript" /></h1>
 <!-- top navigation -->
 <div class="navbar">
-	<a href="02_aboutappscripting.html">Previous</a> | <a href="index.html">Up</a> | <a href="04_gettinghelp.html">Next</a>
+<a href="02_aboutappscripting.html">Previous</a> &bull;
+<a href="index.html">Up</a> &bull;
+<a href="04_gettinghelp.html">Next</a>
+<span>
+<strong><a href="../appscript-manual/index.html">appscript</a></strong> /
+<a href="../mactypes-manual/index.html">mactypes</a> /
+<a href="../osax-manual/index.html">osax</a> /
+<a href="../aem-manual/index.html">aem</a>
+</span>
 </div>
 <!-- content -->
 <div id="content">
+<h2>3. Quick Tutorial</h2>
 <p>The following tutorial provides a practical taste of application scripting with appscript. Later chapters cover the technical details of appscript usage that are mostly skimmed over here.</p>
-<h2>'Hello World' tutorial</h2>
+<h3>'Hello World' tutorial</h3>
 <p>This tutorial uses appscript, TextEdit and the interactive command line Ruby interpreter to perform a simple 'Hello World' exercise.</p>
@@ -33,7 +44,7 @@
 <pre><code>brian% irb
 irb(main):001:0&gt;</code></pre>
-<h3>Target TextEdit</h3>
+<h4>Target TextEdit</h4>
 <p>The first step is to import the appscript module, <code>Appscript</code>, which provides the following functions and classes: <code>app</code>, <code>con</code>, <code>its</code>, <code>CommandError</code> and <code>ApplicationNotFoundError</code>.</p>
@@ -49,7 +60,7 @@ irb&gt; include Appscript
 <p>The application may be identified by name, path, bundle ID, creator type, Unix process id, or, if running remotely, URL. If the application is identified by name, path, bundle ID or creator type and is not already running, it will be launched automatically for you.</p>
-<h3>Create a new document</h3>
+<h4>Create a new document</h4>
 <p>First, create a new TextEdit document by making a new <code>document</code> object. This is done using the <code>make</code> command, passing it a single keyword parameter, <code>:new =&gt; :document</code>, indicating the type of object to create:</p>
@@ -65,7 +76,7 @@ irb&gt; include Appscript
 <pre><code>irb&gt; doc = te.make(:new =&gt; :document)
 =&gt; app("/Applications/TextEdit.app").documents[1]</code></pre>
-<h3>Set the document's content</h3>
+<h4>Set the document's content</h4>
 <p>The next step is to set the document's content to the string <code>"Hello World"</code>. Every TextEdit document has a property, <code>text</code>, that represents the entire text of the document. This property is both readable and writeable, allowing you to retrieve and/or modify the document's textual content as unstyled unicode text.</p>
@@ -82,7 +93,7 @@ irb&gt; include Appscript
 <p>Appscript converts this second form to the first form internally, so the end result is exactly the same. Appscript supports several such special cases, and these are described in the <a href="11_applicationcommands.html">Application Commands</a> chapter. Using these special cases produces more elegant, readable source code, and is recommended.</p>
-<h3>Get the document's content</h3>
+<h4>Get the document's content</h4>
 <p>Retrieving the document's text is done using the <code>get</code> command:</p>
@@ -117,7 +128,7 @@ irb&gt; te.documents.text.get
-<h3>More on <code>make</code></h3>
+<h4>More on <code>make</code></h4>
 <p>The above exercise uses two commands to create a new TextEdit document containing the text '<tt>Hello World</tt>'. It is also possible to perform both operations using the <code>make</code> command alone by passing the value for the new document's <code>text</code> property via the <code>make</code> command's optional <code>with_properties</code> parameter:</p>
@@ -127,7 +138,7 @@ irb&gt; te.documents.text.get
 <p>Incidentally, you might note that every time the <code>make</code> command is used, it returns a reference to document <em>1</em>. TextEdit identifies its <code>document</code> objects according to the stacking order of their windows, with document 1 being frontmost. When the window stacking order changes, whether as a result of a script command or GUI-based interaction, so does the order of their corresponding <code>document</code> objects. This means that a previously created reference such as <code>app('/Applications/TextEdit.app').documents[1]</code> may now identify a different <code>document</code> object to before! Some applications prefer to return references that identify objects by name or unique ID rather than index to reduce or eliminate the potential for confusion, but it's an issue you should be aware of, particularly with long-running scripts where there is greater opportunity for unexpected third-party interactions to throw a spanner in the works.</p>
-<h3>More on manipulating <code>text</code></h3>
+<h4>More on manipulating <code>text</code></h4>
 <p>In addition to getting and setting a document's entire text by applying <code>get</code> and <code>set</code> commands to <code>text</code> property, it's also possible to manipulate selected sections of a document's text directly. TextEdit's <code>text</code> property contains a <code>text</code> object, which in turn has <code>character</code>, <code>word</code> and <code>paragraph</code> elements, all of which can be manipulated using a variety of commands: <code>get</code>, <code>set</code>, <code>make</code>, <code>move</code>, <code>delete</code>, etc. For example, to set the size of the first character of every paragraph of the front document to 24pt:</p>
@@ -145,12 +156,14 @@ irb&gt; te.documents.text.get
 </div>
 <!-- bottom navigation -->
-<div class="navbar">
-	<a href="02_aboutappscripting.html">Previous</a> | <a href="index.html">Up</a> | <a href="04_gettinghelp.html">Next</a>
+<div class="footer">
+<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>
-<!--footer-->
-<p class="footer">&copy; 2006-2008 HAS</p>
 </body>
 </html>

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

@@ -2,7 +2,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
-<title>appscript | 4. Getting Help</title>
+<title>rb-appscript manual | 4. Getting Help</title>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <style type="text/css" media="all"><!--@import url(../full.css);--></style>
@@ -10,21 +10,32 @@
 </head>
 <body>
-<h1>4. Getting Help</h1>
+<h1><img src="../rb-appscript-logo.png" alt="rb-appscript" title="rb-appscript" /></h1>
 <!-- top navigation -->
 <div class="navbar">
-	<a href="03_quicktutorial.html">Previous</a> | <a href="index.html">Up</a> | <a href="05_keywordconversion.html">Next</a>
+<a href="03_quicktutorial.html">Previous</a> &bull;
+<a href="index.html">Up</a> &bull;
+<a href="05_keywordconversion.html">Next</a>
+<span>
+<strong><a href="../appscript-manual/index.html">appscript</a></strong> /
+<a href="../mactypes-manual/index.html">mactypes</a> /
+<a href="../osax-manual/index.html">osax</a> /
+<a href="../aem-manual/index.html">aem</a>
+</span>
 </div>
 <!-- content -->
 <div id="content">
+<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>
-<h2>ASDictionary</h2>
+<h3>ASDictionary</h3>
 <p>ASDictionary, available from the appscript website's <a href="http://rb-appscript.rubyforge.org/downloads.html">Downloads 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>
@@ -32,7 +43,7 @@
-<h2>Built-in <code>help</code> method</h2>
+<h3>Built-in <code>help</code> method</h3>
 <p>Appscript's <code>Application</code> and <code>Reference</code> classes include a powerful interactive help system that allows you to explore applications' scripting interfaces from within running scripts and Ruby's interactive <code>irb</code> interpreter. The <code>help</code> method can provide information on any suite, class, command or reference, and display the inheritance and relationships for a selected class or the entire application.</p>
@@ -94,7 +105,7 @@ app('TextEdit').documents.help('-t count -t close')</code></pre>
-<h2>Introspection</h2>
+<h3>Introspection</h3>
 <p>In addition to supporting Ruby's standard <code>#methods</code> and <code>#respond_to?</code> methods, appscript's <code>Application</code> and <code>Reference</code> classes also define several instance methods for obtaining information on the target application: </p>
@@ -128,12 +139,12 @@ p te.parameters('make')
 # ["at", "new", "with_data", "with_properties"]</code></pre>
-<h2>Notes</h2>
+<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>
-<h2>Other sources of help</h2>
+<h3>Other sources of help</h3>
 <ul>
 <li>The <code>sample</code> folder contains example scripts demonstrating a range of common tasks.</li>
@@ -142,19 +153,23 @@ 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://rb-appscript.rubyforge.org">rb-appscript website</a> has links to mailing lists and other general resources.</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>
 </div>
 <!-- bottom navigation -->
-<div class="navbar">
-	<a href="03_quicktutorial.html">Previous</a> | <a href="index.html">Up</a> | <a href="05_keywordconversion.html">Next</a>
+<div class="footer">
+<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>
-<!--footer-->
-<p class="footer">&copy; 2006-2008 HAS</p>
 </body>
-</html>
+</html>

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

@@ -2,7 +2,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
-<title>appscript | 5. Keyword Conversion</title>
+<title>rb-appscript manual | 5. Keyword Conversion</title>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <style type="text/css" media="all"><!--@import url(../full.css);--></style>
@@ -10,17 +10,28 @@
 </head>
 <body>
-<h1>5. Keyword Conversion</h1>
+<h1><img src="../rb-appscript-logo.png" alt="rb-appscript" title="rb-appscript" /></h1>
 <!-- top navigation -->
 <div class="navbar">
-	<a href="04_gettinghelp.html">Previous</a> | <a href="index.html">Up</a> | <a href="06_classesandenums.html">Next</a>
+<a href="04_gettinghelp.html">Previous</a> &bull;
+<a href="index.html">Up</a> &bull;
+<a href="06_classesandenums.html">Next</a>
+<span>
+<strong><a href="../appscript-manual/index.html">appscript</a></strong> /
+<a href="../mactypes-manual/index.html">mactypes</a> /
+<a href="../osax-manual/index.html">osax</a> /
+<a href="../aem-manual/index.html">aem</a>
+</span>
 </div>
 <!-- content -->
 <div id="content">
-<h2>Keyword conversion</h2>
+<h2>5. Keyword Conversion</h2>
+<h3>Keyword conversion</h3>
 <p>Because application terminology resources specify AppleScript-style keywords for class, property, command, etc. names, appscript uses the following rules to translate these keywords to legal Ruby identifiers:</p>
@@ -80,12 +91,14 @@ id                            wait_reply</code></pre>
 </ul>
 <!-- bottom navigation -->
-<div class="navbar">
-	<a href="04_gettinghelp.html">Previous</a> | <a href="index.html">Up</a> | <a href="06_classesandenums.html">Next</a>
+<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>
-<!--footer-->
-<p class="footer">&copy; 2006-2008 HAS</p>
 </body>
 </html>

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

@@ -2,7 +2,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
-<title>appscript | 6. Classes and Enumerated Types</title>
+<title>rb-appscript manual | 6. Classes and Enumerated Types</title>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <style type="text/css" media="all"><!--@import url(../full.css);--></style>
@@ -10,17 +10,28 @@
 </head>
 <body>
-<h1>6. Classes and Enumerated Types</h1>
+<h1><img src="../rb-appscript-logo.png" alt="rb-appscript" title="rb-appscript" /></h1>
 <!-- top navigation -->
 <div class="navbar">
-	<a href="05_keywordconversion.html">Previous</a> | <a href="index.html">Up</a> | <a href="07_applicationobjects.html">Next</a>
+<a href="05_keywordconversion.html">Previous</a> &bull;
+<a href="index.html">Up</a> &bull;
+<a href="07_applicationobjects.html">Next</a>
+<span>
+<strong><a href="../appscript-manual/index.html">appscript</a></strong> /
+<a href="../mactypes-manual/index.html">mactypes</a> /
+<a href="../osax-manual/index.html">osax</a> /
+<a href="../aem-manual/index.html">aem</a>
+</span>
 </div>
 <!-- content -->
 <div id="content">
-<h2>Appscript keywords</h2>
+<h2>6. Classes and Enumerated Types</h2>
+<h3>Appscript keywords</h3>
 <p>For your convenience, appscript represents Apple event type names and application-specific class and enumerator names as Ruby symbols. Examples:</p>
@@ -45,7 +56,7 @@
 AEM::AEEnum.new('xyz ')</code></pre>
-<h2>Common AE types</h2>
+<h3>Common AE types</h3>
 <table width="100%" summary="AE-Ruby type mappings">
 <thead>
@@ -78,16 +89,16 @@ AEM::AEEnum.new('xyz ')</code></pre>
 <p>(Note that types marked with '*' are officially deprecated and/or their use discouraged in Mac OS X. They remain supported to ensure backwards compatibility with older applications that may use them.)</p>
-<h2>Type mapping notes</h2>
+<h3>Type mapping notes</h3>
 <p>While AEM-Ruby type conversions generally work quite seamlessly, it is sometimes useful to know some of the details involved, particularly when troubleshooting code that deals with older or buggy applications.</p>
-<h3>Numbers</h3>
+<h4>Numbers</h4>
 <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>
-<h3>Strings</h3>
+<h4>Strings</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>
@@ -104,7 +115,7 @@ $KCODE = "UTF8"</code></pre>
 <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>
-<h3>Filesystem references</h3>
+<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>
@@ -119,24 +130,24 @@ $KCODE = "UTF8"</code></pre>
 <p>Also be aware that some applications may not support coercions to all AE file types; you'll need to experiment to find out which coercions are supported.</p>
-<h3>Records</h3>
+<h4>Records</h4>
 <p>The <code>typeAERecord</code> AE type is a struct-like data structure containing zero or more properties. Appscript represents AE records as Ruby hashes. The keys in this hash are usually symbols representing appscript-style property names, although they may also be <code>AEM::AEType</code> values or strings.</p>
 <p>If a hash contains a <code>:class_</code> (or <code>AEM::AEType.new('pcls')</code>) key, appscript will pack the remaining items into an AE record, then coerce it to the type specified by this 'class' property. Similarly, when unpacking an record-like AEDesc with a custom type code, appscript will unpack it as a hash with the type represented by a <code>:class_</code> entry.</p>
-<h3>Types and enumerators</h3>
+<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>
-<h3>Unit types</h3>
+<h4>Unit types</h4>
 <p>Unit type values are represented by instances of the <code>MacTypes::Units</code> class, e.g. <code>MacTypes::Units.inches(3.0)</code>. See the <a href="../mactypes-manual/index.html">mactypes manual</a> for more information.</p>
-<h3>Miscellaneous types</h3>
+<h4>Miscellaneous types</h4>
 <p>The Apple Event Manager defines many other AE types whose names and codes are defined by appscript for completeness. A few of these types are of occasional interest to users, the rest can simply be ignored. In most cases, values of these types will be represented by raw <code>AE::AEDesc</code> instances as appscript doesn't automatically convert them to native objects.</p>
@@ -144,12 +155,14 @@ $KCODE = "UTF8"</code></pre>
 </div>
 <!-- bottom navigation -->
-<div class="navbar">
-	<a href="05_keywordconversion.html">Previous</a> | <a href="index.html">Up</a> | <a href="07_applicationobjects.html">Next</a>
+<div class="footer">
+<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>
-<!--footer-->
-<p class="footer">&copy; 2006-2008 HAS</p>
 </body>
 </html>