#wxwidgets — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #wxwidgets, aggregated by home.social.
-
Flamerobin 0.9.15 is released
-
Flamerobin 0.9.15 is released
-
Flamerobin 0.9.15 is released
-
Flamerobin 0.9.15 is released
-
Flamerobin 0.9.15 is released
-
Curious
The left version is running in an opensuse distrobox, handles emojis properly, runs in X and doesn't respect the system theme.
The right version is running in a ubuntu distrobox, mangles the emoji, runs in wayland and respects dark mode.
Maybe they are using different frontends? #wxWidgets seems to support GTK3 and QT.
Can I find out somehow? I know the ubuntu package uses GTK, but the OpenSuse one won't tell me.
They look very similar.
-
Curious
The left version is running in an opensuse distrobox, handles emojis properly, runs in X and doesn't respect the system theme.
The right version is running in a ubuntu distrobox, mangles the emoji, runs in wayland and respects dark mode.
Maybe they are using different frontends? #wxWidgets seems to support GTK3 and QT.
Can I find out somehow? I know the ubuntu package uses GTK, but the OpenSuse one won't tell me.
They look very similar.
-
Curious
The left version is running in an opensuse distrobox, handles emojis properly, runs in X and doesn't respect the system theme.
The right version is running in a ubuntu distrobox, mangles the emoji, runs in wayland and respects dark mode.
Maybe they are using different frontends? #wxWidgets seems to support GTK3 and QT.
Can I find out somehow? I know the ubuntu package uses GTK, but the OpenSuse one won't tell me.
They look very similar.
-
Curious
The left version is running in an opensuse distrobox, handles emojis properly, runs in X and doesn't respect the system theme.
The right version is running in a ubuntu distrobox, mangles the emoji, runs in wayland and respects dark mode.
Maybe they are using different frontends? #wxWidgets seems to support GTK3 and QT.
Can I find out somehow? I know the ubuntu package uses GTK, but the OpenSuse one won't tell me.
They look very similar.
-
Curious
The left version is running in an opensuse distrobox, handles emojis properly, runs in X and doesn't respect the system theme.
The right version is running in a ubuntu distrobox, mangles the emoji, runs in wayland and respects dark mode.
Maybe they are using different frontends? #wxWidgets seems to support GTK3 and QT.
Can I find out somehow? I know the ubuntu package uses GTK, but the OpenSuse one won't tell me.
They look very similar.
-
I found a new thing to test in my ui-comparison project that I hadn't thought of until now: Grapheme clusters.
I implemented the tests for #wxWidgets today and noticed that I can move the text cursor in-between the codepoints of a multi-codepoint emoji.
E.g. If I enter "👮🏽♀️", I can use the cursor keys and space to pull it apart into "👮 🏽 ♀️"
That seems to be a limitation of the Win32 edit. Sure enough, if I try it on my win32 implementation, the same happens.
QT and SwiftUI seem to work though.
-
I found a new thing to test in my ui-comparison project that I hadn't thought of until now: Grapheme clusters.
I implemented the tests for #wxWidgets today and noticed that I can move the text cursor in-between the codepoints of a multi-codepoint emoji.
E.g. If I enter "👮🏽♀️", I can use the cursor keys and space to pull it apart into "👮 🏽 ♀️"
That seems to be a limitation of the Win32 edit. Sure enough, if I try it on my win32 implementation, the same happens.
QT and SwiftUI seem to work though.
-
I found a new thing to test in my ui-comparison project that I hadn't thought of until now: Grapheme clusters.
I implemented the tests for #wxWidgets today and noticed that I can move the text cursor in-between the codepoints of a multi-codepoint emoji.
E.g. If I enter "👮🏽♀️", I can use the cursor keys and space to pull it apart into "👮 🏽 ♀️"
That seems to be a limitation of the Win32 edit. Sure enough, if I try it on my win32 implementation, the same happens.
QT and SwiftUI seem to work though.
-
I found a new thing to test in my ui-comparison project that I hadn't thought of until now: Grapheme clusters.
I implemented the tests for #wxWidgets today and noticed that I can move the text cursor in-between the codepoints of a multi-codepoint emoji.
E.g. If I enter "👮🏽♀️", I can use the cursor keys and space to pull it apart into "👮 🏽 ♀️"
That seems to be a limitation of the Win32 edit. Sure enough, if I try it on my win32 implementation, the same happens.
QT and SwiftUI seem to work though.
-
I found a new thing to test in my ui-comparison project that I hadn't thought of until now: Grapheme clusters.
I implemented the tests for #wxWidgets today and noticed that I can move the text cursor in-between the codepoints of a multi-codepoint emoji.
E.g. If I enter "👮🏽♀️", I can use the cursor keys and space to pull it apart into "👮 🏽 ♀️"
That seems to be a limitation of the Win32 edit. Sure enough, if I try it on my win32 implementation, the same happens.
QT and SwiftUI seem to work though.
-
I created a Proof-of-Concept for a Desktop Wherigo application. More in my blog: https://blog.mars3142.dev/2026/02/14/wxwherigo/
#wherigo #geocaching #wxwidgets #blog -
I created a Proof-of-Concept for a Desktop Wherigo application. More in my blog: https://blog.mars3142.dev/2026/02/14/wxwherigo/
#wherigo #geocaching #wxwidgets #blog -
I created a Proof-of-Concept for a Desktop Wherigo application. More in my blog: https://blog.mars3142.dev/2026/02/14/wxwherigo/
#wherigo #geocaching #wxwidgets #blog -
I created a Proof-of-Concept for a Desktop Wherigo application. More in my blog: https://blog.mars3142.dev/2026/02/14/wxwherigo/
#wherigo #geocaching #wxwidgets #blog -
New blog post "Why We Need the Gtk Platform for MAUI -- A short wrap-up of our goal and motivation along with a historical overview of events that lead to MauiGtk" https://mauigtk.net/blog/20260125/
#dotnet #dotnetmaui #gtk #gtk3 #qt #wxwidgets #eto #crossplatform #mauigtk #mauilinux #net_maui
-
Unfortunately, Tenacity's Flatpak remains on runtime version 24.08. We're looking to update it along with PortMidi inside the Flatpak so we're all up-to-date (mostly) on updates.
The other concern is wxWidgets, but we're holding off updating that because 1.3.4 can't build against wxWidgets 3.3+. The upcoming 1.3.5 release will, and it should also allow us to improve our default Flatpak permissions because #wxWidgets 3.3 got updated to use portals automatically via GTK!
-
Unfortunately, Tenacity's Flatpak remains on runtime version 24.08. We're looking to update it along with PortMidi inside the Flatpak so we're all up-to-date (mostly) on updates.
The other concern is wxWidgets, but we're holding off updating that because 1.3.4 can't build against wxWidgets 3.3+. The upcoming 1.3.5 release will, and it should also allow us to improve our default Flatpak permissions because #wxWidgets 3.3 got updated to use portals automatically via GTK!
-
Unfortunately, Tenacity's Flatpak remains on runtime version 24.08. We're looking to update it along with PortMidi inside the Flatpak so we're all up-to-date (mostly) on updates.
The other concern is wxWidgets, but we're holding off updating that because 1.3.4 can't build against wxWidgets 3.3+. The upcoming 1.3.5 release will, and it should also allow us to improve our default Flatpak permissions because #wxWidgets 3.3 got updated to use portals automatically via GTK!
-
Unfortunately, Tenacity's Flatpak remains on runtime version 24.08. We're looking to update it along with PortMidi inside the Flatpak so we're all up-to-date (mostly) on updates.
The other concern is wxWidgets, but we're holding off updating that because 1.3.4 can't build against wxWidgets 3.3+. The upcoming 1.3.5 release will, and it should also allow us to improve our default Flatpak permissions because #wxWidgets 3.3 got updated to use portals automatically via GTK!
-
Unfortunately, Tenacity's Flatpak remains on runtime version 24.08. We're looking to update it along with PortMidi inside the Flatpak so we're all up-to-date (mostly) on updates.
The other concern is wxWidgets, but we're holding off updating that because 1.3.4 can't build against wxWidgets 3.3+. The upcoming 1.3.5 release will, and it should also allow us to improve our default Flatpak permissions because #wxWidgets 3.3 got updated to use portals automatically via GTK!
-
@k That's great news to hear! We're also hoping to improve the experience in the Flatpak too, starting with #wxWidgets. For now, we'll have to see what we can do! 😄
-
@k That's great news to hear! We're also hoping to improve the experience in the Flatpak too, starting with #wxWidgets. For now, we'll have to see what we can do! 😄
-
@k That's great news to hear! We're also hoping to improve the experience in the Flatpak too, starting with #wxWidgets. For now, we'll have to see what we can do! 😄
-
@k That's great news to hear! We're also hoping to improve the experience in the Flatpak too, starting with #wxWidgets. For now, we'll have to see what we can do! 😄
-
@k That's great news to hear! We're also hoping to improve the experience in the Flatpak too, starting with #wxWidgets. For now, we'll have to see what we can do! 😄
-
Wait, #wxWidgets has a new dark mode on Windows now...
👀
-
Wait, #wxWidgets has a new dark mode on Windows now...
👀
-
Wait, #wxWidgets has a new dark mode on Windows now...
👀
-
Wait, #wxWidgets has a new dark mode on Windows now...
👀
-
Wait, #wxWidgets has a new dark mode on Windows now...
👀
-
Random #fact: some features in #Tenacity depend on the libraries we use, including #wxWidgets. If you want to see Tenacity get better and want to contribute, we suggest you look into our supporting libraries such as wxWidgets and #PortAudio.
-
Random #fact: some features in #Tenacity depend on the libraries we use, including #wxWidgets. If you want to see Tenacity get better and want to contribute, we suggest you look into our supporting libraries such as wxWidgets and #PortAudio.
-
Random #fact: some features in #Tenacity depend on the libraries we use, including #wxWidgets. If you want to see Tenacity get better and want to contribute, we suggest you look into our supporting libraries such as wxWidgets and #PortAudio.
-
Random #fact: some features in #Tenacity depend on the libraries we use, including #wxWidgets. If you want to see Tenacity get better and want to contribute, we suggest you look into our supporting libraries such as wxWidgets and #PortAudio.
-
Random #fact: some features in #Tenacity depend on the libraries we use, including #wxWidgets. If you want to see Tenacity get better and want to contribute, we suggest you look into our supporting libraries such as wxWidgets and #PortAudio.
-
@alavi I don't know any platform where GUI is light and easy. #Rust people have good experience with #iced - choice for Cosmic Desktop.
Last time I did any GUI it was #Qt and #wxWidgets - both in #C++, but it doesn't mean I recommend that path in 2025.
#Clojure is a JVM language, hence violates your requirement on RAM/resources. IMVHO S-expression languages aren't good for GUI programming.
-
@alavi I don't know any platform where GUI is light and easy. #Rust people have good experience with #iced - choice for Cosmic Desktop.
Last time I did any GUI it was #Qt and #wxWidgets - both in #C++, but it doesn't mean I recommend that path in 2025.
#Clojure is a JVM language, hence violates your requirement on RAM/resources. IMVHO S-expression languages aren't good for GUI programming.
-
@alavi I don't know any platform where GUI is light and easy. #Rust people have good experience with #iced - choice for Cosmic Desktop.
Last time I did any GUI it was #Qt and #wxWidgets - both in #C++, but it doesn't mean I recommend that path in 2025.
#Clojure is a JVM language, hence violates your requirement on RAM/resources. IMVHO S-expression languages aren't good for GUI programming.
-
@alavi I don't know any platform where GUI is light and easy. #Rust people have good experience with #iced - choice for Cosmic Desktop.
Last time I did any GUI it was #Qt and #wxWidgets - both in #C++, but it doesn't mean I recommend that path in 2025.
#Clojure is a JVM language, hence violates your requirement on RAM/resources. IMVHO S-expression languages aren't good for GUI programming.
-
@alavi I don't know any platform where GUI is light and easy. #Rust people have good experience with #iced - choice for Cosmic Desktop.
Last time I did any GUI it was #Qt and #wxWidgets - both in #C++, but it doesn't mean I recommend that path in 2025.
#Clojure is a JVM language, hence violates your requirement on RAM/resources. IMVHO S-expression languages aren't good for GUI programming.
-
Today's #random #idea: #wxWidgets with a native #Haiku port.
-
Today's #random #idea: #wxWidgets with a native #Haiku port.
-
Today's #random #idea: #wxWidgets with a native #Haiku port.
-
Today's #random #idea: #wxWidgets with a native #Haiku port.
-
Today's #random #idea: #wxWidgets with a native #Haiku port.