Gajim - 2024-10-27


  1. cal0pteryx

    meson, any news on the voice message visualization? :) I came accross some sections where I needed to modify code there (already pushed), and I'd like to integrate your changes

  2. cal0pteryx

    it does not have to be perfect

  3. meson

    cal0pteryx: I push in 1h, am busy rigjt now

  4. cal0pteryx

    ah thanks, great :)

  5. snugglybun

    how do i block people on gajim?

  6. snugglybun

    i saw that it supports XEP-191

  7. snugglybun

    but i don't see anything about it

  8. snugglybun

    but i don't see anything about it on the GUI

  9. snugglybun

    for clarification my gajim install is the spanish one

  10. snugglybun

    oh wait nvm i'm dumb

  11. meson

    cal0pteryx, done

  12. aereaux

    I'm unfamiliar with the cache code here: https://dev.gajim.org/gajim/gajim/-/merge_requests/960/diffs . If I pull and build this branch, will it change my gajim data such that I won't be able to revert?

  13. cal0pteryx

    aereaux: cache will be rebuilt, so no problem

    đź‘Ť 1
  14. meson

    cal0pteryx: I've encountered a bug when seeking, but I will fix this later, if that's okay

  15. cal0pteryx

    meson, absolutely! thanks a lot

  16. meson

    and there's still the segfault race condition bug somewhere in gtk4 when seeking due to the rendering: I will try to write minimal reproducing code, when I find the time, and report it upstream

  17. meson

    and there's still the segfault race condition bug somewhere in gtk4 when updating the graph while seeking: I will try to write minimal reproducing code, when I find the time, and report it upstream

  18. meson

    I hope this one gets more attention than the pango issue ...

  19. Link Mauve

    Is that pango issue still present in gtk4?

  20. lovetox

    Pango has nothing to do with gtk or?

  21. meson

    Both are developed by gnome?

  22. meson

    lovetox, I can no longer reproduce the crash fwiw with the code posted @ https://gitlab.gnome.org/GNOME/pango/-/issues/798

  23. meson

    seems to be fixed?

  24. meson

    seems to be fixed? :)

  25. Link Mauve

    The two main GTK devs have hardly anything to do with GNOME fwiw.

  26. Link Mauve

    They are both employed by Red Hat.

  27. meson

    I see, didn't know.

  28. meson

    cal0pteryx, I see I should have labeled the commit `refactor` and not `cfix`. :>

  29. cal0pteryx

    meson, that's fine, since there will be rebases anyway

    đź‘Ť 1
  30. Link Mauve

    Btw I usually idle at xmpp:%23gtk%25irc.libera.chat@irc.jabberfr.org?join to know what they are working on at the moment.

  31. meson

    Link Mauve, `calcium.libera.chat: #gtk: Cannot join channel (+r) - you need to be logged into your NickServ account`

  32. Link Mauve

    Yes, you have to register an account and login for that.

  33. meson

    cal0pteryx, we've asked the gtk devs about CSS colors for custom GTK4 widgets because of the snapshot routine: Gtk widgets are designed to only have a single color. If one wants to use more, one has to use _libadwaita_ or to _poke at the relevant settings manually_. That means changing the state flags is indeed a bit hacky. We should think about changing that at some point I'd say.

  34. cal0pteryx

    meson, yes, changing state flags is indeed hacky. we did that for the emoji shortcode completion as well, but now it's redesigned. a thing to consider for after the port ;)

  35. cal0pteryx

    for the port we're not using `adw` yet, but I'd really like to move to that after the port

  36. meson

    there's a quiet nice pro/con for adw by one of the xournalpp main devs: https://github.com/xournalpp/xournalpp/discussions/5301#discussioncomment-7412697

  37. meson

    because I already see complains incoming - reasoned or not :D

  38. cal0pteryx

    sure there will be :) change always comes with complaints

  39. lovetox

    libadwaita ship some custom theme?

  40. lovetox

    libadwaita ships some custom theme?

  41. Link Mauve

    lovetox, yes, its widgets are different from a pure GTK application as well.

  42. lovetox

    in what way? A custom widget is by definition different than in GTK otherwise it would not be a custom widget

  43. Link Mauve

    Indeed.

  44. Link Mauve

    But yeah, it also uses different CSS I think.

  45. lovetox

    i have no problem with things looking in a certain way, i think users should not care how things look as long as it does the job

  46. lovetox

    but GTK is already not a very good cross platform framework

  47. lovetox

    i fear using a lib that is defined as "only for gnome apps"

  48. Link Mauve

    They’re trying to improve that currently.

  49. lovetox

    the devs have even less motivation to fix anything regarding other systems

  50. cal0pteryx

    well, Gajim (or GTK apps in general) already look alien on Windows for example

  51. lovetox

    but the question would be, can there really be problems in libadwaita that only affects Windows

  52. lovetox

    or would this anyway a GTK problem

  53. lovetox

    im also dont understand can you mix adw and normal gtk stuff?

  54. Link Mauve

    Yes you can.

  55. Link Mauve

    Even libadaita also uses normal gtk widgets in its widgets.

  56. Link Mauve

    Even libadwaita also uses normal gtk widgets in its widgets.

  57. meson

    > They’re trying to improve that currently. Do you have some sources for that?

  58. Link Mauve

    meson, ah, I was replying to “20:31:53 lovetox> but GTK is already not a very good cross platform framework”.

  59. Link Mauve

    I don’t know enough about libadwaita, and I don’t follow their development.