New shiny README and docs, and 2 bugfixes...

Author: vaisarger

README.md

@@ -7,8 +7,8 @@ Simplified way to code bash made GUI frontend dialogs! Check the youtube video:
 
 ## Introduction to EBG
 
-.. there is [bashlib](https://github.com/cyberark/bash-lib) that is for the code 
-itselft, well so then for the GUIs there are **EasyBashGUI** then!
+... There is [bashlib](https://github.com/cyberark/bash-lib) that is for the code 
+itselft, well so for the GUIs there is **EasyBashGUI** then!
 
 **E**asy **B**ash **G**ui shortened as EBG, is a Posix compliant Bash functions 
 library that aims to give unified GUI functions using frontends for dialogs boxeds 
@@ -69,13 +69,16 @@ Please check [docs/README.md](docs/README.md) document file!
 ## Credits.
 
 Thanks to Bash, Yad, Gtkdialog, Xdialog, Kdialog, Zenity, Cdialog, and Whiptail authors, this library was nothing without their work. Many thanks.
+Thanks to PICCORO McKAY Lenz for his efforts and *excellent* work on README (and bug hunting too).
+Thanks to zen0bit for first try and README impulse revival.
 Thanks to Frank Dietermann for suggestion though to make EBG "posix compliant" (since vers. 11.X.X )
 Thanks to Jose Joao Dias de Almeida for the makefile tip.
 Thanks to Chris "cgat" for his many ideas and suggestions that lead to version's "5.X.X" EasyBashGUI "revolution".
 Thanks to Davide Depau for his tests and support, and his effort to make EasyBashGUI Debian policy compliant, and finally for his man page.
 Thanks to Christian Prause for his patience and Git support.
 Thanks to Lucio Messina for "Debian policy" tips and support.
-Thanks to zen0bit for first try and README impulse revival.
+
+
 
 Please, let me know if my work has been useful for you.
 Vittorio Cagnetta

docs/README.md

@@ -35,12 +35,12 @@ write "clean_temp" at the end of all your scripts... ;-)
 
 #### Backend boxes priority
 
-EBG suppport for backend dialog boxeds depends on the runing programs:
+EBG support for backend boxed dialogs depends on the running programs:
 
 1. If all the required backends are available or at least kdialog are.. the EBG
    will try to check if kdebin is running and only will use kdialog.
-2. If only GTK based are running, the EBG will just use zenity, event if xdialog
-   is available and there is no desktop runing (window managers or similar.. )
+2. If only GTK based are running, the EBG will just use yad (or zenity ), even if xdialog
+   is available and there is no desktop managers running (only window managers or similar.. )
 
 #### Box mode windows
 
@@ -61,7 +61,7 @@ message "hola"
 
 All windows functions support options `<-w|-width> [integer]` and `<-h|-height> [integer]` 
 for custom window size with exception of "notify_message" and earlier versions 
-of kdedialog!
+of kdialog !
 
 ``` bash
 source easybashgui
@@ -73,9 +73,9 @@ message -w 800 -h 100 "Hello World!"
 
 #### Input and output
 
-EBG always use STDIN and STDOUT in conjuction with a temporally directory/filename.
+EBG always use STDIN and STDOUT in conjuction with a temporary directory/filename.
 
-The temporally names are managed throught the variables `${dir_tmp}` and `${file_tmp}`
+The temporary names are managed throught the variables `${dir_tmp}` and `${file_tmp}`
 
 #### Functions list features
 
@@ -114,11 +114,11 @@ notify_change -> <-i "[new icon]"> <-t "[new tooltip]"> "[good|bad]"		=>      (
 
 ## Examples
 
-You must made the scripts in `bash` languaje, EBG is coded in `bash`, in this document 
+You must made the scripts in `bash` language, EBG is coded in `bash`, in this document 
 we will use bash to ilustrate example usages:
 
-1. install EBS or sourcered the minimun 3 files
-2. crate the new program script from you
+1. install EBG or source the minimum 3 files
+2. crate your new program script 
 3. source the main endpoint of EBG (check following examples)
 4. saves and launch the new script program
 
@@ -197,7 +197,7 @@ dir="${choices[2]}"
 
 [![](https://img.youtube.com/vi/FEn4doXmiX0/0.jpg)](https://www.youtube.com/watch?v=FEn4doXmiX0)
 
-#### progress bar
+#### progress bar (by percent)
 
 ``` bash
 for i in 10 20 30 40 50 60 70 80 90 100
@@ -213,7 +213,21 @@ done | progress "This is a test progress..."
 adjust "Please, set Volume level" 15 40 75
 ```
 
-#### choose items
+#### choose items (only one)
+``` bash
+menu "Red" "Yellow" "Green"
+choice="$(0< "${dir_tmp}/${file_tmp}" )"
+```
+
+#### choose items (one or more)
+``` bash
+list "+Red" "-Yellow" "+Green"
+choice_list="$(0< "${dir_tmp}/${file_tmp}" )"
+IFS=$'\n' ; choice_array=( $(0< "${dir_tmp}/${file_tmp}" ) ) ; IFS=$' \t\n'
+```
+
+
+#### progress bar (by elements)
 
 ``` bash
 women=( Angela Carla Michelle Noemi Urma Marisa Karina Anita Josephine Rachel )
@@ -223,16 +237,13 @@ today_prefered_woman="${women[${index}]}"
 kiss "${today_prefered_woman}"
 sleep 1
 #
-
 # Job done !!
-
 # then...
-
 echo "PROGRESS"
 #
 done | progress "This is a _LOVE_ progress..." "${#women[@]}"
 
-# if you use "PROGRESS" string in STDIN do not forget second argument ( "[elements number]" )
+# if you use "PROGRESS" string in STDIN do not forget *second* argument ( "[elements number]" )
 ```
 
 #### notify example with yad as backend

docs/install.md

@@ -22,7 +22,8 @@ You can use as system-wide module lib or as quick start module embebed!
 * Interpreter
   * `coreutils` 8.0+ https://www.gnu.org/software/coreutils/
   * `bash` 3.0+ https://tiswww.case.edu/php/chet/bash/bashtop.html
-
+  * `bc` 6.1+ https://www.gnu.org/software/bc/
+  
 ## Quick start usage
 
 Install `git` and then clone the repo, later echoes the required minimal example:
@@ -83,7 +84,7 @@ list +"you" -"me" +"her"
 clean_temp
 ```
 
-Later just lauch it! Just remmembered that this example assumes you have 
+Later just lauch it! Just remember that this example assumes you have 
 installed system-wide the EBG programs.
 
 And... enjoy !! :-)
