rb-appscript 0.5.3 → 0.6.0

data/CHANGES

@@ -1,3 +1,31 @@
+2010-12-20 -- 0.6.1
+
+- removed 32-bit only AE.run_application_event_loop, AE.quit_application_event_loop
+
+- updated AE.launch_application to use LSOpenApplication
+
+
+2010-12-17 -- 0.6.0
+
+- added UTF-8 Encoding support in Ruby 1.9+; added AEMCodecs::Codecs#use_ascii_8bit for optionally disabling it
+
+- AEM::Codecs#pack now accepts Date, DateTime instances; added AEM::Codecs#use_date_time method for unpacking typeLongDateTime descriptors as DateTime instead of Time instances
+
+- removed AE.get_app_terminology() as it relied on deprecated Carbon APIs
+
+- added AE.copy_scripting_definition()
+
+- the OSAX module now now uses OSACopyScriptingDefinition() to obtain scripting addition terminology, so works in both 32- and 64-bit Ruby. Note that in addition to limitations of OSACopyScriptingDefinition (e.g. aete-to-sdef conversion is not 100% reliable), the SdefParser is limited in capability (no support for xi:include, class-extension, synonym elements), but should suffice for parsing relatively simple osax dictionaries.
+
+- modified Terminology.dump() to retrieve aete resources via 'ascrgdte' events; added OSAX.dump() method
+
+- added workaround for transaction id bug in some versions of OS X 10.6
+
+- renamed AEMReference::Base class to AEMReference::Query
+
+- renamed Send::CommandError class to Send::EventError; note that AEM re-exports it as AEM::EventError and [for backwards compatibilty] AEM::CommandError
+
+
 2009-07-18 -- 0.5.3
 
 - fixed pALL code in defaultterminology

data/README

@@ -1,53 +1,73 @@
-Appscript Read Me
+About rb-appscript
+==================
 
-======================================================================
-ABOUT
+Ruby appscript (rb-appscript) is a high-level, user-friendly Apple event 
+bridge that allows you to control AppleScriptable Mac OS X applications 
+from Ruby.
 
-Ruby appscript (rb-appscript) is a high-level Apple event bridge for the Ruby scripting language. rb-appscript is closely based on the Python appscript (py-appscript) bridge.
 
-See the doc folder for more information.
+Requirements
+------------
 
-======================================================================
-REQUIREMENTS
+Appscript supports Ruby 1.8 and later.
 
-- Mac OS X 10.3+
-- Ruby 1.8+
+Appscript requires Mac OS X 10.4 or later.
 
-======================================================================
-INSTALLATION
 
-$ ruby extconf.rb
-$ make
-$ sudo make install
+Installation
+------------
 
--------
+To install appscript, cd to the rb-appscript-0.6.0 directory and run:
 
-Please note that the version of Ruby included with Mac OS X 10.4 (Tiger) is missing the header files needed to build appscript on PPC-based Macs. Tiger users can avoid this issue by installing the latest version of Ruby from <http://www.ruby-lang.org/en/downloads/> and updating their shell login profiles to suit.
+  ruby extconf.rb
+  make
+  make install
 
-======================================================================
-NOTES
 
-- Developer tools for exporting application dictionaries (ASDictionary) and converting application commands from AppleScript to appscript syntax (ASTranslate) are available separately:
+Building appscript from source requires the gcc compiler supplied with 
+Apple's Xcode IDE. Xcode can be obtained from Mac OS X installer disks
+or <http://developer.apple.com>.
 
-	http://appscript.sourceforge.net/tools.html
+Please note that the version of Ruby included with Mac OS X 10.4 (Tiger) 
+is missing the header files needed to build appscript on PPC-based Macs. 
+Tiger users can avoid this issue by installing the latest version of Ruby 
+from <http://www.ruby-lang.org/en/downloads/> and updating their shell 
+login profiles to suit.
 
-- This is a beta release. Please file bug reports if you encounter any problems.
 
-- rb-appscript 0.5.2 contains bug and compatibility fixes; see the CHANGES file and documentation for details.
+Notes
+-----
 
-- rb-appscript currently provides 64-bit support for OS X 10.5 in the following modules: AE, AEM, Appscript. The OSAX module provides partial 64-bit support; see the osax manual for details.
+- rb-appscript 0.6.0 supports string encodings in Ruby 1.9+; see the CHANGES 
+  file and documentation for details.
 
-- ASDictionary 0.11.3 or later is required to use rb-appscript's built-in #help method. If ASDictionary isn't installed, interactive help won't be available but appscript will continue to operate as normal.
+- Developer tools for exporting application dictionaries (ASDictionary) 
+  and converting application commands from AppleScript to appscript syntax 
+  (ASTranslate) are available separately:
 
+    http://appscript.sourceforge.net/tools.html
 
