Thanks. As you said, the IDE is built on winforms, so it's windows only. maybe it was a mistake to not to use a cross platform framework like avalonia, but i really like the winforms designer, and winforms is the only UI framework i ever used, except for MAUI which is not a good idea to build an IDE on.
back
2 comments
Windows.Forms is becoming less of a problem with projects like LibreWinForms [0] progressing quickly. I just tried to build your project and there are only a few classes that are not implemented when it comes to the GUI.
This is really interesting. Thanks
I really miss working with WinForms.
Every other UI framework I worked before and after always left me with the impression that something was lacking, in speed of development, fast iteration, but also in the quality of the abstractions.
Plenty of reasons to continue using WinForms for quick and dirty utils.
WinForms has had a major cleanup over the last few years. Issues with DPI, multiple windows are mostly gone.
You no longer need VS2. vscode on its own is excellent, and you can if you need to, still use VS2 for debugging
(Same applies to AvaloniaUI for cross platform.)
Codex, Claude need guidance if you want something maintainable, otherwise they generate a mess structure wise or reinventing functionality already available in standard controls 'out of the box'.
But people want python ...
> Plenty of reasons to continue using WinForms for quick and dirty utils.
Indeed. But I always found WinForms also better for "slow and polished".
I completely agree with you. It definitely felt like function over form. It was utilitarian, but WinForms was probably the closest thing since Visual Basic (and Delphi) in terms of rapid prototyping of a GUI.