in reply to Re^2: Perl/Tk code structure
in thread Perl/Tk code structure

BTW. Remember that with the gui I posted, you could (for example) check for what was printed and instead of simply displaying it in the listbox, decide to convert a text prompt into a bunch of buttons or a dialog that allows the user to answer the prompt without having to type complex material, and then send the information back to the <STDIN> requests as if he had typed it out in full.

The gui I posted is just the simplest working example I could come up with.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Replies are listed 'Best First'.
Re^4: Perl/Tk code structure
by elef (Friar) on Jan 11, 2012 at 09:24 UTC
    Thanks.
    However, I'm afraid that your definition of "complex" differs quite a bit from mine. Most of the code of the module went right over my head. Even if I ignore everything outside of sub gui {...} on the assumption that I don't need to know anything about how the STDIN/STDOUT redirection chicanery works, most of the code inside the sub is also Greek to me. I get the three Tk widgets and have a vague idea about what the rest does, but no clue how.
    I'm afraid that the recipe for setting up a radiobutton widget based on what the original script prints to STDOUT and passing the selection to its STDIN would begin with "spend a week reading a couple of hundred pages of impossible to find, indecipherable documentation and writing/debugging test scripts" and may end with "give up".
[reply]
[d/l]

      Hm. Is that a request for further explanation or a dismissal of the idea as too much complex "chicanary"?

      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.

      The start of some sanity?
[reply]
        That's a good question, I'm not sure. It'd be nice if I could implement this idea as it seems to be the best solution to the problem. But from your sample it seems that I would need you to hold my hand most of the way through it - or I'd need to read and absorb most of "Advanced Perl Programming", which I find an even less enticing option than contorting my original script around Tk's logic. I assume you probably don't want to do it, and anyway, I don't like to ask people to do my projects for me and/or write detailed 10-page howtos for solving my specific problem...
        If you think you can enlighten my about how to do this in a couple of comments added to the above code and add the code for generating a widget based on specific strings printed to the original script's STDOUT, that'd be great. I was just reluctant to ask you to do it because it's too much like spoonfeeding.
        The danger is that if something breaks or needs changing in the interface between the original script and the GUI module, I won't be able to fix it, but I guess that's not very likely.
[reply]

In Section Seekers of Perl Wisdom