ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/CV/README
(Generate patch)

Comparing CV/README (file contents):
Revision 1.5 by root, Fri Mar 31 10:56:01 2006 UTC vs.
Revision 1.10 by root, Tue Jan 26 02:20:32 2010 UTC

… …
6 6
7FEATURES 7FEATURES
8 CV is supposed to work similar to the venerable XV image viewer, just 8 CV is supposed to work similar to the venerable XV image viewer, just
9 faster. Why faster? 9 faster. Why faster?
10 10
11 * optimized directory scanning algorithm 11 * optimized directory scanning algorithm
12
12 The directory scanning in CV uses some tricks that - on most modern 13 The directory scanning in CV uses some tricks that - on most modern
13 filesystems - makes it possible to detect filetypes faster than 14 filesystems - makes it possible to detect filetypes faster than
14 stat()'ing every file. This makes CV suitable for directories with 15 stat()'ing every file. This makes CV suitable for directories with
15 lots of files (10000+). 16 lots of files (10000+).
16 17
… …
20 21
21 On the positive side, it is usually many orders of magnitude faster 22 On the positive side, it is usually many orders of magnitude faster
22 than traditional scanning techniques (good for directories with 23 than traditional scanning techniques (good for directories with
23 10000 or 100000+ files). 24 10000 or 100000+ files).
24 25
25 * queuing for all time-consuming background tasks 26 * queuing for all time-consuming background tasks
27
26 All tasks, such as unlinking files or generating thumbnails, that 28 All tasks, such as unlinking files or generating thumbnails, that
27 can be done in the background will be done so - no waiting required, 29 can be done in the background will be done so - no waiting required,
28 even when changing directories. 30 even when changing directories.
29 31
30 * use of asynchronous I/O 32 * use of asynchronous I/O
33
31 CV tries to use asynchronous I/O whereever it makes sense, for 34 CV tries to use asynchronous I/O whereever it makes sense, for
32 example while scanning directories, waiting for stat data, unlinking 35 example while scanning directories, waiting for stat data, unlinking
33 files or generating thumbnails. This usually decreases scanning 36 files or generating thumbnails. This usually decreases scanning
34 times for large directories a bit (especially on RAID devices and 37 times for large directories a bit (especially on RAID devices and
35 over NFS) and makes CV much more interactive. 38 over NFS) and makes CV much more interactive.
36 39
37 * fast image loading 40 * fast image loading
41
38 The time span between the user issuing a command and displaying the 42 The time span between the user issuing a command and displaying the
39 new image should be as small as possible. CV uses optimized 43 new image should be as small as possible. CV uses optimized
40 (especially for JPEG) loading functions and sacrifices some quality 44 (especially for JPEG) loading functions and sacrifices some quality
41 (e.g no gamma correction, although this might change) to achieve 45 (e.g no gamma correction, although this might change) to achieve
42 this speed. 46 this speed.
43 47
44 * fast thumbnail creation 48 * fast thumbnail creation
49
45 Thumbnail creation uses both CPU and Disk-I/O. CV interleaves both, 50 Thumbnail creation uses both CPU and Disk-I/O. CV interleaves both,
46 so on modern CPUs, thumbnailing is usually limited by I/O speed. 51 so on modern CPUs, thumbnailing is usually limited by I/O speed.
47 Thumbnail creation for JPEGs has been specially optimized and can 52 Thumbnail creation for JPEGs has been specially optimized and can
48 even take advantage of multiple CPUs. 53 even take advantage of multiple CPUs.
49 54
50 * minimum optical clutter 55 * minimum optical clutter
56
51 CV has no menus or other user interface elements that take up a lot 57 CV has no menus or other user interface elements that take up a lot
52 of screen space (or are useful for beginning users). The schnauzer 58 of screen space (or are useful for beginning users). The schnauzer
53 windows can also be somewhat crowded. 59 windows can also be somewhat crowded.
54 60
55 The point of an image viewer is viewing images, not a nice GUI. This 61 The point of an image viewer is viewing images, not a nice GUI. This
56 is similar to XV's behaviour. 62 is similar to XV's behaviour.
57 63
58 * efficient (and hard to learn) user interface 64 * efficient (and hard to learn) user interface
65
59 CV uses key combinations. A lot. If you are an experienced XV user, 66 CV uses key combinations. A lot. If you are an experienced XV user,
60 you will find most of these keys familiar. If not, CV might be hard 67 you will find most of these keys familiar. If not, CV might be hard
61 to use at first, but will be an efficient tool later. 68 to use at first, but will be an efficient tool later.
62 69
63 * multi-window GUI 70 * multi-window GUI
71
64 CV doesn't force you to use a specific layout, instead it relies on 72 CV doesn't force you to use a specific layout, instead it relies on
65 your window manager, thus enabling you to chose whatever layout that 73 your window manager, thus enabling you to chose whatever layout that
66 suits you most. 74 suits you most.
67 75
68 * i18n'ed filename handling throughout 76 * i18n'ed filename handling throughout
77
69 As long as glib can recognize your filename encoding (either UTF-8 78 As long as glib can recognize your filename encoding (either UTF-8
70 or locale-specific, depending on the setting of G_BROKEN_FILENAMES) 79 or locale-specific, depending on the setting of G_BROKEN_FILENAMES)
71 and you have the relevant fonts, CV will display your filenames 80 and you have the relevant fonts, CV will display your filenames
72 correctly. 81 correctly.
73 82
74 * extensible through plug-ins 83 * extensible through plug-ins
84
75 I have weird plug-ins that access remote databases to find a 85 I have weird plug-ins that access remote databases to find a
76 directory. This is not likely to be of any use to other people. 86 directory. This is not likely to be of any use to other people.
77 Likewise, others might have weird requirements I cannot dream of. 87 Likewise, others might have weird requirements I cannot dream of.
78 88
79 * filename clustering 89 * filename clustering
90
80 Among the standard plug-ins is a filename clustering plug-in, that 91 Among the standard plug-ins is a filename clustering plug-in, that
81 (in case of tens of thousands images in one directory) might be able 92 (in case of tens of thousands images in one directory) might be able
82 to cluster similar names together. 93 to cluster similar names together.
83 94
84DESCRIPTION 95DESCRIPTION
… …
152 ctrl-shift-a select all files currently displayed in the schnauzer window 163 ctrl-shift-a select all files currently displayed in the schnauzer window
153 ctrl-d delete selected files WITHOUT ASKING AGAIN 164 ctrl-d delete selected files WITHOUT ASKING AGAIN
154 ctrl-g force generation of thumbnais for the selected files 165 ctrl-g force generation of thumbnais for the selected files
155 ctrl-s rescan current direcory or files updates/deletes etc. 166 ctrl-s rescan current direcory or files updates/deletes etc.
156 ctrl-u update selected (or all) icons if neccessary 167 ctrl-u update selected (or all) icons if neccessary
157 ctrl-l don't use, will become a plug-in eventually 168 ctrl-- unselected thumbnailed images
169 ctrl-+ keep only thumbnailed images, deselect others
158 170
159 ^ go to parent directory (caret). 171 ^ go to parent directory (caret).
160 172
161 0-9, 173 0-9,
162 a-z find the first filename beginning with this letter 174 a-z find the first filename beginning with this letter
… …
203 or require "/fs/cv/cvplugin.pl"; 215 or require "/fs/cv/cvplugin.pl";
204 216
205 This will load a plug-in, but only if the machine *ether* is reachable 217 This will load a plug-in, but only if the machine *ether* is reachable
206 (supposedly the plug-in is networked in some way :). 218 (supposedly the plug-in is networked in some way :).
207 219
208ENVIRONMENT 220ENVIRONMENT VARIABLES
209 CV_EDITOR 221 CV_EDITOR
210 The program that gets executed when the user presses "CTRL-e" in the 222 The program that gets executed when the user presses "CTRL-e" in the
211 Schnauzer or image window. The default is "gimp". 223 Schnauzer or image window. The default is "gimp".
212 224
225 CV_AUDIO_PLAYER
226 Program used to play all sorts of audio (wav, aif, mp3, ogg...),
227 default "play". Will be called like "$CV_AUDIO_PLAYER -- <path>".
228
213 CV_PRINT_DESTINATION 229 CV_PRINT_DESTINATION
214 The default (perl-style) destination to use in the print dialog. 230 The default (perl-style) destination to use in the print dialog.
215 231
216 CV_TRASHCAN 232 CV_TRASHCAN
217 When set, must point to a directory where all files that are deleted 233 When set, must point to a directory where all files that are deleted
218 are moved to. If unset, files that are deleted are really being 234 by the "Delete Physically" (ctrl-d) action are moved to (other
219 deleted. 235 deletion actions still delete!). If unset, files that are deleted
236 are really being deleted.
237
238SIGNALS
239 Sending CV a SIGUSR1 signal will cause all image viewers to reload the
240 currently loaded image. This is useful if you use CV as a viewer for
241 changing data - just run it in the background with some path and each
242 time the image changes, send it a SIGUSR1.
220 243
221SECURITY CONSIDERATIONS 244SECURITY CONSIDERATIONS
222 CV uses Pixbuf to load non-JPEG images. Pixbuf is not considered safe 245 CV uses Pixbuf to load non-JPEG images. Pixbuf is not considered safe
223 for this purpose, though (from the gtk-2.2 release notes): 246 for this purpose, though (from the gtk-2.2 release notes):
224 247

Diff Legend

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