Earlier quoted context omitted.
For >1 minute incremental compile times? No thanks.
[flagged]
Writing GUI apps for Windows is painful
191–200 of 577 posts
Re: Writing GUI apps for Windows is painful
#192Writing GUI apps is painful everywhere, and has been for years. I remember the half-baked transition from Windows Forms to WPF, which was then taken-over by the Windows Phone initiative, which was also extremely painful and half-baked. There's a reason electron is so popular, despite all the complaints about it as a platform. Don't blame the electron devs, blame Microsoft for completely failing to support their own p…
The lack of windows support for windows GUI's on windows is mind blowing. I remember absolutely whipping up Visual Basic line of business apps using the form designer in Visual Studio and data bound controls etc. If you wanted more there was MFC (with MTL developed by some insiders I guess at microsoft) The absolute insanity of going to WPF (wasn't data binding via reflection -> these apps got horribly sluggish!) the…
Remember when Microsoft honestly thought they had a shot at making a mobile platform to compete with Android and Apple?
Re: Writing GUI apps for Windows is painful
#193I'm working on a GUI toolkit that should match the requirements: Slint - https://slint.dev Can be compiled statically in a single .exe that is smaller than 40M. Has a license that allow proprietary on desktop for free. Has dark/light styles. Even comes with a (work in progress) drag and drop WYSISYG editor.
FLTK static binaries start at 100KB, win32 binaries can start at 1KB, Juce is about 2MB.
Using GLFW or SDL for an openGL window then using IMGUI would start at a few hundred kilobytes.
What are you doing in there that makes your binaries 100x times as big and why would this be a selling point?
Re: Writing GUI apps for Windows is painful
#194Earlier quoted context omitted.
For >1 minute incremental compile times? No thanks.
[flagged]
Long compile times are annoying and affect productivity. Some people are really sensitive to this type of disruption and it gets very difficult to stay in flow when the only thing you can do is sit and stare at a progress bar. This is particularly offensive to C# developers.
Take your elitist attitude and your gigantic C++ monstrosity elsewhere. Tell me you haven't used a modern JIT language without telling me you're a scrub. Jesus.
Re: Writing GUI apps for Windows is painful
#195B. And, if you had to write a cross platform app, which framework would you use?
Re: Writing GUI apps for Windows is painful
#196Earlier quoted context omitted.
It's funny that you mentioned apple because their system shortcuts are integrated as hell and they even let you map them in the OS -> App level, way better than anything MS has ever shipped.
Yep, among other things both Apple-unique and emacs-esque text navigation shortcuts are in every native textfield across all apps and anything that's a menu item in any app can have its shortcut key rebound in System Settings without any extra work on the part of third-party devs. It's one of the reasons why longtime Mac users are disinclined towards non-native apps. Most don't bother to reproduce these behaviors, an…
Oh and of course those shortcuts are activateable by other applications to simplify app integration.
Re: Writing GUI apps for Windows is painful
#197Re: Writing GUI apps for Windows is painful
#198Re: Writing GUI apps for Windows is painful
#199Re: Writing GUI apps for Windows is painful
#200Just use WinUI 3. Opting into MSIX packaging no longer requires an App Container sandbox. More info here: https://learn.microsoft.com/en-us/windows/msix/desktop/deskt... Full disclosure: I work at Microsoft.