proxmark/gaucho-gui

Windows GUI by Gaucho

gaucho-gui's Issues

way to release GUI

Files which need to be released together with GUI in form of dependencies should be put inside GIT too.

Also the settings.xml of the conventional GUI version should have a place a long side th e new GUI on GIT so everyone can access it easily. and practically also keeps an eye on its order, reports issue on fault or requests the need for update

would be best if a setup file, a batch file or install.sh could be released too, which would check the directory you want to install GUI, in, the rest of the job it, the install.sh or setup.bat, does on iits own.

Then our application has much more a flair of professional/commercial a much more grown-up

GUI and plot

When start plot from inside the GUI, plot window should ideally not be placed at same central screen spot or hidden most behind the GUI. The developer could tile the two windows or at least set them starting at different corners, less interference each other

https://github.com/Proxmark/Gaucho-GUI/tree/master

some change I would like to have in the new GUI

If it is feasible and not require too much work, I would like to see the features:

1/ the send command line should accept multi lines

2/ send command line should link to a buffer so you can recall commands you have tested there recently

3/ would be convenient when you are in a small experiment, the command buffer could be quietly reloaded with each restart of the GUI. I know, the other way to do is write a la lua script but many user can not program lua, yet they do experiment on commandline-interface

4/ instead of displaying text when loading setting.xml it should only display a progressing bar indicator, possibly start up time is shorter, (currently it loads and displays text, I don't know what for, it is too fast to read and too slow for the operator who wants to quickly access commands, not reading text he would not understand or does not see any benefit

5/ multi-pages on e for HF one for LF one for extra tools

6/ the list of commands going already longer and loner ... a sorting order or a way to index would be great

pls don't display non-informative rows of texts

instead of doing this, pls use progress indicator, percentage indicator or anything less power consuming, could possibly improve start-up speed.
But main argument against displaying rows of text is: Customer deserves to know how longer he/she must wait, when the program is ready to be used.
Just loading rows of text giving the customer no idea it would load only three more lines, 300 or 3000 lines
Surely you have been at least one time upset with a program which during install process behaves as if frozen, no display any information but installs thing without letting you know where, and let you sitting there wonder how long more it would let you go back to control sit again

window pane for command tree

When start GUI, command tree window should use optimize space to display much of command tree view, that is why user starts the GUI

send command

send command line should link to a buffer so you can recall commands you have tested there recently