|
0
|
1 <!DOCTYPE html>
|
|
|
2 <html>
|
|
|
3 <head>
|
|
|
4 <meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
|
|
5 <title>ImagePrep Read Me</title>
|
|
|
6 <style>
|
|
|
7 html { font-family: "TeX Gyre Schola", serif; }
|
|
|
8 h1, h2, h3, h4, h5, h6 { font-family: "Avenir Next", sans-serif; }
|
|
|
9 pre, code, kbd, samp { font-family: "Menlo", monospace; font-size: 85%; }
|
|
|
10 </style>
|
|
|
11 </head>
|
|
|
12 <body>
|
|
|
13 <h1>ImagePrep Read Me</h1>
|
|
|
14 <p>This is a simple program mainly created for my own benefit.</p>
|
|
|
15 <p>Because it is primarily for my own benefit, it does not build to a
|
|
|
16 “clickable” app. That is too much of a pain to implement.</p>
|
|
|
17 <p>Because I have code to crib, it does contain a help file. It’s pretty
|
|
|
18 rudimentary, however.</p>
|
|
|
19 <p>Because I have code to crib, it does run on a <code>.preferences</code>
|
|
|
20 file, but because coding preferences dialogs is something of a pain, it
|
|
|
21 does not contain a preferences or settings dialog, even though there is
|
|
|
22 some code to crib for both. The <code>.preferences</code> file must be
|
|
|
23 edited by hand* (it will live in the normal place for such files on the
|
|
|
24 system being run under). If no such file exists, a default one will be
|
|
|
25 created. The only things in it will be the maximum dimension to clamp to,
|
|
|
26 where the output file goes by default, and maybe what the output file’s
|
|
|
27 name is by default (i.e. a name suffix).</p>
|
|
|
28 <p>* This program is <em>for my own benefit</em>, and <em>I</em> have no
|
|
|
29 problem editing text files, therefore this is reasonable.</p>
|
|
|
30 <p>Contrary to JpegWasher, which is designed for batch processing, this will
|
|
|
31 have more of a “document editor” style of design. Meaning, you open a
|
|
|
32 file, you edit it, you save it, you close it.</p>
|
|
|
33 <p>Upon opening a file, it will be auto-scaled to the specified maximum
|
|
|
34 dimension. This will default to the value in the preferences file, but the
|
|
|
35 user will be able to change it at open time.</p>
|
|
|
36 <p>At that point, the editing step begins. It is extremely simple and is
|
|
|
37 limited to rotation. Three types of rotation will be offered, 90°
|
|
|
38 clockwise, 180°, and 90° counterclockwise.</p>
|
|
|
39 <p>The user can rotate the file as many times as s/he wants. Sort of silly,
|
|
|
40 but sometimes people are tired and get clockwise and counterclockwise
|
|
|
41 confused, so might as well give ’em a chance to fix their mistakes. Plus,
|
|
|
42 it would take special effort <em>not</em> to allow this.</p>
|
|
|
43 <p>Then comes the closing and saving. It <em>might</em> make the most sense
|
|
|
44 to wrap these two up into one operation, given that there are two
|
|
|
45 operations in one when one opens the thing, too*. (Sort of a compromise
|
|
|
46 between a classic “document editor” design and a batch-processing design.)
|
|
|
47 This will default to the name and directory consistent with the
|
|
|
48 preferences settings, but it will be based around a file dialog so that
|
|
|
49 the user can save the resized image anyplace, with any name.</p>
|
|
|
50 <p>* Leaning towards making “close & save” one operation; again, this
|
|
|
51 program is primarily for <em>my</em> benefit.</p>
|
|
|
52 <p>Ideally, I wouldn’t even puts around with making this a GUI app in the
|
|
|
53 first place. It’s for my own use, so the command line would be good
|
|
|
54 enough. The problem is rotation: it’s a hot mess. There’s really no way to
|
|
|
55 do it right save to show the image to a human and let him (me) decide
|
|
|
56 which way is up.</p>
|
|
|
57 </body>
|
|
|
58 </html>
|
