… | |
… | |
6 | |
6 | |
7 | FEATURES |
7 | FEATURES |
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 | |
84 | DESCRIPTION |
95 | DESCRIPTION |
… | |
… | |
97 | ctrl-sift-m toggle using current image size as max image size |
108 | ctrl-sift-m toggle using current image size as max image size |
98 | u uncrop |
109 | u uncrop |
99 | r set scaling mode to 'nearest' (fastest) |
110 | r set scaling mode to 'nearest' (fastest) |
100 | s set scaling mode to 'bilinear' (default) |
111 | s set scaling mode to 'bilinear' (default) |
101 | shift-s set scaling mode to 'hyper' (slowest) |
112 | shift-s set scaling mode to 'hyper' (slowest) |
102 | t rotate clockwise 90° |
113 | t rotate clockwise 90° |
103 | T rotate counterclockwise° |
114 | T rotate counterclockwise° |
104 | a apply all rotations loslessly to a jpeg file (using exiftran) |
115 | a apply all rotations loslessly to a jpeg file (using exiftran) |
105 | ctrl-v open a new visual schnauzer window for the current dir |
116 | ctrl-v open a new visual schnauzer window for the current dir |
106 | ctrl-c clone the current image window |
117 | ctrl-c clone the current image window |
107 | ctrl-e run an editor ($CV_EDITOR or "gimp") on the current image |
118 | ctrl-e run an editor ($CV_EDITOR or "gimp") on the current image |
108 | ctrl-p fire up the print dialog |
119 | ctrl-p fire up the print dialog |