I agree with the above statements. In our case, the interface was the configuration files. So, our input files turned into small Perl scripts. Those that knew Perl could take advantage immediately and those that didn't could use the examples or small documentation we provided on how to write the input files.
It is important to note that this tool was for people who must program as part of their daily job. So maybe the Perl interface is a better match for that reason. dragonchild alluded to this in the post above; for this to be truly effective, the users should be programmers.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
