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
Oh yes, it’s nearly there, when I get a decent chunk of spare time it will get done. > >> - Pages resource caching (significant memory usage issues) > IMHO could be postponed The catch is that it will be a breaking API change, so it’d be better to get it into 2.0 while we can. Otherwise I’d agree. > >> - Font embedding (particularly TTF) > Is a real show stopper, should be part of 2.0 Yep. We’re getting there slowly, there’s lots of pieces which need to work together. >> - 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 It would be great if we could get rid of the old parser and switch to the non-sequential parser, WDYT? >> - Page Tree (needs completely re-writing) > IMHO could be postponed Once again the catch is that this will be a breaking API change in an important place, so it’d be smart to do it in 2.0. >> - 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? Same thing, so the Java 7 fix will fix this too. >> 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. I feel like we could definitely postpone this one, it seems like we’d just be adding APIs and not breaking anything, so it can wait? >> 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 >>> >>