Hi, > John Hewson <j...@jahewson.com> hat am 10. Oktober 2014 um 20:05 geschrieben: > > > Simon, > > Andreas has the best handle on this, but off the top of my head what we need > is to finish > making breaking API changes and for the code to have been stable for a while > before > making a 2.0 release. > > Improvements and fixes which still need breaking API changes include: > - Pattern rendering That's almost done, isn't it? Should be part of 2.0
> - Pages resource caching (significant memory usage issues) IMHO could be postponed > - Font embedding (particularly TTF) Is a real show stopper, should be part of 2.0 > - Parsing (Andreas?) I guess we won't get a complete new parser in 2.0, but I try to improve the XRef and the COSStream stuff > - Page Tree (needs completely re-writing) IMHO could be postponed > - Text extraction on Java 8 (this might end up being a breaking change >to the sort) I've already commited PDFBOX-1512, so that it works on Java7. What is the issue with java8? > There’s probably more, such as work on Acroforms, and we need to have much > better > example code for 2.0 due to all the changes. Yes, once PDFBOX-922 is implemented (embedding TTFs) we should be able to improve the creation of Appearance streams. > This seems like a good time to explicitly try to make sure that we have JIRA > issues open > for all outstanding tasks, so that we can track how close 2.0 is to being > ready. The stability > of the code is a pretty good indicator - we’re not there yet. > > I’m going to open some JIRA issues. Andreas, Tilman - please open issues for > any > 2.0 features which you think we need. > > Thanks > > -- John BR Andreas Lehmkühler > > On 10 Oct 2014, at 08:08, Simon Steiner <simonsteiner1...@gmail.com> wrote: > > > Hi, > > > > > > > > Could you set a target date for 2.0 release. What's missing to make a > > release? > > > > > > > > Thanks > > >
