To see what's going on next, take a look at the Peruse Workboard and have a look at the listed tasks. In the nature of software projects, a programmer's work is never done, and that is of course the case with Peruse as well. As such, it is not a question of why not Okular, but more the point that it is also Peruse, for when your purpose is reading. As with many other things in Peruse, it functions by standing on the shoulders of the enormous talent and technological abilities available from the KDE community and its many frameworks, and Okular is one of those. The reason for this, however, is simple: When you are reading PDF files inside Peruse, you are in fact using Okular. The choice is also not quite so clear cut as "not Okular". While KDE has had the enormously powerful Okular for quite a while now, the way in which it operates is geared directly towards viewing and commenting on large and small documents of so many different types that, well, it is simply too general purpose. There is also something for those who wish to use the ACBF format, without actually reading or creating books (maybe you're doing a command line tool for doing modifications or introspection of books, maybe you're reading metainfo for use in searching), and for that we have libacbf, a QtCore and C++ based library for managing ACBF data. As of Peruse 2.0, this tool is included as a part of the release. Peruse started out as a reading-only tool, but as we progressed with it, it turned out that having something to easily build new books would be very useful, and so was born Peruse Creator, a tool specifically designed to create books based around the Advanced Comic Book Format as stored in Comic Book Archive Zip files. Peruse Creator uses the Comic Book Archive Zip format with ACBF metadata for making new books. With further support for embedded metadata in one of multiple formats:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |