Is Panther really worth it???

[Fukui]

Originally posted by johnnyjibbs
How come then, when I right click the widgets in Safari, nothing happens? I thought Safari was Cocoa?

No, I mean in Carbon right clicking is not always recognized correctly (try it in the Finder or Quicktime), this behavior is probably because it came from the OS 9 where ony 1 button was ever used, but Cocoa has always had support for multiple button mice, so it had to differentiate between right/left/middle etc...

 

[Counterfit]

The method I used was to try and move a window so that part is obscured by the Dock. Cocoa apps don't let you move anything behind the Dock, but Carbon apps are not "Dock-aware" and let you move them freely.

 

[coolsoldier]

Originally posted by Counterfit
The method I used was to try and move a window so that part is obscured by the Dock. Cocoa apps don't let you move anything behind the Dock, but Carbon apps are not "Dock-aware" and let you move them freely.

This only works if you have your dock on the bottom of the screen. I have my dock on the left side of the screen, and it lets me move any program behind the dock, but if I move the dock to the bottom of the screen, then it keep windows from being blocked by the dock. Also, carbon apps can be written to be dock aware, so that's not quite a foolproof method.

But, if a carbon app is written to be dock aware and support system services, then it really doesn't matter much if it's not a cocoa app, does it?

 

[Fukui]

Originally posted by coolsoldier

But, if a carbon app is written to be dock aware and support system services, then it really doesn't matter much if it's not a cocoa app, does it?

No, it doesn't, but it is more difficult for developers to. In Cocoa, these things are automatic.

But yea, I agree, we really SHOULD NOT be able to tell the difference at all. Back in the public beta days, I couldn't really tell, but when you use an app like photoshop with its wierd pallets all over the place, or word and Dreamweaver, they just scream carbon...apple has done a good job of making them appear the same though, third party give carbon a bad name.

I think though, its annoying that apple has to concurrently develop two framworks at the same time. When they add functionality to cocoa, what about carbon? Though one can access cocoa from carbon now, its still not as easy as using cocoa directly (carbon events vs other cocoa paradigms)...as another example, using QT from cocoa is still not fun.

At some point, apple is gonna have to say where the line ends, and carbon will just "stay the way it is," kind of like what MS is doing with win32 compared to .NYET...