I started to make a large-scale project through the console application, with the thought “now I will gain experience in code descriptions, and then I will simply connect the interface, and everything will work” ... Yeah, I connected ..

Initially, I wanted to use WindowsForm , because there is a very convenient constructor, but I did not suspect that it does not work with streams from std , and using streams through System.Threading is not an option at all. I thought about Qt, but adapt all strings, mutexes, lockguards, etc. under Qt-shny style a little laziness. There is another option with WinAPI, but it is absolutely inconvenient for me, and I will have to give up many chips with the interface, but it will not suit me.

In short, the question itself: can I somehow use the interface from WindowsForm , but what would it not interfere with my std ? Or what other options are there?

  • CLI is a generic term, the “Command Line Interface”. So the mention of some constructor raises the question of which library you used for this. And where did you get System.Threading ? This is also some kind of non-standard class from a third-party library (if we talk about C ++). - ߊߚߤߘ
  • What does your question have to do with C ++? - user227465 7:43 pm
  • @Arhad seems to be confusing. I meant WindowsForm. - Verm ww
  • The user interface can be executed as a separate wrapper application that will run the main program (currently available) as a child process without a visible console window and translate user actions from the GUI to text commands for it, and translate the answers back to the GUI. The great advantage of this approach is that you don’t have to touch your program at all, and the GUI wrapper will be functionally isolated from the main logic. Plus, if you wish, in the future you will be able to screw some other interfaces in the same way. - ߊߚߤߘ
  • one
    It is not clear that you want ncurses? wxWidgets? GTK? - GarfieldCat

0