Reddit reviews Programming Windows®, Fifth Edition (Developer Reference)
We found 8 Reddit comments about Programming Windows®, Fifth Edition (Developer Reference). Here are the top ones, ranked by their Reddit score.
We found 8 Reddit comments about Programming Windows®, Fifth Edition (Developer Reference). Here are the top ones, ranked by their Reddit score.
The lowest-level Windows API is called win32. It's been the same foundation of Windows from Windows 95 all the way through Windows 7. Everything that's possible in Windows can be done via win32. Today there are many other layers on top of that - C++ libraries, C#, VB.NET and the Common Language Runtime, and much more...but win32 is still there under the hood, and if you really want to understand everything that's what you should learn.
This is as good a reference as any:
http://www.amazon.com/Programming-Windows%C2%AE-Fifth-Microsoft/dp/157231995X/
However, once you have a better understanding and can write some simple Windows apps, you may want to consider a higher-level tool.
Most people don't write win32 anymore.
In C++, you could use MFC, Microsoft's C++ library on top of win32. Or you could use wxWidgets, which is slightly similar in design but more generic and actually works on Mac & Linux too. Or you could use Qt which is similar to wxWidgets but gives you an even higher level of abstraction. All of these will feel more like Java's API.
If you don't need to use C++, consider C#,F# and the other CLR/.NET languages - most Windows-specific development is moving there because of a lot of tools you get to enable more rapid development.
Still, learning a little win32 will help understand how Windows works under the hood, which will be pretty helpful.
I think you really need to learn how to program windows in C, not this new .net or sharp stuff.
https://www.amazon.com/Programming-Paperback-Addison-Wesley-Microsoft-Technology/dp/0134382250
https://www.amazon.com/Programming-Windows%C2%AE-Fifth-Developer-Reference/dp/157231995X
edit: oops, you wanted courses, not books.
Senior Level Software Engineer Reading List
Read This First
Fundamentals
Development Theory
Philosophy of Programming
Mentality
Software Engineering Skill Sets
Design
History
Specialist Skills
DevOps Reading List
This old book from 1998 teaches GDI I believe:
http://www.amazon.com/Programming-Windows%C2%AE-Fifth-Developer-Reference/dp/157231995X
Seeing as GDI went entirely out of style not long after, I'm not too surprised that GDI tutorials are hard to find - GDI+ even harder. But that's about as official as it gets, and used copies are $5 on Amazon.
This book will answer all of your questions. It's dated, but is hands down the best Windows API book out there.
If you want a good book to get you started with the WinAPI check out this book http://www.amazon.com/Programming-Windows%C2%AE-Fifth-Developer-Reference/dp/157231995X/ref=sr_1_5?ie=UTF8&qid=1419265479&sr=8-5 it was the curriculum material used by a Win32 class I took and it's actually a very solid book worth having in your personal library.
Well there are quite a few ways you could go actually. I am going to assume you are on a Windows platform. If you want to learn the internals of Windows, pick up a book on Win32 programming. http://www.amazon.com/Programming-Windows-Microsoft-Charles-Petzold/dp/157231995X this book seems to be the best in the various Win32 genre.
Other than that you could try to pick up another API. DirectX and OpenGL were built for graphics programming, but they certainly have the tools available to build GUI's. I have also heard mixed things about C++.net and MFC; never learned either though.
>>Why choke people with details of inconsequence?
Permit me an analogy.
Here is a book on the Windows API. Please go write Starcraft III from scratch.
Here is a book on Homotopy Type Theory. Please use it to replicate and expand on the results of Goedel and rederive a proof of Fermat's last theorem.
Here is a book on Kant. Please revisit and critique post-modern philosophy and the inherent issues it inhereits by rejecting all systemic philosophy.
It shouldn't be a problem, right? All the information here is transparent. You should not at all be confused. Ever. Because all the information is in front of you.
On the other hand, here is a book on elementary mathematical reasoning.. Use it to figure out how many combinations there are of 3 committee members from a pool of 11 (very close to a situation in the book).
------
Clearly that's a terrible way to go about advancing knowledge or understanding of a subject. There is an orderly transition from beginner to experienced to contributor.
Now, one may talk as to when the appropriate time to introduce the confounding issues into the pedagogy is appropriate -- that is the whole crux of milk before meat.
The Church shouldn't care a flip about the small details of, say, Zina, because it's entirely inconsequential to the message it's taking to the world. Prophets are men like the rest of us, with a bit of a greater burden on their shoulders to teach the word of God -- meaning they have to go to God to get it. Their "credibility" is not at stake -- the invitation is, remains, and always will be to take it to God and see what he has to say about things.