refactor: remove UIKit-to-SwiftUI hosting in reader pages#536
Merged
Conversation
Replace the curl reader UIHostingController bridge with native UIKit page and end page controllers to keep rendering one-way from SwiftUI into UIKit. Extract NativePageItem implementations into dedicated iOS and macOS files for reuse from scroll-based readers. Align the native end page presentation with the SwiftUI design, including next-book metadata, cover rendering, and adaptive button styling on iOS 26.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
UIHostingControllerbridge with native UIKit page controllers to keep rendering flow one-way (SwiftUI -> UIKit).NativeBookCoverViewControllerso mask/shadow/image-loading behavior is reusable and isolated.Testing
make build-iosmake build-macosmake build-tvos