Thanks for all the effort you guys put into writing libpar2, it was really easy to integrate thanks to all the effort you put into writing the library. Even with the lack of API documentation the source code was very easy to understand.
One minor snag I ran into is that the signals aren't emitted if the -qq flag is passed to the CommandLine instance. It would be desirable that developers who are linking to the library are given the option to connect the signals to their own application even when libpar2 is outputting no information to the console.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Bleh, forgot to mention : it's integrates into KDE as a kpart, so it's also embedded into konqueror and can easily be reused in other KDE applications. Eventually it will end up being ported to KDE4 and integrated into my binary newsreader KNewz.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I have written a KDE 3.5 frontend for libpar2. It's called KPar2 and is hosted on http://code.google.com/p/kpar2/ It also has a page on KDE-Apps : http://www.kde-apps.org/content/show.php/KPar2?content=70101
Thanks for all the effort you guys put into writing libpar2, it was really easy to integrate thanks to all the effort you put into writing the library. Even with the lack of API documentation the source code was very easy to understand.
One minor snag I ran into is that the signals aren't emitted if the -qq flag is passed to the CommandLine instance. It would be desirable that developers who are linking to the library are given the option to connect the signals to their own application even when libpar2 is outputting no information to the console.
Bleh, forgot to mention : it's integrates into KDE as a kpart, so it's also embedded into konqueror and can easily be reused in other KDE applications. Eventually it will end up being ported to KDE4 and integrated into my binary newsreader KNewz.