RubyGems - rb-appscript - Versions diffs - 0.2.0 - Mend

rb-appscript 0.2.0

Files changed (83) hide show

data/CHANGES +243 -0
data/LICENSE +1 -0
data/README +42 -0
data/TODO +31 -0
data/doc/aem-manual/01_introduction.html +48 -0
data/doc/aem-manual/02_apioverview.html +89 -0
data/doc/aem-manual/03_packingandunpackingdata.html +98 -0
data/doc/aem-manual/04_references.html +401 -0
data/doc/aem-manual/05_targettingapplications.html +133 -0
data/doc/aem-manual/06_buildingandsendingevents.html +175 -0
data/doc/aem-manual/07_findapp.html +54 -0
data/doc/aem-manual/08_examples.html +85 -0
data/doc/aem-manual/09_notes.html +41 -0
data/doc/aem-manual/aemreferenceinheritance.gif +0 -0
data/doc/aem-manual/full.css +21 -0
data/doc/aem-manual/index.html +43 -0
data/doc/appscript-manual/01_introduction.html +82 -0
data/doc/appscript-manual/02_aboutappscripting.html +244 -0
data/doc/appscript-manual/03_quicktutorial.html +154 -0
data/doc/appscript-manual/04_gettinghelp.html +101 -0
data/doc/appscript-manual/05_keywordconversion.html +91 -0
data/doc/appscript-manual/06_classesandenums.html +174 -0
data/doc/appscript-manual/07_applicationobjects.html +181 -0
data/doc/appscript-manual/08_realvsgenericreferences.html +86 -0
data/doc/appscript-manual/09_referenceforms.html +232 -0
data/doc/appscript-manual/10_referenceexamples.html +142 -0
data/doc/appscript-manual/11_applicationcommands.html +204 -0
data/doc/appscript-manual/12_commandexamples.html +129 -0
data/doc/appscript-manual/13_performanceissues.html +115 -0
data/doc/appscript-manual/14_problemapps.html +193 -0
data/doc/appscript-manual/15_notes.html +84 -0
data/doc/appscript-manual/application_architecture.gif +0 -0
data/doc/appscript-manual/application_architecture2.gif +0 -0
data/doc/appscript-manual/finder_to_textedit_event.gif +0 -0
data/doc/appscript-manual/full.css +21 -0
data/doc/appscript-manual/index.html +49 -0
data/doc/appscript-manual/relationships_example.gif +0 -0
data/doc/appscript-manual/ruby_to_itunes_event.gif +0 -0
data/doc/index.html +30 -0
data/doc/mactypes-manual/index.html +216 -0
data/doc/osax-manual/index.html +169 -0
data/extconf.rb +54 -0
data/misc/adobeunittypes.rb +14 -0
data/misc/dump.rb +72 -0
data/rb-appscript.gemspec +20 -0
data/sample/AB_list_people_with_emails.rb +8 -0
data/sample/Create_daily_iCal_todos.rb +72 -0
data/sample/Hello_world.rb +9 -0
data/sample/List_iTunes_playlist_names.rb +7 -0
data/sample/Make_Mail_message.rb +29 -0
data/sample/Open_file_in_TextEdit.rb +9 -0
data/sample/Organize_Mail_messages.rb +57 -0
data/sample/Print_folder_tree.rb +12 -0
data/sample/Select_all_HTML_files.rb +8 -0
data/sample/Set_iChat_status.rb +20 -0
data/sample/Simple_Finder_GUI_Scripting.rb +14 -0
data/sample/Stagger_Finder_windows.rb +21 -0
data/sample/TextEdit_demo.rb +126 -0
data/sample/iTunes_top40_to_html.rb +64 -0
data/src/lib/_aem/aemreference.rb +1006 -0
data/src/lib/_aem/codecs.rb +617 -0
data/src/lib/_aem/connect.rb +100 -0
data/src/lib/_aem/findapp.rb +83 -0
data/src/lib/_aem/mactypes.rb +228 -0
data/src/lib/_aem/send.rb +257 -0
data/src/lib/_aem/typewrappers.rb +57 -0
data/src/lib/_appscript/defaultterminology.rb +245 -0
data/src/lib/_appscript/referencerenderer.rb +132 -0
data/src/lib/_appscript/reservedkeywords.rb +107 -0
data/src/lib/_appscript/terminology.rb +314 -0
data/src/lib/aem.rb +216 -0
data/src/lib/appscript.rb +830 -0
data/src/lib/kae.rb +1484 -0
data/src/lib/osax.rb +171 -0
data/src/rbae.c +766 -0
data/test/README +1 -0
data/test/test_aemreference.rb +112 -0
data/test/test_appscriptreference.rb +102 -0
data/test/test_codecs.rb +159 -0
data/test/test_findapp.rb +24 -0
data/test/test_mactypes.rb +67 -0
data/test/testall.sh +9 -0
metadata +143 -0

