search

Proxmark / Gaucho-GUI

Windows GUI by Gaucho
33 stars 25 forks source link

way to release GUI #2

Open ntkntk opened 7 years ago

ntkntk commented 7 years ago

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

0xFFFF commented 7 years ago

The releases should include all dependencies or make obtaining them simple.

pm3Commands.xml = settings.xml Probably a poor name choice. As you suggested, pm3Commands.xml exists so everyone can access and update it easily. The same also applies to the Documentation folder. Anyone with basic HTML knowledge can modify index.html or add more web pages as required.

ntkntk commented 7 years ago

"everyone can access and update it easily."

Yes, or at least can raise issue, raise idea to improve/correcting, making update request to reflect command timely to a new release. That would be best if during beta release phase, update of pm3commands.xml could receive a hint to start its update.