home.social

#gtk3 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gtk3, aggregated by home.social.

  1. Con GTK2 estaba todo tan bien... luego fue todo cuesta abajo #linux #gtk2 #gtk #gtk3 #ux

  2. Con GTK2 estaba todo tan bien... luego fue todo cuesta abajo #linux #gtk2 #gtk #gtk3 #ux

  3. Oh, look GIMP's Open dialog box has crashed.
    No worries, just close it.
    WHAT DO YOU MEAN, YOU CAN'T CLOSE IT?!?
    THERE ARE NO WINDOW DECORATIONS! IT'S ALL CLIENT-SIDE!!!

    This moment of utterly unnecessary stupidity was brought to you by #ClientSideDecorations.

    #ThanksIHateIt
    #KillItWithFire
    #GTK3
    #CSD #CSDs
    #UIDesign

  4. Oh, look GIMP's Open dialog box has crashed.
    No worries, just close it.
    WHAT DO YOU MEAN, YOU CAN'T CLOSE IT?!?
    THERE ARE NO WINDOW DECORATIONS! IT'S ALL CLIENT-SIDE!!!

    This moment of utterly unnecessary stupidity was brought to you by #ClientSideDecorations.

    #ThanksIHateIt
    #KillItWithFire
    #GTK3
    #CSD #CSDs
    #UIDesign

  5. Oh, look GIMP's Open dialog box has crashed.
    No worries, just close it.
    WHAT DO YOU MEAN, YOU CAN'T CLOSE IT?!?
    THERE ARE NO WINDOW DECORATIONS! IT'S ALL CLIENT-SIDE!!!

    This moment of utterly unnecessary stupidity was brought to you by #ClientSideDecorations.

    #ThanksIHateIt
    #KillItWithFire
    #GTK3
    #CSD #CSDs
    #UIDesign

  6. Oh, look GIMP's Open dialog box has crashed.
    No worries, just close it.
    WHAT DO YOU MEAN, YOU CAN'T CLOSE IT?!?
    THERE ARE NO WINDOW DECORATIONS! IT'S ALL CLIENT-SIDE!!!

    This moment of utterly unnecessary stupidity was brought to you by #ClientSideDecorations.

    #ThanksIHateIt
    #KillItWithFire
    #GTK3
    #CSD #CSDs
    #UIDesign

  7. Oh, look GIMP's Open dialog box has crashed.
    No worries, just close it.
    WHAT DO YOU MEAN, YOU CAN'T CLOSE IT?!?
    THERE ARE NO WINDOW DECORATIONS! IT'S ALL CLIENT-SIDE!!!

    This moment of utterly unnecessary stupidity was brought to you by #ClientSideDecorations.

    #ThanksIHateIt
    #KillItWithFire
    #GTK3
    #CSD #CSDs
    #UIDesign

  8. Playing around with the gtk.css of #gtk3 to have equal borders in #gnome. (not quite done).

  9. Playing around with the gtk.css of #gtk3 to have equal borders in #gnome. (not quite done).

  10. > forking and maintaining Gtk3 as co-working effort between multiple projects

    Do you think it will happen?

    #Mate #xfce #gtk #gtk3
  11. > forking and maintaining Gtk3 as co-working effort between multiple projects

    Do you think it will happen?

    #Mate #xfce #gtk #gtk3
  12. #Schemacs update

    I have been banging my head against #Gtk3 for the past 3 weeks and all progress has pretty much come to a stand-still. No matter how simple and straight-forward my GUI is, Gtk makes it simply impossible to get the layout correct. I am now convinced that programming my own layout algorithm from scratch and using the GtkLayout container (which lets you place widgets at arbitrary X,Y coordinates) is the only way to proceed at this point. It is soooo frustrating.

    The #Gtk documentation is good, but not at all good enough. The people on the Gnome Discourse have been very kind and helpful, and I truly appreciate the engagement I have had there, but ultimately I am still not able to solve my problems.

    I have decided I need find some way to keep making progress without postponing the release of the work I have done so far for an indeterminate length of time. So rather than work out all the bugs in this version before merging it to the main Git branch, what I will do instead is have the main program launch a debugger window. The debugger window will have all layout calculated in advance, and all widgets will be declared once and only once throughout the lifetime of the application to avoid the reference counting issues. Obviously the debugger GUI will be very rigid, but you will at least be able to edit files and run commands in a REPL within this debugger.

    Then maybe I can merge the code I have written to the main Git branch, and people will at least be able to use it through the debugger. Maybe also I could use this debugger to help with writing my layout algorithm. Also, I need to get back to the Emacs Lisp interpreter, I haven’t worked on it in almost two months now.

    #tech #software #Lisp #Emacs #EmacsLisp #Scheme #SchemeLang #R7RS

  13. #Schemacs update

    I have been banging my head against #Gtk3 for the past 3 weeks and all progress has pretty much come to a stand-still. No matter how simple and straight-forward my GUI is, Gtk makes it simply impossible to get the layout correct. I am now convinced that programming my own layout algorithm from scratch and using the GtkLayout container (which lets you place widgets at arbitrary X,Y coordinates) is the only way to proceed at this point. It is soooo frustrating.

    The #Gtk documentation is good, but not at all good enough. The people on the Gnome Discourse have been very kind and helpful, and I truly appreciate the engagement I have had there, but ultimately I am still not able to solve my problems.

    I have decided I need find some way to keep making progress without postponing the release of the work I have done so far for an indeterminate length of time. So rather than work out all the bugs in this version before merging it to the main Git branch, what I will do instead is have the main program launch a debugger window. The debugger window will have all layout calculated in advance, and all widgets will be declared once and only once throughout the lifetime of the application to avoid the reference counting issues. Obviously the debugger GUI will be very rigid, but you will at least be able to edit files and run commands in a REPL within this debugger.

    Then maybe I can merge the code I have written to the main Git branch, and people will at least be able to use it through the debugger. Maybe also I could use this debugger to help with writing my layout algorithm. Also, I need to get back to the Emacs Lisp interpreter, I haven’t worked on it in almost two months now.

    #tech #software #Lisp #Emacs #EmacsLisp #Scheme #SchemeLang #R7RS

  14. #Schemacs update

    I have been banging my head against #Gtk3 for the past 3 weeks and all progress has pretty much come to a stand-still. No matter how simple and straight-forward my GUI is, Gtk makes it simply impossible to get the layout correct. I am now convinced that programming my own layout algorithm from scratch and using the GtkLayout container (which lets you place widgets at arbitrary X,Y coordinates) is the only way to proceed at this point. It is soooo frustrating.

    The #Gtk documentation is good, but not at all good enough. The people on the Gnome Discourse have been very kind and helpful, and I truly appreciate the engagement I have had there, but ultimately I am still not able to solve my problems.

    I have decided I need find some way to keep making progress without postponing the release of the work I have done so far for an indeterminate length of time. So rather than work out all the bugs in this version before merging it to the main Git branch, what I will do instead is have the main program launch a debugger window. The debugger window will have all layout calculated in advance, and all widgets will be declared once and only once throughout the lifetime of the application to avoid the reference counting issues. Obviously the debugger GUI will be very rigid, but you will at least be able to edit files and run commands in a REPL within this debugger.

    Then maybe I can merge the code I have written to the main Git branch, and people will at least be able to use it through the debugger. Maybe also I could use this debugger to help with writing my layout algorithm. Also, I need to get back to the Emacs Lisp interpreter, I haven’t worked on it in almost two months now.

    #tech #software #Lisp #Emacs #EmacsLisp #Scheme #SchemeLang #R7RS

  15. #Schemacs update

    I have been banging my head against #Gtk3 for the past 3 weeks and all progress has pretty much come to a stand-still. No matter how simple and straight-forward my GUI is, Gtk makes it simply impossible to get the layout correct. I am now convinced that programming my own layout algorithm from scratch and using the GtkLayout container (which lets you place widgets at arbitrary X,Y coordinates) is the only way to proceed at this point. It is soooo frustrating.

    The #Gtk documentation is good, but not at all good enough. The people on the Gnome Discourse have been very kind and helpful, and I truly appreciate the engagement I have had there, but ultimately I am still not able to solve my problems.

    I have decided I need find some way to keep making progress without postponing the release of the work I have done so far for an indeterminate length of time. So rather than work out all the bugs in this version before merging it to the main Git branch, what I will do instead is have the main program launch a debugger window. The debugger window will have all layout calculated in advance, and all widgets will be declared once and only once throughout the lifetime of the application to avoid the reference counting issues. Obviously the debugger GUI will be very rigid, but you will at least be able to edit files and run commands in a REPL within this debugger.

    Then maybe I can merge the code I have written to the main Git branch, and people will at least be able to use it through the debugger. Maybe also I could use this debugger to help with writing my layout algorithm. Also, I need to get back to the Emacs Lisp interpreter, I haven’t worked on it in almost two months now.

    #tech #software #Lisp #Emacs #EmacsLisp #Scheme #SchemeLang #R7RS

  16. 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" mauigtk.net/blog/20260125/

  17. One Open-source Project Daily

    Xournal++ is a handwriting notetaking software with PDF annotation support. Written in C++ with GTK3, supporting Linux (e.g. Ubuntu, Debian, Arch, SUSE), macOS and Windows 10. Supports pen input from devices such as Wacom Tablets.

    https://github.com/xournalpp/xournalpp

    #1ospd #opensource #cplusplus #crossplatform #gtk3 #notes #notetaking #pdf #pdfviewer #pen

  18. One Open-source Project Daily

    Xournal++ is a handwriting notetaking software with PDF annotation support. Written in C++ with GTK3, supporting Linux (e.g. Ubuntu, Debian, Arch, SUSE), macOS and Windows 10. Supports pen input from devices such as Wacom Tablets.

    https://github.com/xournalpp/xournalpp

    #1ospd #opensource #cplusplus #crossplatform #gtk3 #notes #notetaking #pdf #pdfviewer #pen

  19. I just opened up chromium, and it is using my system theme, for both color AND the tabs bar???? My firefox has never done that????¿¿?? I'm using cinnamon theme, semabe, and does anyone know how to make my firefox do that, all the old tricks don't seem to work any more. And it is so so beautiful. #firefox #waterfox #chrome #chromium #gtk #gtk3 #cinnamon #linuxmint #linux #ricing

  20. Question about Gtk programming for Linux experts.

    Actually, I already asked the question on the Gtk Discourse app, but I am posting it here on the fediverse in the hope that maybe a few more people will see it. I don’t mind if you answer in Discorse or here on the fediverse.

    #tech #software #Linux #LinuxProgramming #Gtk #Gtk3

    So my goal was to have a read-only GtkTextView widgets in which text can be arranged with layouts like grids, flowbox, vbox, or hbox layouts. Imagine my app to be a textual dashboard where end-users can decide how to place each dashboard widget, following the principles of tiling window managers.

    I did not have much luck achieving this with GtkTextViews, so I tried a different approach of adding GtkLabels to GtkGrid and GtkFlowBox widgets all with the “selectable” property enabled. So far so good. However the default behavior for GtkGrid or GtkFlowBox seems to always highlight all of the text in the first selectable GtkLabel added to whatever container I am using. I would instead like for nothing to be selected until it is explicitly selected by the end-user.

    The attached image shows what the window looks like when it is first made visible and before any user interaction — the upper-left GtkLabel is highlighted. I would like for this to not happen until the end-user drags over the widget with the mouse, but I am not sure how to go about it.

    A different but related question: I would also like if the user drags beyond the boundary of a GtkLabel for the selection to continue to neighboring GtkLabel widgets, sort-of like how it works in a web browser. Is there an easy way to achieve this in Gtk without writing lots of custom drag event handlers for all the the widgets I construct in the UI?

  21. Question about Gtk programming for Linux experts.

    Actually, I already asked the question on the Gtk Discourse app, but I am posting it here on the fediverse in the hope that maybe a few more people will see it. I don’t mind if you answer in Discorse or here on the fediverse.

    #tech #software #Linux #LinuxProgramming #Gtk #Gtk3

    So my goal was to have a read-only GtkTextView widgets in which text can be arranged with layouts like grids, flowbox, vbox, or hbox layouts. Imagine my app to be a textual dashboard where end-users can decide how to place each dashboard widget, following the principles of tiling window managers.

    I did not have much luck achieving this with GtkTextViews, so I tried a different approach of adding GtkLabels to GtkGrid and GtkFlowBox widgets all with the “selectable” property enabled. So far so good. However the default behavior for GtkGrid or GtkFlowBox seems to always highlight all of the text in the first selectable GtkLabel added to whatever container I am using. I would instead like for nothing to be selected until it is explicitly selected by the end-user.

    The attached image shows what the window looks like when it is first made visible and before any user interaction — the upper-left GtkLabel is highlighted. I would like for this to not happen until the end-user drags over the widget with the mouse, but I am not sure how to go about it.

    A different but related question: I would also like if the user drags beyond the boundary of a GtkLabel for the selection to continue to neighboring GtkLabel widgets, sort-of like how it works in a web browser. Is there an easy way to achieve this in Gtk without writing lots of custom drag event handlers for all the the widgets I construct in the UI?

  22. https://thoughts.greyh.at/posts/celestial-gtk-theme/

    @zquestz published an article on Gtk theming which I found fascinating. It is an overview of the kind of things you have to consider when trying to create your own theme for #Linux . He fusses over the little details that are very important when doing UI/UX design properly. He also made sure the themes worked properly on various Gtk desktop environments, including Cinnamon, MATE, and Xfce (three of the best DEs, in my humble opinion).

    He also mentions the qt6gtk2 plugin for Qt which I did not know about. It translates Gtk themes to Qt themes so all of your applications, whether they use Gtk or Qt, have the correct theme. This is extremely useful since the impedance mismatch between Qt and Gtk is the biggest source of UI/UX inconsistencies in Linux apps.

    #tech #software #Linux #UI #UX #theming #LinuxThemes #CinnamonDE #Xfce #MateDE #LinuxMint #Xubuntu #UbuntuMATE #ArchLinux #Gtk #Gtk2 #Gtk3 #Qt5 #Qt6 #UnixPorn #ricing

  23. https://thoughts.greyh.at/posts/celestial-gtk-theme/

    @zquestz published an article on Gtk theming which I found fascinating. It is an overview of the kind of things you have to consider when trying to create your own theme for #Linux . He fusses over the little details that are very important when doing UI/UX design properly. He also made sure the themes worked properly on various Gtk desktop environments, including Cinnamon, MATE, and Xfce (three of the best DEs, in my humble opinion).

    He also mentions the qt6gtk2 plugin for Qt which I did not know about. It translates Gtk themes to Qt themes so all of your applications, whether they use Gtk or Qt, have the correct theme. This is extremely useful since the impedance mismatch between Qt and Gtk is the biggest source of UI/UX inconsistencies in Linux apps.

    #tech #software #Linux #UI #UX #theming #LinuxThemes #CinnamonDE #Xfce #MateDE #LinuxMint #Xubuntu #UbuntuMATE #ArchLinux #Gtk #Gtk2 #Gtk3 #Qt5 #Qt6 #UnixPorn #ricing

  24. https://thoughts.greyh.at/posts/celestial-gtk-theme/

    @zquestz published an article on Gtk theming which I found fascinating. It is an overview of the kind of things you have to consider when trying to create your own theme for #Linux . He fusses over the little details that are very important when doing UI/UX design properly. He also made sure the themes worked properly on various Gtk desktop environments, including Cinnamon, MATE, and Xfce (three of the best DEs, in my humble opinion).

    He also mentions the qt6gtk2 plugin for Qt which I did not know about. It translates Gtk themes to Qt themes so all of your applications, whether they use Gtk or Qt, have the correct theme. This is extremely useful since the impedance mismatch between Qt and Gtk is the biggest source of UI/UX inconsistencies in Linux apps.

    #tech #software #Linux #UI #UX #theming #LinuxThemes #CinnamonDE #Xfce #MateDE #LinuxMint #Xubuntu #UbuntuMATE #ArchLinux #Gtk #Gtk2 #Gtk3 #Qt5 #Qt6 #UnixPorn #ricing

  25. https://thoughts.greyh.at/posts/celestial-gtk-theme/

    @zquestz published an article on Gtk theming which I found fascinating. It is an overview of the kind of things you have to consider when trying to create your own theme for #Linux . He fusses over the little details that are very important when doing UI/UX design properly. He also made sure the themes worked properly on various Gtk desktop environments, including Cinnamon, MATE, and Xfce (three of the best DEs, in my humble opinion).

    He also mentions the qt6gtk2 plugin for Qt which I did not know about. It translates Gtk themes to Qt themes so all of your applications, whether they use Gtk or Qt, have the correct theme. This is extremely useful since the impedance mismatch between Qt and Gtk is the biggest source of UI/UX inconsistencies in Linux apps.

    #tech #software #Linux #UI #UX #theming #LinuxThemes #CinnamonDE #Xfce #MateDE #LinuxMint #Xubuntu #UbuntuMATE #ArchLinux #Gtk #Gtk2 #Gtk3 #Qt5 #Qt6 #UnixPorn #ricing

  26. Glad to announce the October 2025 FontForge release.

    Some interesting stuff:
    * Show CNC fonts in Font View
    * Harfbuzz integration
    * GTK3 support kick-off

    #FontForge #typography #FOSS #GTK #GTK3

  27. Glad to announce the October 2025 FontForge release.

    Some interesting stuff:
    * Show CNC fonts in Font View
    * Harfbuzz integration
    * GTK3 support kick-off

    github.com/fontforge/fontforge

    #FontForge #typography #FOSS #GTK #GTK3

  28. I'm happy to share that Phantom Player is now also running on FreeBSD !

    I have not yet created an standard package, but installation sh scripts are now available.

    phantom-player.rsm92.fr

    #FreeBSD #VLC #VideoPlayer #GTK3

  29. Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.

    Covered topics:
    1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
    2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
    3) #Xrandr for multimonitor configuration
    4) #Xserver settings for #HighDPI
    5) #XDG utils and #Emacs as a system file manager
    6) #XDM login window

    eugene-andrienko.com/en/it/202

    #FreeBSD

  30. Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.

    Covered topics:
    1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
    2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
    3) #Xrandr for multimonitor configuration
    4) #Xserver settings for #HighDPI
    5) #XDG utils and #Emacs as a system file manager
    6) #XDM login window

    eugene-andrienko.com/en/it/202

    #FreeBSD

  31. Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.

    Covered topics:
    1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
    2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
    3) #Xrandr for multimonitor configuration
    4) #Xserver settings for #HighDPI
    5) #XDG utils and #Emacs as a system file manager
    6) #XDM login window

    eugene-andrienko.com/en/it/202

    #FreeBSD

  32. Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.

    Covered topics:
    1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
    2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
    3) #Xrandr for multimonitor configuration
    4) #Xserver settings for #HighDPI
    5) #XDG utils and #Emacs as a system file manager
    6) #XDM login window

    eugene-andrienko.com/en/it/202

    #FreeBSD

  33. Wrote a blogpost about simple (I mean with a shell and a text editor) configuration.

    Covered topics:
    1) configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
    2) Theming: , installing cursor(s), fonts and icons.
    3) for multimonitor configuration
    4) settings for
    5) utils and as a system file manager
    6) login window

    eugene-andrienko.com/en/it/202