… | |
… | |
160 | |
160 | |
161 | =over 4 |
161 | =over 4 |
162 | |
162 | |
163 | =item * optimized directory scanning algorithm |
163 | =item * optimized directory scanning algorithm |
164 | |
164 | |
165 | The directory scanning in CV plays some tricks that - on most modern |
165 | The directory scanning in CV uses some tricks that - on most modern |
166 | filesystems - makes it possible to detect filetypes faster than stat()'ing |
166 | filesystems - makes it possible to detect filetypes faster than stat()'ing |
167 | every file. This makes CV suitable for directories with lots of files |
167 | every file. This makes CV suitable for directories with lots of files |
168 | (10000+). |
168 | (10000+). |
169 | |
169 | |
170 | This algorithm is quite unprecise - it doesn't make a difference between |
170 | This algorithm is quite unprecise - it doesn't make a difference between |
171 | files, device nodes, symlinks and the like, and filetype detection is done |
171 | files, device nodes, symlinks and the like, and filetype detection is done |
172 | using the file extension only. |
172 | using the file extension only. |
|
|
173 | |
|
|
174 | On the positive side, it is usually many orders of magnitude faster than |
|
|
175 | traditional scanning techniques (good for directories with 10000 or |
|
|
176 | 100000+ files). |
173 | |
177 | |
174 | =item * queuing for all time-consuming background tasks |
178 | =item * queuing for all time-consuming background tasks |
175 | |
179 | |
176 | All tasks, such as unlinking files or generating thumbnails, that can be |
180 | All tasks, such as unlinking files or generating thumbnails, that can be |
177 | done in the background will be done so - no waiting required, even when |
181 | done in the background will be done so - no waiting required, even when |
… | |
… | |
188 | =item * fast image loading |
192 | =item * fast image loading |
189 | |
193 | |
190 | The time span between the user issuing a command and displaying the new |
194 | The time span between the user issuing a command and displaying the new |
191 | image should be as small as possible. CV uses optimized (especially |
195 | image should be as small as possible. CV uses optimized (especially |
192 | for JPEG) loading functions and sacrifices some quality (e.g no gamma |
196 | for JPEG) loading functions and sacrifices some quality (e.g no gamma |
193 | correction) to achieve this speed. |
197 | correction, although this might change) to achieve this speed. |
194 | |
198 | |
195 | =item * fast thumbnail creation |
199 | =item * fast thumbnail creation |
196 | |
200 | |
197 | Thumbnail creation is crucial for me, so it's better be fast. Thumbnail |
201 | Thumbnail creation uses both CPU and Disk-I/O. CV interleaves both, so |
|
|
202 | on modern CPUs, thumbnailing is usually limited by I/O speed. Thumbnail |
198 | creation for JPEGs has been specially optimized. |
203 | creation for JPEGs has been specially optimized and can even take |
|
|
204 | advantage of multiple CPUs. |
199 | |
205 | |
200 | =item * minimum optical clutter |
206 | =item * minimum optical clutter |
201 | |
207 | |
202 | CV has no menus or other user interface elements that take up a lot of |
208 | CV has no menus or other user interface elements that take up a lot of |
203 | screen space. The schnauzer windows can also be somewhat crowded. |
209 | screen space (or are useful for beginning users). The schnauzer windows |
|
|
210 | can also be somewhat crowded. |
204 | |
211 | |
205 | The point of an image viewer is viewing images, not a nice GUI. This is |
212 | The point of an image viewer is viewing images, not a nice GUI. This is |
206 | similar to XV's behaviour. |
213 | similar to XV's behaviour. |
207 | |
214 | |
208 | =item * efficient (and hard to learn) user interface |
215 | =item * efficient (and hard to learn) user interface |
209 | |
216 | |
210 | CV uses key combinations. A lot. If you are an experienced XV user, you |
217 | CV uses key combinations. A lot. If you are an experienced XV user, you |
211 | will find most of these keys familiar. If not, CV might be hard to use at |
218 | will find most of these keys familiar. If not, CV might be hard to use at |
212 | first, but will be an efficient tool later. |
219 | first, but will be an efficient tool later. |
213 | |
220 | |
|
|
221 | =item * multi-window GUI |
|
|
222 | |
|
|
223 | CV doesn't force you to use a specific layout, instead it relies on your |
|
|
224 | window manager, thus enabling you to chose whatever layout that suits you |
|
|
225 | most. |
|
|
226 | |
214 | =item * i18n'ed filename handling throughout |
227 | =item * i18n'ed filename handling throughout |
215 | |
228 | |
216 | As long as glib can recognize your filename encoding (either UTF-8 or |
229 | As long as glib can recognize your filename encoding (either UTF-8 or |
217 | locale-specific, depending on your settings) and you have the relevant |
230 | locale-specific, depending on the setting of G_BROKEN_FILENAMES) and you |
218 | fonts, CV will display your filenames correctly. |
231 | have the relevant fonts, CV will display your filenames correctly. |
219 | |
232 | |
220 | =item * extensible through plug-ins |
233 | =item * extensible through plug-ins |
221 | |
234 | |
222 | I have weird plug-ins that access remote databases to find a |
235 | I have weird plug-ins that access remote databases to find a |
223 | directory. This is not likely to be of any use to other people. Likewise, |
236 | directory. This is not likely to be of any use to other people. Likewise, |