Well its been a pretty good year of learning c++ at uni. But I always ask myself, who wants crappy console based applications? If someone came up to me and wanted a program, they are probably expecting something with a WIMP interface, not some old style dos thing.
Can someone enlighten me on this matter?
If you are on a windows platform, then a quick look at a windows tutorial would be a start
http://www.sunlightd.com/
It's a little "alien" to begin with, but it's worth sticking at
You shall reach the path to Nirvana by learning one of these:
OpenGL
DirectX
Both are graphics libraries, no more consoles, now you have a powerful tool to create programs like Doom, or Call of Duty...
There is SDL too, dunno what that does, I'm not going to pretend to be a genius on these matters....
But you could look at C++ as the brain as your code, and OGL or DX as the eyes...
And then you have MFC, less graphical, more GUI like (ever try playing with Visual Basic? Kinda like that, only with C++)
None C++ sucks go learn BASIC if you want to do things.
Woop?
Colsole programming allows you to learn the c++ language without the added complexity of learning an API at the same time. Once you are familiar with c++ you can then go on to learn the windows API or whatever OS you want to use.Originally Posted by jlf029
There are many uses of console programs in real-life. One use is for programs that run with no human intervention, such as database servers, internet servers, programs that a network administrator may run remotely (that runs on another computer). Server programs I mentioned don't even have a window let alone a GUI window. And some operating systems don't even support windows, either MS-DOS style or MS-Windows style.
>But I always ask myself, who wants crappy console based applications?
Well, since I make a very good living writing "crappy console based applications", and I seem to have skills that are in demand, I would say that quite a few people want them. You have to remember that "console based" doesn't necessarily mean stuff like simple text based calculators and stuff that you've probably been writing. It could simply mean a back-end application that can be plugged into a visual interface. For example, nobody in their right mind would use VB to handle the processing of a sophisticated program, but because VB makes for nice and easy user interfaces, you glue it together with a non-graphical back-end written in C++ and things work nicely. It could also mean system level applications that don't need a graphical interface, or any interface with end-users at all. Device drivers and such typically count as console applications, but they probably don't use a console and certainly don't need any help from a user.
Then there are tools that are easier to use from a console. Consider filtering programs that you can pipe together on a file or list of files. Each filter does one job very well, and running them in sequence is trivial, where doing the same thing with a graphical program would be more complicated, take longer, and cater to naive and casual users rather than the power users who the filters would more likely be written for. And what about recovery tools? If all you have is a console due to some catastrophic failure, launching that GUI diagnostic tool is a good way to get laughed at.
My best code is written with the delete key.
How does the glueing together work?It could simply mean a back-end application that can be plugged into a visual interface. For example, nobody in their right mind would use VB to handle the processing of a sophisticated program, but because VB makes for nice and easy user interfaces, you glue it together with a non-graphical back-end written in C++ and things work nicely.
It depends. COM, CORBA, XML-RPC, SOAP are a few choices. If you are interfacing with VB COM is likely the answer.
The crows maintain that a single crow could destroy the heavens. Doubtless this is so. But it proves nothing against the heavens, for the heavens signify simply: the impossibility of crows.
SDL can do input, output (and can help with managing OpenGL), and their are a few extra libraries that can go with SDL do do such things like networking and sound.
If any part of my post is incorrect, please correct me.
This post is not guarantied to be correct, and is not to be taken as a matter of fact, but of opinion or a guess, unless otherwise noted.
I used my big, thick C++ book as a doorstop one time. If I hadn't tried to learn C++, I wouldn't have had a book heavy enough to hold the door open. Real uses of C++.
ned: Hey everybody, check out my new app!Well its been a pretty good year of learning c++ at uni. But I always ask myself, who wants crappy console based applications? If someone came up to me and wanted a program, they are probably expecting something with a WIMP interface, not some old style dos thing.
Can someone enlighten me on this matter?
jimmy: Awesome doood! That is super kewl looking. What's it for?
ned: I dunno. I haven't learned how to make it do anything yet.
If you use a GUI library with C++ you can do these types of applications.Well its been a pretty good year of learning c++ at uni. But I always ask myself, who wants crappy console based applications?
The programs cashiers use(POS systems) are usually console based.If someone came up to me and wanted a program, they are probably expecting something with a WIMP interface, not some old style dos thing.
you have to crawl before you walk and walk before you jog and jog before you can run =).
thats have c++ goes basically.
c++ is more sophisticated then visual BASIC
