[Savannah-register-public] [task #13746] Submission of Text User Interface, framework for scripts

[Simon Arjuna Erat]

URL:
  <http://savannah.nongnu.org/task/?13746>

                 Summary: Submission of Text User Interface, framework for
scripts
                 Project: Savannah Administration
            Submitted by: sea
            Submitted on: Mo 21 Sep 2015 16:23:10 CEST
         Should Start On: Mo 21 Sep 2015 00:00:00 CEST
   Should be Finished on: Do 01 Okt 2015 00:00:00 CEST
                Category: Project Approval
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________

Details:

A new project has been registered at Savannah 
This project account will remain inactive until a site admin approves or
discards the registration.


= Registration Administration =

While this item will be useful to track the registration process, *approving
or discarding the registration must be done using the specific Group
Administration
<https://savannah.nongnu.org/siteadmin/groupedit.php?group_id=11510> page*,
accessible only to site administrators, effectively *logged as site
administrators* (superuser):

* Group Administration
<https://savannah.nongnu.org/siteadmin/groupedit.php?group_id=11510>


= Registration Details =

* Name: *Text User Interface, framework for scripts*
* System Name:  *tui*
* Type: non-GNU software and documentation
* License: GNU General Public License v2 or later (The texinfo manual is
GFDL.)

----

==== Description: ====
Every scripter writes his own functions for very common shared features, like
- but not limited to:  status & yesno.

TUI is not only a collection of commands of such kind, but accomplishes its
name and provides an interface like feeling that is very easy to attain and
maintain.

It also takes care of issues when sharing your scripts with your own
functions... 
For example, when you need to call external applications, such as webbrowser,
filemanagers or editors, TUI not only checks for you wether the user is in GUI
or CLI mode, but it also openes his selected application for that specific
environmental task. 
In short? - tui-edit, might open EMACS in GUI, while it would open VIM in CLI
(i'm aware they're both CLI capable).

Evenmore endusers have reported, they would feel more comfortable with a TUI
script, rather than a regular script.
In the matters of: 'I have more chances to find the info i need'.

However, TUI would not be a TUI without its 4 core displaying modes.
* tui-printf (the absolute core, but not as powerfull as its name-cousin)
* tui-echo (like the other 4, first string left, 2 strings l/r,
3strings=left,center,right)
* tui-title (borders, colored inbound, first string in center)
* tui-header (borders, colored outbound)

Its all written in bash, because its all it needs, with the exception of the
docs.

What's so special?
Ncruses is great, but its to compile.
Wiptail is nice, but its boxed.
But TUI... REALLY is for scripts.


==== Other Software Required: ====
www.gnu.org
* bash
* coreutils
* awk, grep, sed

Seriously, i have to provide you those licenses? ;)


==== Other Comments: ====
TUI is in the evaluation process to become part of the GNU familiy.
yay :)

It provides no binaries expect a tarball that contains a template directory
structure with some files for new projects.


==== Tarball URL: ====
https://github.com/sri-arjuna/tui/archive/v0.8.9-GNU-RC15.tar.gz






    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?13746>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.nongnu.org/