@@ -95,19 +96,19 @@ but due it relies on backend and coreutils programs there are some
 directions:
 
 * **Minimalist people should depends on coreutils!** we used some command 
-like `wc`, `type`, `cut` and `bash` and we reliles on their important features 
+like `wc`, `type`, `cut` and `bash` and we relies on their important features 
 that `busybox` neither `dash`/`sh` can provide it!
-* **backends (frontends) are not dependencies, but dialog it is!**, we are 
-aware that we need a backend, but dialog is the backend that must be placed as 
-a dependency, but since not only does whiptail depend on a library separate 
-from its own but it has fewer functionalities in itself, dialog is by far 
+* **backends (frontends) are not dependencies, but (c)dialog it is!**, we are 
+aware that we need a backend, but "dialog" is the backend that must be placed as 
+a dependency, but since not only does "whiptail" depend on a library separate 
+from its own but it has fewer functionalities in itself, "dialog" is by far 
 compatible with everything created since the beginning of times.
-* **dont recommends any backend (frontend), its not necesary!**, no so much 
-package managers have the suggestion part like debian, but please dont recommends 
-any backend, the EBG must use the already provided and present in your env! 
+* **don't recommend any backend (frontend), it's not necessary!**, not so much 
+package managers have the suggestion part like Debian, but please don't recommend 
+any backend, the EBG must use the already provided one and present in your env ! 
 your project that will inplement EBG will manage those depends and recommends!
 * **follows installation paths** the EBG does not put any file outside of the 
 right place, so please dont change anything!
-* **none of the requirements are build requirements!** yeah, EBG its fully 
+* **none of the requirements are build requirements!** yeah, EBG it's fully 
 runtime script!