Love this, if I never have to write a wrapper around objc again I'd be in heaven.
C-Macs – a pure C macOS application
11–20 of 138 posts
Re: C-Macs – a pure C macOS application
#12Earlier quoted context omitted.
MacOS apps are typically written in either Objective-C or Swift as these are the officially supported languages for the MacOS APIs. The code in this template is interfacing with the Objective-C runtime but with pure C.
Does this mean that, theoretically, this could lead to the ability to build MacOS apps in higher languages that interoperate well with C such as Python? I know you can build MacOS apps with Python now, but does this potentially improve the experience?
That is what objC scripting brige is for.
Re: C-Macs – a pure C macOS application
#13No license typically means copyright with all rights reserved in the U.S. Perhaps you want to release this into the public domain (see SQLite)?
I’d say the license is:
“ Use it at your own risk, and don't blame me if anything bad happens. Oh, and if you extend it, make sure there isn't any Objective-C in it!”
I’d classify it as Open Source.
Re: C-Macs – a pure C macOS application
#14No license typically means copyright with all rights reserved in the U.S. Perhaps you want to release this into the public domain (see SQLite)?
I’d say the license is: “ Use it at your own risk, and don't blame me if anything bad happens. Oh, and if you extend it, make sure there isn't any Objective-C in it!” I’d classify it as Open Source.
Oh no that won't fly at all. People around here really like "proper" licenses. And they'll tell you about it.
Re: C-Macs – a pure C macOS application
#15I did a straight C++ app for MacOS but 1) I used SDL2 and 2) it was a full-screen game so no Cocoa UI needed. It was kind of fun though in a retro-computing way.
(I'm a big fan of SDL now.)
Re: C-Macs – a pure C macOS application
#16No license typically means copyright with all rights reserved in the U.S. Perhaps you want to release this into the public domain (see SQLite)?
I’d say the license is: “ Use it at your own risk, and don't blame me if anything bad happens. Oh, and if you extend it, make sure there isn't any Objective-C in it!” I’d classify it as Open Source.
It's open source but it is still under copyright. There are notices in the source file:
https://github.com/CodaFi/C-Macs/blob/master/CMacs/View.c#L5...
I would definitely ask permission and encourage the author to change the license before using this code.
Since API calls are purely functional and not covered by copyright you can mimic the behavior here but you'll need to rewrite everything from scratch, notably the most expressive parts, which are:
https://github.com/CodaFi/C-Macs/blob/master/CMacs/CMacsType...
https://github.com/CodaFi/C-Macs/blob/master/CMacs/CMacsType...
The organization and structure of this code is arbitrary and within the author's creative expression.
Re: C-Macs – a pure C macOS application
#17Earlier quoted context omitted.
I’d say the license is: “ Use it at your own risk, and don't blame me if anything bad happens. Oh, and if you extend it, make sure there isn't any Objective-C in it!” I’d classify it as Open Source.
Oh no that won't fly at all. People around here really like "proper" licenses. And they'll tell you about it.
I don't like the (perhaps actually a) license, because it set's limits on what the user can do with the source code. (Not allowing Objective C in it.)
Re: C-Macs – a pure C macOS application
#18No license typically means copyright with all rights reserved in the U.S. Perhaps you want to release this into the public domain (see SQLite)?
I’d say the license is: “ Use it at your own risk, and don't blame me if anything bad happens. Oh, and if you extend it, make sure there isn't any Objective-C in it!” I’d classify it as Open Source.
I do love the vibe of that license
Re: C-Macs – a pure C macOS application
#19Earlier quoted context omitted.
I’d say the license is: “ Use it at your own risk, and don't blame me if anything bad happens. Oh, and if you extend it, make sure there isn't any Objective-C in it!” I’d classify it as Open Source.
It's open source but it is still under copyright. There are notices in the source file: https://github.com/CodaFi/C-Macs/blob/master/CMacs/View.c#L5... I would definitely ask permission and encourage the author to change the license before using this code. Since API calls are purely functional and not covered by copyright you can mimic the behavior here but you'll need to rewrite everything from scratch, notably the…
In most jurisdictions almost everything is under copyright, until it expires. (Which is approximately right before the heat death of the universe, after Disney get their way. Or 70 years after the authors death, or something like that.)
Re: C-Macs – a pure C macOS application
#20Earlier quoted context omitted.
I’d say the license is: “ Use it at your own risk, and don't blame me if anything bad happens. Oh, and if you extend it, make sure there isn't any Objective-C in it!” I’d classify it as Open Source.
Oh no that won't fly at all. People around here really like "proper" licenses. And they'll tell you about it.
I'm not a lawyer but one would definitely let you know that at least in the US, software without a license is more dangerous than software with even a very restrictive one. Someone can come along and determine the license at any time. So there is good reason to point it out unless you crave legal jeopardy.