ReadViewSDK/.planning/phases/04-reader-capabilities/04-01-SUMMARY.md

17 lines
882 B
Markdown

# 04-01 Summary
## Outcome
Wave 1 reconnected the native text backend as a first-class reader path inside the existing shell.
- `RDEPUBReaderController` now builds a real native snapshot from `RDEPUBTextBook` instead of leaving `activePages` / `activeChapters` empty
- Native restore and current-location resolution now go through shared controller helpers instead of scattered text-book special cases
- Native page turns update `RDEPUBReadingSession` with page/spine/chapter context, so reader state stays coherent with the visible page
- `RDReaderView` remained unchanged; it still only consumes content views and page counts
## Compatibility
- No new reader shell or page-turn container was introduced
- TXT and EPUB native text flows still use `RDEPUBReaderController` and `RDEPUBTextContentView`
- `RDEPUBTextBook` remains the backend contract for native reflowable pages