rb-appscript 0.6.0 → 0.6.1

Sign up to get free protection for your applications and to get access to all the features.
data/CHANGES CHANGED
@@ -1,9 +1,11 @@
1
- 2010-12-20 -- 0.6.1
1
+ 2010-03-19 -- 0.6.1
2
2
 
3
3
  - removed 32-bit only AE.run_application_event_loop, AE.quit_application_event_loop
4
4
 
5
5
  - updated AE.launch_application to use LSOpenApplication
6
6
 
7
+ - minor documentation fixes
8
+
7
9
 
8
10
  2010-12-17 -- 0.6.0
9
11
 
data/README CHANGED
@@ -17,7 +17,7 @@ Appscript requires Mac OS X 10.4 or later.
17
17
  Installation
18
18
  ------------
19
19
 
20
- To install appscript, cd to the rb-appscript-0.6.0 directory and run:
20
+ To install appscript, cd to the rb-appscript-0.6.1 directory and run:
21
21
 
22
22
  ruby extconf.rb
23
23
  make
@@ -38,7 +38,7 @@ login profiles to suit.
38
38
  Notes
39
39
  -----
40
40
 
41
- - rb-appscript 0.6.0 supports string encodings in Ruby 1.9+; see the CHANGES
41
+ - rb-appscript 0.6.0+ supports string encodings in Ruby 1.9+; see the CHANGES
42
42
  file and documentation for details.
43
43
 
44
44
  - Developer tools for exporting application dictionaries (ASDictionary)
@@ -51,10 +51,6 @@ Notes
51
51
  in #help method. If ASDictionary isn't installed, interactive help won't
52
52
  be available but appscript will continue to operate as normal.
53
53
 
54
- - This is a Beta release. Please report any issues you find, particularly in
55
- the new Ruby 1.9 string encoding support which is not yet heavily tested.
56
- If no major problems are reported, Release Candidate 1 will follow.
57
-
58
54
 
59
55
  Copyright
60
56
  ---------
@@ -67,7 +67,7 @@
67
67
 
68
68
  <p><img src="ruby_to_itunes_event.gif" alt="Sending Apple event from Ruby to iTunes"/></p>
69
69
 
70
- <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>
70
+ <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>core/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>
71
71
 
72
72
 
73
73
  <h3>What is a scriptable application?</h3>
@@ -83,7 +83,7 @@
83
83
  <ul>
84
84
  <li>support automatic translation of human-readable terminology to four-letter codes in high-level bridges such as AppleScript and appscript</li>
85
85
 
86
- <li>generate basic human-readable documentation by applications such as Script Editor and HTMLDictionary.</li>
86
+ <li>generate basic human-readable documentation by applications such as AppleScript Editor and ASDictionary.</li>
87
87
  </ul>
88
88
 
89
89
  <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>
@@ -2,9 +2,8 @@ require "rubygems"
2
2
 
3
3
  spec = Gem::Specification.new do |s|
4
4
  s.name = "rb-appscript"
5
- s.version = "0.6.0"
5
+ s.version = "0.6.1"
6
6
  s.homepage = "http://appscript.sourceforge.net/"
7
- s.rubyforge_project="rb-appscript"
8
7
  s.summary="Ruby appscript (rb-appscript) is a high-level, user-friendly Apple event bridge that allows you to control scriptable Mac OS X applications using ordinary Ruby scripts."
9
8
  s.files = Dir["**/*"].delete_if { |name| ["MakeFile", "ae.bundle", "mkmf.log", "rbae.o", "SendThreadSafe.o", "src/osx_ruby.h", "src/osx_intern.h"].include?(name) }
10
9
  s.extensions = "extconf.rb"
metadata CHANGED
@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
5
5
  segments:
6
6
  - 0
7
7
  - 6
8
- - 0
9
- version: 0.6.0
8
+ - 1
9
+ version: 0.6.1
10
10
  platform: ruby
11
11
  authors: []
12
12
 
@@ -14,7 +14,7 @@ autorequire:
14
14
  bindir: bin
15
15
  cert_chain: []
16
16
 
17
- date: 2011-02-07 00:00:00 +00:00
17
+ date: 2011-03-19 00:00:00 +00:00
18
18
  default_executable:
19
19
  dependencies: []
20
20
 
@@ -148,7 +148,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
148
148
  version: "0"
149
149
  requirements: []
150
150
 
151
- rubyforge_project: rb-appscript
151
+ rubyforge_project:
152
152
  rubygems_version: 1.3.7
153
153
  signing_key:
154
154
  specification_version: 3