Hi all,
I am very greatful to zyx for his work in reviewing and committing patches
to PoDoFo! Thanks again for your efforts! Similarly, all other
contributions to PoDoFo are welcome and these contributions are mostly
which keeps the development ongoin nowadays.
Still, I also agree with zyx that unnecessary API changes should be
avoided.
Is there a chance to create a separate patch of yours, which e.g. fixes
only the typos in the documentation and includes all the cleanup which DO
NOT break the API? I am quite sure this could be committed.
Best regards,
Dominik
Best regards,
Dominik
On Mon, Feb 1, 2016 at 10:07 AM, zyx <z...@litepdf.cz> wrote:
> On Sun, 2016-01-31 at 23:58 +0000, Matthew Brincke wrote:
> > I read your other e-mail about a build error, AFAIK I have corrected it
> with
> > the patch attached to this e-mail to be applied in addition to the both
> parts.
>
> Hi,
> your message is not properly threaded, I wasn't sure you talk to me
> until I read it to the very bottom. Also because other users claimed
> build errors in various environments recently.
>
> > - zyx maintains a product based on PoDoFo himself so I suspect why he
> acts like this
>
> Heh. Should I take this personally? I do not mind myself, as the
> litePDF maintainer, I do not expect any massive changes being needed in
> the litePDF project, because its main aim is drawing. I wrote both
> reasons in the initial email. I can repeat them here again, in a more
> verbose way, if it'll help:
>
> 1) API changes *in any* project is a pita, especially when the API
> change doesn't bring anything new, when it's just a cleanup of function
> names and similar "boring" changes.
>
> 2) I am *not* a maintainer of PoDoFo. The only reason why I have commit
> rights to this project is that I did upstream my changes in the PoDoFo
> drawing API. It was an API change and it allowed PoDoFo to have more
> generic drawing API, following PDF specification closely. I believe
> that drawing API change was a pita for exiting users too, but again, it
> was a good change and brought many good things for the drawing. Thus,
> as I am *not* the maintainer, it's not my duty to decide whether any
> API change can be done or not.
>
> Honestly, I do not know why I take care of patches to PoDoFo from this
> list for the past several years. I just want to return back something
> to the community of PoDoFo, the same reason why I did upstream my
> drawing API changes. To let people benefit from the Open Source
> project.
>
> Thus no, this is not a selfish decision from my side. It's only a
> historical experience as a developer and a user of several libraries.
>
> Bye,
> zyx
>
> --
> http://www.litePDF.cz i...@litepdf.cz
>
>
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Podofo-users mailing list
> Podofo-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/podofo-users
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users