-======================================================================
-AUTHOR
+  ASDictionary 0.13.1 or later is also required to use rb-appscript's built-
+  in #help method. If ASDictionary isn't installed, interactive help won't 
+  be available but appscript will continue to operate as normal.
 
-- HAS -- hhas -at- users - sourceforge - net <http://rb-appscript.rubyforge.org> <http://appscript.sourceforge.net>
+- This is a Beta release. Please report any issues you find, particularly in 
+  the new Ruby 1.9 string encoding support which is not yet heavily tested. 
+  If no major problems are reported, Release Candidate 1 will follow.
 
-======================================================================
-COPYRIGHT
 
-Copyright (C) 2006-2009 HAS 
+Copyright
+---------
 
-Appscript is released under the MIT License. See the LICENSE file for more information.
+Appscript is released into the public domain, except for the following code:
+
+- extconf.rb, which is a modified version of the RubyAEOSA/RubyOSA install 
+  script; see code for details
+
+- safeobject.rb, which is a modified version of basicobject 
+  <http://facets.rubyforge.org> released under the Ruby License; 
+  see code for details
+
+- SendThreadSafe.h/SendThreadSafe.m, which are modified versions of Apple 
+  code (http://developer.apple.com/samplecode/AESendThreadSafe); see code 
+  for details

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

@@ -54,8 +54,6 @@
 <a href="index.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="02_apioverview.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/aem-manual/02_apioverview.html

@@ -37,16 +37,16 @@
 
 <dl>
 <dt>Application</dt>
-<dd>Represents a scriptable application, and provides an <code>event</code> method for constructing Apple events.</dd>
+<dd>Represents a scriptable application, and provides an <code>#event</code> method for constructing Apple events.</dd>
 
 <dt>Event</dt>
-<dd>Represents a ready-to-send Apple event, and provides a <code>send</code> method for sending it. Returned by the <code>Application</code> class's <code>event</code> method.</dd>
+<dd>Represents a ready-to-send Apple event, and provides a <code>#send</code> method for sending it. Returned by the <code>Application</code> class's <code>#event</code> method.</dd>
 
-<dt>CommandError</dt>
+<dt>EventError</dt>
 <dd>Exception raised to indicate an application or Apple Event Manager error.</dd>
 
 <dt>Codecs</dt>
-<dd>Provides <code>pack</code> and <code>unpack</code> methods for converting Ruby values to AE types, and vice-versa. Clients usually don't need to access this class directly.</dd>
+<dd>Provides <code>#pack</code> and <code>#unpack</code> methods for converting Ruby values to AE types, and vice-versa. Clients usually don't need to access this class directly.</dd>
 
 <dt>AEType, AEEnum</dt>
 <dd>Represent Apple event type and enumerator values.</dd>
@@ -72,17 +72,23 @@
 </dl>
 
 
-<p>References are constructed from these base objects using chained property/method calls.</p>
+<p>References are constructed from these base objects using chained method calls.</p>
 
 
-<h3>Modules</h3> <!-- TO DO: improve; move to top -->
+<h3>Modules</h3>
 
-<p>The aem package also exports the following support module:</p>
+<p>The following support modules are also provided:</p>
 
 <dl>
 <dt>FindApp</dt>
 <dd>Provides functions for locating applications by name, bundle id or creator code.</dd>
 
+<dt>AE</dt>
+<dd>Low-level extension that defines an <code>AEDesc</code> class representing Carbon Apple event descriptors (AEDescs). Also provides a number of support methods used by AEM, appscript and related packages.</dd>
+
+<dt>KAE</dt>
+<dd>Exports constants defined by Apple Event Manager and Open Scripting APIs.</dd>
+
 </dl>
 
 
@@ -95,8 +101,6 @@
 <a href="01_introduction.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="03_packingandunpackingdata.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

data/doc/aem-manual/03_packingandunpackingdata.html

@@ -41,7 +41,9 @@
         new
 
     Methods:
-
+        
+        # pack/unpack data
+        
         pack(data) -- convert Ruby data to an AEDesc; will raise
                 a TypeError if data's type/class is unsupported
             data : anything
@@ -51,10 +53,40 @@
                 the AEDesc unchanged if it's an unsupported type
             desc : AEDesc
             Result : anything
-
-        add_unit_types(types) -- register custom unit type definitions
-            types : list -- a list of lists, where each sublist is of form
-                    [name, code] or [name, code, pack_proc, unpack_proc]</code></pre>
+        
+        # compatibility options
+        
+        add_unit_types(types) -- register custom unit type 
+                definitions
+            types : list -- a list of lists, where each sublist  
+                    is of form [name, code, pack_proc, unpack_proc] 
+                    or [name, code]; if the packer and unpacker 
+                    procs are omitted, the AEDesc data is packed/
+                    unpacked as a double-precision float
+        
+        dont_cache_unpacked_specifiers -- by default, object 
+                specifier descriptors returned by an application 
+                are reused for efficiency; invoke this method to 
+                use AppleScript-style behavior instead (i.e. fully 
+                unpacking and repacking object specifiers each time) 
+                for better compatibility with problem applications
+        
+        pack_strings_as_type(code) -- by default, strings are 
+                packed as typeUnicodeText descriptors; some older 
+                non-Unicode-aware applications may require text 
+                to be supplied as typeChar/typeIntlText descriptors
+            code : String -- four-char code, e.g. KAE::TypeChar 
+                    (see KAE module for available text types)
+        
+        use_ascii_8bit -- by default, text descriptors are unpacked 
+                as Strings with UTF-8 Encoding on Ruby 1.9+; invoke 
+                this method to mimic Ruby 1.8-style behavior where 
+                Strings contain UTF-8 encoded data and ASCII-8BIT 
+                Encoding
+        
+        use_datetime -- by default, dates are unpacked as Time 
+                instances; invoke this method to unpack dates as 
+                DateTime instances instead</code></pre>
 
 
 
@@ -71,10 +103,12 @@
 
     Methods:
         code
-            Result : str -- the four-character code
+            Result : str -- Apple event code</code></pre>
 
 
-AEType &lt; AETypeBase -- represents an AE object of typeType
+<p>The four concrete classes are:</p>
+
+<pre><code>AEType &lt; AETypeBase -- represents an AE object of typeType
 
 
 AEEnum &lt; AETypeBase -- represents an AE object of typeEnumeration
@@ -95,8 +129,6 @@ AEKey &lt; AETypeBase -- represents an AE object of typeKeyword</code></pre>
 <a href="02_apioverview.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="04_references.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>

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

@@ -16,7 +16,7 @@
 <div class="navbar">
 <a href="03_packingandunpackingdata.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
-<a href="05_targettingapplications.html">Next</a>
+<a href="05_targetingapplications.html">Next</a>
 
 <span>
 <a href="../appscript-manual/index.html">appscript</a> /
@@ -49,32 +49,28 @@
 <dd>selector data (e.g. in a by-name specifier, this would be a string)</dd>
 </dl>
 
-<p>The Apple Event Manager 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>The Apple Event Manager (and, in turn, the <code>AE</code> 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>
+<p>For example, consider the reference <code>text of document 1</code>. The code for constructing this reference using the low-level <code>AE</code> bridge would be:</p>
 
-<pre><code>ref = OSX::AEDesc.null
+<pre><code>rootref = AE::AEDesc.new("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 ')
+docref = AE::AEDesc.new_list(true).coerce("obj ")
+docref.put_param("want", AE::AEDesc.new("type", "docu"))
+docref.put_param("from", rootref)
+docref.put_param("form", AE::AEDesc.new("enum", "indx"))
+docref.put_param("seld", AE::AEDesc.new("long", "\x00\x00\x00\x01"))
 
-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 ')
+textref = AE::AEDesc.new_list(true).coerce("obj ")
+textref.put_param("want", AE::AEDesc.new("type", "prop"))
+textref.put_param("from", docref)
+textref.put_param("form", AE::AEDesc.new("enum", "prop"))
+textref.put_param("seld", AE::AEDesc.new("type", "ctxt"))
 
-p ref 
-#&lt;AEDesc:0x57594 type='obj '&gt;</code></pre>
+p textref
+#&lt;AE::AEDesc type="obj " size=152&gt;</code></pre>
 
-<p>(The equivalent C code 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>This code works by creating an AEDesc of <code>typeObjectSpecifier</code> to represent each specifier and populating its fields one at a time. 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>
 
@@ -82,7 +78,7 @@ p ref
 
 <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>AEM.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>#by_index</code>).</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>documents</code>, and another to specify the selection, e.g. <code>[1]</code>).</p>
 
 <p>Note that <code>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>
 
@@ -119,25 +115,20 @@ p ref
 <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 (e.g. Script Editor) applets to identify script properties. AEM supports this extra form more for sake of completeness than usefulness.)</p>
+<p>(Actually, there's nine forms if you count the 'user property' reference form, although this is only used by OSA (e.g. AppleScript Editor) 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 methods of other AEM specifier objects, starting with the <code>app</code>, <code>con</code> and <code>its</code> objects that form the root of all aem references.</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" alt="AEM reference class hierarchy" title="AEM reference class hierarchy" /></p>
 
-
-<!-- TO DO: finish -->
-
+<p>Note that the user shouldn't instantiate these classes directly; instead, AEM will instantiate them as appropriate when the client calls the methods of other AEM reference objects, starting with the <code>app</code>, <code>con</code> and <code>its</code> objects that form the root of all AEM references.</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>
+<dt><code>Query</code></dt>
 <dd>Defines comparison and hashing methods.</dd>
 
 <dt><code>PositionSpecifier</code></dt>
@@ -156,7 +147,7 @@ p ref
 
 <h4>Basic methods</h4>
 
-<pre><code>BASE -- Base class for all reference form and test clause classes.
+<pre><code>Query -- 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>
@@ -289,7 +280,7 @@ p ref
 
 <h4>Methods for all test clause classes</h4>
 
-<pre><code>Test &lt; BASE -- represents a comparison/logic test
+<pre><code>Test &lt; Query -- represents a comparison/logic test
 
     Methods:
 
@@ -305,8 +296,8 @@ p ref
                 objects
             Result : Test
 
-        not
-            Result : Test -- apply a logical 'not' test to self</code></pre>
+        not -- apply a logical 'not' test to self
+            Result : Test</code></pre>
 
 
 
@@ -377,6 +368,8 @@ AllElements &lt; MultipleElements -- refers to all elements of the given class
 
 <h4>Reference Roots</h4>
 
+<p>The following classes are used to construct standard AEM references:</p>
+
 <pre><code>ApplicationRoot &lt; PositionSpecifier
        -- AEM.app returns an instance of this class
 
@@ -386,9 +379,20 @@ CurrentContainer &lt; PositionSpecifier
 ObjectBeingExamined &lt; PositionSpecifier
        -- AEM.its returns an instance of this class</code></pre>
 
+<p>Clients shouldn't instantiate the above classes directly; instead, they should use the <code>AEM.app</code>, <code>AEM.con</code> and <code>AEM.its</code> methods which return the appropriate objects.</p>
+
+<p>The <code>CustomRoot</code> class is used to construct AEM references with a non-standard root:</p>
+
+<pre><code>CustomRoot(ReferenceRoot) -- used to construct references with
+        a custom root
 
+    Constructor:
 
-<!-- TO DO: note on AEM_resolve -->
+        initialize(value)
+            value : anything -- value to use as innermost container
+                    in nested object specifiers</code></pre>
+
+<p>Clients can use the <code>AEM.custom_root</code> method to create new <code>CustomRoot</code> instances, passing the root object as method's sole argument.</p>
 
 
 </div>
@@ -398,9 +402,7 @@ ObjectBeingExamined &lt; PositionSpecifier
 <div class="footer">
 <a href="03_packingandunpackingdata.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
-<a href="05_targettingapplications.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
+<a href="05_targetingapplications.html">Next</a>
 </div>
 
 </body>

data/doc/aem-manual/{05_targettingapplications.html → 05_targetingapplications.html}

@@ -2,7 +2,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
 
-<title>rb-aem manual | 5. Targetting Applications</title>
+<title>rb-aem manual | 5. Targeting 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>
@@ -29,7 +29,7 @@
 <!-- content -->
 <div id="content">
 
-<h2>5. Targetting Applications</h2>
+<h2>5. Targeting Applications</h2>
 
 <h3>The <code>Application</code> class</h3>
 
@@ -109,7 +109,7 @@
 
 <h3>Creating <code>Application</code> objects</h3>
 
-<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. If the application can't be launched for some reason (e.g. if it's in the Trash), an <code>AEM::CantLaunchApplicationError</code> error will be raised.</p>
+<p>When targeting 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. If the application can't be launched for some reason (e.g. if it's in the Trash), an <code>AEM::CantLaunchApplicationError</code> error will be raised.</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>typeApplicationURL</code>. The target machine must have Remote Apple Events enabled in its Sharing preferences.</p>
 
@@ -141,7 +141,7 @@ KAE::TypeProcessSerialNumber</code></pre>
 
 <h3>Reconnecting to local applications</h3>
 
-<p>Because local applications are identified by process serial number, an existing <code>Application</code> object created using the <code>by_path</code> constructor will no longer hold a valid <code>AEAddressDesc</code> if the target application subsequently 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>Because local applications are identified by process serial number, an existing <code>Application</code> object created using the <code>by_path</code> constructor will no longer hold a valid <code>AEAddressDesc</code> if the target application subsequently quits. Sending events to an invalid address will cause a <code>EventError</code> -600 ("application isn't running") or -609 ("connection is invalid") to be raised.</p>
 
 <p>The <code>process_exists_for_path?</code> class method can be used to check if a local application is running or not, given its full path.</p>
 
@@ -158,8 +158,6 @@ KAE::TypeProcessSerialNumber</code></pre>
 <a href="04_references.html">Previous</a> &bull;
 <a href="index.html">Up</a> &bull;
 <a href="06_buildingandsendingevents.html">Next</a>
-
-<span>&copy; 2006-2008 HAS</span>
 </div>
 
 </body>