data/doc/aem-manual/04_references.html ADDED Viewed

@@ -0,0 +1,401 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<title>aem | 4. References</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<style type="text/css" media="all"><!--@import url(full.css);--></style>
+</head>
+<body>
+<h1>4. References</h1>
+<!-- top navigation -->
+<div class="navbar">
+	<a href="03_packingandunpackingdata.html">Previous</a> | <a href="index.html">Up</a> | <a href="05_targettingapplications.html">Next</a>
+</div>
+<!-- content -->
+<div id="content">
+<h2>About references</h2>
+<p>An Apple Event Object Model query (a.k.a. "reference") essentially consists of a linked list made up of one or more Apple event descriptors (AEDescs) of, for the most part, <code>typeObjectSpecifier</code>. Object specifiers are used to identify properties and elements in the application's AEOM. Each object specifer contains four fields:</p>
+<dl>
+<dt>want</dt>
+<dd>four-char-code indicating desired element(s)'s class code (e.g. 'docu' = document), or 'prop' if it's a property specifier</dd>
+<dt>from</dt>
+<dd>an object specifer identifying container object(s)</dd>
+<dt>form</dt>
+<dd>four-char-code indicating how the element(s) should be selected (by index ['indx'], name ['name'], etc.), or 'prop' if it's a property specifier</dd>
+<dt>seld</dt>
+<dd>selector data (e.g. in a by-name specifier, this would be a string)</dd>
+</dl>
+<p>The Apple Event Manager (and, in turn, the ae extension) provides several ways to construct object specifiers and assemble them into a complete reference, but these are all rather verbose and low-level. Aem hides all these details behind an object-oriented wrapper that uses chained property and method calls to gather the data needed to create object specifiers and assemble them into linked lists.</p>
+<p>For example, consider the reference <code>text of document 1</code>. The code for constructing this reference using a relatively low-level bridge, in this case RubyAEOSA, would be:</p>
+<pre><code>ref = OSX::AEDesc.null
+ref = OSX::AEDesc.record({
+    'want' =&gt; OSX::AEDesc.new('type', 'docu'),
+    'from' =&gt; ref,
+    'form' =&gt; OSX::AEDesc.new('enum', 'indx'),
+    'seld' =&gt; 1,
+}).coerce('obj ')
+ref = OSX::AEDesc.record({
+    'want' =&gt; OSX::AEDesc.new('type', 'prop'),
+    'from' =&gt; ref,
+    'form' =&gt; OSX::AEDesc.new('enum', 'prop'),
+    'seld' =&gt; OSX::AEDesc.new('type', 'ctxt'),
+}).coerce('obj ')
+p ref
+#&lt;AEDesc:0x57594 type='obj '&gt;</code></pre>
+<p>(The ae extension is even lower-level and more verbose.)</p>
+<p>This code works by creating each AEDesc of <code>typeAERecord</code> in turn, populating it, then coercing it to <code>typeObjectSpecifier</code>. Each AEDesc is nested within the next to form a linked list of object specifier records; the last (innermost) descriptor in the finished list indicates the reference's root object in the AEOM (in this case, the <code>application</code> object, which is represented by a null descriptor).</p>
+<p>Now, compare the above with the aem equivalent:</p>
+<pre><code>AEM.app.elements('docu').by_index(1).property('ctxt')</code></pre>
+<p>As you can see, aem still uses low-level four-character codes to identify the <code>text</code> property and <code>document</code> class, but is otherwise a high-level object-oriented API. Once again, each reference begins with a root object, in this case <code>app</code>. New aem specifiers are constructed by method calls; each call returning a new specifier object whose own methods can be called, and so on. This allows clients to build up a chain of aem specifier objects that aem can later pack into AEDescs for sending to applications.</p>
+<p>One more thing to notice: in aem, specifying a class of elements and indicating which of those elements should be selected are performed by separate method calls, although the information provided will eventually be packed into a single AEDesc of <code>typeObjectSpecifier</code>. This two-step approach makes it easier to integrate aem with the higher-level appscript bridge, which also uses two calls to construct element specifiers (one to specify the element class, e.g. <code>document</code>, and another to specify the selection, e.g. <code>[1]</code>).</p>
+<p>Note that <code>AEM.app.elements('docu')</code> is itself a valid reference, identifying <em>all</em> the document elements of the application class. You do not have to call an explicit <code>all</code> selector (indeed, none is provided) as aem automatically handles the details for you. Aem even allows for some convenient shorthand, e.g. writing:</p>
+<pre><code>AEM.app.elements('docu').by_filter(...).first</code></pre>
+<p>is equivalent to writing:</p>
+<pre><code>AEM.app.elements('docu').by_filter(...).elements('docu').first</code></pre>
+<p>This allows clients to specify the first document that matches the given condition without having to specify the element class a second time. In AppleScript, the equivalent to this is:</p>
+<pre><code>first document whose ...</code></pre>
+<p>which is short for:</p>
+<pre><code>first document of (documents whose ...)</code></pre>
+<p>(Again, this additional behaviour primarily exists to serve the syntactically sugared appscript layer.)</p>
+<h2>Reference forms</h2>
+<p>Aem defines a number of classes representing each of the AEOM reference forms. There are eight AEOM reference forms:</p>
+<ul>
+<li>insertion location</li>
+<li>property</li>
+<li>element by absolute position (index or ordinal)</li>
+<li>element by name</li>
+<li>element by id</li>
+<li>element by relative position</li>
+<li>elements by range</li>
+<li>elements by test</li>
+</ul>
+<p>(Actually, there's nine forms if you count the 'user property' reference form, although this is only used by OSA applets to identify script properties. Aem supports this extra form more for sake of completeness than usefulness.)</p>
+<p>Each of these reference forms is represented by a different aem specifier class, apart from the absolute position form which is represented by three different classes according to the kind of selector used: a numerical index (e.g. <code>1</code>, <code>-3</code>), a named ordinal identifying a single element (<code>first</code>, <code>middle</code>, <code>last</code>, <code>any</code>), or a named ordinal identifying all elements (<code>all</code>).</p>
+<p>The following diagram shows the aem reference class hierarchy (slightly simplified for legibility); concrete classes are shown in bold:</p>
+<p><img src="aemreferenceinheritance.gif" title="aem reference class hierarchy" />
+<p>Note that the user shouldn't instantiate these classes directly; instead, aem will instantiate them as appropriate when the client calls the properties and methods of one of the three root objects - <code>app</code>, <code>con</code>, <code>its</code> - of of other aem reference objects.</p>
+<p>In fact, it really isn't necessary to remember the reference class hierarchy at all, only to know which concrete classes implement which methods. All user-accessible properties and methods are defined by just four superclasses:</p>
+<dl>
+<dt><code>BASE</code></dt>
+<dd>Defines comparison and hashing methods.</dd>
+<dt><code>PositionSpecifier</code></dt>
+<dd>Defines methods for identifying properties and all elements, insertion locations, elements by relative position. Also defines comparison and logical test methods for use in constructing its-based references.</dd>
+<dt><code>MultipleElements</code></dt>
+<dd>Defines methods for identifying specific elements of a multi-element reference.</dd>
+<dt><code>Test</code></dt>
+<dd>Defines logical test methods for use in constructing its-based references.</dd>
+</dl>
+<h2>Base classes</h2>
+<h3>Basic methods</h3>
+<pre><code>BASE -- Base class for all reference form and test clause classes.
+    hash -- aem references can be used as dictionary keys
+    ==(value) -- aem references can be compared for equality</code></pre>
+<h3>Methods for all position specifiers</h3>
+<pre><code>PositionSpecifier &lt; Specifier -- base class for all property and element
+        reference forms (i.e. all forms except insertion location)
+    Methods:
+        start
+            Result : InsertionSpecifier
+        end
+            Result : InsertionSpecifier
+        before
+            Result : InsertionSpecifier
+        after
+            Result : InsertionSpecifier
+        property(property_code)
+            property_code : str -- four-char code
+            Result : Property
+        user_property(name)
+            name : str
+            Result : UserProperty
+        elements(class_code)
+            class_code : str -- four-char code
+            Result : AllElements
+        previous(class_code)
+            class_code : str -- four-char code
+            Result : Element
+        next(class_code)
+            class_code : str -- four-char code
+            Result : Element
+        -- Note: following methods are for use on
+           its-based references only
+        gt(val) -- self is greater than value
+            val : anything
+            Result : Test
+        ge(val) -- self is greater than or equal to value
+            val : anything
+            Result : Test
+        eq(val) -- self equals value
+            val : anything
+            Result : Test
+        ne(val) -- self does not equal value
+            val : anything
+            Result : Test
+        lt(val) -- self is less than value
+            val : anything
+            Result : Test
+        le(val) -- self is less than or equal to value
+            val : anything
+            Result : Test
+        starts_with(val) -- self starts with value
+            val : anything
+            Result : Test
+        ends_with(val) -- self ends with value
+            val : anything
+            Result : Test
+        contains(val) -- self contains value
+            val : anything
+            Result : Test
+        is_in(val) -- self is in value
+            val : anything
+            Result : Test
+        and(*operands) -- equivalent to self.eq(True).and(*operands)
+            operands : Test/Test
+            Result : Test
+        or(*operands) -- equivalent to self.eq(True).or(*operands)
+            operands : Test/Test
+            Result : Test
+        not
+            Result : Test -- equivalent to self.eq(True).not</code></pre>
+<h3>Methods for all multi-element specifiers</h3>
+<pre><code>MultipleElements &lt; PositionSpecifier -- base class for all multi-
+        element reference forms
+    Methods:
+        first
+            Result : Element
+        middle
+            Result : Element
+        last
+            Result : Element
+        any
+            Result : Element
+        by_index(key)
+            key : integer -- normally an integer, though some apps may
+                    accept other types (e.g. Finder accepts a MacTypes::Alias)
+            Result : ElementByIndex
+        by_name(key)
+            key : string -- the object's name
+            Result : ElementByName
+        by_id(key)
+            key : anything -- the object's unique id
+            Result : ElementByID
+        by_range(start_ref, end_ref)
+            start_ref : Element -- an app- or con-based reference
+            end_ref : Element -- an app- or con-based reference
+            Result : ElementByRange
+        by_filter(testref)
+            test_ref : Test -- an its-based reference
+            Result : ElementsByFilter</code></pre>
+<h3>Methods for all test clause classes</h3>
+<pre><code>Test &lt; BASE -- represents a comparison/logic test
+    Methods:
+        and(*operands) -- apply a logical 'and' test to self and
+                one or more other operands
+            *operands : Test -- one or more comparison/logic test
+                objects
+            Result : Test
+        or(*operands) -- apply a logical 'or' test to self and one
+                    or more other operands
+            *operands : Test -- one or more comparison/logic test
+                objects
+            Result : Test
+        not
+            Result : Test -- apply a logical 'not' test to self</code></pre>
+<h2>Concrete classes</h2>
+<h3>Insertion location reference form</h3>
+<pre><code>InsertionSpecifier &lt; Specifier -- refers to insertion point before or after/at
+        start or end of element(s); e.g. ref.before</code></pre>
+<h3>Property reference forms</h3>
+<pre><code>Property &lt; PositionSpecifier -- refers to a property (whose value
+        may be a basic type, application object or reference);
+        e.g. ref.property('ctxt')
+UserProperty &lt; PositionSpecifier -- refers to a user-defined property
+        (typically in an OSA applet); e.g. ref.user_property('myVar')</code></pre>
+<h3>Single element reference forms</h3>
+<pre><code>ElementByIndex &lt; SingleElement -- refers to a single element in the referenced
+        container object(s) by index; e.g. ref.by_index(3)
+ElementByName &lt; SingleElement -- refers to a single element in the referenced
+        container object(s) by name; e.g. ref.by_name('Documents')
+ElementByID &lt; SingleElement -- refers to a single element in the referenced container
+        object(s) by unique id; e.g. ref.by_id(3456)
+ElementByOrdinal &lt; SingleElement -- refers to first, middle, last or any element in
+        the referenced container object(s); e.g. ref.first
+ElementByRelativePosition &lt; SingleElement -- refers to the previous or next element
+        of the given class in the referenced container object(s);
+        e.g. ref.next('cpar')</code></pre>
+<h3>Multiple element reference forms</h3>
+<pre><code>ElementsByRange &lt; MultipleElements -- refers to a range of elements
+        in the referenced container object(s) (including start and
+        end points); e.g. ref.by_range(AEM.con.elements('cpar').by_index(2),
+                AEM.con.elements('cpar').last)
+ElementsByFilter &lt; MultipleElements -- refers to all elements in the
+        referenced container object(s) that fulfill a given condition;
+        e.g. ref.by_filter(AEM.its.name.startswith('a'))
+AllElements(MultipleElements) -- refers to all elements of
+        the given class in the referenced container object(s);
+        e.g. ref.elements('docu')</code></pre>
+<h3>Tests</h3>
+<p>The <code>Test</code> class represents a comparison test or logical test, and defines methods for composing additional logical tests on top of these. Each kind of test clause is represented by a different subclass of the main <code>Test</code> class. The details are not that important, however, so they're not listed here.</p>
+<h3>Reference Roots</h3>
+<pre><code>ApplicationRoot &lt; PropertySpecifier -- AEM.app returns an instance of
+       this class
+CurrentContainer &lt; PropertySpecifier -- AEM.con returns an instance of
+       this class
+ObjectBeingExamined &lt; PropertySpecifier -- AEM.its returns an instance
+       of this class</code></pre>
+<!-- TO DO: note on AEM_resolve -->
+</div>
+<!-- bottom navigation -->
+<div class="navbar">
+	<a href="03_packingandunpackingdata.html">Previous</a> | <a href="index.html">Up</a> | <a href="05_targettingapplications.html">Next</a>
+</div>
+<!--footer-->
+<p class="footer">&copy; 2006 HAS</p>
+</body>
+</html>

data/doc/aem-manual/05_targettingapplications.html ADDED Viewed

@@ -0,0 +1,133 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<title>aem | 5. Targetting Applications</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<style type="text/css" media="all"><!--@import url(full.css);--></style>
+</head>
+<body>
+<h1>5. Targetting Applications</h1>
+<!-- top navigation -->
+<div class="navbar">
+	<a href="04_references.html">Previous</a> | <a href="index.html">Up</a> | <a href="06_buildingandsendingevents.html">Next</a>
+</div>
+<!-- content -->
+<div id="content">
+<h2>The <code>Application</code> class</h2>
+<p>The <code>Application</code> class represents an application to which Apple events will be sent. Its constructor allows applications to be identified in one of four ways: by full path, by eppc URL, by custom <code>AEAddressDesc</code>, or the host application if no other value is given. Its main method, <code>event</code>, is used to construct the Apple events to send. Several utility methods are also provided.</p>
+<pre><code>Application -- the target application
+    Class methods:
+        launch(path) -- launch an application in background if not
+                already running, and send it a 'ascrnoop' event
+            path : string -- application's path, e.g. '/Applications/iCal.app'
+        is_running?(path) -- Is an application currently running?
+            path : string -- application's path, e.g. '/Applications/iCal.app'
+            Result : bool
+    Constructors:
+        by_path(path)
+            path : string -- full path to local application
+                    (e.g. '/Applications/TextEdit.app')
+        by_pid(pid)
+            pid : integer -- Unix process id
+        by_url(url)
+            url : string -- url for remote process
+                    (e.g. 'eppc://user:pass@0.0.0.1/TextEdit')
+        by_desc(desc)
+            desc : AEDesc -- AEAddressDesc for application
+        current -- the host process
+    Methods:
+        event(...) -- construct an Apple event (see next chapter for details)
+        start_transaction -- start a new transaction; all Events
+                constructed after start_transaction is called will
+                belong to the same transaction until end_transaction
+                or abort_transaction is called
+        end_transaction -- end the current transaction
+        abort_transaction -- abort the current transaction
+        reconnect -- Make sure this Application object has a valid
+                AEAddressDesc for the target application, relaunching
+                the target application if it's not currently running.
+                (Note: this only works for Application objects created
+                via the by_path constructor.)</code></pre>
+<h2>Creating <code>Application</code> objects</h2>
+<p>When targetting a local application by path, the full path to the application (or application bundle) must be given, including a <code>.app</code> suffix if present. Note that aem identifies local applications by process serial number for reliability. If the target application is not already running when a new <code>Application</code> instance is created, it will be started automatically so that a PSN can be acquired.</p>
+<p>If the <code>by_url</code> constructor is used, its <code>url</code> argument should be an eppc URL string. Aem will pack this as an <code>AEDesc</code> of <code>typeApplSignature</code>. The target machine must have Remote Apple Events enabled in its Sharing preferences.</p>
+<p>Clients can also supply their own <code>AEAddressDesc</code> if they prefer. This should be an <code>AE::AEDesc</code> of one of the following types:</p>
+<pre><code>KAE::TypeApplicationBundleID
+KAE::TypeApplicationURL
+KAE::TypeApplSignature
+KAE::TypeKernelProcessID
+KAE::TypeMachPort
+KAE::TypeProcessSerialNumber</code></pre>
+<p>See the Apple Event Manager documentation for more information on these addressing modes.</p>
+<h2>Launching applications</h2>
+<p><code>Application.launch</code> is a class method attached to the <code>Application</code> class for convenience. It allows a non-running application to be launched without sending it the 'run' event (<code>aevtoapp</code>) normally sent to applications - a 'no-op' event (<code>ascrnoop</code>) is sent instead. It should be called before creating an <code>Application</code> object for the target application, otherwise the application will be launched as normal.</p>
+<h2>Transactions</h2>
+<p>The <code>start_transaction</code> and <code>end_transaction</code> methods are used to start and stop transaction sessions for applications that support this. All events <em>created</em> while a transaction session is active will be identified as part of that transaction.</p>
+<p>Note that during a transaction, sending the application an event not created during that transaction will cause an error. Similarly, sending the application an event created during a transaction after that transaction has ended will cause an error.</p>
+<p>The <code>end_transaction</code> method must be called to close both successful and failed transactions on completion. If a transaction session is accidentally left open, aem will attempt to close it when the <code>Application</code> object is garbage-collected, although this cannot be guaranteed to succeed.</p>
+<h2>Reconnecting to local applications</h2>
+<p>Because local applications are identified by process serial number, an existing <code>Application</code> object created using the <code>path</code> argument will no longer hold a valid <code>AEAddressDesc</code> if the target application quits. Sending events to an invalid address will cause a <code>CommandError</code> -600 ("application isn't running") or -609 ("connection is invalid") to be raised.</p>
+<p>The <code>is_running?</code> class method can be used to check if a local application is running or not, given its full path.</p>
+<p>Calling the <code>reconnect</code> method will create a new <code>AEAddressDesc</code> for an existing <code>Application</code> object. If the application is not running at the time, it will be started automatically.</p>
+<p>Note that only <code>Event</code> instances created after <code>reconnect</code> is called will receive the new <code>AEAddressDesc</code>.  Any <code>Event</code> instances created before <code>reconnect</code> is called will still contain the old <code>AEAddressDesc</code>. Also note that the <code>reconnect</code> method will only work for <code>Application</code> objects created using the <code>by_path</code> constructor.</p>
+</div>
+<!-- bottom navigation -->
+<div class="navbar">
+	<a href="04_references.html">Previous</a> | <a href="index.html">Up</a> | <a href="06_buildingandsendingevents.html">Next</a>
+</div>
+<!--footer-->
+<p class="footer">&copy; 2006 HAS</p>
+</body>
+</html>