The Readium project is therefore split in different parts: On the other side, desktop applications (on Windows, OSX and Linux) are approached using cross-platform technologies, i.e. The Swift and Kotlin toolkits can nevertheless be integrated in applications based on cross-platform frameworks like Flutter and ReactNative. This enables the use of the most powerful aspects of each native environment and ends up with a small and efficient codebase. Swift for the iOS target and Kotlin for the Android target. At the same time, these modules are designed so that they CAN be easily and seamlessly combined to produce complete reading systems.įor rendering content, these toolkits leverage the capabilities of modern browser engines and supplement those capabilities with modules (polyfills, if you will) that provide additional functionalities.Ī specific aspect of the mobile toolkits is that instead of a “platform-neutral” C++ core, the codebase is implemented in native code, i.e. The different software modules composing these toolkits are intended to be, insofar as possible, independent of each other and can be used outside of the overall architecture. These toolkits enable the processing and display of multiple kinds of publication, including EPUB 2 and EPUB 3, PDF, audiobooks and Divina visual narratives (comics / manga / bandes dessinées). Different implementations can therefore share the same architecture, model, interfaces a developer should therefore be able to switch from one implementation to another without feeling lost. The main goal of this project is to create a modular open-source codebase, with a clean software architecture and documentation, which allows the easy development of reading applications on three types of platforms: mobile, desktop and Web.
0 Comments
Leave a Reply. |