home.social

#gnomecalendar — Public Fediverse posts

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

fetched live
  1. Hi, for those relying on a screen reader, we would like to have your feedback on what we could do to make GNOME Calendar friendly for you. If you would like to share some feedback on anything regarding the screen reader experience with GNOME Calendar, please consider reading and commenting on the following issue on GitLab: gitlab.gnome.org/GNOME/gnome-c

    Or this thread on Discourse: discourse.gnome.org/t/figure-o

    (Boost appreciated)

    #RFC #GNOME #GNOMECalendar #GTK #GTK4 #accessibility #a11y #boost4reach #Blind #AccessibilityInFreeSoftware

  2. RE: ouo.sh/@nate/117179073824551892

    When I said I'd like to bring some skeuomorphism back to GNOME Calendar, I did not imagine something as intense as this 😳

    #GNOME #GNOMECalendar #skeuomorphism

  3. One of the fixes merged in GNOME Calendar tonight is @tytan652's nice solution for those elusive "405: Method Not Allowed" errors when subscribing to some online calendars that had non-spec-compliant line breaks. It was one of my last known webcal parsing bugs: gitlab.gnome.org/GNOME/gnome-c

    Those of you with janky calendar servers can rejoice (but you should still contact the devs of those server apps to ask them to adhere to the specs 🤨)

    #GNOMECalendar #GNOME #ical #webcal #CalDAV #calendaring

  4. Tune in to youtube.com/live/nBL7dkdDEmg at 21h UTC this Friday night (in ~20 minutes) to see Georges livestreaming his GNOME Calendar coding & merge requests review session :blobcatcoffee:

    #GNOMECalendar #programming #GNOME #FLOSS #OpenSource #Linux #LoFi #GTK

  5. GNOME Calendar received a nice keyboard navigation upgrade after some small patches were merged yesterday: in the month view, when a cell is in focus, pressing Shift+Tab will now focus the event widget right in front of it 🥹

    #GNOMECalendar #GNOME #GTK4 #GTK #libadwaita #Accessibility #a11y #OpenSource #FreeSoftware #FOSS #OSS #Linux #AccessibilityInFreeSoftware

  6. PSA to #infosec researchers reporting issues on desktop software: y'all, a simple CPU-hogging performance issue where we're showing too many widgets (instead of a summary when importing a large file) is not a "Denial of Service", come on :blobmiou:

    Sometimes, a cigar is just a cigar.

    gitlab.gnome.org/GNOME/gnome-c

    #MaintainerLife #QA #GNOMECalendar #Sysprof #performance #GNOME #security #Linux #OpenSource

  7. This GNOME Calendar bug report is proof that there is no Swedish Conspiracy in #GNOME, and that Schrödinger's cat is alive and well: gitlab.gnome.org/GNOME/gnome-c

    I've been experiencing it seemingly randomly for two months, and finally sat down today for a couple of hours to narrow down the cause. I'm glad I caught it on time before version 51.0's official release :blobsweats:

    #GNOMECalendar #SwedishConspiracy #heisenbug #QA

  8. Why can't I sync from a local ics in Gnome calendar? It'll on take an ics file if it's on Https, Webdav or Caldav: but not a local file.

    I know. It's a rhetorical question, so you don't have to answer it. I just have to install Evolution and I'll be able to set it up.

    But it's the whole of Evolution, which I will never use ...

    /me mutters on, "the whole of blinkin' Evolution, arg"

    #gnome #emacs #gnomecalendar

  9. @dee
    “One Calendar to rule all recurrences,
    One Calendar to find free/busy slots,
    One Calendar to invite them all,
    and in the .ics bind them
    in the Wayland of GNOME where the Dropshadows lie.”

    Some day, #GNOMECalendar will be the One Calendar on #Linux :blobpeek:

  10. Screen reader users using a free and open-source calendar app on Linux, what do you use? I'd like to use one as a reference to make GNOME Calendar more screen reader friendly.

    (Boost appreciated)

    #a11y #accessibility #accessible #GNOME #GNOMECalendar #Linux

  11. GNOME Calendar 51 will be able to recognize Microsoft Teams meetings links in events, surfacing them with a convenient "Join" button (instead of gibberish) like other videoconferencing systems known to us: gitlab.gnome.org/GNOME/gnome-c

    Daily-drive the nightly flatpak like all the cool kids and you'll be able to immediately hop onto calls to circle back and synergize with your clients or colleagues who use this… thing :blobmiou:

    #GNOMECalendar #GNOME #productivity #meetings #Teams #MicrosoftTeams

  12. All of this brings me to GNOME Calendar and @linuxmint. For years, we've been dealing with users reporting issues about Linux Mint's package of GNOME Calendar to us, that were either never present or addressed releases ago.

    Just a couple of examples:

    There were a couple of discussions regarding this in the past, in chat, but none of it ended up being productive. Eventually, we got fed up by it and I opened issue #1 on Mint's package of GNOME Calendar — the first issue ever in their package's repository — asking them to remove all links pointing to upstream GNOME Calendar and rebranding the app. This had no response for 6 months, all the while we were still getting bug reports about Mint's broken package. @nekohayo eventually got fed up (again!) and pinged the packager. The packager replied with something completely unrelated and asked which modifications we did not like, completely ignoring our actual request. So, I just told him bluntly that we don't have the time to look through the code just to pinpoint specific issues, so I'll just loosely say "everything", and the only way for us to be happy is if they could rebrand and we can move on.

    Then, the packager responds with something unrelated once again, ignoring the essence of my comment, and follows with a whataboutism — "As i said, 46 and 48 are used by millions of people right now in Ubuntu LTS and Debian Stable. Are you going to request Debian and Ubuntu stop shipping GNOME apps?" — in other words, "what about Ubuntu LTS and Debian Stable?" — as a bonus, twisting my words and going from GNOME Calendar to "GNOME apps".

    So, once again, I reminded that this is not what the issue is about.

    As a side note: no, never would we go after Debian or Ubuntu over this. If the distribution in question is doing its job properly by simply not bothering the people writing the software that they package, then why should we go after them? They are not the ones misleading users into opening in the wrong place, so there is no reason for us to be upset about. In this case, Linux Mint is leeching off of Debian, and pushing their responsibility onto us.

    The packager then explains what to do, and redirects us to Debian to take down the package, essentially roping Debian into Linux Mint's problem — all the while completely ignoring the premise of this post. Sure, both Linux Mint and Debian's packages share the same source; however, this is just a technical detail. The actual problem, one that regularly affects us, is that Linux Mint users report issues to us, whereas Debian users report them to Debian.

    So, I remind him bluntly that this is not our responsibility as an upstream to fix his problems.

    He then suggests to incorporate code upstream to check if the user is running an outdated version or not. In other words, either phoning home, somehow keeping track of releases every 6 months, or something unrealistic.

    I lose my patience and hostily tell him that we upstreams don't care about how distributions operate, and reminded, once again, that all we want is for them to rebrand. To which he replied with "If you don't care, then neither do we." — confirming that Linux Mint doesn't care about Debian or even itself as a distribution. Then says "probably requires GNOME Calendar to move away from free licenses" and locks the issue — once again, completely ignoring the essence of this entire issue.

    Now they know what the problem is, and have refused to act on it by shoving their responsibilities onto us, but this time intentionally, because that should show upstream for hurting my feelings, never mind the fact that we are the ones doing the hard work, and they are making us do more work. This is the length some distributors will go to abuse people's generosity.

    #MaintainerLife #Linux #GNOME #GNOMECalendar #FOSS #OpenSource #FreeSoftware

  13. #TechIsShitDispatch
    I receive via email an invitation to an event. I attempt to accept the invitation and import it into my #Google calendar in #Thunderbird. I get two error pop-ups, one on top of the other:
    #Mozilla #GNOME #GNOMECalendar #Bugzilla #GoogleCalendar (1/5)

  14. PSA to GNOME Calendar contributors: we just merged a pair of refactoring branches that rearchitect tons of code to eliminate a whole class of problems in the backend and the views: gitlab.gnome.org/GNOME/gnome-c

    This unfortunately means many contributors with pending merge requests will have to manually rebase and deconflict their code on top of the latest main branch. It may feel like reloading a Patlabor's revolver, but should be worth it.

    #GNOME #GNOMECalendar #OpenSource #MaintainerLife #Patlabor

  15. Making the most out of GitLab's "Work Items" SNAFU that doesn't let you easily filter between Open and Closed issues without doing search filters manually, in #GNOMECalendar I have created three shared custom search filtering views for your convenience:

    * Newcomer items: gitlab.gnome.org/GNOME/gnome-c
    * All open bugs: gitlab.gnome.org/GNOME/gnome-c
    * Requests by designers: gitlab.gnome.org/GNOME/gnome-c

    If you are logged in, you can "add" those to the top of the "work items" list UI.

    #GitLab #UX #usability #GNOME

  16. @parrot_33
    Point du tout… j'utilise l'application presque exclusivement au clavier quotidiennement, et ça marche, incluant passer d'un champ à l'autre au clavier avec Tab (ou même d'un événement à l'autre avec les touches directionnelles, dans la dernière version), tel que démontré dans la vidéo ci-jointe.

    #GNOMECalendar met énormément d'efforts pour rendre l'application accessible autant que possible, majoritairement grâce aux contributions de code de @TheEvilSkeleton

    @sebsauvage @Natouille

  17. @auinobackonlinux @zoeyTheWitch
    The "export" feature has been gracefully implemented by @FineFindus in #GNOMECalendar versions 49 and 50.

    As for the "file attachments" idea, this is gitlab.gnome.org/GNOME/gnome-c, which sounds a bit like a synchronization + UI + security nightmare to me.

  18. Also, why isn’t it possible to share an event or attach files to it? #GnomeCalendar

  19. PSA: following the example from various other projects within GNOME (such as Loupe and libadwaita), GNOME Calendar now explicitly forbids AI-generated contributions, with the same policy: gitlab.gnome.org/GNOME/gnome-c

    We honor the exquisite art of organic homegrown code made with care and a willingness to learn the craft, and want to protect the time of people who help review merge requests.

    #MaintainerLife #FreeSoftware #FLOSS #OpenSource #GNOMECalendar #NoAI #aislop #genAI #LLM #GNOME #libadwaita

  20. Finally realized what has been bugging me for years with the GNOME "Document Scanner" (Simple Scan) app's cropping feature: it doesn't set the mouse cursors to indicate where and how you can interact to adjust the cropping rectangle.

    I filed this issue with some hints, so that any newcomer can contribute a fix for it: gitlab.gnome.org/GNOME/simple-

    (BTW, there's a similar papercut in GNOME Calendar: gitlab.gnome.org/GNOME/gnome-c)

    #UX #usability #GNOME #SimpleScan #SANE #scanning #paperwork #GNOMECalendar

  21. Everyone, rejoice 🙌

    Georges livestreamed himself reviewing and merging accessibility contributions in GNOME Calendar again, specifically the entirety of merge request !564, which introduces keyboard-navigable month cells. This means, as of GNOME 50, GNOME Calendar's month view will be fully navigable with a keyboard for the first time in its history! The only high-level goal that needs work now is conveying these information with assistive technologies properly.

    Do note that the screen recording attached won't have any alt text, to avoid redundancy. Everything written below is a detailed explanation of the experience, and the recording is essentially a visual demonstration:

    - When tabbing between events, focus moves chronologically. This means that focus continues to move down until there are no event widgets overlaying the current cell. Then, focus moves to the topmost event widget in the next cell or row. Tabbing backwards with Shift+Tab moves in the opposite direction.
    - On the last event widget, pressing Tab moves the focus to the adjacent month cell. Conversely, pressing Ctrl+Tab on any event widget has the same effect.
    - Pressing an activation button (such as Enter or Space) displays the popover for creating an event. Additionally, pressing and holding the Shift key while pressing the arrow keys selects every cell between the start and end positions until the Shift key is released, which displays the popover with the selected range.

    Both merge requests !564 and !598 took us almost an entire year to explore various approaches and finally settle on the best one for our use case. Everything was done voluntarily, relying solely on support from donors and those who share these posts, without any financial backing from other entities. In contrast, most, if not all, calendar apps backed by trillion-dollar companies still don't offer proper keyboard navigation across their views. In many cases, they haven't even reached feature parity. If it is not too much trouble, please consider funding my accessibility work on GNOME. Thank you! ♥️

    #GNOMECalendar #GNOME #Accessibility #a11y #Calendar #GTK #libadwaita #OpenSource #FreeSoftware #FOSS #OSS #Linux

  22. An update on GNOME Calendar: Georges livestreamed himself reviewing and merging parts of merge request !598, making the month view easier than ever to navigate with a keyboard!

    This merge request introduces a coordinate-aware navigation system in the month view, which computes the coordinates of relevant event widgets and finds the nearest widget relative to the one in focus when using arrow keys. When tabbing, focus moves chronologically, meaning focus continues to move down until there are no event widgets overlaying that specific cell, which then moves focus to the topmost event widget found in the next cells or rows; tabbing backwards goes in the opposite direction.

    To illustrate the sheer complexity of navigation in a calendaring app, here is Georges's live reaction:

    "Wow, congratulations, this is looking INSANE, Hari... The hell is going on here"

    — Georges, maintainer of GNOME Calendar - youtu.be/smofXzVwNwQ?t=1h24m6s

    #GNOMECalendar #GNOME #GTK4 #libadwaita #accessibility #a11y #FOSS #OpenSource #Linux

  23. An example of a 10-years-old feature request in GNOME Calendar that has been superseded by the combination of 5 other UX improvements, to the point where I am comfortable putting the original ticket to rest until a new technological development comes up: gitlab.gnome.org/GNOME/gnome-c

    Same with this 2.5-years-old feature request of mine (which has now been superseded by two of those UX enhancements): gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar #MaintainerLife #GNOME #UX #QA #productivity

  24. Huge thanks to @maximiliano and @TheEvilSkeleton for reviewing & merging this very long-awaited UX improvement in GNOME Calendar's infinitely scrolling month view: the previous/next buttons (and corresponding keyboard shortcuts) now properly clamp to the beginning of months when switching months! :blobmiou:

    See the "before" vs "after" demonstration videos in the merge request: gitlab.gnome.org/GNOME/gnome-c

    #GNOMECalendar #GNOME #UX #productivity #calendaring #planning #OpenSource #FLOSS

  25. @pranabekka @FineFindus Oh, yes! That's an incredible idea! Type the title, and maybe even a date and time into the search bar and select Add to calendar to add the event directly! Yes, that's even better than a keyboard shortcut, possibly!

    #gnome #GnomeCalendar