Often, it is more productive to use what one already knows.

FWIW, the people - including software developers - for this particular client of mine are especially adverse to the command line. With other clients, it has been enough to make sure to wait for input (on STDIN) when the (other command line oriented) program is started without parameters or options (as happens when a user double-clicks on the file). And, of course, state in the shown help text that the program needs to run from the command line. Since the programs I'm trying "friendly up" just read 1 or 2 files and write another, the only GUI needed is file open/save dialogs.

In reply to Re^2: Just getopenfile/getsavefile for MS Windows? by RonW
in thread Just getopenfile/getsavefile for MS Windows? by RonW

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.