Adding other Project to Qt like PoDoFo (LGPL)
-
Hallo,
there are good libraries which went dormant or went down. Also some OSS Projects. Some of them were good or at least in some points.
It seems like PoDoFo went dormant, at least the links to BugTracker and the link to Mailing List Archives are dead. The Archive is reachable via Google.
As far as I know Qt PDF is not capable of creating PDFs with Forms like Textboxes. PoDoFo is capable to create AcroForms.Since Qt (Community Edition) is LGPL and PoDoFo is LGPL. Qt could include PoDoFo and continue it. There is only one Problem to solve since Qt is Dual Licensed.
What do you guys think of including other Projects into Qt?
Greetings
-
Hallo,
there are good libraries which went dormant or went down. Also some OSS Projects. Some of them were good or at least in some points.
It seems like PoDoFo went dormant, at least the links to BugTracker and the link to Mailing List Archives are dead. The Archive is reachable via Google.
As far as I know Qt PDF is not capable of creating PDFs with Forms like Textboxes. PoDoFo is capable to create AcroForms.Since Qt (Community Edition) is LGPL and PoDoFo is LGPL. Qt could include PoDoFo and continue it. There is only one Problem to solve since Qt is Dual Licensed.
What do you guys think of including other Projects into Qt?
Greetings
-
Even if there were no licensing issues, adding unmaintained piece of 3rd party code to Qt Project would not be an easy decision
-
Even if there were no licensing issues, adding unmaintained piece of 3rd party code to Qt Project would not be an easy decision
@Konstantin-Tokarev said in Adding other Project to Qt like PoDoFo (LGPL):
Even if there were no licensing issues, adding unmaintained piece of 3rd party code to Qt Project would not be an easy decision
you could just add the AcroForm support in it. And podofo last upload was begin of 2018, not that old.
-
QtPDF is based on pdfium, so to make this possible you need to add support for alternative engine, or implement missing functionality in pdfium
-
Hi,
In addition to what @Konstantin-Tokarev wrote, here's a question:
- Who would maintain that project forward ?
Are you volunteering to do that ?
-
Hi,
In addition to what @Konstantin-Tokarev wrote, here's a question:
- Who would maintain that project forward ?
Are you volunteering to do that ?
If I get into the PDF Standard and had enough time I would but I doubt that a successful project can be maintained by one Person :/
My first action were removing or replacing the parts which are incompatible with C++17 and later like auto_ptr in PoDoFo . When it compiles and behaves as it should I would maintain it.
@Konstantin-Tokarev
Isn't pdfium made by Google?The Problem is then the Naming. If I fork it and rename it to prevent legal naming issues, no one recognizes the library and will only be used by a small group the rest will stick to PoDoFo until it is that old that you can't use it effectively.
ATM (lib)podofo is still findable with "apt search podofo".My Intention is that either PoDoFo will be included into a living library or someone continues the work without different forks of it.
Imagine if the Company stops Qt and release it as Open Source and now 3 Forks with their own Communities start continuing it. It would not make such progress as it woul if only one bigger Community working and maintaining it. In my Opinion a waste of resourcing splitting communities.
-
@SeppyQT said in Adding other Project to Qt like PoDoFo (LGPL):
Isn't pdfium made by Google?
It is, so in order to contribute you'll have to comply to their terms, and maintain your code as well
