I have a TUI for my scripts but sometimes the computer is only used with a mouse, so I want to make them clickable entries for the user
the code uses python
The code is too long to paste here so here's a link to the github page
Basicly what I want is clickable terminal text that opens one of the programs inside the code to minimalize the load on the computer, in this case the code runs on a raspberry pi, and because of the limited RAM and the 8 GB SD card I try to keep everything as minimalistic as possible.
so I was looking around the web while I posted this answer and found TKinter for graphical light weight gui's, I started messing around and found that in order to have my scripts show with text an all I needed a terminal window inside the gui, so I googled a bit and found this
someone was basicly doing the same as I had in mind but he faced an error, surprisingly after a good 1 hour of trying to solve it, I actually did and now have a working GUI with buttons and terminal unit :)
----------------------------FINALLY FULL EXPLAINATION-------------------------
So, After finding out a TUI in xterm is impossible to click at I looked into different options, I found multiple option, one was using zenity but I didn't like it because I installed it before ( keep in mind this is a raspberry pi with limited 1 GB ram) and it nearly drained the RPI from its memory, practicly terrified this was going to happen again I skipped zenity.
I saw Tkinter, which is basicly text to GUI its simplistic, light (since its nearly all code instead of heavy GUI like zenity) and just easy to use if you know Python, so I looked further into it and saw nearly endless possibilities.
Thus I started rewriting my TUI to a light GUI (eventually it became its own Thin client as seen on this screen shot)
However when I started I was unable to get it working like I wanted (since most my own tools rely on a terminal based execution (user ease of use :) ), so after what, a couple of hours of googling I found this unixSE post, that code was EXACTLY what I needed, but as I saw it was bugged, so I looked into it (its a hobby and my job to fix stuff from others!), some minutes later I fixed it up and got it in working order, so I started editing most of it, eventually using snippets of it in my own code.
Nearly two weeks later (WOOPS!) it is finally done, the code is uploaded on github for anyone wanting to see it.