ncurses Dialogs for your Linux Shell Script tutorial

filmsbykris.com
/ metalx1000
Playlist:
• The Linux Shell - 2016...
This video was sponsored by:
Karl Arvid
John Tedesco - stainlesssteeltoolwrap.com/
Steven C. Morreale
For help: filmsbykris.com/irc
FaceBook: / 225113590836253

[@sarnobat2000]

11:05 This is the part I as a beginner needed. I can't believe how difficult it was to find a minimal working example. Wait, I better try it before I speak too soon.

[@tonpo27]

Every time I try to find something tough/obscure, I stumble on you. Thank you for being a pioneer!

[@BUYXR]

yeah no kidding! Doom, programming, he does everything

[@TraceguyRune]

This are so annoying but so worth it. I spend hours trying to tweak it exactly as I need it.

[@TransexistenceMusic]

Absolute lifesaver for me! Thank you very much!!!! I was looking everywhere trying to figure out how to use dialog in this exact manner and was having zero luck! TYVM!

[@DigitalMetal]

Glad it helped!

[@LundMr1]

This is so cool :) Thank you for making this short video. This helped me a lot when I needed a file selector in bash!

[@WeedMIC]

ty ever sm - i was going to use urwid, but this seems so much easier (the way you presented it).

[@markharrington5826]

Excellent learn t something new again today beats having to create a message box with C++ or with java for ease and use thank you Kris Its an exit code same as all msgboxes which return and integer 0,1,2 depending on what type of msgbox you use

[@AmichaiRotman]

Great job. Very simple to understand!

[@GeekMustHave]

Nice video. I've used dialog "back in the day". I needed a refresher to help kick-start the memory. I'm going to try and used Dialog with CYGWin in Powershell. Need to make the Powershell scripts easier for the operator to uderstand. I like yor presentation style. Keep broadcasting!!

[@joeyvico]

Your channel is awesome Kris!!!

[@DigitalMetal]

Thanks. And thank you for spelling my name correctly. :D Be sure to check out the second channel I just started: kzbin.info/door/FsvtR4aNPwefLjR1a9Hgvg

[@maxmeranda]

Thanks Kris!

[@SO-dl2pv]

in 12:00 , the 2>file.txt means redirect the stderr output to file.txt

[@AIGenerated]

Just what I needed, thanks

[@dderudito]

Really useful/efficient!

[@user-sh6nv1sx9o]

Thanks for short but useful video! One question: can I create with dialog multi-line input box?

[@hrnekbezucha]

This is great!

[@markharrington5826]

Could be very useful for creating a simple text based database For example , names and telephone numbers without the extremes of perhaps having to got through the entire procedure of creating a GUI in another language , having to open a stream to write to a file and then further a read the file back that file with a separate GUI based mechanism and again opening up a read stream to read file back in You could then combine this with basic bash scripts plus GUI depending on your exit code to select an operation , for example a sort or find or what ever other operation you might need on small scale with out all the massive intricacy of coding and understanding class inheritance , polymorphism and having to use try catch statements so as to deal with any errors although yes you could build these in with bash script mechanisms Ideal thinking here might be a simple logon GUI which operates or allows use of browser for example btw certain times checking that user is allowed and has access rights For other people who would like to go into this more then here are some more notes for you on using dialog part of the N curses library www.linuxjournal.com/article/2807 Just an idea !!

[@baee7478]

That is what I looking for. Thanks

[@EricMuranoAU]

So cool!!

[@Asimov16]

I have used dialog in Bash but would like to also use it i C++. Have you any pointers?

[@rematador14]

hi Kris, do u know how can i run some instructions when i select an option? tks :D

[@johnny5240]

One annoying thing when running dialog in a script is that the blue background does not disappear when you are done with the dialog box. I know that many have had the same problem. After hours of searching, I figured it out. Run this script twice in a row and you'll understand what I mean. #!/bin/bash # This is the solution to the problem where the blue background # does not disappear when you exit the dialog. # Use --keep tite. # Show information before dialog echo "Information that should not disappear from the terminal." echo "More information can be found here." # Show a dialog box dialog --title "Example" --keep-tite --msgbox "This is a message." 10 50 # Continue with the script echo "The dialog box has closed and we continue with the script here." exit 0

[@MrApplewine]

Mine just seems to print the image to the console, but it is not interactive. If I press enter it just shows the terminal prompt and there is no blinking cursor on the dialog boxes or anything.

[@joelamoako6778]

how do i store it in a variable

[@alerey4363]

This looks a lot like Debian text install; also reminds me of 90s Borland's TurboVision

[@derekfrost8991]

Very helpful.. :)

[@angelflores5893]

how cn i see the return from the menu? :(

[@krzysztofwaleska]

Your shell is bash or something different? Like exit code on red in prompt. Nice feature :)

[@weizhang6725]

It is zsh.

[@mahfuzurrahman601]

Since it has grml name there , I'm gussing it's zsh. But above is doable in bash.

[@marcello4258]

isnt 2> the error output?

[@jamescobb2618]

Cool

[@osiris5449]

Wait-- With this we could basically design a computer from scratch? Like, Boot, GUI and everything? Even login credentials and stuff? :s

[@trinketos]

nope

[@keokawasaki7833]

@@trinketos lol, that was kinda mean... but someone *had* to pop his bubble, i guess. XD

[@otsen82]

Hello Kris and everyone, do you know how to save the output into a var, I try this but it doesn't work. :( $> myvar=$(dialog --textbox "Enter something" 5 30) Any idea? Great video, thanks for all.

[@rabblerabble4969]

AnsInput=$(dialog --inputbox "Enter Something:" 20 60 "Text here..." 2>&1 >/dev/tty)

[@techwithdave]

Here is an example of what worked for me: exec 3>&1 sizeX=10 sizeY=30 options=3 value=$(dialog -menu “Please pick One” $sizeX $sizeY $options 1 “blue” 2 “green” 3 “pink” 2&1 1>3) returnValue=$? exec 3>&- echo “user selected”$value echo “return value is 1 for cancel, 0 for OK”$returnValue

[@markharrington5826]

For further reading once you have followed the tutorial via Kris then you might like to try this in C which is provided with Linux distros although you may have to install the library to use this and the c compiler Please see the following I think you will notice the difference very quickly and how much more you have to do as opposed to what Kris is showing you here tldp.org/HOWTO/NCURSES-Programming-HOWTO/helloworld.html

[@MoreChannelNoise]

Thanks fot that ncurses link, I downloaded the Tutorial in pdf format.

[@markharrington5826]

+MoreChannelNoise Welcome

[@mason-pe5lk]

4:49, it's sad that you choose no.

[@Crazmuss]

But 2> is stderr, why its put output in stderr?

[@DigitalMetal]

Because the dialog box itself is the Standard Output. Try redirecting the standard output into a file and you won't see anything on the screen, because it's going into the file. Then open the with something like VIM and you will see the characters that created the dialog box.

[@ShivamJha00]

But how to implement it in c++

[@user-gr5do8nk7e]

lmgtfy.com/?q=ncurses+tutorial+for+c%2B%2B first link

[@binarysaiyan9389]

Menu at 8:52

[@douwehuysmans5959]

return value

[@janjezek9333]

Why is "yes" 0 and "no" a 1 (one)? totally upside down! I cant understand who decided to swap that against ALL programming languages on this planet...

[@DigitalMetal]

Be cause the standard for exit codes in programming is '0' for success and '1' for fail. I think this is true for all programming languages, because it's how all operating system interpret exit codes. If there are no problems then the result is '0'. tldp.org/LDP/abs/html/exitcodes.html