Earlier quoted context omitted.
Would it be good enough on platforms like iOS to dynamically link, include the DLLs in the bundle, and tell people they are on their own if they want to switch them out? You theoretically can.
>> Would it be good enough on platforms like iOS to dynamically link, include the DLLs in the bundle, and tell people they are on their own if they want to switch them out? You also have to offer them source code, or just ship it along with.
WxWidgets 3.2
61–70 of 84 posts
Re: WxWidgets 3.2
#62A truly excellent toolkit. The code is very readable and the developers are quick to communicate/respond on the forum or stackoverflow. I wish more people used it instead of writing "apps" that are just a giant web browser with javascript and a hack to get menus working correctly, with fake UI widgets that don't respond like native window controls (no proper tab navigation, no moveable or resizeable dialogs, keyboard…
I get near parity on design on all platforms yet keep full native speed on mobile.
The main issue with old widget system is how hard is to theme them, and theming is, I think, a major driver of the use of HTML/CSS (certainly on my business customers, where they demand the UI be colorized with their corporate stuff!).
Fix that (like with SwiftUI) and suddenly using native is more doable (bussines-wise).
Combining with server-driven architecture, so far my eCommerce app with 3 dozens of screens is made with 2 files of SwiftUI (app specific, plus a one-time cost in build the boilerplate), very doable to a solo guy to code all in 3 platforms.
Re: WxWidgets 3.2
#63I used this 15+ years ago with C++, it was so much easier to do cross platform things that way and it had good performance. Now I think I have not worked on a native desktop app on at least 10 years. And everything I see others make is more hybrid, javascript, electron kind of things. The performance of that even though we have much faster hardware feels worse than what WxWidgets / C++ did 15 years ago...
I was an active user until 2 years ago, when I quit my last enterprise software job. They had a cross platform (including embedded systems) enterprise video security system, a suite of applications all written in wxWidgets. They screamed, they were so fast. They had to be, for our enterprise clients. But those same clients had typical "give me candy" managers, and they complained about the ancient native interface. T…
Re: WxWidgets 3.2
#64WxWidgets is like React Native but for desktops. It uses the platforms' native UI frameworks. Gtk on Linux. Audacity the audio editor uses WxWidgets.
Re: WxWidgets 3.2
#65wxWidgets has a sublime idea: an api that is just a wrapper over native controls. For cross platform frameworks it is fast and light. The very opposite of bloatware. But it also has a terrible flaw: its heavy-templated C++ api, hard to port to other languages. I don't want to get stuck on C++. I want to use Go and Rust. And all the wxWidgets ports to those languages suck, big time. Show me a solid wxWidgets for Rust…
Re: WxWidgets 3.2
#66wxWidgets are a perfect choice if you want cross-platform native controls. Just a reminder, Qt doesn't use native controls, it just emulates the native look and feel. Besides wxWidgets I know only IUP that uses system native controls (though Cocoa is a work in progress), and IUP deals with just UI, wx is like a Qt, a lot more.
Eclipse's SWT for Java also uses native controls, and IIRC it does so more consistently across platforms than wx. In 2015 I wanted to develop a desktop app in Python, but use SWT, so I did a hacky mongrel setup where I used the pyjnius Python package to load the Avian lightweight JVM into my CPython process so I could use SWT. Avian is dead now, so if I ever have to port that app to ARM64 for Apple Silicon Macs (righ…
I have successfully used the wrapper from C and Zig as a proof of concept. The main goal was to originally expose SWT for Nim, but I got pretty side tracked. I'll probably make a show HN later this year when I have it in a usable state. I haven't gotten callbacks working quite yet, which makes it pretty useless.
I'm a bit worried about performance, but I'll throw a cassowary constraint manager on top of a ton of widgets and see how it does. Memory usage with an empty window is ~35mb at 1920x1080. It successfully works on Windows, Linux, and MacOS x86 and aarch64.
Re: WxWidgets 3.2
#67A truly excellent toolkit. The code is very readable and the developers are quick to communicate/respond on the forum or stackoverflow. I wish more people used it instead of writing "apps" that are just a giant web browser with javascript and a hack to get menus working correctly, with fake UI widgets that don't respond like native window controls (no proper tab navigation, no moveable or resizeable dialogs, keyboard…
I' redoing all the UI on my eCommerce app to be "server driven" across iOS, Android, Web. I get near parity on design on all platforms yet keep full native speed on mobile. The main issue with old widget system is how hard is to theme them, and theming is, I think, a major driver of the use of HTML/CSS (certainly on my business customers, where they demand the UI be colorized with their corporate stuff!). Fix that (l…
Re: WxWidgets 3.2
#68wxWidgets has a sublime idea: an api that is just a wrapper over native controls. For cross platform frameworks it is fast and light. The very opposite of bloatware. But it also has a terrible flaw: its heavy-templated C++ api, hard to port to other languages. I don't want to get stuck on C++. I want to use Go and Rust. And all the wxWidgets ports to those languages suck, big time. Show me a solid wxWidgets for Rust…
wxPython is the only maintained alternative there. I think there’s an opportunity to create bindings to other languages with libClang nowadays. However, it’s gotta be done selectively, since there’s so much surface area in the API to fill in the gaps for C++’s standard library.
Re: WxWidgets 3.2
#69Earlier quoted context omitted.
But it just wraps the native controls...? You're effectively saying that native controls are not for 2022...
A serious question: what are native controls on Windows? Is the Windows XP era where each control is its own HWND (and usually drawn with GDI+)? Is it Windows 7 era where the drawing is Direct2D? Windows 8 where the elements of the app come together with DirectComposition? Or maybe Windows 10 style which is an evolution of UWP (now rebranded WinUI), with drawing in Win2D?
Re: WxWidgets 3.2
#70wxWidgets are a perfect choice if you want cross-platform native controls. Just a reminder, Qt doesn't use native controls, it just emulates the native look and feel. Besides wxWidgets I know only IUP that uses system native controls (though Cocoa is a work in progress), and IUP deals with just UI, wx is like a Qt, a lot more.
Eclipse's SWT for Java also uses native controls, and IIRC it does so more consistently across platforms than wx. In 2015 I wanted to develop a desktop app in Python, but use SWT, so I did a hacky mongrel setup where I used the pyjnius Python package to load the Avian lightweight JVM into my CPython process so I could use SWT. Avian is dead now, so if I ever have to port that app to ARM64 for Apple Silicon Macs (righ…
I do not remember why. Perhaps I thought it will be more portable or performant.
But I quickly abandoned that (would not want to get stuck on a legacy tech like java and awt) and ported all my projects to Pascal for maximal performance.