Peruse 2.0 Beta 1 uses Advanced Comic Book Format metadata

For those of you who are new, Peruse is the KDE project for the comic book reader, which consists of the reader application, Peruse Reader and the comic book creation tool called Peruse Creator. The project also includes a library named libacbf, which allows applications to use Advanced Comic Book Format (ACBF) metadata without performing manual analysis or XML data generation.

Since the most recent release, a lot of things have happened, including a lot of fixes:

FRAMEWORK BASED ON FRAMES

A frame of a much larger page, so you can see all the beautiful details.

TRANSLATED BANDS

Translations - because language should not be a barrier to a good comic book.

VERY EXTENSIVE CREATOR

Editing a link text area.

CACHE BOOK COLLECTION

Previously, Peruse scanned the system at startup each time and built a complete database with all the books. It now has a persistent cache.

PLAYGROUND

Peruse graduated from a playground project (the experimental section of KDE for projects that are not yet considered complete enough) and is now a full member of KDE.

ACBF LIBRARY

Details of a book

KIRIGAMI 2

Peruse's initial launch was built on top of Kirigami 1, in the early days of development to what would eventually become Plasma Mobile. One of the first things that happened after the release of version 1.2 was the porting of Peruse to Kirigami 2, and the result for the user is partially a more modern and stable code, but also much easier to navigate using a keyboard.

SOFTER PROCESSING, SAFER

The way images are served in QML is something called an image provider. The old method used by Peruse was a set of simple image providers that tried to reduce their own behavior somewhat, but in reality tended to block operations quite badly and also caused severe thread overload. on slower systems (such as on a PinePhone).

THEY ARE NO LONGER SUBMODULES

Peruse had previously used code to read comics based on book archives (those with the cbr file suffix - the most common). This proved to be an endless headache for packers and the decision was made to import the full code into Peruse.