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

Comparing CV/bin/cv (file contents):
Revision 1.10 by root, Tue Nov 4 02:48:09 2003 UTC vs.
Revision 1.58 by root, Wed Sep 7 20:17:25 2005 UTC

1#!/opt/bin/perl 1#!/opt/bin/perl
2
3use Cwd ();
4use Encode ();
2 5
3use Gtk2 -init; 6use Gtk2 -init;
4use Gtk2::Gdk::Keysyms; 7use Gtk2::Gdk::Keysyms;
5 8
9use Gtk2::CV;
10
6use Gtk2::CV::ImageWindow; 11use Gtk2::CV::ImageWindow;
7use Gtk2::CV::Schnauzer; 12use Gtk2::CV::Schnauzer;
8 13
14BEGIN {
15 require Gtk2::CV::Plugin;
16 require "$ENV{HOME}/.cvrc" if -r "$ENV{HOME}/.cvrc";
17}
18
19use Gtk2::CV::Plugin::NameCluster;
20use Gtk2::CV::Plugin::RCluster;
21
22Gtk2::Rc->parse (Gtk2::CV::find_rcfile "gtkrc");
23
24use File::Spec;
25
26my $mainwin;
9my $viewer; 27my $viewer;
10my $schnauzer; 28my $schnauzer;
29my $info;
30my $help;
31
32my $schnauzer_idx = 0;
11 33
12sub new_schnauzer { 34sub new_schnauzer {
13 my $w = new Gtk2::Window;
14 $w->add (my $s = new Gtk2::CV::Schnauzer); 35 my $s = new Gtk2::CV::Schnauzer;
15 36
16 $s->signal_connect (activate => sub { $viewer->load_image ($_[1]) });
17 $s->signal_connect_after (key_press_event => \&std_keys); 37 $s->signal_connect_after (key_press_event => \&std_keys);
38 $s->signal_connect (activate => sub {
39 my $label = sprintf "%s (%d)",
40 (File::Spec->splitpath ($_[1]))[2],
41 -s $_[1];
42 $info->set_label ($label);
43 $viewer->load_image ($_[1]);
44 });
18 45
19 $s->set_dir ("."); 46 Gtk2::CV::Plugin->call (new_schnauzer => $s);
20 $w->show_all;
21 47
22 $s; 48 $s
23} 49}
24 50
25sub std_keys { 51sub std_keys {
26 my $key = $_[1]->keyval; 52 my $key = $_[1]->keyval;
27 my $state = $_[1]->state; 53 my $state = $_[1]->state;
28 54
29 my $ctrl = grep $_ eq "control-mask", @$state; 55 my $ctrl = $state * "control-mask";
30 56
31 if ($key == $Gtk2::Gdk::Keysyms{q}) { 57 if ($key == $Gtk2::Gdk::Keysyms{q}) {
32 main_quit Gtk2; 58 main_quit Gtk2;
33 } elsif ($ctrl && $key == $Gtk2::Gdk::Keysyms{v}) { 59 } elsif ($ctrl && $key == $Gtk2::Gdk::Keysyms{v}) {
34 new_schnauzer; 60 my $w = new Gtk2::Window;
61
62 $w->set_title ("CV: Schnauzer");
63 $w->add (my $s = new_schnauzer);
64 $s->set_dir (File::Spec->curdir);
65 $s->set_geometry_hints;
66 $w->show_all;
67
68 } elsif ($ctrl && $key == $Gtk2::Gdk::Keysyms{h}) {
69 unless ($help) {
70 require Gtk2::PodViewer;
71
72 $help = new Gtk2::Window;
73 $help->set_title ("CV: Help");
74 $help->set_default_size (500, 300);
75 $help->signal_connect (delete_event => sub { $help->hide; 1 });
76
77 $help->add (my $sw = new Gtk2::ScrolledWindow);
78 $sw->add (my $h = new Gtk2::PodViewer);
79
80 #binmode DATA, ":utf8";
81 $h->load_string (do { local $/; <DATA> });
82 }
83
84 $help->show_all;
35 } else { 85 } else {
36 $schnauzer->handle_key ($key, $state); 86 return 0;
37 } 87 }
38 88
39 1; 89 1
40} 90}
41 91
92{
42$viewer = new Gtk2::CV::ImageWindow; 93 $viewer = new Gtk2::CV::ImageWindow;
94
95 $viewer->set_title ("CV: Image");
96
43$viewer->signal_connect (key_press_event => \&std_keys); 97 $viewer->signal_connect (key_press_event => sub {
98 &std_keys
99 or $schnauzer->signal_emit (key_press_event => $_[1])
100 });
44$viewer->signal_connect (delete_event => sub { main_quit Gtk2 }); 101 $viewer->signal_connect (delete_event => sub { main_quit Gtk2 });
45 102
103 $viewer->signal_connect (button3_press_event => sub {
104 $mainwin->visible
105 ? $mainwin->hide
106 : $mainwin->show_all;
107 1
108 });
109
110 Gtk2::CV::Plugin->call (new_imagewindow => $viewer);
111
46$schnauzer = new_schnauzer; 112 $schnauzer = new_schnauzer;
113
114 $mainwin = new Gtk2::Window;
115 $mainwin->set_title ("CV");
116 $mainwin->add (my $vbox = new Gtk2::VBox);
117 $mainwin->signal_connect (delete_event => sub { $mainwin->hide; 1 });
118
119 $vbox->add ($schnauzer);
120 $vbox->pack_end (my $frame = new Gtk2::Frame, 0, 0, 0);
121 $frame->add (my $hbox = new Gtk2::HBox 0, 0);
122 $hbox->pack_start ((new Gtk2::Label "Info: "), 0, 0, 0);
123 $hbox->pack_end (my $labelwindow = new Gtk2::EventBox, 1, 1, 0);
124 $labelwindow->add ($info = new Gtk2::Label);
125 $labelwindow->signal_connect_after (size_request => sub { $_[1]->width (0); 0 });
126 $info->set (selectable => 1, xalign => 0, justify => "left");
127
128 $schnauzer->set_geometry_hints;
129}
47 130
48if (@ARGV) { 131if (@ARGV) {
49 $viewer->load_image ($ARGV[0]); 132 @ARGV == 1 && -d $ARGV[0]
50 133 ? $schnauzer->set_dir (Glib::filename_to_unicode shift)
51 if (@ARGV > 1) { 134 : $schnauzer->set_paths ([map Glib::filename_to_unicode $_, @ARGV]);
52 $schnauzer->set_paths (\@ARGV); 135 $schnauzer->show_all;
53 } 136 $schnauzer->handle_key ($Gtk2::Gdk::Keysyms{space}, []);
137} else {
138 $schnauzer->set_dir (File::Spec->curdir);
139 $mainwin->show_all;
54} 140}
55 141
56$viewer->show_all; 142$viewer->show_all;
57 143
58main Gtk2; 144main Gtk2;
59 145
146__DATA__
60 147
148=encoding utf-8
149
150=head1 NAME
151
152cv - a fast gtk+ image viewer loosely modeled after XV
153
154=head1 SYNOPSIS
155
156 cv [file...]
157
158=head1 FEATURES
159
160CV is supposed to work similar to the venerable XV image viewer, just
161faster. Why faster?
162
163=over 4
164
165=item * optimized directory scanning algorithm
166
167The directory scanning in CV uses some tricks that - on most modern
168filesystems - makes it possible to detect filetypes faster than stat()'ing
169every file. This makes CV suitable for directories with lots of files
170(10000+).
171
172This algorithm is quite unprecise - it doesn't make a difference between
173files, device nodes, symlinks and the like, and filetype detection is done
174using the file extension only.
175
176On the positive side, it is usually many orders of magnitude faster than
177traditional scanning techniques (good for directories with 10000 or
178100000+ files).
179
180=item * queuing for all time-consuming background tasks
181
182All tasks, such as unlinking files or generating thumbnails, that can be
183done in the background will be done so - no waiting required, even when
184changing directories.
185
186=item * use of asynchronous I/O
187
188CV tries to use asynchronous I/O whereever it makes sense, for example
189while scanning directories, waiting for stat data, unlinking files or
190generating thumbnails. This usually decreases scanning times for large
191directories a bit (especially on RAID devices and over NFS) and makes CV
192much more interactive.
193
194=item * fast image loading
195
196The time span between the user issuing a command and displaying the new
197image should be as small as possible. CV uses optimized (especially
198for JPEG) loading functions and sacrifices some quality (e.g no gamma
199correction, although this might change) to achieve this speed.
200
201=item * fast thumbnail creation
202
203Thumbnail creation uses both CPU and Disk-I/O. CV interleaves both, so
204on modern CPUs, thumbnailing is usually limited by I/O speed. Thumbnail
205creation for JPEGs has been specially optimized and can even take
206advantage of multiple CPUs.
207
208=item * minimum optical clutter
209
210CV has no menus or other user interface elements that take up a lot of
211screen space (or are useful for beginning users). The schnauzer windows
212can also be somewhat crowded.
213
214The point of an image viewer is viewing images, not a nice GUI. This is
215similar to XV's behaviour.
216
217=item * efficient (and hard to learn) user interface
218
219CV uses key combinations. A lot. If you are an experienced XV user, you
220will find most of these keys familiar. If not, CV might be hard to use at
221first, but will be an efficient tool later.
222
223=item * multi-window GUI
224
225CV doesn't force you to use a specific layout, instead it relies on your
226window manager, thus enabling you to chose whatever layout that suits you
227most.
228
229=item * i18n'ed filename handling throughout
230
231As long as glib can recognize your filename encoding (either UTF-8 or
232locale-specific, depending on the setting of G_BROKEN_FILENAMES) and you
233have the relevant fonts, CV will display your filenames correctly.
234
235=item * extensible through plug-ins
236
237I have weird plug-ins that access remote databases to find a
238directory. This is not likely to be of any use to other people. Likewise,
239others might have weird requirements I cannot dream of.
240
241=item * filename clustering
242
243Among the standard plug-ins is a filename clustering plug-in, that (in
244case of tens of thousands images in one directory) might be able to
245cluster similar names together.
246
247=back
248
249=head1 DESCRIPTION
250
251=head2 THE IMAGE WINDOW
252
253You can use the following keys in the image window:
254
255 q quit the program
256 < half the image size
257 > double the image size
258 , shrink the image by 10%
259 . enlarge the image by 10%
260 n reset to normal size
261 m maximize to screensize
262 M maximize to screensize, respecting image aspect
263 ctrl-m toggle maxpect-always mode
264 u uncrop
265 r set scaling mode to 'nearest' (fastest)
266 s set scaling mode to 'bilinear' (default)
267 shift-s set scaling mode to 'hyper' (slowest)
268 t rotate clockwise 90°
269 T rotate counterclockwise°
270 ctrl-v open a new visual schnauzer window for the current dir
271 ctrl-e run an editor ($CV_EDITOR or "gimp") on the current image
272 ctrl-p fire up the print dialog
273 escape cancel a crop action
274
275And when playing movies, these additional keys are active:
276
277 left rewind by 10 seconds
278 right forward by 10 seconds
279 down rewind by 60 seconds
280 up forward by 60 seconds
281 pg_up rewind by 600 seconds
282 pg_down forward by 600 seconds
283 o toggle on-screen display
284 p pause/unpause
285 escape stop playing
286 9 turn volume down
287 0 turn volume up
288
289Any other keys will be sent to the default schnauzer window, which can be
290toggled on and off by right-clicking into the image window.
291
292Left-clicking into the image window will let you crop the image (usually
293to zoom into large images that CV scales down).
294
295=head2 THE VISUAL SCHNAUZER
296
297You can use the following keys in the schnauzer window:
298
299 ctrl-space,
300 space move to and display next image
301 ctrl-backspace,
302 backspace move to and display previous image
303 ctrl-return,
304 return display selected picture, or enter directory
305
306 cursor keys move selection
307 page-up move one page up
308 page-down move one page down
309 home move to first file
310 end move to last file
311
312 ctrl-a select all files
313 ctrl-shift-a select all files currently displayed in the schnauzer window
314 ctrl-d delete selected files WITHOUT ASKING AGAIN
315 ctrl-g force generation of thumbnais for the selected files
316 ctrl-s rescan current direcory or files updates/deletes etc.
317 ctrl-u update selected (or all) icons if neccessary
318 ctrl-l don't use, will become a plug-in eventually
319
320 ^ go to parent directory (caret).
321
322 0-9,
323 a-z find the first filename beginning with this letter
324
325Right-clicking into the schnauzer window displays a pop-up menu with
326additional actions.
327
328=head1 FILES
329
330When starting, CV runs the F<.cvrc> file in your F<$HOME> directory as if
331it were a perl script. in that, you will mostly load plug-ins.
332
333Example:
334
335 system "fping -q -t 10 ether"
336 or require "/fs/cv/cvplugin.pl";
337
338This will load a plug-in, but only if the machine I<ether> is reachable
339(supposedly the plug-in is networked in some way :).
340
341=head1 ENVIRONMENT
342
343=over 4
344
345=item CV_EDITOR
346
347The program that gets executed when the user presses C<CTRL-e> in the
348Schnauzer or image window. The default is C<gimp>.
349
350=item CV_PRINT_DESTINATION
351
352The default (perl-style) destination to use in the print dialog.
353
354=item CV_TRASHCAN
355
356When set, must point to a directory where all files that are deleted are
357moved to. If unset, files that are deleted are really being deleted.
358
359=back
360
361=head1 SECURITY CONSIDERATIONS
362
363CV uses Pixbuf to load non-JPEG images. Pixbuf is not considered safe for
364this purpose, though (from the gtk-2.2 release notes):
365
366"While efforts have been made to make gdk-pixbuf robust against invalid
367images, using gdk-pixbuf to load untrusted data is not recommended, due to
368the likelyhood that there are additional problems where an invalid image
369could cause gdk-pixbuf to crash or worse."
370
371=head1 BUGS/TODO
372
373 Lots of functionality is missing.
374
375 Pixbuf doesn't always honor G_BROKEN_FILENAMES, so accessing files with
376 names incompatible with utf-8 might fail.
377
378 rotate on disk
379 lots of ui issues
380 save(?)
381 preferences
382
383=head1 AUTHOR
384
385Marc Lehmann <cv@plan9.de>.
386
387=cut
388

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines