Best way to learn Windows programming ?

[Neto_D_Walker]

I cannot seem to figure Chili's framework... i mean, i can understand the codes he gives us... but i dont get why he is putting other things in other files and such things... and i dont get why some codes must be after the compose frame... i need help O.e

[Musi]

Putting things in separate files is good in many ways, it makes the codes easier to read, usually easier to debug and it will re-compile faster because only the files that have been edited need to be compiled instead of the whole project.

The different files group together related code, like Windows.cpp has all the code for creating a window and a message loop (every Windows program needs these), the D3DGraphics files contain all the code to set up DirectX and also contains any drawing functions.

[Neto_D_Walker]

It makes sense as the compiler wont have to debug it again... but what about the rest of the framework ? im just at tutorial 12, is he going to explain the rest of the codes at his framework ? will he teach us to build our own framework ?

[Musi]

He goes over the framework in the intermediate lessons i think. It's basically made to separate the Win32 code and the DirectX code from you game logic.

To understand what the windows.cpp file does I'd recommend reading "Windows Programming fifth edition" by Charles Petzold, it has all you need to know about creating a window and the message loop. As for DirectX you could get a DirectX 9 book, but in my opinion you'd be better finishing the tutorials and then start learning DirectX 11 cause the way things are done has changed a fair bit. That's if your graphics card supports it of course.

[Neto_D_Walker]

I see, thanks for the help... I plan to master C++ in DOS first, then I'll read the book

[DreamBliss]

Imagine you are creating a 3D video game. Well one single file could be 10,000 lines or so in length. Probably more. So you have different files and different classes and different functions. You may have a terrain source code page. An animation page. A model page. Or even these may be split up. Perhaps you have a terrain page for the general terrain and another for tools. That's why you use different pages or source files. Makes it easier to edit stuff, to spread the code amongst other coders, etc.

[Syncan]

As for DirectX you could get a DirectX 9 book, but in my opinion you'd be better finishing the tutorials and then start learning DirectX 11 cause the way things are done has changed a fair bit. That's if your graphics card supports it of course.

What book about DirectX would be recommended? Is this one a good one?

[Clodi]

@Musi

"Windows Programming fifth edition" by Charles Petzold
Is probably the book I'll end up buying. Are you sure it's accessible enough for people like me who started off with Chili's tutorials? I have been away for a while but I reckon you know "my level" as I haven't learned anything new from "BoxWar"..

I have finally finished my exams and now I have a lot of free time and I am keen to keep learning C++ and Windows programming but I looked up online and the book you suggest is apparently the size of a couple of dictionaries XD

Is it worth the investment if all I care is being able to write my own framework from scratch?
I am really looking for something very much like a "textbook" to be able to follow along with Chili's stuff. It took me a long while to get through arrays, strings and pointers and I really think I'll get lost trying to find my way around the framework without a book.

Thanks a lot,
Clodi

[nG Inverse]

For learning new APIs (like for Windows and DirectX), I actually don't suggest reading books! Reason is, many only cover one way on how to approach the API.

What I have done with DirectX is gone through MANY tutorials, both video and text, to see the different ways people go at the API. There are many different routes, all of which should be learned so you can decide which would be best for what you are trying to do (like Chili's isn't necessarily the best for creating games!). Purchasing a couple books too, though, couldn't be hurtful. It just seems like a lot of money for little gain.