VOICE Home Page: http://www.os2voice.org
[Previous Page] [Next Page]
I have performed the tests again, having converted the same image to PNG format
(to retain both quality and color depth). I started with a freshly booted system
and opened the image into PMView 1.04 from the Drives object. I then rebooted the
system and did the same for PMView 2.0 beta 8. I then did both tests in reverse
order, again on freshly booted systems each time.
PMView 1.04 slowed down quite a bit compared to my original tests, signifying
that PNG decoding is not as efficient as raw bitmap decoding. Both new tests on
version 1.04 showed a 50 second load time.
Conversely, PMView 2.0 actually decoded the PNG image faster than it had decoded
the BMP! Load time went down from 96 seconds to only 90 seconds. Still slower than
PMView 1.04, but this is primarily due to my system's memory. I have only 32 megabytes
of RAM and PMView 2.0 uses 2 megabytes more RAM than version 1.04, therefore my
system is swapping to the hard drive more in version 2.0. Swapping equals a major
slowdown. If your system has 64 or more megabytes of RAM, you will probably never
notice a difference between the two.
Also, I was incorrect in stating that the inability to quickly and easily display
[+] next to drives upon first opening the File Open Container was due to a developer
tool limitation. It is in fact a limitation of the container which is a part of
OS/2 itself. Nevertheless, the problem is unlikely to be remedied by anyone other
than IBM. The Win32 container does allow the [+] to be applied next to the drive
letters without having to scan each drive for subdirectories. However, even when
the [+] is displayed automatically, you may not like it -- PMView might then tell
you a drive has subdirectories when it does not, and you'll never be sure until
you click it.
Another nice new feature for people who need to view a large number of images
one after another is a read-ahead cache which will speed up loading the previous
and next images in the current directory.
For those of us running (or planning to run) multiple operating systems, not
only will there be the OS/2 and Win32 versions of PMView, but Nielsen is looking
to build Linux and BeOS versions after 2.0 goes on the open market.
With the birth of the Linux version of PMView, we are likely to see support not
only for CFM and STI TWAIN scanning but also for the free open-source SANE scanning
Another feature planned for a future release is support for merging bitmaps while
maintaining transparency -- for instance, to take a GIF image of a dog which has
a completely transparent background all around the dog and place it into another
GIF file. "Transparent" sections are actually of a color, but the GIF
file tells any program which supports transparency to not display that color and
to let whatever is beneath the GIF show through. Currently, trying to merge a "transparent"
image onto another image in PMView will display a rather ugly output file with the
"transparency color" showing. In the future this will be changed, according
CFM TWAIN (http://www.cfm.de/f_products_start.htm)
STI TWAIN (http://www.stiscan.com)