@Maruan, thanks for starting this initative :-)
Am 11.10.23 um 07:53 schrieb [email protected]:
Dear colleagues,
with 3.0 being released and 4.0 being started I'd like to start
discussing what the major plans are for 4.0. And maybe in a way that
the release can be made faster than what we had for 3.0. (maybe size it
in a way that we can do the dev stuff by spring 2024 and then release
in summer 2024 followed by a 4.1 release to add to that instead of
doing a big bang like 3.0)
Sounds good to me.
Shall we share some ideas via the mailing list or start a page on our
website (I think ml is easier to do). We can still document the major
initiatives as soon as we have agreed in a blog post.
I agree, we need some sort of plan for the next version to avoid another
big bang release. I don't have to be that formal, but we shall agree on
bigger changes to be added to the next major release
Here are my current thoughts (some of which might also be backported to
3.0) in no particular order
- appareance stream handlers for interactive form widgets (similar to
what we have for annotations) also allowing one to add their own
handler
- replacement or at least new base for XMPBox (current thought is to
have a new base parser and add if possible XMPBox current end user api
on top - might be able to reuse xmlgraphics XMP lib). Would allow to
better deal with XMPs which are not standard and make it easier to add
to existing XMPs low level.
IMHO XMP-support is not essential but optional so that it is a good idea
to use some existing lib instead of implementing our own one.
- then we had the discussion about an event handler/listener similar to
what fop provides so one can listen to corrections/repairs done under
the hood (I know that we can only lay the ground for that as this is a
major undertaking given all the places where we correct things)
That might be a big thing ...
- enhance the parsing to keep the information about incremental
versions (better debugging, trace of changes done ...)
I'm not sure which details maybe be important, but let us start a discussion
- review and add some more PDF 2.0 capabilities
In most cases this can be done in little steps
- better text formatting/language support (maybe by including fop parts
or looking into using HarfBuzz)
- I'd also like to discuss reaching out to fop to look at integrating
some of their font handling into fontbox
Good ideas as well ....
...
That list is already long and I think would be too much given above
idea of release planning.
;-)
With regards to versioning I'd like to propose that we have 2.0 as LTS
and 4.x being the next LTS.
First of all, what is your definition of a LTS version? Of course is a
long term version, but what is long and when does such version reach EOL?
Why did you choose 2.0 as LTS? 2.0.0 was released in 2016, doesn't that
already qualify as LTS? 2.0 requires java 6, a very old version.
Why not choose 3.0 as LTS? It requires java 8, a more or less old
version but still widely used and the last version before they start
removing apis. 3.0 is the last version including preflight.
We should discuss that in a separate thread, juts wanted to share my
thoughts as a starter
Thoughts
BR
Maruan
---------------------------------------------------------------------
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]
