I have not tried developing for Mac yet. I was just wondering what made the port of Carbon to Cocoa so time consuming? I was wondering if I would any of these pains: going from Windows to Mac.
Thanks
Carbon and Cocoa are completely different frameworks. It’s not so much what is different for Xojo users but the underlying framework was quite a bit different. Carbon was a bridge from the old Classic OS 9 and lower into OS X. Cocoa is really the modern version of the old NeXT framework.
Developing for Window and Mac is not that difficult. A few things are different. Apps generally run easier and better in Mac from what I’ve seen. But then again, I’m not a Windows expert.
[quote=133460:@Jon Ogden]Carbon and Cocoa are completely different frameworks. It’s not so much what is different for Xojo users but the underlying framework was quite a bit different. Carbon was a bridge from the old Classic OS 9 and lower into OS X. Cocoa is really the modern version of the old NeXT framework.
Developing for Window and Mac is not that difficult. A few things are different. Apps generally run easier and better in Mac from what I’ve seen. But then again, I’m not a Windows expert.[/quote]
[quote=133460:@Jon Ogden]Carbon and Cocoa are completely different frameworks. It’s not so much what is different for Xojo users but the underlying framework was quite a bit different. Carbon was a bridge from the old Classic OS 9 and lower into OS X. Cocoa is really the modern version of the old NeXT framework.
Developing for Window and Mac is not that difficult. A few things are different. Apps generally run easier and better in Mac from what I’ve seen. But then again, I’m not a Windows expert.[/quote]
So really the switch from Carbon to Cocoa is just matter of giving up on Classic OS 9 users?
Thanks
It’s replacing the Mac OS Classic framework from 1984 with the NextStep framework 
PS: You can’t access controls from threads any more. Biggest change for me to fix!
and painting in Canvas must happen in paint event, not outside.
Ah, this stuff is old standards that I have avoided so this should not be a problem for me.
The nice thing about Xojo is that most of your Windows code should work just fine. You just need to take into account that line endings are different , that permissions work differently, etc. In general it’s not that bad.
Don’t worry about the Carbon to Cocoa stuff. The way Xojo works it is pretty much all under the hood. Once the Cocoa platform was released, it worked with few problems with my code. There’s still a few bugs in it but hopefully those will get sorted out.
Switching our apps from Carbon to Coco didn’t require too many changes to our code, as most of the changes were handled by Xojo.
For us at least, the switch was a minor bump, not a significant problem, although we had a few Mac users on earlier versions of OS X (10.6/Snow Leopard and earlier) who couldn’t run our new Coco versions. They can continue to run our older products, but will have to upgrade their OS X to run current and future versions. (I’m generally reluctant to drop support for older OS versions, but we couldn’t justify the resources to try to continue a Carbon version as well as the mainstream Coco and Windows versions.)
Delivering the same apps on Windows and Mac/Coco does require a fair amount of testing, with conditional compiles where it’s necessary to do things differently on each platform.
I definitely wouldn’t consider coding for OS X/Windows without having test systems for both, or at least having Windows running as a virtual machine on a Mac. As Jon mentioned, Xojo apps tend to run better on OS X, so it’s a good idea to test frequently on Windows to spot any problems as early as possible. (This most often relates to screen flash/redraws, which can be a nuisance on Windows.)
[quote=133522:@Dan Oja]Switching our apps from Carbon to Coco didn’t require too many changes to our code, as most of the changes were handled by Xojo.
For us at least, the switch was a minor bump, not a significant problem, although we had a few Mac users on earlier versions of OS X (10.6/Snow Leopard and earlier) who couldn’t run our new Coco versions. They can continue to run our older products, but will have to upgrade their OS X to run current and future versions. (I’m generally reluctant to drop support for older OS versions, but we couldn’t justify the resources to try to continue a Carbon version as well as the mainstream Coco and Windows versions.)
Delivering the same apps on Windows and Mac/Coco does require a fair amount of testing, with conditional compiles where it’s necessary to do things differently on each platform.
I definitely wouldn’t consider coding for OS X/Windows without having test systems for both, or at least having Windows running as a virtual machine on a Mac. As Jon mentioned, Xojo apps tend to run better on OS X, so it’s a good idea to test frequently on Windows to spot any problems as early as possible. (This most often relates to screen flash/redraws, which can be a nuisance on Windows.)[/quote]
I recently bought a OS X laptop. I can conveniently test it out that way.
Thanks
Its A LOT easier developing Xojo apps cross platform than it using say Mono/C#, personally I found the Mac version of my Xojo app less problematic than the Windows one… which was weird considering I haven’t got a clue about Mac, it just seemed common sense to adapt certain things.
I found it painless, I have projects that I do on a old Linux laptop when I’m away from my PC and I don’t change anything
I really thought I was in for threading problems like Christian Schmitz mentioned, my C# project an awful on Mac, but my Xojo project is floorless in that respect
[quote=133549:@nige cope]Its A LOT easier developing Xojo apps cross platform than it using say Mono/C#, personally I found the Mac version of my Xojo app less problematic than the Windows one… which was weird considering I haven’t got a clue about Mac, it just seemed common sense to adapt certain things.
I found it painless, I have projects that I do on a old Linux laptop when I’m away from my PC and I don’t change anything
I really thought I was in for threading problems like Christian Schmitz mentioned, my C# project an awful on Mac, but my Xojo project is floorless in that respect[/quote]
*flawless
[quote=133549:@nige cope]Its A LOT easier developing Xojo apps cross platform than it using say Mono/C#, personally I found the Mac version of my Xojo app less problematic than the Windows one… which was weird considering I haven’t got a clue about Mac, it just seemed common sense to adapt certain things.
I found it painless, I have projects that I do on a old Linux laptop when I’m away from my PC and I don’t change anything
I really thought I was in for threading problems like Christian Schmitz mentioned, my C# project an awful on Mac, but my Xojo project is floorless in that respect[/quote]
Thanks. Sounds really good then.[quote=133549:@nige cope]Its A LOT easier developing Xojo apps cross platform than it using say Mono/C#, personally I found the Mac version of my Xojo app less problematic than the Windows one… which was weird considering I haven’t got a clue about Mac, it just seemed common sense to adapt certain things.
I found it painless, I have projects that I do on a old Linux laptop when I’m away from my PC and I don’t change anything
I really thought I was in for threading problems like Christian Schmitz mentioned, my C# project an awful on Mac, but my Xojo project is floorless in that respect[/quote]
oops sorry,… I was educated by a Geordie dyslexic mountain goat 
That’s fine.