Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

GUI Design/Organization - Recommended Practices?

by atcroft (Abbot)
on Sep 23, 2016 at 19:26 UTC ( #1172494=perlquestion: print w/replies, xml ) Need Help??

atcroft has asked for the wisdom of the Perl Monks concerning the following question:

Are there currently any recommended common or "best" practices when creating a GUI for a script? (In terms of organization, etc.?)

  • Comment on GUI Design/Organization - Recommended Practices?

Replies are listed 'Best First'.
Re: GUI Design/Organization - Recommended Practices?
by BrowserUk (Pope) on Sep 23, 2016 at 19:37 UTC

    I've done this a few times and have my preferred practice, which comes with no "best practice" recommendation, but its something for you to consider.

    The basic thing is that I construct the main script as a standard, command line, switch driven script. I then construct another script using the appropriate gui framework -- I've used Tk and Win32::GUI -- and use it to present the options to the user for selection and have a button that simply runs the script in the background with the arguments the user has selected.

    Then I generally use a piped-open to run the command; as that gives me the pid for use with kill should the user decide to abort, and gives me access to the output from the CLI script, which I can the present back to the user either when the script has ended, or dynamically as the run progresses.

    This separation of concerns is a win-win in my book as it allows both scripts to be developed, tested and used independently, and also provides uncomplicated multi-tasking that ensures the GUI remains responsive without affecting the performance, or complicating the construction, of the CLI script that does the work.


    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". I knew I was on the right track :)
    In the absence of evidence, opinion is indistinguishable from prejudice.
        SoC seems to be a common best practice recommendation ... or is "design principle" somehow different from that?

        I simply meant that I didn't read it somewhere, nor can I cite some well documented philosophy; it is just the way I've evolved to do things.

        The problem I have with most of the guidelines, rules and philosophies, typified by those in your links, is that they become ends unto themselves -- Is your application XYZ complient! -- rather than being used to guide, they become hard and fast rules that must be followed. Even when that it to the detriment of the application requirements. And that's a crock.


        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". I knew I was on the right track :)
        In the absence of evidence, opinion is indistinguishable from prejudice.
Re: GUI Design/Organization - Recommended Practices?
by eyepopslikeamosquito (Chancellor) on Sep 24, 2016 at 05:18 UTC

    It probably contains more than what you asked for, but you might find some useful tips in this node:

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: perlquestion [id://1172494]
Approved by BrowserUk
Front-paged by planetscape
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (4)
As of 2019-09-20 01:02 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    The room is dark, and your next move is ...












    Results (253 votes). Check out past polls.

    Notices?