summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* event-popover: Remove leftover debug codeHEADmainGeorges Basile Stavracas Neto2023-05-111-1/+0
|
* Update Italian translationGianvito Cavasoli2023-05-091-123/+138
| | | | (cherry picked from commit c71d7a5a4fd2d06e2797a55750d5ce06caca1d25)
* Add Gnome contribute linkTitouan Real2023-04-251-0/+1
|
* Add control requirementsTitouan Real2023-04-251-0/+5
|
* Update display length requirementsTitouan Real2023-04-251-1/+5
|
* Add display length requirementsTitouan Real2023-04-251-0/+5
|
* Add missing newlinesTitouan Real2023-04-251-0/+4
|
* Add release types to gnome3 releasesTitouan Real2023-04-251-20/+20
|
* Add release types to gnome40+ releasesTitouan Real2023-04-251-13/+14
|
* Add Calendar gitlab page linkTitouan Real2023-04-251-0/+1
|
* Add Gnome donate linkTitouan Real2023-04-251-0/+1
|
* appdata: Fix nesting <ul> and <p> in metainfo filePhilip Withnall2023-04-241-43/+37
| | | | | | | | | | | The only allowed child elements of `<p>` are `<em>` and `<code>`: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-description Spotted in https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2154 Signed-off-by: Philip Withnall <pwithnall@endlessos.org> Fixes: #1012
* weather-service: don't print error when geolocation is disabledMichael Catanzaro2023-04-221-1/+2
| | | | Fixes #954
* search/engine: Increase range to a whole yearGeorges Basile Stavracas Neto2023-04-221-2/+2
| | | | | | | | | | This is still not the ideal solution, but now that we have widgetry that can handle hundreds of thousands of events, no limitations to the maximum number of events, and no crashes related on the search engine, we can increase the search range to a broader value and show more results. Helps: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/624
* search/hit-event: Fix compare functionGeorges Basile Stavracas Neto2023-04-221-1/+1
| | | | | The current compare function puts events closer to today at the end of the list, instead of the beginning. Revert that.
* search: Remove artificial limitsGeorges Basile Stavracas Neto2023-04-225-20/+17
| | | | | | | Now that we use a widget that appropriately handles infinite items, we don't need to limit anything anymore. Related: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/624
* search/model: Shuffle some code aroundGeorges Basile Stavracas Neto2023-04-221-5/+5
|
* search/hit: Fix double unrefGeorges Basile Stavracas Neto2023-04-221-1/+1
| | | | | | | | When I originally wrote the code, I expected to create a new icon every time that function was called. That expectation changed, but the code wasn't fully updated. Use g_value_set_object() instead of g_value_take_object().
* style: Fix source button stylesAlexander Mikhaylenko2023-04-223-8/+10
| | | | | | - Port the style to GTK4 and remove obsolete styles - Fix double border in high contrast - Update for libadwaita toolbar margin changes
* gcal-schedule-section: Port "Repeat" to AdwComboRowCyber Phantom2023-04-223-42/+36
| | | | | GtkComboBox is going to be deprecated in GTK 4.10. This commit updates the "Repeat" rows in new schedule window to use AdwComboRow.
* Post-branching version bumpGeorges Basile Stavracas Neto2023-04-221-1/+1
|
* 44.144.1Georges Basile Stavracas Neto2023-04-221-0/+6
|
* Update Vietnamese translationNgọc Quân Trần2023-04-081-328/+356
|
* Update Friulian translationFabio Tomat2023-04-051-84/+99
|
* Update Russian translationAleksandr Melman2023-04-031-49/+53
|
* Update Dutch translationNathan Follens2023-03-261-93/+102
|
* Update Chinese (China) translationBoyuan Yang2023-03-221-87/+100
|
* event-popover: Set better default focus widgetGeorges Basile Stavracas Neto2023-03-171-0/+24
| | | | | | | When mapped, move focus to either the first meeting row - if any - or to the edit button. Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/980
* meeting-row: Implement grab_focus()Georges Basile Stavracas Neto2023-03-171-0/+17
| | | | | We'll use this in the next commit to properly grab focus of the first meeting row, if any.
* meeting-row: Remove leftover layout codeGeorges Basile Stavracas Neto2023-03-171-5/+0
| | | | It's not necessary anymore.
* event-popover: Set default widgetGeorges Basile Stavracas Neto2023-03-171-0/+1
| | | | Helps: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/980
* meeting-row: Make row unfocusableGeorges Basile Stavracas Neto2023-03-171-0/+1
| | | | | | But child widgets are. That is, the Join button. Helps: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/980
* event-popover: Update to GtkUriLauncherGeorges Basile Stavracas Neto2023-03-162-6/+26
| | | | And bump the GTK dependency to 4.10
* gschema: Remove accidental new stringsGeorges Basile Stavracas Neto2023-03-161-0/+2
| | | | | I didn't realize these were translated, and accidentally broke string freeze. Let's temporarily remove these strings for now.
* Update Portuguese translationHugo Carvalho2023-03-161-57/+62
|
* calendar-management: Switch to GtkColorDialogButtonGeorges Basile Stavracas Neto2023-03-164-16/+28
|
* calendar-manager/new: Switch to GtkFileDialogGeorges Basile Stavracas Neto2023-03-164-76/+72
| | | | Cleans up a few more compiler warnings.
* views/month: Cleanup mathGeorges Basile Stavracas Neto2023-03-161-47/+18
| | | | | | | | | | The Month view is a complicated beast when it comes to allocating events, but it's unnecessarily complicated since it tries to take margins of events into accounts. With GTK4, that's not necessary anymore, as GTK4 will independently and correctly apply margins in widgets by itself, we don't have to do manually anymore. Clean that up.
* search-button: Port results to GtkListViewgbsneto/search-widgetry-improvementsGeorges Basile Stavracas Neto2023-03-169-338/+228
| | | | | | Port the search results list to GtkListview. Use bindings to set the title, icon, and subtitle of each row. Remove GcalSearchHitRow as it's unused now.
* search/hit-event: Compare calendars tooGeorges Basile Stavracas Neto2023-03-161-1/+11
| | | | This allows not mixing up similar events from different calendars.
* search/model: Don't ignore results past limitsGeorges Basile Stavracas Neto2023-03-161-19/+12
| | | | | | | Instead, monitor where items are added relative to each other, and proxy the 'items-changed' call to match the inner list. Helps https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/989
* search/model: Use boolean result to find equal hitsGeorges Basile Stavracas Neto2023-03-161-6/+6
| | | | It's a bit better than using -1 with an unsigned int :)
* search-button: Cleanup unused shortcut controllerGeorges Basile Stavracas Neto2023-03-161-13/+0
|
* search-button: React to 'stop-search' signalGeorges Basile Stavracas Neto2023-03-162-7/+22
| | | | | | | | Quit the search entry state when the search entry emits stop-search, usually that's when Escape is pressed when the search entry is focused. Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/830
* search-button: Don't do anything when popover closesGeorges Basile Stavracas Neto2023-03-162-13/+0
| | | | | It's, at best, annoying. Also stop resetting the entry text when hiding suggestions, as it may loop with the text changed callback.
* search-button: Use 'search-changed' signalGeorges Basile Stavracas Neto2023-03-162-5/+4
| | | | | It uses a 150ms delay, which helps with reducing the number of queries we do.
* search-button: Instrument some functionsGeorges Basile Stavracas Neto2023-03-161-1/+9
|
* search-button: Use GtkSearchEntryGeorges Basile Stavracas Neto2023-03-162-13/+1
| | | | | Allows us to cleanup style a bit. Next commits will use search entry functionality better.
* core/calendar-monitor: Keep event alive while removing itGeorges Basile Stavracas Neto2023-03-161-0/+4
| | | | | This might be the last reference to it, so keep it alive while the signal is being emitted.
* search: Rework threadingGeorges Basile Stavracas Neto2023-03-163-84/+100
| | | | | | | | | | | | | Search uses GcalTimeline, an object that is meant to be single threaded, in multple threads. That mostly worked okay because GcalTimeline mostly relies on GcalCalendarMonitor, which is heavily threaded. But, sometimes it failed. Rework that to be single-threaded, and asynchronous. Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/981 Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/987 Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/988