ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/CV/README
Revision: 1.7
Committed: Sun Jan 27 16:49:40 2008 UTC (16 years, 3 months ago) by root
Branch: MAIN
CVS Tags: rel-1_51
Changes since 1.6: +24 -13 lines
Log Message:
*** empty log message ***

File Contents

# User Rev Content
1 root 1.1 NAME
2 root 1.3 cv - a fast gtk+ image viewer loosely modeled after XV
3 root 1.1
4     SYNOPSIS
5     cv [file...]
6    
7 root 1.3 FEATURES
8     CV is supposed to work similar to the venerable XV image viewer, just
9     faster. Why faster?
10    
11 root 1.7 * optimized directory scanning algorithm
12    
13 root 1.3 The directory scanning in CV uses some tricks that - on most modern
14     filesystems - makes it possible to detect filetypes faster than
15     stat()'ing every file. This makes CV suitable for directories with
16     lots of files (10000+).
17    
18     This algorithm is quite unprecise - it doesn't make a difference
19     between files, device nodes, symlinks and the like, and filetype
20     detection is done using the file extension only.
21    
22     On the positive side, it is usually many orders of magnitude faster
23     than traditional scanning techniques (good for directories with
24     10000 or 100000+ files).
25    
26 root 1.7 * queuing for all time-consuming background tasks
27    
28 root 1.3 All tasks, such as unlinking files or generating thumbnails, that
29     can be done in the background will be done so - no waiting required,
30     even when changing directories.
31    
32 root 1.7 * use of asynchronous I/O
33    
34 root 1.3 CV tries to use asynchronous I/O whereever it makes sense, for
35     example while scanning directories, waiting for stat data, unlinking
36     files or generating thumbnails. This usually decreases scanning
37     times for large directories a bit (especially on RAID devices and
38     over NFS) and makes CV much more interactive.
39    
40 root 1.7 * fast image loading
41    
42 root 1.3 The time span between the user issuing a command and displaying the
43     new image should be as small as possible. CV uses optimized
44     (especially for JPEG) loading functions and sacrifices some quality
45     (e.g no gamma correction, although this might change) to achieve
46     this speed.
47    
48 root 1.7 * fast thumbnail creation
49    
50 root 1.3 Thumbnail creation uses both CPU and Disk-I/O. CV interleaves both,
51     so on modern CPUs, thumbnailing is usually limited by I/O speed.
52     Thumbnail creation for JPEGs has been specially optimized and can
53     even take advantage of multiple CPUs.
54    
55 root 1.7 * minimum optical clutter
56    
57 root 1.3 CV has no menus or other user interface elements that take up a lot
58     of screen space (or are useful for beginning users). The schnauzer
59     windows can also be somewhat crowded.
60    
61     The point of an image viewer is viewing images, not a nice GUI. This
62     is similar to XV's behaviour.
63    
64 root 1.7 * efficient (and hard to learn) user interface
65    
66 root 1.3 CV uses key combinations. A lot. If you are an experienced XV user,
67     you will find most of these keys familiar. If not, CV might be hard
68     to use at first, but will be an efficient tool later.
69    
70 root 1.7 * multi-window GUI
71    
72 root 1.3 CV doesn't force you to use a specific layout, instead it relies on
73     your window manager, thus enabling you to chose whatever layout that
74     suits you most.
75    
76 root 1.7 * i18n'ed filename handling throughout
77    
78 root 1.3 As long as glib can recognize your filename encoding (either UTF-8
79     or locale-specific, depending on the setting of G_BROKEN_FILENAMES)
80     and you have the relevant fonts, CV will display your filenames
81     correctly.
82    
83 root 1.7 * extensible through plug-ins
84    
85 root 1.3 I have weird plug-ins that access remote databases to find a
86     directory. This is not likely to be of any use to other people.
87     Likewise, others might have weird requirements I cannot dream of.
88    
89 root 1.7 * filename clustering
90    
91 root 1.3 Among the standard plug-ins is a filename clustering plug-in, that
92     (in case of tens of thousands images in one directory) might be able
93     to cluster similar names together.
94    
95 root 1.1 DESCRIPTION
96     THE IMAGE WINDOW
97     You can use the following keys in the image window:
98    
99 root 1.3 q quit the program
100     < half the image size
101     > double the image size
102     , shrink the image by 10%
103     . enlarge the image by 10%
104     n reset to normal size
105     m maximize to screensize
106     M maximize to screensize, respecting image aspect
107     ctrl-m toggle maxpect-always mode
108 root 1.4 ctrl-sift-m toggle using current image size as max image size
109 root 1.3 u uncrop
110     r set scaling mode to 'nearest' (fastest)
111     s set scaling mode to 'bilinear' (default)
112     shift-s set scaling mode to 'hyper' (slowest)
113 root 1.7 t rotate clockwise 90°
114     T rotate counterclockwise°
115 root 1.5 a apply all rotations loslessly to a jpeg file (using exiftran)
116 root 1.3 ctrl-v open a new visual schnauzer window for the current dir
117 root 1.4 ctrl-c clone the current image window
118 root 1.3 ctrl-e run an editor ($CV_EDITOR or "gimp") on the current image
119 root 1.4 ctrl-p fire up the print dialog
120 root 1.3 escape cancel a crop action
121 root 1.1
122 root 1.2 And when playing movies, these additional keys are active:
123    
124 root 1.3 left rewind by 10 seconds
125     right forward by 10 seconds
126     down rewind by 60 seconds
127     up forward by 60 seconds
128     pg_up rewind by 600 seconds
129     pg_down forward by 600 seconds
130     o toggle on-screen display
131     p pause/unpause
132     escape stop playing
133     9 turn volume down
134     0 turn volume up
135 root 1.2
136 root 1.3 Any other keys will be sent to the default schnauzer window, which can
137     be toggled on and off by right-clicking into the image window.
138 root 1.1
139 root 1.3 Left-clicking into the image window will let you crop the image (usually
140     to zoom into large images that CV scales down).
141 root 1.1
142     THE VISUAL SCHNAUZER
143 root 1.4 Any image-loading action in a schnauzer window acts on the
144     "last-recently-activated" imagewindow, which currently is simply the
145     last image window that received a keypress.
146    
147 root 1.1 You can use the following keys in the schnauzer window:
148    
149 root 1.3 ctrl-space,
150     space move to and display next image
151     ctrl-backspace,
152     backspace move to and display previous image
153     ctrl-return,
154     return display selected picture, or enter directory
155    
156     cursor keys move selection
157     page-up move one page up
158     page-down move one page down
159     home move to first file
160     end move to last file
161    
162     ctrl-a select all files
163     ctrl-shift-a select all files currently displayed in the schnauzer window
164     ctrl-d delete selected files WITHOUT ASKING AGAIN
165     ctrl-g force generation of thumbnais for the selected files
166     ctrl-s rescan current direcory or files updates/deletes etc.
167     ctrl-u update selected (or all) icons if neccessary
168     ctrl-l don't use, will become a plug-in eventually
169    
170     ^ go to parent directory (caret).
171    
172     0-9,
173     a-z find the first filename beginning with this letter
174    
175     Right-clicking into the schnauzer window displays a pop-up menu with
176     additional actions.
177    
178 root 1.4 SELECTION
179     You can select entries in the Schnauzer in a variety of ways:
180    
181     Keyboard
182     Moving the cursor with the keyboard will first deselect all files
183     and then select the file you moved to.
184    
185     Clicking
186     Clicking on an entry will select the one you clicked and deselect
187     all others.
188    
189     Shift-Clicking
190     Shift-clicking will toggle the selection on the entry under the
191     mouse.
192    
193     Dragging
194     Dragging will select all entries between the one selected when
195     pushing the button and the one selected when releasing the button.
196     If you move above or below the schnauzer area while drag-selecting,
197     the schnauzer will move up/down one row twice per second. In
198     addition, horizontal mouse movement acts as a kind of invisible
199     horizontal scrollbar.
200    
201     Hint: double-click works while click-selecting
202     You can double-click any image while click-selecting to display it
203     without stopping the selection process. This will act as if you
204     normally double-clicked the image to display it, and will toggle the
205     selection twice, resulting in no change.
206    
207 root 1.3 FILES
208     When starting, CV runs the .cvrc file in your $HOME directory as if it
209     were a perl script. in that, you will mostly load plug-ins.
210    
211     Example:
212    
213     system "fping -q -t 10 ether"
214     or require "/fs/cv/cvplugin.pl";
215    
216     This will load a plug-in, but only if the machine *ether* is reachable
217     (supposedly the plug-in is networked in some way :).
218 root 1.1
219     ENVIRONMENT
220 root 1.2 CV_EDITOR
221     The program that gets executed when the user presses "CTRL-e" in the
222     Schnauzer or image window. The default is "gimp".
223    
224 root 1.6 CV_AUDIO_PLAYER
225     Program used to play all sorts of audio (wav, aif, mp3, ogg...),
226     default "play". Will be called like "$CV_AUDIO_PLAYER -- <path>".
227    
228 root 1.1 CV_PRINT_DESTINATION
229     The default (perl-style) destination to use in the print dialog.
230    
231 root 1.2 CV_TRASHCAN
232     When set, must point to a directory where all files that are deleted
233     are moved to. If unset, files that are deleted are really being
234     deleted.
235    
236 root 1.1 SECURITY CONSIDERATIONS
237 root 1.3 CV uses Pixbuf to load non-JPEG images. Pixbuf is not considered safe
238     for this purpose, though (from the gtk-2.2 release notes):
239 root 1.1
240     "While efforts have been made to make gdk-pixbuf robust against invalid
241     images, using gdk-pixbuf to load untrusted data is not recommended, due
242     to the likelyhood that there are additional problems where an invalid
243     image could cause gdk-pixbuf to crash or worse."
244    
245     BUGS/TODO
246 root 1.3 Lots of functionality is missing.
247    
248     Pixbuf doesn't always honor G_BROKEN_FILENAMES, so accessing files with
249     names incompatible with utf-8 might fail.
250 root 1.1
251     rotate on disk
252     lots of ui issues
253     save(?)
254     preferences
255    
256     AUTHOR
257     Marc Lehmann <cv@plan9.de>.
258