From: Jonathan P. <jp...@dc...> - 2006-04-08 16:33:31
|
On 7 Apr 2006, at 6:00, Jordan Breeding wrote: > i have a few questions regarding RubyCocoa and RubyAeosa: > > 1) is RubyAeosa no longer supported at all? it hasn't been touched > in a long time and it doesn't seem to want to even configure itself > on 10.4.6. I've been using it a fair amount on 10.4.5, but have yet to try it on 10.4.6 (not upgraded yet). I've also been looking at creating a gem version of aeosa, to make it easier to install. Can you give specific error messages etc you're experiencing? > 2) if RubyAeosa is no longer supported than is there a way to run > an AppleScript through RubyCocoa and take a returned list/array > from AppleScript and get the ruby types for everything? i would > then also like to do some computations and run some command line > programs based on some of the contents of the list/array and extra > some file aliases from the array as well, which i would like to be > able to return directly to AppleScript/Automator from ruby. is any > of this feasible/possible? if i can at least get the AppleScript > working and the results into ruby types i can do without returning > things back to AppleScript/Automator, although that would make my > life slightly easier. RubyAeosa is the way to go I think. I have been developing a ruby project similar to python's appscript, which allows you to operate applescript-style things directly in ruby. Would you be interested in testing it? e.g., finder = OSX::Application.new("Finder") puts finder.selection[0].name which would be similar to the AppleScript: tell application "Finder" get name of first item of (selection as list) end tell |