Well, webman...
First of all, my method, even if you want only "dialog mode" boxes, already has an advantage: it simplifies a lot scripter work.
An example.
This would be command line handling directly "dialog" (from its man page), about a "menu" box:
>dialog --menu ...
Special options:
[--create-rc "Ifile"]
Common options:
[--aspect ] [--backtitle ] [--beep] [--beep-after]
[--begin ] [--cancel-label ] [--clear] [--colors]
[--cr-wrap] [--default-item ] [--defaultno] [--exit-label ]
[--extra-button] [--extra-label ] [--help-button]
[--help-label ] [--help-status] [--ignore] [--input-fd ]
[--insecure] [--item-help] [--keep-window] [--max-input ]
[--no-cancel] [--no-collapse] [--no-kill] [--no-label ]
[--no-shadow] [--ok-label ] [--output-fd ] [--print-maxsize]
[--print-size] [--print-version] [--separate-output]
[--separate-widget ] [--shadow] [--single-quoted] [--size-err]
[--sleep ] [--stderr] [--stdout] [--tab-correct] [--tab-len ]
[--timeout ] [--title ] [--trim] [--visit-items]
[--version] [--yes-label ]
As you see, features are a lot, you have a great control on almost everything, but it's a little bit confusing, at least at beginning.
EasyBashGUI, instead, since its goal is simplify scripter's work, would be like so:
>export supermode="dialog" && source easybashgui
>menu ...
...it's enough.
If you want deepest control, maybe EasyBashGUI is not for you; if you want simplicity, maybe EasyBashGUI is useful for your needs.
Moreover, you should carefully consider that your script could one day used in a graphical environment.
It's not an improbable event. You wrote a program to your geek friend, but now he's asking to you to give a nicer gui; or former intended target user is now no more comfortable with terminal programs, now being an happy KDE user; and so forth...
In that way, using my library,
>adjust "Please, set Volume" "0" "35" "100"
will work exactly the same, with dialog and, in KDE, with kdialog, without any modification.
This is, IMO, a priceless potential feature, you should consider it.
