comment on

I wrote an utility very close to your description; mostly my utility coincides with your description, but I have only Perl scripts to invoke.

Each utility to invoke has common agreements on parameters, and, indeed, parameters could be entered via GUI, or from command line, or both methods (entered in command line and then edited by afterwards in GUIby user), or without GUI - all ways of invocation are possible in my case.

GUI was implemented with Tcl::Tk, which is like perl/Tk but much more capable.

I can provide may be more details on this.

Also, http://search.cpan.org/~srezic/Tk-Getopt-0.49/ could be of interest for you as a starting point of your own way.

Best regards,
Courage, the Cowardly Dog

In reply to Re: Need feedback on a wrapper script design. by Courage
in thread Need feedback on a wrapper script design. by selk

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.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks