Why so many Common Libraries?

[herrmannj]

hmmm, thats sounds a bit counterproductive. the goal should be to simplify and speed up things - now this tends to go in the other direction.

may be we should start with a subset of features, which we already should be define.

[whurlston]

Not sure what the impact of this is, we may need to drop the 'scraping' functions until a home-grown replacement methodology for parsing the html is developed.

I've got some code that may help get that started. I parse the Netflix pages for the data I need. It could help as a starter for someone who wants to tackle a class for that.

[MixMan]

The WizUtilities use the HTMLAgilityPack which has a creative commons "ShareAlike" license.

Not sure what the impact of this is, we may need to drop the 'scraping' functions until a home-grown replacement methodology for parsing the html is developed.

After reading this
http://creativecommons.org/licenses/by-sa/1.0/
http://www.codeproject.com/info/Licenses.aspx
I think that CC and LGPL has very much in common.
.... but I'm not a layer.
Why not write to the author and ask him?

I think that JavaWiz har raised some very good questions in this thread.
The Wiki is good, but not for presenting documentaion.
I am sure that Sub can allow space on his server for web pages documentation.

I started to sum up questions and answers on this wiki page .... today.
feel free to write there.
http://gbpvr.com/pmwiki/pmwiki.php/Devel...nLibraries

Regarding Library distribution. I think that some kind of automatic downloader would be the best, so the Libraries never would be distributed together with plugins.
Otherwise there will always be older version around on the wiki.

[MixMan]

I found this MediaArtAggregator program that is LGPL and supports many web sources.

A digital media art aggregator. Finds cover art for music, tv shows, movies or any other type of media. Searches different sources including Google Images, Yahoo Images, Live Images, Deviant Art, Amazon.com and Walmart. Additional sources can be customized by defining the url to get the source from and a regular expression to determine the image url or by defining new classes that inherit from a base class.

http://www.codeplex.com/maa

http://www.codeplex.com/maa/SourceContro...SetId=3120

[MixMan]

An even better article of License Types at:
http://www.codeproject.com/info/Licenses.aspx

[McBainUK]

Can a program with a "GNU Lesser General Public" License call code in proprietary (closed source) DLLs?

[McBainUK]

bump

[pz1]

Can a program with a "GNU Lesser General Public" License call code in proprietary (closed source) DLLs?

I think this depends more on the terms under which the called DLLs are being licensed. If the DLLs are part of a bigger package which has in its license that you are not allowed to reverse engineer the package, it is not allowed.

[mvallevand]

As Pieter says it partly depends on the DLL's. However LGPL doesn't require you to describe the method to compile or run the source code, so you can dynamically link to any commercial and proprietary drivers etc. that you have the right too. GPLv3 would not allow this. Static linking would likely not be allowed.

Martin

[McBainUK]

Sorry for being such a noob. What's the difference between static and dynamically linking.

If it helps, the DLLs in question are the JavaWiz's WizTools DLLs and sub GBPVR public DLLs.