[ViewVC] Diff of: cvs/CV/bin/cv

Comparing CV/bin/cv (file contents):
Revision 1.54 by root, Fri Aug 19 00:19:52 2005 UTC vs.
Revision 1.55 by root, Mon Aug 22 00:30:58 2005 UTC

 =over 4
 =item * optimized directory scanning algorithm
-The directory scanning in CV plays some tricks that - on most modern
+The directory scanning in CV uses some tricks that - on most modern
 filesystems - makes it possible to detect filetypes faster than stat()'ing
 every file. This makes CV suitable for directories with lots of files
 (10000+).
 This algorithm is quite unprecise - it doesn't make a difference between
 files, device nodes, symlinks and the like, and filetype detection is done
 using the file extension only.
+On the positive side, it is usually many orders of magnitude faster than
+traditional scanning techniques (good for directories with 10000 or
+100000+ files).
 =item * queuing for all time-consuming background tasks
 All tasks, such as unlinking files or generating thumbnails, that can be
 done in the background will be done so - no waiting required, even when
 =item * fast image loading
 The time span between the user issuing a command and displaying the new
 image should be as small as possible. CV uses optimized (especially
 for JPEG) loading functions and sacrifices some quality (e.g no gamma
-correction) to achieve this speed.
+correction, although this might change) to achieve this speed.
 =item * fast thumbnail creation
-Thumbnail creation is crucial for me, so it's better be fast. Thumbnail
+Thumbnail creation uses both CPU and Disk-I/O. CV interleaves both, so
+on modern CPUs, thumbnailing is usually limited by I/O speed. Thumbnail
-creation for JPEGs has been specially optimized.
+creation for JPEGs has been specially optimized and can even take
+advantage of multiple CPUs.
 =item * minimum optical clutter
 CV has no menus or other user interface elements that take up a lot of
-screen space. The schnauzer windows can also be somewhat crowded.
+screen space (or are useful for beginning users). The schnauzer windows
+can also be somewhat crowded.
 The point of an image viewer is viewing images, not a nice GUI. This is
 similar to XV's behaviour.
 =item * efficient (and hard to learn) user interface
 CV uses key combinations. A lot. If you are an experienced XV user, you
 will find most of these keys familiar. If not, CV might be hard to use at
 first, but will be an efficient tool later.
+=item * multi-window GUI
+CV doesn't force you to use a specific layout, instead it relies on your
+window manager, thus enabling you to chose whatever layout that suits you
+most.
 =item * i18n'ed filename handling throughout
 As long as glib can recognize your filename encoding (either UTF-8 or
-locale-specific, depending on your settings) and you have the relevant
+locale-specific, depending on the setting of G_BROKEN_FILENAMES) and you
-fonts, CV will display your filenames correctly.
+have the relevant fonts, CV will display your filenames correctly.
 =item * extensible through plug-ins
 I have weird plug-ins that access remote databases to find a
 directory. This is not likely to be of any use to other people. Likewise,

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing CV/bin/cv (file contents): Revision 1.54 by root, Fri Aug 19 00:19:52 2005 UTC vs. Revision 1.55 by root, Mon Aug 22 00:30:58 2005 UTC

Diff Legend

Comparing CV/bin/cv (file contents):
Revision 1.54 by root, Fri Aug 19 00:19:52 2005 UTC vs.
Revision 1.55 by root, Mon Aug 22 00:30:58 2005 UTC