… | |
… | |
43 | $viewer->load_image ($_[1]); |
43 | $viewer->load_image ($_[1]); |
44 | }); |
44 | }); |
45 | |
45 | |
46 | Gtk2::CV::Plugin->call (new_schnauzer => $s); |
46 | Gtk2::CV::Plugin->call (new_schnauzer => $s); |
47 | |
47 | |
48 | $s; |
48 | $s |
49 | } |
49 | } |
50 | |
50 | |
51 | sub std_keys { |
51 | sub std_keys { |
52 | my $key = $_[1]->keyval; |
52 | my $key = $_[1]->keyval; |
53 | my $state = $_[1]->state; |
53 | my $state = $_[1]->state; |
… | |
… | |
102 | |
102 | |
103 | $viewer->signal_connect (button3_press_event => sub { |
103 | $viewer->signal_connect (button3_press_event => sub { |
104 | $mainwin->visible |
104 | $mainwin->visible |
105 | ? $mainwin->hide |
105 | ? $mainwin->hide |
106 | : $mainwin->show_all; |
106 | : $mainwin->show_all; |
107 | 1; |
107 | 1 |
108 | }); |
108 | }); |
109 | |
109 | |
110 | Gtk2::CV::Plugin->call (new_imagewindow => $viewer); |
110 | Gtk2::CV::Plugin->call (new_imagewindow => $viewer); |
111 | |
111 | |
112 | $schnauzer = new_schnauzer; |
112 | $schnauzer = new_schnauzer; |
113 | |
113 | |
114 | $mainwin = new Gtk2::Window; |
114 | $mainwin = new Gtk2::Window; |
115 | $mainwin->set_title ("CV"); |
115 | $mainwin->set_title ("CV"); |
116 | $mainwin->add (my $vbox = new Gtk2::VBox); |
116 | $mainwin->add (my $vbox = new Gtk2::VBox); |
117 | $mainwin->signal_connect (delete_event => sub { $mainwin->hide; 1; }); |
117 | $mainwin->signal_connect (delete_event => sub { $mainwin->hide; 1 }); |
118 | |
118 | |
119 | $vbox->add ($schnauzer); |
119 | $vbox->add ($schnauzer); |
120 | $vbox->pack_end (my $frame = new Gtk2::Frame, 0, 0, 0); |
120 | $vbox->pack_end (my $frame = new Gtk2::Frame, 0, 0, 0); |
121 | $frame->add (my $hbox = new Gtk2::HBox 0, 0); |
121 | $frame->add (my $hbox = new Gtk2::HBox 0, 0); |
122 | $hbox->pack_start ((new Gtk2::Label "Info: "), 0, 0, 0); |
122 | $hbox->pack_start ((new Gtk2::Label "Info: "), 0, 0, 0); |
… | |
… | |
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 | |
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). |
|
|
177 | |
|
|
178 | =item * queuing for all time-consuming background tasks |
|
|
179 | |
|
|
180 | All tasks, such as unlinking files or generating thumbnails, that can be |
|
|
181 | done in the background will be done so - no waiting required, even when |
|
|
182 | changing directories. |
|
|
183 | |
174 | =item * use of asynchronous I/O |
184 | =item * use of asynchronous I/O |
175 | |
185 | |
176 | CV tries to use asynchronous I/O whereever it makes sense, for example |
186 | CV tries to use asynchronous I/O whereever it makes sense, for example |
177 | while scanning directories, waiting for stat data or unlinking files. This |
187 | while scanning directories, waiting for stat data, unlinking files or |
178 | usually decreases scanning times for large directories a bit (especially |
188 | generating thumbnails. This usually decreases scanning times for large |
179 | on RAID devices and over NFS). |
189 | directories a bit (especially on RAID devices and over NFS) and makes CV |
|
|
190 | much more interactive. |
180 | |
191 | |
181 | =item * fast image loading |
192 | =item * fast image loading |
182 | |
193 | |
183 | 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 |
184 | image should be as small as possible. CV uses optimized (especially |
195 | image should be as small as possible. CV uses optimized (especially |
185 | 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 |
186 | correction) to achieve this speed. |
197 | correction, although this might change) to achieve this speed. |
187 | |
198 | |
188 | =item * fast thumbnail creation |
199 | =item * fast thumbnail creation |
189 | |
200 | |
190 | 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 |
191 | creation for JPEGs has been specially optimized. |
203 | creation for JPEGs has been specially optimized and can even take |
|
|
204 | advantage of multiple CPUs. |
192 | |
205 | |
193 | =item * minimum optical clutter |
206 | =item * minimum optical clutter |
194 | |
207 | |
195 | 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 |
196 | 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. |
197 | |
211 | |
198 | 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 |
199 | similar to XV's behaviour. |
213 | similar to XV's behaviour. |
200 | |
214 | |
201 | =item * efficient (and hard to learn) user interface |
215 | =item * efficient (and hard to learn) user interface |
202 | |
216 | |
203 | 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 |
204 | 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 |
205 | first, but will be an efficient tool later. |
219 | first, but will be an efficient tool later. |
206 | |
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 | |
207 | =item * i18n'ed filename handling throughout |
227 | =item * i18n'ed filename handling throughout |
208 | |
228 | |
209 | 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 |
210 | locale-specific, depending on your settings) and you have the relevant |
230 | locale-specific, depending on the setting of G_BROKEN_FILENAMES) and you |
211 | fonts, CV will display your filenames correctly. |
231 | have the relevant fonts, CV will display your filenames correctly. |
212 | |
232 | |
213 | =item * extensible through plug-ins |
233 | =item * extensible through plug-ins |
214 | |
234 | |
215 | 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 |
216 | 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, |
… | |
… | |
245 | shift-s set scaling mode to 'hyper' (slowest) |
265 | shift-s set scaling mode to 'hyper' (slowest) |
246 | t rotate clockwise 90° |
266 | t rotate clockwise 90° |
247 | T rotate counterclockwise° |
267 | T rotate counterclockwise° |
248 | ctrl-v open a new visual schnauzer window for the current dir |
268 | ctrl-v open a new visual schnauzer window for the current dir |
249 | ctrl-e run an editor ($CV_EDITOR or "gimp") on the current image |
269 | ctrl-e run an editor ($CV_EDITOR or "gimp") on the current image |
250 | ctrl-p fire up the print fialog |
270 | ctrl-p fire up the print dialog |
251 | escape cancel a crop action |
271 | escape cancel a crop action |
252 | |
272 | |
253 | And when playing movies, these additional keys are active: |
273 | And when playing movies, these additional keys are active: |
254 | |
274 | |
255 | left rewind by 10 seconds |
275 | left rewind by 10 seconds |
… | |
… | |
293 | ctrl-g force generation of thumbnais for the selected files |
313 | ctrl-g force generation of thumbnais for the selected files |
294 | ctrl-s rescan current direcory or files updates/deletes etc. |
314 | ctrl-s rescan current direcory or files updates/deletes etc. |
295 | ctrl-u update selected (or all) icons if neccessary |
315 | ctrl-u update selected (or all) icons if neccessary |
296 | ctrl-l don't use, will become a plug-in eventually |
316 | ctrl-l don't use, will become a plug-in eventually |
297 | |
317 | |
|
|
318 | ^ go to parent directory (caret). |
|
|
319 | |
298 | 0-9, |
320 | 0-9, |
299 | a-z find the first filename beginning with this letter |
321 | a-z find the first filename beginning with this letter |
300 | |
322 | |
301 | Right-clicking into the schnauzer window displays a pop-up menu with |
323 | Right-clicking into the schnauzer window displays a pop-up menu with |
302 | additional actions. |
324 | additional actions. |
… | |
… | |
334 | |
356 | |
335 | =back |
357 | =back |
336 | |
358 | |
337 | =head1 SECURITY CONSIDERATIONS |
359 | =head1 SECURITY CONSIDERATIONS |
338 | |
360 | |
339 | CV uses Pixbuf to load images. Pixbuf is not considered safe for this |
361 | CV uses Pixbuf to load non-JPEG images. Pixbuf is not considered safe for |
340 | purpose, though (from the gtk-2.2 release notes): |
362 | this purpose, though (from the gtk-2.2 release notes): |
341 | |
363 | |
342 | "While efforts have been made to make gdk-pixbuf robust against invalid |
364 | "While efforts have been made to make gdk-pixbuf robust against invalid |
343 | images, using gdk-pixbuf to load untrusted data is not recommended, due to |
365 | images, using gdk-pixbuf to load untrusted data is not recommended, due to |
344 | the likelyhood that there are additional problems where an invalid image |
366 | the likelyhood that there are additional problems where an invalid image |
345 | could cause gdk-pixbuf to crash or worse." |
367 | could cause gdk-pixbuf to crash or worse." |
… | |
… | |
347 | =head1 BUGS/TODO |
369 | =head1 BUGS/TODO |
348 | |
370 | |
349 | Lots of functionality is missing. |
371 | Lots of functionality is missing. |
350 | |
372 | |
351 | Pixbuf doesn't always honor G_BROKEN_FILENAMES, so accessing files with |
373 | Pixbuf doesn't always honor G_BROKEN_FILENAMES, so accessing files with |
352 | names incompatible might utf-8 fail. |
374 | names incompatible with utf-8 might fail. |
353 | |
375 | |
354 | rotate on disk |
376 | rotate on disk |
355 | lots of ui issues |
377 | lots of ui issues |
356 | save(?) |
378 | save(?) |
357 | preferences |
379 | preferences |
358 | shift-cursor in schnauzer |
|
|
359 | |
380 | |
360 | =head1 AUTHOR |
381 | =head1 AUTHOR |
361 | |
382 | |
362 | Marc Lehmann <cv@plan9.de>. |
383 | Marc Lehmann <cv@plan9.de>. |
363 | |
384 | |