From: Chris Gehlker Date: 2002-06-30T22:08:07+09:00 Subject: Re: Ruby on Mac OS X On 6/30/02 3:37 AM, "Tobias Reif" wrote: > Chris Gehlker wrote: > > >>> I also think that it would be awesome if Apple worked on native GUI >>> toolkit for Ruby. (no AppleScript required) >>> >> You lost me a bit there. What's missing from the C binding to Cocoa or even >> Carbon/Core Foundation? > > > I don't know about what's avilable. I just thought that since on > http://www.imasy.or.jp/~hisa/mac/rubycocoa/ > there's > "Ways not to use RubyCocoa: > > * development of a commercial software > * development of a mission critical software > * development of a long life cycle software" > > Apple could help turn this into a fully solid kit. I think that's just Fujimoto being conservative. Maybe I'll discover a flaw with his implementation as I use it more, but I think it's more of a comment on the rapid evolution of Ruby. I haven't seen a performance difference between the bindings to Cocoa and the ones to Fx or Qt. Ruby AEOSA, on the other hand, works but needs to be more convenient. People in the workflow business just can't be expected to look up 4 letter codes. There needs to be a way to use the dictionary vocabulary directly. Apple could be of great help here by open sourcing Script Editor or even publishing the tricky bits as sample code. I have read on their Project Builder list that they intend at some point to have a public interface for adding languages to PB. As I think of it, that might work as well. -- There is, nevertheless, a certain respect and a general duty of humanity that ties us, not only to beasts that have life and sense, but even to trees and plants. -Michel de Montaigne, essayist (1533-1592)