5 ms·

Be warned, that code is GPLv3. I don't know the specific legal issues with using it or porting it to another language, but if you're going to use it you should

by Skroob 13y ago

Be warned, that code is GPLv3. I don't know the specific legal issues with using it or porting it to another language, but if you're going to use it you should check.

eduardordm 13y ago
You can do whatever you want, really, you just need to keep it open source. I can give permission for pieces of that project in any license you need, just not the whole project. Just list the files you need and will grant you a license (no questions asked :D) (except code not written by me, like the dropbox integration, etc)
- Skroob 13y ago
  Right. Like, for instance, I need some line smoothing code, but I don't want to use that in my closed source project because I don't know how far GPLv3 infects my project.
  - eduardordm 13y ago
    GPL pretty much kills closed source. But because I'm the copyright owner I can grant people any license: ====== Me, J Eduardo Mourao hereby grant any reader of this comment the full rights to any source needed for line smoothing and hand drawing included in the WireframeApp project (https://github.com/eduardordm/wireframeapp/ https://github.com/eduardordm/wireframeapp/). To receive a copy of this grant just send me an email (optional) This does not include code not written by me (which should have a header with the original authors license and contact info) eduardo@intermeta.com.br Mar 23rd 2013
georgemcbay 13y ago
Less than 200 lines of code, only a couple of which aren't basically boilerplate stuff specific to ObjC/Cocoa/iOS. So who cares what the license is? Just rewrite it. I assure you: x = (p1.x + p2.x) * 0.5; y = (p1.y + p2.y) * 0.5; is not now only allowed in GPLv3 code just because it appeared in this larger body of code which is GPLv3.
- eduardordm 13y ago
  Rewriting is also nice because you will actually make it better and more fit to your own project
- deleted 13y ago
  [deleted]
_delirium 13y ago
Are we going to post these kinds of inane comments every time someone writes code, but doesn't license it under a license someone happens to prefer? E.g.: WARNING: ABOVE CODE IS PROPRIETARY in response to every link to a code snippet that isn't open source?
- eridius 13y ago
  GPLv3 is absurdly dangerous. Not just the viral nature of its license, but the patent crap in v3 makes it infinitely worse for companies. So yes, I definitely appreciate it when people give warnings about links to GPLv3 code. I'd rather not even look at the code to begin with.
  - _delirium 13y ago
    It's no more dangerous than proprietary software in that regard. Proprietary software virally infects any project that uses it, as well as even people who merely look at it, which is why "clean-room" implementations require such careful hygiene to avoid being infected. Should we have an "MIT/BSD only" policy for HN links, and call out any links to dangerous proprietary code?
    - eridius 13y ago
      What do you mean by "proprietary software virally infects any project that uses it"? You're saying nonsense. And yes, the GPLv3 is extremely dangerous, with its patent crap, and it's anti-tivoing clause. Moreso than any other attribute of software, proprietary or free, that I can think of. For example, just imagine how devastating it would be if one bit of GPLv3 software made its way onto iOS. Edit: Thanks for the downvotes, guys. Yes, big shock, not everybody loves GPLv3, and some of us actually have legitimate reasons to do so.
      - david_b 13y ago
        Yes, the horror of an open ecosystem on iOS would hardly be bearable. You do know that nobody forces you to use foreign code to earn your money? Pretty much everybody in a commercial setting knows about licensing restrictions, so these warnings are useless.

by Skroob 13y ago

Be warned, that code is GPLv3. I don't know the specific legal issues with using it or porting it to another language, but if you're going to use it you should check.

eduardordm 13y ago

You can do whatever you want, really, you just need to keep it open source. I can give permission for pieces of that project in any license you need, just not the whole project. Just list the files you need and will grant you a license (no questions asked :D) (except code not written by me, like the dropbox integration, etc)

Skroob 13y ago
Right. Like, for instance, I need some line smoothing code, but I don't want to use that in my closed source project because I don't know how far GPLv3 infects my project.
- eduardordm 13y ago
  GPL pretty much kills closed source. But because I'm the copyright owner I can grant people any license: ====== Me, J Eduardo Mourao hereby grant any reader of this comment the full rights to any source needed for line smoothing and hand drawing included in the WireframeApp project (https://github.com/eduardordm/wireframeapp/ https://github.com/eduardordm/wireframeapp/). To receive a copy of this grant just send me an email (optional) This does not include code not written by me (which should have a header with the original authors license and contact info) eduardo@intermeta.com.br Mar 23rd 2013

georgemcbay 13y ago

Less than 200 lines of code, only a couple of which aren't basically boilerplate stuff specific to ObjC/Cocoa/iOS. So who cares what the license is? Just rewrite it. I assure you: x = (p1.x + p2.x) * 0.5; y = (p1.y + p2.y) * 0.5; is not now only allowed in GPLv3 code just because it appeared in this larger body of code which is GPLv3.

eduardordm 13y ago
Rewriting is also nice because you will actually make it better and more fit to your own project
deleted 13y ago
[deleted]

_delirium 13y ago

Are we going to post these kinds of inane comments every time someone writes code, but doesn't license it under a license someone happens to prefer? E.g.: WARNING: ABOVE CODE IS PROPRIETARY in response to every link to a code snippet that isn't open source?

eridius 13y ago
GPLv3 is absurdly dangerous. Not just the viral nature of its license, but the patent crap in v3 makes it infinitely worse for companies. So yes, I definitely appreciate it when people give warnings about links to GPLv3 code. I'd rather not even look at the code to begin with.
- _delirium 13y ago
  It's no more dangerous than proprietary software in that regard. Proprietary software virally infects any project that uses it, as well as even people who merely look at it, which is why "clean-room" implementations require such careful hygiene to avoid being infected. Should we have an "MIT/BSD only" policy for HN links, and call out any links to dangerous proprietary code?
  - eridius 13y ago
    What do you mean by "proprietary software virally infects any project that uses it"? You're saying nonsense. And yes, the GPLv3 is extremely dangerous, with its patent crap, and it's anti-tivoing clause. Moreso than any other attribute of software, proprietary or free, that I can think of. For example, just imagine how devastating it would be if one bit of GPLv3 software made its way onto iOS. Edit: Thanks for the downvotes, guys. Yes, big shock, not everybody loves GPLv3, and some of us actually have legitimate reasons to do so.
    - david_b 13y ago
      Yes, the horror of an open ecosystem on iOS would hardly be bearable. You do know that nobody forces you to use foreign code to earn your money? Pretty much everybody in a commercial setting knows about licensing restrictions, so these warnings are useless.