Actually a question.
Why with languages like C #, VBasic in MSVS when creating a
Win project, FormBuilder immediately appears and you can drag the mouse quickly to wrap up the form and describe the necessary event handlers, and have the pros been deprived of this opportunity? Well, that is there is
wxWidgets , for example,
Qt , but writing with a pens a graphical interface, somehow, hmm, is not clearly something. It would be wise to automate this process before working with the mouse, I think.
Why did this happen and what were the historical prerequisites for that? Is there any \ IDE library (with support for modern compilers) that somehow fixes the current situation?
It's just, well, really, somehow reluctant to me to write a class hierarchy with inheritance on
wxWidgets when I need to create an application with three buttons and a couple of
Edit'ов to count overhead, for example.
Actually a question.
MFC is one of the first libraries for the GUI, the first version of EMNIP was released in 93, in parallel with it appeared like 2 drops of water similar to wxWidges. Both did not have graphic editors, and both are more likely to resemble a macro wrapper over the API (although OOP and MVC are there, in what form the floating ones know xA). Whether historically it was so or this is the malicious intent of the developers, you need to look at the autobiography;).
By sabzh - for wxWidgets there are several live and neochen editors, incl. plugin for code :: blocks. In MFC, besides the built-in dialog editor, I did not see it.
Shl. Libraries closer to the API can hardly be found, which is why their performance is high. There is an opinion that editors will be harmful for them.
Why cheated? Never cheated.
- There is a C ++ Builder. Essentially the same Delphi, but C ++ is used as the programming language.
- In MSVS, you can also program "visually". But there really the form editor does not appear immediately, but you need to call it yourself. Then the code is quietly written there. Those. just slip your standard event handlers. In MFC, it makes sense to inherit from the base classes of controls only when you extend their functionality. Well, or override the behavior of the control.
Why did this happen and what were the historical prerequisites for that?
The reasons are simple. Previously, computers were not so powerful. It is terrible to think when something like that was not a mouse, but there were no other usual things. When this interface was generally only a text and graphics editor was not needed. C # created those times when many people did not even remember when windows did not exist.
and the advantages of such an opportunity cheated? you need to understand that the “pluses” is a wider language than just creating gui. If for c ++ programs you need gui, then you just take the appropriate library. And it can be a convenient (and this is very subjective) editor.
In addition, think about how to standardize the graphical interface for different platforms, on the pros, because not only under Windows they write.
Therefore, C ++ nobody infringed. Just the opposite.
For Qt, there is a very convenient tool for visual interface creation: Qt Creator and Qt Disigner. Even for GTK there is a program called Glade. So, C ++ is not deprived of anything. Quite the contrary.
Yes, and pens in Qt to write the interface is not so difficult.