Re: [Rubycocoa-talk] Ruby/Cocoa and CoreData

[Jonathan P. <jp...@dc...>]

>> I think I'd like to figure out the problem with the Cocoa-provided  
>> mechanisms, since then the dependency tracking should just work  
>> (since we already send change notifications through kvc_accessor).
>
> I hadn't seen kvc_reader, kvc_writer or kvc_accessor previously  
> either - they remove the need for cocoa_property. (they weren't in  
> the 0.4.1 release that I started out with).

Yes, those were added after 0.4.1. I think there are quite a few  
limitations in 0.4.1 release that make things hard! The current CVS  
has got some nice features added though (like my exception-wrapping  
patch, which stops applications from dying unexpectedly if any  
uncaught ruby exceptions occur). :)

>> I still think cocoa_depends_on is useful since it has far nicer  
>> syntax, and can easily be reimplemented in terms of  
>> setKeys_trigger... once that works.
>
> OK, sounds like a good idea. I no longer have any basis for  
> asserting that setKeys_trigger... doesn't work anymore, it seems fine.

Would 'kvc_depends_on' be a better name, to match up with the other  
kvc_* methods?