pdfrx 3.0

[espresso3389]

• Layout enhancements + discrete transitions #505 Layout enhancement (including Snap pages? #112)
• Upcoming Flutter Feature: Platform-Specific Asset Inclusion (No More Manual Removal Needed) #530 Build Hooks (requires Dart 3.10) for native libraries (https://dart.dev/tools/hooks)
• Annotation support (extraction and editing? Rel: @feat: Enhanced PDF annotation support with comprehensive metadata ext… #546)
• Hooks (Switch to package:hooks #564)
• Improving loading behavior with explicit initialPageNumber (Repeated viewport “jumping” when opening a PDF at a non-first page (high initialPageNumber) — reproducible with a specific file #586)
• More editing features?

[espresso3389]

Minor changes are aleady merged in 2.X though some of them have minor breaking changes that do not affect majority of the users.

The changes that result in large breaking changes should be implemented on 3.0 (or later). I want to summerize what should be in 3.0 release here.

[enhancient]

Some support for annotations would be good - perhaps starting with converting text highlight annotations and enabling text highlights in pdfrx to be optionally saved to the PDF as an annotation. The ability to delete annotations, possibly move them, and later on create/edit different annotations.

When are you thinking to release 3.0?

[espresso3389]

When are you thinking to release 3.0?

I've closed almost all existing issues and now is the time to go pdfrx 3.0. I hope we can release the first 3.0 release before December?????

So, the actual implementation of editing features can be implemented after releasing 3.0 but we should implement the basic logic that handles page level changes correctly. Especially, some of the annotations are animating interactively, so we should confirm that we can handle it smooth enough.

[hkhere]

Is version 3.0 ready to be released now? Many thanks for the hard work.

[espresso3389]

I'm now super-busy for my business (in Japan, December is the most busiest month) and I promise to start 3.0 plan after finishing the business things...

[espresso3389]

I'm on very complicated situation on merging #505, #581, and #582 (I've force-pushed a old master commit to revert recent PR merges anyway)...

How can I deal with the situation... Help me someone...

[enhancient]

I've resubmitted #505 as #589 - this pulls in changes from master - I didn't have to do any manual merging.

Perhaps you could create a 3.0 branch with #589 merged, and then @quaaantumdev could merge #582 into that? From a quick Look at #582, I didn't think there was too much in there that conflicted, although I wonder if the physics interactions introduced would be better handled in InteractiveViewer?

[davidengler]

any news on this? thank you