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

Comparing CV/bin/cv (file contents):
Revision 1.51 by root, Sun Aug 14 02:25:44 2005 UTC vs.
Revision 1.55 by root, Mon Aug 22 00:30:58 2005 UTC

… …
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
51sub std_keys { 51sub 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);
… …
127 127
128 $schnauzer->set_geometry_hints; 128 $schnauzer->set_geometry_hints;
129} 129}
130 130
131if (@ARGV) { 131if (@ARGV) {
132 @ARGV == 1 && -d $ARGV[0]
133 ? $schnauzer->set_dir (Glib::filename_to_unicode shift)
132 $schnauzer->set_paths ([map Glib::filename_to_unicode $_, @ARGV]); 134 : $schnauzer->set_paths ([map Glib::filename_to_unicode $_, @ARGV]);
133 $schnauzer->show_all; 135 $schnauzer->show_all;
134 $schnauzer->handle_key ($Gtk2::Gdk::Keysyms{space}, []); 136 $schnauzer->handle_key ($Gtk2::Gdk::Keysyms{space}, []);
135} else { 137} else {
136 $schnauzer->set_dir (File::Spec->curdir); 138 $schnauzer->set_dir (File::Spec->curdir);
137 $mainwin->show_all; 139 $mainwin->show_all;
… …
158 160
159=over 4 161=over 4
160 162
161=item * optimized directory scanning algorithm 163=item * optimized directory scanning algorithm
162 164
163The directory scanning in CV plays some tricks that - on most modern 165The directory scanning in CV uses some tricks that - on most modern
164filesystems - makes it possible to detect filetypes faster than stat()'ing 166filesystems - makes it possible to detect filetypes faster than stat()'ing
165every file. This makes CV suitable for directories with lots of files 167every file. This makes CV suitable for directories with lots of files
166(10000+). 168(10000+).
167 169
168This algorithm is quite unprecise - it doesn't make a difference between 170This algorithm is quite unprecise - it doesn't make a difference between
169files, device nodes, symlinks and the like, and filetype detection is done 171files, device nodes, symlinks and the like, and filetype detection is done
170using the file extension only. 172using the file extension only.
171 173
174On the positive side, it is usually many orders of magnitude faster than
175traditional scanning techniques (good for directories with 10000 or
176100000+ files).
177
178=item * queuing for all time-consuming background tasks
179
180All tasks, such as unlinking files or generating thumbnails, that can be
181done in the background will be done so - no waiting required, even when
182changing directories.
183
172=item * use of asynchronous I/O 184=item * use of asynchronous I/O
173 185
174CV tries to use asynchronous I/O whereever it makes sense, for example 186CV tries to use asynchronous I/O whereever it makes sense, for example
175while scanning directories, waiting for stat data or unlinking files. This 187while scanning directories, waiting for stat data, unlinking files or
176usually decreases scanning times for large directories a bit (especially 188generating thumbnails. This usually decreases scanning times for large
177on RAID devices and over NFS). 189directories a bit (especially on RAID devices and over NFS) and makes CV
190much more interactive.
178 191
179=item * fast image loading 192=item * fast image loading
180 193
181The time span between the user issuing a command and displaying the new 194The time span between the user issuing a command and displaying the new
182image should be as small as possible. CV uses optimized (especially 195image should be as small as possible. CV uses optimized (especially
183for JPEG) loading functions and sacrifices some quality (e.g no gamma 196for JPEG) loading functions and sacrifices some quality (e.g no gamma
184correction) to achieve this speed. 197correction, although this might change) to achieve this speed.
185 198
186=item * fast thumbnail creation 199=item * fast thumbnail creation
187 200
188Thumbnail creation is crucial for me, so it's better be fast. Thumbnail 201Thumbnail creation uses both CPU and Disk-I/O. CV interleaves both, so
202on modern CPUs, thumbnailing is usually limited by I/O speed. Thumbnail
189creation for JPEGs has been specially optimized. 203creation for JPEGs has been specially optimized and can even take
204advantage of multiple CPUs.
190 205
191=item * minimum optical clutter 206=item * minimum optical clutter
192 207
193CV has no menus or other user interface elements that take up a lot of 208CV has no menus or other user interface elements that take up a lot of
194screen space. The schnauzer windows can also be somewhat crowded. 209screen space (or are useful for beginning users). The schnauzer windows
210can also be somewhat crowded.
195 211
196The point of an image viewer is viewing images, not a nice GUI. This is 212The point of an image viewer is viewing images, not a nice GUI. This is
197similar to XV's behaviour. 213similar to XV's behaviour.
198 214
199=item * efficient (and hard to learn) user interface 215=item * efficient (and hard to learn) user interface
200 216
201CV uses key combinations. A lot. If you are an experienced XV user, you 217CV uses key combinations. A lot. If you are an experienced XV user, you
202will find most of these keys familiar. If not, CV might be hard to use at 218will find most of these keys familiar. If not, CV might be hard to use at
203first, but will be an efficient tool later. 219first, but will be an efficient tool later.
204 220
221=item * multi-window GUI
222
223CV doesn't force you to use a specific layout, instead it relies on your
224window manager, thus enabling you to chose whatever layout that suits you
225most.
226
205=item * i18n'ed filename handling throughout 227=item * i18n'ed filename handling throughout
206 228
207As long as glib can recognize your filename encoding (either UTF-8 or 229As long as glib can recognize your filename encoding (either UTF-8 or
208locale-specific, depending on your settings) and you have the relevant 230locale-specific, depending on the setting of G_BROKEN_FILENAMES) and you
209fonts, CV will display your filenames correctly. 231have the relevant fonts, CV will display your filenames correctly.
210 232
211=item * extensible through plug-ins 233=item * extensible through plug-ins
212 234
213I have weird plug-ins that access remote databases to find a 235I have weird plug-ins that access remote databases to find a
214directory. This is not likely to be of any use to other people. Likewise, 236directory. This is not likely to be of any use to other people. Likewise,
… …
332 354
333=back 355=back
334 356
335=head1 SECURITY CONSIDERATIONS 357=head1 SECURITY CONSIDERATIONS
336 358
337CV uses Pixbuf to load images. Pixbuf is not considered safe for this 359CV uses Pixbuf to load non-JPEG images. Pixbuf is not considered safe for
338purpose, though (from the gtk-2.2 release notes): 360this purpose, though (from the gtk-2.2 release notes):
339 361
340"While efforts have been made to make gdk-pixbuf robust against invalid 362"While efforts have been made to make gdk-pixbuf robust against invalid
341images, using gdk-pixbuf to load untrusted data is not recommended, due to 363images, using gdk-pixbuf to load untrusted data is not recommended, due to
342the likelyhood that there are additional problems where an invalid image 364the likelyhood that there are additional problems where an invalid image
343could cause gdk-pixbuf to crash or worse." 365could cause gdk-pixbuf to crash or worse."
… …
345=head1 BUGS/TODO 367=head1 BUGS/TODO
346 368
347 Lots of functionality is missing. 369 Lots of functionality is missing.
348 370
349 Pixbuf doesn't always honor G_BROKEN_FILENAMES, so accessing files with 371 Pixbuf doesn't always honor G_BROKEN_FILENAMES, so accessing files with
350 names incompatible might utf-8 fail. 372 names incompatible with utf-8 might fail.
351 373
352 rotate on disk 374 rotate on disk
353 lots of ui issues 375 lots of ui issues
354 save(?) 376 save(?)
355 preferences 377 preferences
356 shift-cursor in schnauzer
357 378
358=head1 AUTHOR 379=head1 AUTHOR
359 380
360Marc Lehmann <cv@plan9.de>. 381Marc Lehmann <cv@plan9.de>.
361 382

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines