Update from QWT to JKQtPlotter

[doug1234]

QWT is dated and painful to build. I would like to update to JKQTPloter: https://github.com/jkriege2/JKQtPlotter

I've updated from QWT to JKQTPloter before and I don't think it would be too difficult but would like thoughts.

[jrw972]

Our main concerns are licensing and integration.

It looks like JKQTPlotter is LGPL2.

How would it become part of the build? Some kind of package manager, submodule, download and build, etc.?

[doug1234]

On my end I have my own way of dealing with packages. What would be most consistent with your build processes for git hub?

[simpsont-oci]

QWT is a modified LGPL license, with specific exceptions for inheritance from widgets not counting as derivative work. I don't know if those exceptions do much legally, but perhaps we need to determine how much of the code would be expected to inherit from JKQTPlotter types. As for how to integrate it, it looks like it's already got a cmake build and is only dependent on Qt (correct me if I'm wrong there), so hopefully checking it out and building is pretty straightforward, and GitHub Actions caching can be used to speed up repeated builds of the latest stable / LTS version.

…

On Tue, Oct 24, 2023 at 5:33 PM Doug ***@***.***> wrote: On my end I have my own way of dealing with packages. What would be most consistent with your build processes for git hub? — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHWIMO5GC4QCLNIXBOGHHW3YA7UUHAVCNFSM6AAAAAA6JMXUC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZXGYYDOMJZHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[doug1234]

Sounds good then. I don't expect to inherit from any of their classes so it sounds like I can move forward on this.