1-------- 2Schnauzer: add fields to BRINFO structure. Want to be able to sort on 3name, size, and mtime (atime is useless, given that we access files all 4the time in the schnauzer...) 5 6Have a '-noshrink' option & resource. When enabled, and you view an image 7 that's larger than the max window size, it should *crop* the image 8 to the window, rather than shrink it. This should probably also 9 become the new default behavior, so maybe call it '-shrink' or 10 something... (Concerns: 'Normal' command, 'Uncrop' command...) 11 12Option to change how TrackPicValues displays stuff. Let user enter 13conversion factors (slope + offset) for intensity and x,y values (so folks 14can do x,y -> lat,long or i -> temperature conversions automagically) 15 Craig Motell - motell@avian.nmfs.hawaii.edu 16 17 18 19CODE TO WRITE (maybe) 20--------------------- 21> From: Peder Langlo 22> To do comments without writing a full-blown text-editor... 23> one could push a "Annotate" button for a subwindow 24> prompting for a one line annotation or a file containing the text. 25> 26> BETTER IDEA: 27> write comments (if any) to a temp file, exec an emacs (or whatever 28> 'EDITOR' is set to) on that file, and when it exits, reload contents of 29> the file as comments. Should be easy enough, but I'm not making any more 30> changes until after 3.10 ships... 31 32An Iconify All button. 33 34A 'show hidden' checkbox in load/save windows 35 36Be able to load/save colormap files? 37 38'-alg #' option to execute a specific algorithm on initial image load? 39 40"slideshow" script files that would contain image manip. commands and file 41 names and times to wait (or wait for key/mouse). Need to load up and 42 manip the next image while displaying the current one... 43 (David Koontz (dak@mosaic.uncc.edu)) 44 45The only thing missing in your package is a raw file reader. Since I get my 46data from NASA/JPL, they use their strange VICAR stuff and so I can not 47open their files using xv. Can you provide an OPEN AS... option, where I 48can define the parameters of the image (such as No of rows, No. of cols, 49header bytes and No. of channels (interleaved or not)). It would be very 50helpful, because the different file formats at our site are really slowing 51down the working process! 52 53On-line help of some sort! (Maybe an HTML page.) 54 55Make a '-update' option to do an 'Update' (generate icons) in the specified 56 directory, without any user intervention. 57 58If '-perfect' or '-owncmap', we could create a private colormap when in 59 stdcmap mode (and then we can pick a 3/3/2 on 8-bit displays, and 60 have a better chance of getting 2/2/2 on 6-bit displays.) 61 62Add '-1xlimit' option (to keep 'old style' behavior, for folks who liked it), 63 and make '-2xlimits' the default. Also change UnCrop behavior 64 (should uncrop at current expansion: if that would be bigger than 65 the screen, just go back to 'normal' size) 66 67Add a '-convert {gif,tiff,jpeg,pm,etc...}' option that suppresses most of the 68 X stuff. Never needs to fall into HandleEvent(), ferinstance... 69 70Make the 'uncrop' less likely to generate a HUGE image, and then relax the 71window max-size limitations to see what happens... 72 73Instead of alternating diversity and popularity, you could 74multiply the distance by the popularity of a color (expressed, 75for example, as a percentage of the total points). 76 From: rjohnson@shell.com (Roy Johnson) 77 78 79UNLIKELY, BUT GOOD IDEAS TO THINK ABOUT 80--------------------------------------- 81Scroll bars for the image window. Have a toggle to specify whether resizing 82the window rescales the image, or just shows more or less of it. 83 84Continue to handle events ('exposes' and keypresses, at least) during certain 85long computations? (such as smooth, loading jpegs, etc.) 86 87look into a more-diverse 'slow24' algorithm (n****.tif) 88 From: mjm@as.arizona.edu (Mark McCaughrean) 89 90Stick in a '-cecmap' checkbox in the color editor window, somewhere. 91 92be able to select 'ncols' values with a dial (while the program is running). 93 Useful for folks trying to generate reduced color images. 94 95Keyboard accelerators for the RGB dials in the color editor. 96 97 98 99 100RIGHT BEFORE HELL FREEZES OVER 101------------------------------ 102 103> Let you type 'xv <dirname>' it should do the 'right thing' (including 104> recursing down subdirs...) 105> Should probably have a '-only_use_recognized_suffixes' option to speed things 106> up? (ie, so it won't bother stat'ing (or including in the list, at least) 107> things that don't end with '.gif', '.jpg', etc...) 108 109 110> Deal with the virtual WM scene (tvtwm, at least) 111> 112> '-root' modes in tvtwm core dump? 113> 114> '-virtual' option: geomspecs should normally be relative to the physical 115> root window. If '-virtual' is specified, they should be relative to the 116> virtual root window (if any) (ALTERNATELY: modify parsing of the geometry 117> string slightly (look for a leading 'a' or 'r'???) 118> 119> Also, '-vmax' or something to let you generate a root image that's the size 120> of the *virtual* root, not the physical root. 121 122 123Faster compressed/color-on-grayscale-printers postscript output? 124 125> The Hue remapping control is a wonder. Would it be possible to put xv in 126> a mode so that saturation and value changes only apply for colors in the 127> `From' dial? This would surely make xv more powerful in making the sky more 128> blue and lipstick more red. ('global' checkboxes next to the two controls) 129 130Randomize function shouldn't be *so* random. Maybe just randomly swap r,g,b 131 colormap components, flip their signs, etc. ??? 132 133 134'real' colormap undo/redo controls. (Hook into main coloreditor undo/redo 135 controls. Keep 'revert', though) 136 137One question re usage: can I place the "xv" window on one 138"screen" (smaller, color) and the controls on another (large, grey-scale)? 139I looked/read the docs, but couldn't figure out if this was possible. 140 141 142Histograms (possibly toggle switches for all four graph windows?) Possibly 143it's own window... (See message from Jon Brinkmann describing ideas.) 144 145 146> What I want is that if I Shift-rightbutton'ed on a pixel in the image, the 147> pixel got the yanked color. Should be very easy to implement if desired. 148 149 150 151--------- 152 1531) (this is a minor point, but would be a nice touch) 154 in 24bit mode, you can't turn the image to gray by simply clicking 155the "gray" button in the colormap editor -- since there is no 156colormap. However, turning the image to grayscale is still a useful, 157and fairly simple, operation. (I know, you can always save the image 158as grayscale, and the re-load it, but that's kinda a long way to go 159for something as simple as this.) 160 1612) (my big wish) 162we run X on 8-bit greyscale machines (DECstations to be precise). 163Now, 8 bit grey can display all the gray information there is in a 16424bit image. However, color images are still dithered down to gray -- 165especially in 24bit mode, with 6x6x6 color dithering, this makes the 166image look far worse than it could. I propose, therefore, an 167additional 24bit->8bit algorithm : Display as Gray (or something like 168that), which should be the default on greyscale servers, or if the 169-mono flag is used. This would not dither the image, but simply 170convert it to grey. this would be pretty fast (right?) and would make 17124bit images look _much_ better on 8bit greyscale devices (but we 172wouldn't be sacrificing speed). Preferrably, this should be selectable 173just like the other 24bit algorithms. 174 175 176 177----------- 178From: Phil.Richards@prg.oxford.ac.uk 179 180 (iii) possibly make the Image window keeping backing store an option 181 (command-line/resources); I'm sure you've already thought of that 182 183 184 185---------- 186From: "Anthony A. Datri" <aad@lovecraft.siemens.com> 187 188It seems that when I save (eg., after cropping) or delete a file, XV 189stats and opens *every* file in the current directory, even if -nostat 190is specified. 191 192