According to <http://developer.apple.com/documentation/Cocoa/ Conceptual/CoreData/Articles/cdMultiThreading.html>, "For the most part, the Application Kit is not thread safe; in particular, Cocoa bindings and controllers are not thread safe".
And from <http://developer.apple.com/documentation/Cocoa/Conceptual/ Multithreading/articles/CocoaSafety.html> -- Immutable objects are generally thread-safe. Once you create them, you can safely pass these objects to and from threads. On the other hand, mutable objects are generally not thread-safe. Implementing delegates in REALbasic is certainly possible, and possible in a type-safe way. I wrote an article from RB Developer that explained how to do it. Charles Yeomans On Feb 20, 2007, at 5:23 PM, Stefan wrote: > > Definitely. I wouldn't even start. > > Notifications, delegates, and all such stuff. Moreover much of cocoa > is thread-safe, while RB is not. > > All in all, I would propose to start a cocoa app new using the xcode > tool chain. > > Am 20.02.2007 um 17:14 schrieb Charles Yeomans: > >> My understanding is that there will be a lot of significant >> differences. >> >> Charles Yeomans >> >> On Feb 20, 2007, at 12:50 AM, Ryan Dary wrote: >> >>> The REALbasic Cocoa implementation is probably going to just be a >>> "buzzword" effect, but no REAL difference. >>> >>> - Ryan Dary >>> >>> Thom McGrath wrote: >>> >>>> The bottom line is this. If you want your application to look, >>>> feel, and >>>> behave like a true Mac OS X app then you need to use true Cocoa. >>>> You'll >>>> gain access to the new Mac OS X features long before somebody >>>> "hacks" >>>> them into RB, or RS pulls a half-assed job of implementing them. >>> >>>> -- >>>> Thom McGrath >>>> The ZAZ Studios _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
