October 8th, 2011· Fixed missing Windows start menu entry and shortcuts when using installer.
· Added support for environment variable JAVA_HOME to chose a specific JVM in the Windows launcher jomic.bat.
August 5th, 2011· Fixed conversion of CBR comics which still tried to use the unrar command line tool.
· Fixed processing of CBR comics that use Unicode for contained file names.
· Cleaned up order of comics during conversion, which seemed rather random.
April 22nd, 2011Application:
· Fixed excessive CPU usage if an image could not be read due to certain error conditions.
· Fixed spurious broken images if a comic ZIP was created using Mac OS X's compress in Finder. For every image like some.png, compress adds a file __MACOSX/.some.png containing the resource fork [Bug 3285681].
· Fixed help menu under Mac OS X, which automatically got a search bar that never found anything and disabled all other help menu entries.
· Fixed size and location of dialog to set blur options. If the dialog now has a sensible size when opened for the first time and remembers its size and location between application launches.
· Fixed missing images for web start.
· Changed comic conversion to continue with next comic in case one comic fails.
· Added possibility to open and convert more PDF comics than before by upgrading to PDFBox 1.5.
· Changed memory available for Java from 256 MB to 768 MB in order to cope with PDFBox's increased memory requirements when reading complex PDF documents.
· Improved look and feel under Mac OS X 10.6 by updating to Quaqua 6.5.
· Changed internal image reading, rendering and filtering to use the Java standard library instead of JAI. Ideally you should not notice any difference. Some things you might notice: Certain broken images cannot be read anymore ("Booh! Hiss!" - Fix 'em!). Detection and processing of broken images is slightly faster. Application launch is slightly faster. The user interface is a little snappier. Certain error messages are less incomprehensible.
Development:
· Changed filters for blur to be based on code by JHLabs instead if JAI.
· Removed the need to be online in order to build the documentation.
· Changed XML pretty printer from Java to Python. In order for this to work, you need the lxml Python library. Refer to the developer guide for details.
· Removed application dependency on JAI. Some test cases still use it to show difference and validate test results, so JAI is still part of the repository.
· Improved section on getting the first build to work. (After trying it myself for the first time in 3 years, I noticed some pitfalls...).
April 22nd, 2008· Fixed error: Problem occurs when computing a tile by the owner [Bug 1827855].
· Fixed rendering of black and white images [Bug 1456026].
· Fixed various rendering issues in windowed mode by getting rid of the deprecated and buggy DisplayJAI and using code similar to full screen mode.
· Fixed resource leaks related to image drawing (Developer note: missing Graphics.dispose()).
· Improved performance of displaying certain JFIF/JPEG images that until now occupied the CPU for several seconds. (Developer note: This was caused by Graphics2D.drawRenderedImage() being awfully slow with a scale transformation and render settings using VALUE_INTERPOLATION_BILINEAR and has been fixed by internally enforcing all images to be 32-bit RBG without alpha channel.)
· Fixed "Can't find resouce for bundle" error when attempting to warn that aweb page could not be opened [Bug 1886584].
· Changed space bar and mouse navigation to automatically open previous/nextcomic when reaching the beginning/end of comic. Page up/down still behavethe old way and can be used to navigate without possible files being opened.
· Added rotation set with View Rotate right and View Rotate left to bepreserved over sessions.
· Added http://jomic.sourceforge.net/PAD_FILE.XML to make it simple forautomatic tools and interested web sites to check for updates of Jomic.
· Updated Quaqua to version 4.4.1.
· Added frequently asked question "Why are some images of a comic displayedin wrong order?"
Find us on Google+
