Hi,
why it ist not allowed to derivate or set the an own PageDrawer at the
current trunk-version of Pdfbox.
It is not possible to derivate it because the PageDrawer is final. It's
also not possible to set the PageDrawer because he is defined fixed in
PDFRenderer.
I need this, because i wan
That disappoints me too. I have been deriving from Page drawer for several
years in order to render in .Net. in order to use 2.0, I would need to make
my own build of PDF box that changed that.
On Feb 24, 2015 8:24 AM, "Manfred Pock" wrote:
> Hi,
>
> why it ist not allowed to derivate or set the
Hi Daniel, hi Manfred,
if you could describe your use case - maybe in a JIRA ticket with an
enhancement request or by discussing it further in the mailing list - we might
be able to come up with a solution. There are many changes in PDFBox 2.0
compared to 1.8 with the intention to make it bette
Thanks, Maruan. I've added mine at
https://issues.apache.org/jira/browse/PDFBOX-2691
Manfred, if you'd add a comment explaining your use case, I'm sure that
will help the active developers evaluate possible solutions.
On Tue, Feb 24, 2015 at 2:37 PM, Maruan Sahyoun
wrote:
> Hi Daniel, hi Manfr
Hi Manfred,
This was a conscious decision for 2.0. By allowing subclassing, we expose the
internal details of PageDrawer in our public API, which prevents us from making
modifications to the internal workings of PageDrawer, which means we can’t fix
bugs or make improvements which require intern
