Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copy Qt function documentation into Go comments for IDE hinting #6

Closed
mappu opened this issue Aug 25, 2024 · 2 comments
Closed

Copy Qt function documentation into Go comments for IDE hinting #6

mappu opened this issue Aug 25, 2024 · 2 comments
Labels
wishlist wontfix This will not be worked on

Comments

@mappu
Copy link
Owner

mappu commented Aug 25, 2024

It should be possible to codegenerate better function comments based on Qt's own documentation.

But what license is the Qt documentation under, what are the license implications of this?

@mappu mappu added the wishlist label Aug 25, 2024
@mappu
Copy link
Owner Author

mappu commented Oct 13, 2024

General explanitory Qt documentation in qtdoc is under the GFDL. Functions are described directly in .cpp comments in qtbase, marked LGPL/Commercial.

  • Option 1: MIQT remains MIT license but "redistributions in source form must..." comply with docs licensing
  • Option 2: Give up on this idea, not worth the legal hassle

Behaviour of other bindings:

  • Kitech (LGPL): Does copy in documentation, LGPL required
  • NodeGui (MIT): Does not copy in documentation
  • Ritual (MIT): ...

@mappu
Copy link
Owner Author

mappu commented Oct 13, 2024

I think the documentation was deliberately put into the cpp instead of the public header. I think that suggests that the Qt company feel like it's part of the implementation, not the interface. Copying the implementation is beyond what MIQT is allowed.

Because a primary purpose of MIQT is to maintain the permissive licence for static linking I think it's impossible to resolve this in a legal way.

This can be reopened if there is a better legal theory.

@mappu mappu closed this as completed Oct 13, 2024
@mappu mappu added the wontfix This will not be worked on label Oct 13, 2024
@mappu mappu closed this as not planned Won't fix, can't repro, duplicate, stale Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wishlist wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant