Hi,
Thanks to everyone who answered or commented on this question. This is my
understanding of one path forward. (And everybody sing along, I am not a
lawyer, and the fact that the license is so convoluted that almost literally
everyone feels the need to make this disclaimer is one of the thing
Keep in mind that LGPL restrictions got tighter in v3, and I know there remain
many projects out there that are LGPL but have refused v3 for these reasons.
> On Jan 29, 2016, at 11:28 AM, thatsanicehatyouh...@me.com wrote:
>
> Hi,
>
> Thanks to everyone who answered or commented on this questio
On Jan 29, 2016, at 11:37 AM, Dru Satori wrote:
> Keep in mind that LGPL restrictions got tighter in v3, and I know there
> remain many projects out there that are LGPL but have refused v3 for these
> reasons.
True. Based on my understanding, what I outlined should satisfy both v2 and v3.
On
On Jan 29, 2016, at 09:27 , thatsanicehatyouh...@me.com wrote:
>
> One thing I forget to add; probably the *very best way* to address this issue
> is to contact the library author and say, “Hey, I want to use your LGPL code
> in my Mac app and put it on the App Store; is that ok? Do you mind if
I think that this is a slightly uncharitable view of OSS devs, but not terribly
inaccurate.
> On Jan 29, 2016, at 1:30 PM, Quincey Morris
> wrote:
>
> On Jan 29, 2016, at 09:27 , thatsanicehatyouh...@me.com wrote:
>>
>> One thing I forget to add; probably the *very best way* to address this
The whole idea behind “open source” vs. “free software” has a long and very
muddy history. Generally speaking, “open source” is a development methodology
and “free software” is a political methodology. I don’t think it is correct to
even use something like “vs.” between them like I did above.
On Jan 29, 2016, at 10:50 , Dru Satori wrote:
>
> I think that this is a slightly uncharitable view of OSS devs, but not
> terribly inaccurate.
To clarify, I wasn’t trying to be sarcastic at the expense of open-/free-source
developers. There are some developers and some projects which they hap
Hello there,
I have a project I am working on and I was wondering if anyone has had to catch
a status of a light or set of lights. For example, green safe, yellow caution,
red stop. Then I need to relay this to the program I am building so that it
knows what the lights actually mean.
Hi Scott,
Are you talking about writing a machine vision app for the Mac or iPhone
specifically meant to identify colored lights or LEDs to help the visually
impaired?
If I am understanding you correctly, this is extraordinarily non-trivial.
If you would like me to go into more detail, I am ce
> I think a better technical approach would be to embed the library as a
> framework in your app, but arrange that if a version of the framework is in
> (say) /Library/Frameworks, that one is dynamically loaded instead of the
> built-in framework. You might also need to be able to provide the sourc
> On 30 Jan 2016, at 9:42 AM, Scott Berry wrote:
>
> Hello there,
>
> I have a project I am working on and I was wondering if anyone has had to
> catch a status of a light or set of lights. For example, green safe, yellow
> caution, red stop. Then I need to relay this to the program I am bu
>
> One thing I forget to add; probably the *very best way* to address this
> issue is to contact the library author and say, “Hey, I want to use your
> LGPL code in my Mac app and put it on the App Store; is that ok? Do you mind
> if people can’t dynamically link their own copy, because really, no
color filters might simplify the problem. Also are the lights in a
fixed location?
Do you plan to let your iDevice do the driving? ;-D
Michael David Crawford, Baritone
mdcrawf...@gmail.com
One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light.
On Fri, Jan 29, 2016 at 5
By the way, for what it's worth, Apple has some LGPL code on the
system. For example, JavaScriptCore and WebKit are under the LGPL.
(Though I suspect the majority of the copyright is now Apple and they
won't file a claim against themselves.)
___
Cocoa-de
14 matches
Mail list logo