Take a look at the Android UI/runtime packages already in the Termux dependency set and decide which are useful for an IB Android viewport.
Candidates worth inspecting:
- AndroidX
- Material / Material 3
- Markwon
- AndroidX Window
- termux-am-library
Lower-priority / probably infrastructure-only unless a concrete need appears:
- Guava
- Commons IO
- HiddenApiBypass
- core-library desugaring
Architectural constraint: keep the view separate from the rest of IB. UI state and UI-framework decisions should not become the canonical document / fragment / link / index model. The view should consume system state and emit actions; only data deliberately promoted out of the view (for example a saved reading position or annotation) should become persistent core state.
In particular, inspect whether Markwon can serve as a thin renderer for IB fragments while Pensieve retains ownership of fragment identity, document order, links, annotations, provenance, indexes, and navigation.
This is an investigation note, not a request to adopt these dependencies yet.
Take a look at the Android UI/runtime packages already in the Termux dependency set and decide which are useful for an IB Android viewport.
Candidates worth inspecting:
Lower-priority / probably infrastructure-only unless a concrete need appears:
Architectural constraint: keep the view separate from the rest of IB. UI state and UI-framework decisions should not become the canonical document / fragment / link / index model. The view should consume system state and emit actions; only data deliberately promoted out of the view (for example a saved reading position or annotation) should become persistent core state.
In particular, inspect whether Markwon can serve as a thin renderer for IB fragments while Pensieve retains ownership of fragment identity, document order, links, annotations, provenance, indexes, and navigation.
This is an investigation note, not a request to adopt these dependencies yet.