Forum > Carbon
How future "safe" is Carbon - anyone knows?
Trenatos:
I know this is an old thread, but it's still a valid question, one I have myself right now.
My biggest issues with Cocoa is that looking at the Wiki, it's not completely implemented, and I know from testing that some things just work differently between the two.
I can't just select Cocoa and expect it to actually work the same (Write once, compile maybe?). Is anyone actively working on the Cocoa implementation?
dbannon:
I have an application, tomboy-ng, which is cross platform, Linux, Windows and Mac
I advise users, at present, to use the 32bit version on the Mac but do release a 64bit Cocoa version. I note that a number of things don't work as expected =
Mac 64bit Cocoa - is experimental, it has several known issues and probably more. Known ones include ... unable to display trayicon. Printing fails and copying into and out of the application fails.
https://wiki.gnome.org/Apps/Tomboy/tomboy-ng/BugsAndIssues
I have had to restructure things to ensure the crossplatform-ness does not require too many ifdefs. On a more positive note, the way it is now, I can switch between carbon and cocoa just by changing compiler options. And same code base works on Linux and Windows too. About seven thousand lines of code.
Davo
Trenatos:
Carbon's been working very well for me, but I'm pretty sure Apple has restricted Carbon to 32bit, and are now showing warnings for applications that aren't 64bit, so it really is time to look for a solution.
Unfortunately.. I don't know what that solution is.
Cocoa doesn't work right, and afaik none of the others look native.
Phil:
--- Quote from: Trenatos on June 15, 2018, 03:42:55 pm ---Carbon's been working very well for me, but I'm pretty sure Apple has restricted Carbon to 32bit, and are now showing warnings for applications that aren't 64bit, so it really is time to look for a solution.
Unfortunately.. I don't know what that solution is.
Cocoa doesn't work right, and afaik none of the others look native.
--- End quote ---
The forthcoming Mojave (10.14) is the last version of macOS to support 32-bit apps. Period. That's been discussed elsewhere on this forum.
The time to move to Cocoa was probably 5-6 years ago when there was still some air left in desktop app development. Microsoft was actually a bit late to the transition, moving Office on Mac to Cocoa in 2011 and going 64-bit only in 2016. The first commit to the Lazarus Cocoa widgetset was May 2008, so it certainly got off to the right start. My prediction this last winter was 1-2 years for a stable Cocoa widgetset for LCL.
Some production software like QGIS and Microsoft Remote Desktop do use Qt libraries since these apps are cross-platform. But for smaller, non-production hobby apps Qt probably is not the right choice. So I guess I agree with you: there is no solution short of rewriting the UI portion of an app using Cocoa directly as described here (ProjectXC):
https://macpgmr.github.io
marcov:
--- Quote from: Phil on June 15, 2018, 06:21:20 pm ---So I guess I agree with you: there is no solution short of rewriting the UI portion of an app using Cocoa directly as described here (ProjectXC):
https://macpgmr.github.io
--- End quote ---
Well, or just think different, and go to windows ? >:D
Navigation
[0] Message Index
[#] Next page
[*] Previous page