matplotlib-devel Mailing List for matplotlib

On Tue, Jun 14, 2011 at 8:46 AM, Kevin Davies <dav...@ya...> wrote:
> Hello,
> I should have sent the original email in plain text rather than HTML, so I am resending it. Please give me suggestions regarding my email below. Thanks.
Hey Kevin,
the toolkit looks quite nice and we would be happy to distribute it,
but we require a BSD compatible license (for a rationale, please see
http://matplotlib.sourceforge.net/devel/coding_guide.html#license-discussion).
 Although we could technically distribute a GPL licensed product as a
toolkit, I think it might be confusing to users so I prefer to keep
everything in our distribution BSD compatible. I think the benefits
of having your code part of the core distribution with users seeing
samples on our web pages and gallery outweigh the risks that someone
might sell your code, but that is just my opinion. Having a lot of
visibility and users increases the odds that others will contribute to
and extend your toolkit. Personally, it doesn't bother me that
companies sell products that use matplotlib, despite having
contributed a considerable amount of time on the code. Some of these
companies have expressed interest in supporting matplotlib development
via donations or sponsored features. But I understand that you may
feel otherwise.
If you elect to keep your code under a GPL license, feel free to
distribute it as you see fit. Many scientific computing projects in
python use github. Google code is another option. We would be happy
to link to your code from our existing sankey examples, etc.

Hello,
I should have sent the original email in plain text rather than HTML, so I am resending it. Please give me suggestions regarding my email below. Thanks.
Kevin
________________________________
From: Kevin Davies <dav...@ya...>
To: "mat...@li..." <mat...@li...>
Sent: Sunday, June 12, 2011 2:32 PM
Subject: Sankey diagram toolkit
Hello,
I'm new to the matplotlib-devel list, but I wanted to ask for your opinions and suggestions about sharing a toolkit/module for drawing Sankey diagrams. I've continued from the work of Yannick Chopin (see http://matplotlib.sourceforge.net/examples/api/sankey_demo.html) to help support more complex diagrams. I'm attaching an example. 
Specifically, I'd like to know:
1. Would the matplotlib community be interested in the code shared under a GPL license? Due to the fact that there are companies selling Sankey software (see http://www.sankey-diagrams.com/sankey-diagram-software/), I'd rather keep a little more control than BSD provides. 
2. If there is interest, would the code be best shared as a matplotlib toolkit? It seems so, but I don't think it directly fits with any of the other current toolkits.
3. If it is best shared as a toolkit, how would I go about doing it? Currently, the code exists as about 900 lines of Python with five examples and inline documentation. Do I need to make special preparations?
Thank you!
Kevin

Hi,
1.0.3 packages are available for OS X.
I'll be going on vacation next week and my work project using PySide 
will be winding down over the same period. It would be nice if the 
PySide changes could be pulled into master before then
Thanks,
Gerald.
On 31/05/2011 5:10 PM, Gerald Storer wrote:
> 1.0.3 packages for Windows and Ubuntu/Debian are available to test with.
>
> I'm not sure that the OS X package is ready yet. If you want to get
> testing with it quicker jumping up and down on their mailing list
> normally gets them out faster.
>
> I also added an update to formlayout.py. I've merged in Pierre's latest
> version that validates the floats so an exception isn't thrown when a
> user inputs an invalid number.
>
> Gerald.
>
> On 31/05/2011 4:43 PM, David Trémouilles wrote:
>> The pyside bug affecting matplotlib pyside backend is now fixed
>> with pyside 1.0.3
>>
>> I would be nice to have the pyside option in the next matplotlib release...
>>
>> Regards,
>>
>> David
>>
>> Le 06/05/11 10:32, David Trémouilles a écrit :
>>> Hello,
>>>
>>> This is not directly related to your patch but I would like to
>>> report here that I still have at least one issue on MacOs
>>> that prevent matplotlib to work with your pyside backend.
>>> Indeed current PySide version (1.0.2) have a bug on MacOS that seems to
>>> have been fixed recently:
>>> http://bugs.pyside.org/show_bug.cgi?id=809
>>> But I will have to wait for next PySide release to
>>> confirm your pyside patch works on MacOs.
>>> Will test as soon as next pyside version is out and available on
>>> macports. I do not have time nor will to test with the latest current
>>> pyside head.
>>>
>>> Regards,
>>>
>>> David
>>>
>>>
>>>
>>> Le 06/05/11 03:36, Gerald Storer a écrit :
>>>> Hi,
>>>> I was wondering if I could get a comment on this. Its been 4 weeks
>>>> since I submitted the original version and it has been more or less
>>>> production ready since Monday.
>>>>
>>>> https://github.com/matplotlib/matplotlib/pull/80
>>>>
>>>> Thanks,
>>>> Gerald.
>>>>
>>>> On 11/04/2011 4:49 PM, Gerald Storer wrote:
>>>>> Hi,
>>>>> I've submitted a pull request with backend changes that (should) let
>>>>> all currently supported versions of PyQt work along side PySide. I've
>>>>> tested with PyQt 4.8.3 and PySide 1.0.0.
>>>>>
>>>>> I haven't bothered chasing down old versions of PyQt as they seem
>>>>> elusive.
>>>>>
>>>>> Gerald.
>>>>>
>>>>> On 29/03/2011 3:25 AM, bu...@gm... wrote:
>>>>>> Looking forward, supporting the Python 3 compatible PyQt API is
>>>>>> likely the way to go.
>>>>>>
>>>>>> Le , Gerald Storer<gd...@mr...> a écrit :
>>>>>>> On 28/03/2011 1:10 AM, Peter Butterworth wrote:
>>>>>>>
>>>>>>>
>>>>>>> Wouldn't it be possible to use a single backend compatible with both
>>>>>>>
>>>>>>> PyQt and Pyside ?
>>>>>>>
>>>>>>>
>>>>>>> The current Qt mpl backend uses the old PyQt slots/signals API
>>>>>> which PySide doesn't really support (there are some macros but they
>>>>>> don't work 100% the same). From a quick glance at the IPython
>>>>>> implementation it looks like they are using the new API which means
>>>>>> older versions (<4.5) of PyQt won't be supported. This might be ok, I
>>>>>> don't know.
>>>>>>> If it isn't then, there will need to be some try...excepts around
>>>>>> the place or separate back ends. If you ignore the PySide bugs I had
>>>>>> to work around I've only changed ~4 lines in the main backend.
>>>>>>>
>>>>>>> Pierre's formlayout is also using an obsolete method that isn't
>>>>>> present in PySide. I've opted to emulate it, but it would be best to
>>>>>> change the code to use the alternative method available in both PyQt
>>>>>> and PySide. formlayout also uses the old QString implementation of
>>>>>> PyQt, PySide only supports the new implementation where QString is
>>>>>> transparently convert to/from str/unicode. Setting QString = unicode
>>>>>> seems to work though.
>>>>>>>
>>>>>>> Gerald.
>>>>>>>
> ------------------------------------------------------------------------------
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel