I decided to publish the source for ToneBoards. I just haven't had as much time to work on it as I would have liked this past year. Perhaps someone will find it useful. Also I'm kind of thinking about letting my Apple developer account lapse. It's just another expense for me right now, and was sort of a hassle to set up. I'm becoming more interested in other ways to assure users of quality/integrity of a piece of software. I've recently discovered a makeshift alternative to apple developer certificates(i think). I mean what is the point of code signing when you can just compare digests using openSSL?------------------------------------------------------------------------------
Below are some Github links, and I'm also posting digests and filesizes. I think this should provide a way for users to gain 99% of the assurances provided by the Appstore(with a couple added steps on the user's part).
https://github.com/kipbits/ToneBoards/releases
xxd ToneBoards.app.zip
size(hex):0db4330
openssl dgst -sha512 ToneBoards.app.zip
SHA512(ToneBoards.app.zip)= ef8c3a1e54301c8a6ad0e53706e4e5e5c9f0fc85ee4d8d1aee6faf195801494a1b919b02be1de4455f005d04308270b8e8c3c06c254849a7a4c0b74ed6a2881c
https://github.com/kipbits/SFML-2.3.2-Updated-plist_altered-keyboard/releases
xxd Frameworks.tar.gz
size(hex):0367110
openssl dgst -sha512 Frameworks.tar.gz
SHA512(Frameworks.tar.gz)= 3524096384e6337b654a85286f91bebdd86534d0719e735f4e29b40687efb36d4de9add983d56a12c78cf2f58aba3876104f2f3b851d39dbb8df5131070448c9
So... it plays a sound on a key press with a pitch determined by the key?
I think it would be a good idea (if not just somewhat polite) if you were to put that really long list in that post above inside spoiler tags:(click to show/hide)
I noticed some of the libraries SFML uses are LGPL, GPL. from what i understand LGPL is not necessarily a problem, but GPL makes me worry.
Will I need to release all my source-code?
I noticed some of the libraries SFML uses are LGPL, GPLI really wonder which ones are GPL.