comment on

Maybe it's a matter of terminology, but I bet you aren't scripting the GUI. You are driving the GUI from "command-line" programs that can display graphics widgets.

But let me come along and now try to "script" your application. I can't. I haven't found any decent "scripting language" for your typical "GUI" that let's me say "click THIS button when THAT button turns green". If you have, please help us out here.

Sure, I use multiple windows, with CLIs in each window. I don't call that a GUI. I call the gimp or Photoshop (depending on your bent) a GUI. Try scripting that in a meaningful way. It won't be from the GUI end. Gimp scripting is done because they have a (surprise!) CLI interface specially grafted on to the back end. And Photoshop has its little macro language, and I can tweak at that with some Applescript if I'm desparate. But it's just not the same as taking the output of "ps" and looking for the "httpd" processes.

Imagine if you didn't have "ps", but only the "top" program. (Welcome to MacOS or Windows98 {grin}). This is what I'm talking about. You cannot script a GUI!

-- Randal L. Schwartz, Perl hacker

In reply to RE: RE: GUIs and CLIs by merlyn
in thread The sad state of Perl documentation by SuperCruncher

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks