This looks nice. Busy, but necessarily so and very straightforward. One could argue that it's too cluttered with options, but I could argue counter that it just needs to be better organized. A tab named "Standard" really isn't very descriptive.
All in all, though, I think this UI is worth the effort to develop, and it wouldn't surprise me at all if this were a third-party CLI wrapper.
Because I can type faster than I can navigate a cluttered UI.
The amount of time you can take with a script vs. the amount of time it takes me to write code to auto-generate a UI is irrelevant to this discussion. It is about the time you save the end user. It will also allow your utilities to reach a wider base, allowing you to gain more recognition as a developer. I do not understand why script kiddies and CLI fags like to remain in the dark underground. It's like they think it's cool that filthy casuals can't use their shit. I just makes them the incels of the software world.
Adding a new flag/field to a GUI does NOT break workflow unless you just slap it in there in a random place. You act as if no program relying on a GUI has ever, in the history of software, undergone an update that resulted in new checkboxes or dropdown lists being added to a GUI. What argument are you even making?
It's almost as if you've never written anything that outputs form data to JSON or a flat file. Do I have to create a sample form like I did above and show you how clicking a button can collect the user inputs and output it to JSON or a flat command-line string? Give me any format and I will give you that output.
Easy. Your help file is actually XML or JSON with a key/description for each field. You will have a utility (easy to write in a few lines of code) that will convert that to a flat file for easy viewing in a text editor. You can then use it in your UI to look up field descriptions by field name for use in a mouseover tooltip or, if the UI is small enough, just display it right below the control itself.
{ isFaggot: { desc: "Determines whether or not OP is a faggot. Always true." }, gayNessLevel: { desc: "Numeric value to determine the level of gayness. Always maximum value allowed." }, gaynessDate: { desc: "The date and time that OP achieved gayness. Always the date/time of thread." }}
Seriously, you script kiddies are brainlet-tier plebs if you can't wrap your tiny heads around these very simple concepts.
The don't use a fucking GUI. Read this, dipshit:
why is cli wrapper gui a thing in the FOSS world when you can very easily turn the cli into an API and shared object / dll?
even with a tardlang like python or java FFI is dead simple.
To make a cli wrapper reliable stdout & stderr need to have a consistant syntax, which never happens, parsing is usually some dogshit adhoc glued together with PCRE.
UNIX is the operating system of undless unnesecary parsing.
The right way to do it is with a library that exposes an API that can be used with any interface you want. Dynamic linking was a late addition to UNIX, so they still don't fully understand libraries and the difference between linking code and copying and pasting.
The real enlightenment is discovering that the UNIX "shell" is just a shitty programming language.
GUIs also suck on UNIX. On a real OS, a basic GUI program would be a few kilobytes. Improvements in operating system design used to lead to smaller code. That was the whole point of an OS and OS research. Whenever something is "improved" on UNIX, everything gets bigger. It doesn't make sense to have to write more code just so every user has to write more code, but if UNIX weenies did things that made sense, UNIX wouldn't be UNIX.
Subject: The Decline And Fall Of Western CivilizationThese stupid shit-for-brains weenix unie "programmers" havemanaged to break that mainstay of Western enlightenment andeducation, the dictionary. And I'll bet they excuse theirbehavior by saying, "Well, it's all Greek to me"!I suppose it's only appropriate that the invading hordesscraped the librarian at Alexandria to death with shells.They must have had a premonition that UNIX was coming.
can you provide an example of an OS where a basic GUI program is only a few kilobytes and the code is minimal?
Can someone explain to me why there's so much concern over GUI file size in the current year where storage space is barely anything to worry about? I bet you anything that a JPG taken on your phone is 10x larger than a simple GUI. Remember, the GUI is just the frontend that does nothing more than accept user input and then deliver that input to the backend or, if it's a wrapper, generate a command-line string that's passed to the exe.
it's not the size of the file, it's the number of lines of code you have to add to deal with a gui, it adds a bunch of unnecessary complexity and depending on what your doing it turns 3/4 of your code into GUI code instead of doing whatever it is it's doing.
consider most CLI programs are sequential, there is a simple start to finish
take arguments -> do work -> return results
with GUI code it's n o longer sequential, the entire thing must redesigned to accommodate and event/response system / loop.
instead of the above, it becomes
initialize gui -> wait for event -> respond to event -> do work ( but do it in a thread to make sure you don't lock the gui; even more unnecessary complexity) -> fill GUI with response, wait for another event
not to mention having to deal with retards sending multiple events at once, you have to deal with that.
what if retard clicks your long running "do work" button 50 times before it finishes the first one? are you going to launch 50 threads at once? no you have to detect it and prevent it, resulting in even more unnecessary code
Guess how many it takes for you to read this reply.