Closed GoogleCodeExporter closed 9 years ago
Hello Greg,
Windows phone 7 runs .NET CF, which has some limitation. For example, GDI+
support is reduced there. So it will affect AForge.Imaging, which is the
biggest part of the framework. Making a hack for few routines for some specific
application could be an option. But recoding significant amount of code is a
question and is not something quick to do.
Original comment by andrew.k...@gmail.com
on 22 Jun 2011 at 9:02
WP7 does not allow LGPL or GPL licenses afaik. Any chance of seeing a dual
license model for Aforge so one can try to port bits and pieces of the code
until we may see a full port one day?
Original comment by bengt.al...@gmail.com
on 27 Jun 2011 at 8:04
Window Phone 7 is just a platform. It has nothing to do with your application,
which can be open source. Is not it?
What is wrong with LGPL for you? It allows you to do modifications, but you
will need to keep all modifications open and allow users to reproduce result.
Or you want a closed source app with modification to the framework?
Original comment by andrew.k...@gmail.com
on 27 Jun 2011 at 8:10
Microsoft has explicitilly forbidden GPL style licenses from WP7. I think the
phrasing of the licensing is somehow incompatible with app-stores.
http://www.osnews.com/story/24433/GPL-like_Licenses_Explicitly_Banned_from_WP7_M
arketplace
http://www.thinq.co.uk/2011/2/17/microsoft-bans-open-source-marketplace/
Original comment by bengt.al...@gmail.com
on 27 Jun 2011 at 8:23
>> Microsoft has explicitilly forbidden GPL style licenses from WP7.
No. It is forbidden for marketplace, but not for the platform itself. Don't
need to mess these things together.
Original comment by andrew.k...@gmail.com
on 27 Jun 2011 at 8:32
Hi... could you please clarify what you mean? I read it as you cannot have code
that contains LGPL:ed/GPL:ed code in the marketplace.
The only way for a user to install an application is either to have a developer
unlocked phone or to install it via the marketplace. So while you are correct
in the assessment that I could theoretically make a LGPL:ed port of Aforge for
WP7, noone but a developer would be able to install an app using it?
Original comment by bengt.al...@gmail.com
on 27 Jun 2011 at 8:37
Yes, my point was that nothing stops you to put whatever you want to the phone
you want using development tools. But it is just for you Your phone. Obviously
you want to share/sell your software on the market. And here MS blocks it. But
it is market's restriction. This is all wanted to say.
Original comment by andrew.k...@gmail.com
on 27 Jun 2011 at 8:43
Okies... then we are on the same page... So, do you think there is any chance
of you adding a WP7 friendly license? The library seems very competent so it
would be great... Otherwise I'll either have to find another library or worst
case scenario, pick up some image processing literature and brew my own... :/
Original comment by bengt.al...@gmail.com
on 27 Jun 2011 at 8:51
Original comment by andrew.k...@gmail.com
on 23 Jan 2012 at 11:49
It seems like Microsoft has loosened its restrictions on GPL-esque licenses for
the Windows Phone Store now, there is no prohibitive wording about GPL in the
most recent agreement:
http://cmsresources.windowsphone.com/devcenter/en-us/legal/Windows-Phone-Store-A
pplication-Provider-Agreement.pdf
A subset of AForge applicable to Windows Phone 8 is now available here:
https://github.com/cureos/aforge
Original comment by cureos...@gmail.com
on 8 Jan 2014 at 11:06
1) About GPL:
It says any derived work must be open. Will you be ready to open source code of
your app you do for Win App Store?
2) About LGPL:
It says that end result must be reproducible. So if I purchase your app, will
be able to update version of LGPL component (lets say its binaries) on my
phone/table?
The fact MS does not word it, does not mean there is easy way to do it without
violating the license.
Original comment by andrew.k...@gmail.com
on 8 Jan 2014 at 11:13
> A subset of AForge applicable to Windows Phone 8 is now available here:
> https://github.com/cureos/aforge
I would say anyone who is using that will violate LGPL text. Can not see the
way how they can satisfy requirement, that the end result must be reproducible.
Original comment by andrew.k...@gmail.com
on 8 Jan 2014 at 11:14
Rejecting this ticket in its original form. There is no point to invest in WP7,
since MS basically fucked it up - applications are not compatible with WP8.
Original comment by andrew.k...@gmail.com
on 8 Jan 2014 at 11:16
Original issue reported on code.google.com by
greg.mal...@bigpond.com
on 19 Jun 2011 at 2:41