Win32 API Programming - is it worth it?
Now I am code win32 api windows explorer. But it seems very difficult to me. I have a month. But after a time when I code, I wonder if the win32 api code is worth me ?, when we create GUIs with ease with MFC, or even easier with C #.
What should I do?
1- Save encoding with win32 api to understand them deeply.
2 Just study and code some programs to understand how they work.
Can you figure out how long each selection takes (or how many projects).
thanks for reading, as a 2nd IT university student, I really want your advice on this. My goal is to become a good and efficient programmer :)
PS: Recommended books are really appreciated.
a source to share
If it's purely from a learning perspective, I'll say do it. However, if it was for a business application, I would say, "Go with the latest technology."
Since you are currently in the learning phase, a deep understanding of the Win32 API will help you in the long run, although this may seem difficult right now. I went through a similar path myself, and I ended up better equipped with a basic knowledge of things.
a source to share
- If you're serious about wanting to know how programs work, go to the Windows API.
- MFC is more than a thin shell around windows. CDC wraps HDC, CWnd wraps HWND, etc. You didn't get much using it.
- If you want to write flashy GUIs, go to WPF in .NET language. For better or worse, Microsoft is not interested in updating the GUI capabilities of the win32 api. Windows dialog boxes allow windows to handle tabs between controls and automatic scaling of the GUI to compensate for font and DPI settings. WPF on the other hand is where MS added support for animation effects for controls, ribbon bars, etc.
They have created a "modern" GUI suite for win32 api applications such as their login dialogs and explorer windows. It's called DirectUI, but they don't share. For us, its .NET, third party gui library or bust if we want nice things for Win32 api apps: / (Well, we could take the time to build our OWN "flash" GUI with effects, but that seems like a waste time for me).
a source to share
Move to WPF, C # - seriously the WinAPI time for high level stuff is over. ESPECIALLY that WinAPI (DIrectX, etc. stay around much longer) where most things are not very time / memory sensitive to start with. You'd be surprised how easy it is to great forms in XAML / WPF - that is, if you have a hand for graphics at all;)
a source to share