#include <windows.h>

What do you guys think? I wrote a program in C at work that will grab some data from various places and put it in a better format, but it's all done from the command prompt.

Ever try explaining to people how to use the command prompt for the first time? Not fun. I can't do that for everyone that wants to use it.

Easiest thing for them would be a windows applications where you can enter values into fields rather than command line arguments, but this would take much longer.

What does /prog/think?

Retards shouldn't be allowed to use computers.

A++ would laugh again

>>3
What the fuck is your problem?

>>2
Such a pity 99.99% are "retards" and the remaining 0.01% aren't a profitable enough market.

>>1
You can't ask people to use the command prompt. Forget that immediately. And no, it won't take much time and pain to decorate the thing with nice windows and forms.

>>6
And no, it won't take much time and pain to decorate the thing with nice windows and forms.
Yes it will, I've never done it before.

Can you make a template with just a couple fields from which those strings will be sent to my actual function once a button is pushed?

You can't ask people to use the command prompt. Forget that immediately.
Why not? The sooner they learn the better.

>>1

I personally find command line arguments, combined with thorough and easily search-able documentation, to be much more user friendly windows and fields, where each field is described with a single name and that is all you get for documentation. But after some practice with windowing stuff, it isn't too difficult to make one as a replacement for command line arguments.

>>8

They don't understand the long term benefits of learning the new skill.

>>8
They don't care to learn. They are dumb as shit and you have to take that into consideration. They see the computer as a facebook machine that can also run MS Office. If you try to educate them they will complain and you'll be fired.

>>10,11
So I gather by your definition the ``intelligent'' approach is wasting a few hours a month reading man pages to figure out the arguments for some utilities you use once a year.

Good thing people don't put up with that shit anymore. There's a hell for people like you in which each door, tap and switch has a nice man page. But hey, on the bright side, you can script them!

Good thing people don't put up with that shit anymore. There's a hell for people like you in which each door, tap and switch has a nice man page. But hey, on the bright side, you can script them!

I'm ok with that. I would enjoy this hell, scripting every door, tap and switch.

http://www.cprogramming.com/tutorial/opengl_first_windows_app.html
This is fucking hideous. Fuck that, those faggots are going to use the command prompt. I guess I can just have them input shit from the prompt itself.

>>12

Once you learn how to read man pages, and to jump to the information that is relevant to you, it doesn't take that much time to find what you need. It would take a while if you initially had no idea or background in what the application did, but the same would be true if it only had labeled text inputs in a window. Really, the only difference between the two is that the window style presents each optional argument as the user is filling it out. When there are lots and lots of arguments, they have to be organized in a way that is hopefully intuitive. The user has to perform depth first search through your interface, to find the options he or she needs. Eventually, the user memorizes the locations of the needed options. Using the command line interface, with a reference to a man page and maybe a few usage examples will take about the same amount of time to master, but the difference is the appearance. The user has to get over the void space of the command line. The options aren't presented to the user while he/she types them out. He/she has to type them him/herself. If he/she had a man page open in an adjacent terminal, this wouldn't be an issue though. But it is intimidating, so people avoid it.

>>14

try using a horrible and primitive, cross platform gui-kit. Do something in Java or something. You just make windows and buttons and shit.

Please help.

No shit? Where did this come from? Story development doesn't mean it has to be mystery.

Pure muscle memory for me. Some of the harder songs I might fail a bunch, but I catch on if I keep it up.
Rin-chan Now! is a good example of a song that I got stuck on for a long time before I was able to do it.