--- a/Readme.html	Fri Jul 17 23:13:13 2020 -0700
+++ b/Readme.html	Fri Jul 17 23:25:33 2020 -0700
@@ -16,15 +16,15 @@
       “clickable” app. That is too much of a pain to implement.</p>
     <p>Because I have code to crib, it does contain a help file. It’s pretty
       rudimentary, however.</p>
-    <p>Because I have code to crib, it does run on a <code>.preferences</code>
+    <p>Because I have code to crib, it does run on a <code>.properties</code>
       file, but because coding preferences dialogs is something of a pain, it
       does not contain a preferences or settings dialog, even though there is
-      some code to crib for both. The <code>.preferences</code> file must be
-      edited by hand* (it will live in the normal place for such files on the
-      system being run under). If no such file exists, a default one will be
-      created. The only things in it will be the maximum dimension to clamp to,
-      where the output file goes by default, and maybe what the output file’s
-      name is by default (i.e. a name suffix).</p>
+      some code to crib for both. The <code>.</code><code>properties</code>
+      file must be edited by hand* (it will live in the normal place for such
+      files on the system being run under). If no such file exists, a default
+      one will be created. The only things in it will be the maximum dimension
+      to clamp to, where the output file goes by default, and maybe what the
+      output file’s name is by default (i.e. a name suffix).</p>
     <p>* This program is <em>for my own benefit</em>, and <em>I</em> have no
       problem editing text files, therefore this is reasonable.</p>
     <p>Contrary to JpegWasher, which is designed for batch processing, this will
@@ -32,7 +32,21 @@
       file, you edit it, you save it, you close it.</p>
     <p>Upon opening a file, it will be auto-scaled to the specified maximum
       dimension. This will default to the value in the preferences file, but the
-      user will be able to change it at open time.</p>
+      user will be able to override it with a command-line argument.</p>
+    <p>Ah, the command-line. Because it’s not a full “clickable” app, it is
+      launched from the command line, and accepts arguments, much like the old
+      days of using X Windows. This is actually <em>more</em> user-friendly for
+      my purposes, because it ends up honoring the concept of the current
+      working directory. (Directory management is one area where GUI programs
+      fall short.)</p>
+    <p>The current working directory is the input files directory. Depending on
+      how the properties are configured, the output directory is either the
+      current working directory, or a specified output file directory. Both
+      directories act like a current working directory; the next time an input
+      or output dialog is brought up in a given session, it will be in the same
+      spot the previous dialog was when it was closed. All this makes it easy to
+      rapidly edit files in a directory of images downloaded from a camera,
+      without polluting that directory with the edited files.</p>
     <p>At that point, the editing step begins. It is extremely simple and is
       limited to rotation. Three types of rotation will be offered, 90°
       clockwise, 180°, and 90° counterclockwise.</p>
@@ -40,15 +54,8 @@
       but sometimes people are tired and get clockwise and counterclockwise
       confused, so might as well give ’em a chance to fix their mistakes. Plus,
       it would take special effort <em>not</em> to allow this.</p>
-    <p>Then comes the closing and saving. It <em>might</em> make the most sense
-      to wrap these two up into one operation, given that there are two
-      operations in one when one opens the thing, too*. (Sort of a compromise
-      between a classic “document editor” design and a batch-processing design.)
-      This will default to the name and directory consistent with the
-      preferences settings, but it will be based around a file dialog so that
-      the user can save the resized image anyplace, with any name.</p>
-    <p>* Leaning towards making “close &amp; save” one operation; again, this
-      program is primarily for <em>my</em> benefit.</p>
+    <p>Then comes the closing and saving. They are one operation, because that
+      makes the program easier <em>for me</em> to use.</p>
     <p>Ideally, I wouldn’t even puts around with making this a GUI app in the
       first place. It’s for my own use, so the command line would be good
       enough. The problem is rotation: it’s a hot mess. There’s really no way to