4 ms·
If you want something that works now, there is Chameleon, the project this is based on: http://chameleonproject.org/ http://chameleonproject.org/ Unfortunatel
by a-priori 11y ago
If you want something that works now, there is Chameleon, the project this is based on:
http://chameleonproject.org/ http://chameleonproject.org/
Unfortunately, it seems the project's maintainers have mostly lost interest in the project (last push to Github in May 2014), but there's a few forks that have kept on. I maintained this one for a few years for our own uses:
https://github.com/toushay/Chameleon https://github.com/toushay/Chameleon
Unfortunately, the company behind that fork, Toushay, went out of business last year so there won't be any further work done on that fork. There may be others out there that are still maintained.
- LeoNatan25 11y agoOr, instead of debugging and maintaining over-ambitious lowest common denominator projects, which will limit you any way you look at them, just re-write the UI portion of your software with proper Mac design in mind, in AppKit.
- a-priori 11y agoUsing something like Chameleon can get you up and running in a very short time. Literally, it took one afternoon for me to get our app running on Chameleon. True story. I actually did it without management approval on the day they said "we should have an OS X app" and demoed it to them at the end of the day. It wasn't perfect, and took another week or two to iron out a few bugs in Chameleon we ran into. That was the start of our fork, actually. But it worked, and it would have taken two to three months to get to that point from scratch. I should know, because I did from-scratch ports to other platforms and that's how long it took each time. You can mix and match Chameleon (UIKit) and AppKit in the same application, so you can incrementally replace Chameleon with a "proper" solution. If you find that's important to you.