> On 26 Jul 2015, at 13:00, Andreas Lehmkuehler <[email protected]> wrote: > > Hi, > > I like all those new features which were added to PDFDebugger lately, as far > as I've already found them ;-) > > I'm thinking about removing PDFReader as PDFDebugger is now able to render > single pages as well and it is doing it even better. > > > WDYT?
Yes. PDFReader is overly complex. It's a terrible example of how to render a PDF using Swing. PDFDebugger achieves a better result in a fraction of the number of lines of code. Given the long-standing rendering glitches in PDFReader, it's unlikely to have "production" users, so I doubt it would be missed. It's useful as a quick debugging tool, but we could (and should) easily extend PDFDebugger to serve that purpose better. One related question is "should we offer a standalone Swing component?", personally I don't think so, firstly because Java GUIs are not so popular anymore - the demand just isn't there, and secondly because doing so is very hard to get right for a "one size fits all" approach. Smooth scrolling, multi-page views, double buffering, background rendering, etc. are needed to produce a "production-ready" experience. That's not something I have any appetite for. It might be worth moving PDFDebugger into its own module where it can develop freely without intermingling with our public APIs in the tools module. -- John > > BR > Andreas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
