On Nov 23, 2006, at 4:36 PM, Terry Ford wrote:
Yes, but it depends what you're doing. If you're manipulating
controls? No. Windows? Some things (though you'll have to modify
your code a bit). Misc system calls? Yes.
Doesn't that depend on the cross support of Carbon to Cocoa that
the OS controls? Rb still doesn't support declares to Cocoa yet and
the likelyhood of them doing this within their previous time frame
is unlikely considering the UB change problems.
You can Cocoa from Carbon and Carbon from Cocoa. It just works.
Will things like system colors one gets via carbon declares be
right for Cocoa?
Yes, and you can also get them through Cocoa.
Which isn't supported yet in Rb.
What's your point? The original poster asked about when it does.
And that aside, you certainly can call into Cocoa now. It's just a
pain to have to use the Obj-C runtime to do it. See Charles's code.
Well, it definitely depends on what modules you want to create.
Cocoa has a lot of stuff that's easier to use than Carbon.
That's well known. But I wonder where the focus is now in Rb since
Apple's switch to Intel chips. PEF apps will probably be
depreciated and Mach-O won't be far behind. Once again, Intel will
rule and PC users will be the true winners on both Mac and MS.
Let's face the facts. Money determines everything and, if the
market for Intel use is the largest, that will be the focus for
REAL Software.
I don't see what your point is. What does this have to do with Carbon
declares in Cocoa?
(Being picky: They aren't going to deprecate Mach-O, they'd deprecate
Carbon since Cocoa uses Mach-O)
--
Seth Willits
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
