Nsprogressindicator not updating
Ruby Cocoa and Py Obj C already give us full access to the native Scripting Bridge, but I think this often becomes unwieldy.We end up writing Ruby (or Python) versions of Objective-C calls on Apple Script APIs. In fact, my biggest complaint comes from the terminology.Most importantly, Leopard integrates both languages more tightly into the operating system.
Unfortunately, Cocoa seems to have a one-bridge-at-a-time rule.
Still, I think this issue will smooth itself out with future updates.
We can also use Ruby and Python to communicate with scriptable applications using the Open Scripting Architecture (OSA).
Both include a bridge to the Objective-C runtime, and both can communicate with scriptable applications.
Leopard ships with the popular Ruby Cocoa and Py Obj C libraries already installed.
For example, to update the current version of Rails, just type: However, if you're like me, the thought of wildly upgrading your system libraries makes your stomach churn. This also makes rolling back to factory defaults quite easy. Leopard keeps built-in libraries in the /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ folder. Just to be complete, Leopard stashes the Ruby Cocoa files in a third location: /System/Library/Frameworks/Ruby Cocoa.framework I highly recommend poking around in these directoriesparticularly the Ruby Cocoa header files.