Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
On Thu Dec 3 15:24:52 GMT 2009, Rajeev J Sebastian rajeev.sebastian at gmail.com wrote: On Thu, Dec 3, 2009 at 8:45 PM, Wilbert Berendsen wbsoft at xs4all.nl wrote: But for the binding to be useful for others, the API coverage would need to be completed. I for myself need the links() method of the Page object and the various Link* classes, but I would be willing to make the binding complete and cover and test the full API of libpoppler-qt4. Cool that would be awesome! :) My main reason for creating a (googlecode) repo, is that it would make it easier for me to work on both my machines and commit to the repo often. And to have a well-known place to provide source tarballs I can point users of my application to. OK. I'll create a bitbucket repo. That should allow you to commit often and also point your users to place where they can get tarballs. How far did you guys come with this project? I'd be very interested in using it myself, as well as in packaging it for Gentoo Linux. Cheers, -- Ben de Groot Gentoo Linux developer ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
Op donderdag 03 december 2009 schreef Rajeev: However, some other projects have made some mods, but not contributed back. No idea why (or whether its ethical). I would be willing to update and extend the bindings to cover the full api of libpoppler-qt4. Is it OK that I create a small googlecode SVN project for it and maintain the source there, providing versioned tarballs for others to use as soon as it is complete? That way this nice binding could become part of distributions instead of everyone including its own fork (which is OK of course). with many regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ You must be the change you wish to see in the world. -- Mahatma Gandhi ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
On Thu, Dec 3, 2009 at 7:56 PM, Wilbert Berendsen wbs...@xs4all.nl wrote: Op donderdag 03 december 2009 schreef Rajeev: However, some other projects have made some mods, but not contributed back. No idea why (or whether its ethical). I would be willing to update and extend the bindings to cover the full api of libpoppler-qt4. Is it OK that I create a small googlecode SVN project for it and maintain the source there, providing versioned tarballs for others to use as soon as it is complete? That way this nice binding could become part of distributions instead of everyone including its own fork (which is OK of course). Personally, I do not understand why people make their own fork anyway. It doesnt have much to do with distributions, because these projects are doing it for their own needs and not for their distributions. Why do you need a fork on googlecode ? You can simply checkout on your local, make mods and send me patches. But if its really necessary, I can move it off Pardus' SVN repo and put it on Bitbucket. Regards Rajeev J Sebastian ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
Op donderdag 03 december 2009 schreef Rajeev: It doesnt have much to do with distributions, because these projects are doing it for their own needs and not for their distributions. I meant that python-poppler-qt4 could become a package in the Linux distribution sense, and that other programs could simply depend om that package, instead of including (some fork of) it in their own source tarball. I write and distribute a free software application (written in Python, called Frescobaldi, see www.frescobaldi.org ). In the future I want to extend that app with a PDF widget based on libpoppler-qt4. But I would rather not include the Python binding with my program (as it requires users to compile code). Users should install the python binding separately. Other projects also can then depend on that package instead of including their own version. But for the binding to be useful for others, the API coverage would need to be completed. I for myself need the links() method of the Page object and the various Link* classes, but I would be willing to make the binding complete and cover and test the full API of libpoppler-qt4. Then the binding could be released as tarballs so that other people can easily install it and (Linux) distributions can include packaged versions of the Python binding for libpoppler-qt4. Why do you need a fork on googlecode ? You can simply checkout on your local, make mods and send me patches. But if its really necessary, I can move it off Pardus' SVN repo and put it on Bitbucket. I would rather not create a fork. If I can contribute patches it's good as well. My main reason for creating a (googlecode) repo, is that it would make it easier for me to work on both my machines and commit to the repo often. And to have a well-known place to provide source tarballs I can point users of my application to. Best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ You must be the change you wish to see in the world. -- Mahatma Gandhi ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
RE: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
Hi Wilbert I'm very much interested on your approach so please keep us updated on your progress. Cheers Rui -Message d'origine- De : pyqt-boun...@riverbankcomputing.com [mailto:pyqt-boun...@riverbankcomputing.com]de la part de Wilbert Berendsen Envoyé : jeudi 3 décembre 2009 16:15 À : pyqt@riverbankcomputing.com Objet : Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4 Op donderdag 03 december 2009 schreef Rajeev: It doesnt have much to do with distributions, because these projects are doing it for their own needs and not for their distributions. I meant that python-poppler-qt4 could become a package in the Linux distribution sense, and that other programs could simply depend om that package, instead of including (some fork of) it in their own source tarball. I write and distribute a free software application (written in Python, called Frescobaldi, see www.frescobaldi.org ). In the future I want to extend that app with a PDF widget based on libpoppler-qt4. But I would rather not include the Python binding with my program (as it requires users to compile code). Users should install the python binding separately. Other projects also can then depend on that package instead of including their own version. But for the binding to be useful for others, the API coverage would need to be completed. I for myself need the links() method of the Page object and the various Link* classes, but I would be willing to make the binding complete and cover and test the full API of libpoppler-qt4. Then the binding could be released as tarballs so that other people can easily install it and (Linux) distributions can include packaged versions of the Python binding for libpoppler-qt4. Why do you need a fork on googlecode ? You can simply checkout on your local, make mods and send me patches. But if its really necessary, I can move it off Pardus' SVN repo and put it on Bitbucket. I would rather not create a fork. If I can contribute patches it's good as well. My main reason for creating a (googlecode) repo, is that it would make it easier for me to work on both my machines and commit to the repo often. And to have a well-known place to provide source tarballs I can point users of my application to. Best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ You must be the change you wish to see in the world. -- Mahatma Gandhi ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
On Thu, Dec 3, 2009 at 8:45 PM, Wilbert Berendsen wbs...@xs4all.nl wrote: Op donderdag 03 december 2009 schreef Rajeev: It doesnt have much to do with distributions, because these projects are doing it for their own needs and not for their distributions. I meant that python-poppler-qt4 could become a package in the Linux distribution sense, and that other programs could simply depend om that package, instead of including (some fork of) it in their own source tarball. Thats exactly what I meant too. This being in the Pardus repo has no bearing on whether it can be packaged (as in .deb, .rpm or .pisi packages). [see below] But for the binding to be useful for others, the API coverage would need to be completed. I for myself need the links() method of the Page object and the various Link* classes, but I would be willing to make the binding complete and cover and test the full API of libpoppler-qt4. Cool that would be awesome! :) My main reason for creating a (googlecode) repo, is that it would make it easier for me to work on both my machines and commit to the repo often. And to have a well-known place to provide source tarballs I can point users of my application to. OK. I'll create a bitbucket repo. That should allow you to commit often and also point your users to place where they can get tarballs. Regards Rajeev J Sebastian ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
On Tue Dec 1 10:22:24 GMT 2009, Wilbert Berendsen wrote: at http://websvn.pardus.org.tr/trunk/playground/pypoppler-qt4/?root=uludag there are Python bindings for Poppler-Qt4. I would really like to use them in my application, but I also need the links() method of the Page object working. This method (and the link classes) is not available. Any chance this nice package gets updated? Otherwise I'll try myself but then I need to learn SIP a lot better. :) I made some private modifications to this package some time ago but never got round to doing anything with them. I think Roberto Alsina has something more up to date: http://code.google.com/p/rst2pdf/ David ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
On Thu, Dec 3, 2009 at 4:10 AM, David Boddie da...@boddie.org.uk wrote: On Tue Dec 1 10:22:24 GMT 2009, Wilbert Berendsen wrote: at http://websvn.pardus.org.tr/trunk/playground/pypoppler-qt4/?root=uludag there are Python bindings for Poppler-Qt4. I would really like to use them in my application, but I also need the links() method of the Page object working. This method (and the link classes) is not available. Any chance this nice package gets updated? Otherwise I'll try myself but then I need to learn SIP a lot better. :) I made some private modifications to this package some time ago but never got round to doing anything with them. I think Roberto Alsina has something more up to date: http://code.google.com/p/rst2pdf/ Roberto had sent me his patches and they were integrated into the binding. However, some other projects have made some mods, but not contributed back. No idea why (or whether its ethical). Regards Rajeev J Sebastian ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
On Thu Dec 3 01:07:20 GMT 2009, Rajeev J Sebastian wrote: Roberto had sent me his patches and they were integrated into the binding. However, some other projects have made some mods, but not contributed back. No idea why (or whether its ethical). Mine were quickly done for an article I was writing, though in the end, I never used the bindings. The only possibly worthwhile change I made was removing some hard-coded paths in the configure.py file. David ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4
Hi, at http://websvn.pardus.org.tr/trunk/playground/pypoppler-qt4/?root=uludag there are Python bindings for Poppler-Qt4. I would really like to use them in my application, but I also need the links() method of the Page object working. This method (and the link classes) is not available. Any chance this nice package gets updated? Otherwise I'll try myself but then I need to learn SIP a lot better. :) with best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ You must be the change you wish to see in the world. -- Mahatma Gandhi ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
