I would like to switch from console applications to window applications, but no matter how I look at these api functions, I have only square eyes. In general, I cannot drag in what to do with this function, where to write it, although when I wrote for the console, there were no problems with the functions. Maybe you can help who can do this: with a website, a reference book, or so it can be explained ... In general, thanks immediately. )

Closed due to the fact that it is necessary to reformulate the question so that you can give an objectively correct answer to the party PashaPash ♦ 4 Oct '16 at 7:56 .

The question gives rise to endless debates and discussions based not on knowledge, but on opinions. To get an answer, rephrase your question so that it can be given an unambiguously correct answer, or delete the question altogether. If the question can be reformulated according to the rules set out in the certificate , edit it .

    10 answers 10

    Try Qt, this is not winapi, maybe it will suit you

      Looking at what windows you want to go. If it is under Windows, then you can see WinForms. In general, it is better to write in C # or Java under the windows. On pure winApi complicated. I tried ... I did not really like it. Of course, there is an MFC wrapper for winApi, but this is generally the last century, it’s better not even go there.

      If in C ++, if cross-platform frameworks: look at Qt, wxWidget (I'm studying this framework a little now), GTK +.

      • 3
        May already be enough to advise WinForms? :) There is WPF, which promotes a much more "correct" approach to building gui. WinForms is actually a wrapper over WinAPI - Oleg Nechitailo
      • WinForms is simply much simpler than WPF. For training will go. Although it is better to immediately learn the right things. - Walter Nuss
      • one
        WinForms is much worse than WPF in that (1) it’s hard to write applications with a normal architecture, (2) there are a lot of details specific to WinAPI programming that a normal programmer couldn’t learn, especially in light of WinRT that has already come to us. It’s better to start right away with conceptually clean WPF. - VladD
      • Or just look in the direction of WinRT, despite everything that is being watered, the API is pretty clean and beautiful, there is no heavy legacy and crutches of backward compatibility, like in WPF or WinAPI - Oleg Nechitailo

      I recently came across this page, everything is described in a fairly accessible language: Basics of programming for the Win32 API

        Try libraries: Qt or GTK +

        WinAPI is certainly a powerful and fast tool, but not cross-platform, and the development speed on it leaves much to be desired.

          If we are talking about WinAPI , then from my own experience, I can say that functions and truth seem very scary at first, but everything starts, oddly enough, with classes and bicycles that no one talks about, because they are embarrassed, but they all write. ))

          And in my opinion, there is nothing surprising in that there is a lot of things in WinAPI, and to solve basic tasks, only a fraction of this is enough, so you can see how the same API functions are used in several different wrapper classes.

          Some people write by looking into ready-made frameworks, such as MFC, WTL, I was then looking into Delphi.

          To make life easier, I advise you to take a course on integrated work with some ready-made set of primitives, such as STL, and without fail to learn how to work in MSDN

          • the local copy of MSDN doesn’t really put in; well, it’s very, very direct, yes, yes, it’s in the beginning that you have to spend most of your time.

            Read here about the very principle of using WinAPI in C ++

              Creating a Win32 Application (C ++)

              This walkthrough demonstrates how to create a basic Win32-based application that is displayed in the "Hello, World!" Window. You can use the code, when developing as a template, to create other Win32-based applications in this walkthrough.

                You can learn the basics of Vinapi in a few days, but then you’ll have to work hard, I’ve studied and taught Vinapi until now. See the lessons on the Internet. We write on WinAPI from scratch - for example.

                  According to numerous advice, I use the book "Programming for Windows 95 Petzold Ch.". Everything is very accessible and gives at least some basics, and then it will be easier and you don’t need to look at what it is for windows 95, because for the same advice, there are minor changes in winapi and almost none regarding this book. If I am mistaken, then correct.

                    I advise you to start with WinAPI, Yuri Shchupak will help you with this and his book "Win32 Api. Effective application development" is an excellent book in terms of a textbook and in terms of a reference book. It can and should be read to all beginners in the development of window applications, it’s fine and most importantly, the basic concepts of Windows are described. I give a tooth that after studying this book you will be able to write a window application with almost any functionality, which cannot be said about its external beauty :)
                    By the way, so that you are not afraid of types in WinAPI, look at the Hungarian notation .