libdazzle issueshttps://gitlab.gnome.org/GNOME/libdazzle/-/issues2022-05-25T20:57:49Zhttps://gitlab.gnome.org/GNOME/libdazzle/-/issues/65dzl-file-manager.c should use portal on Linux2022-05-25T20:57:49ZBastien Noceradzl-file-manager.c should use portal on LinuxIt currently calls out directly to `org.freedesktop.FileManager1` which doesn't work on sandboxed filesystems.
Ideally, the API would also be adapted to allow passing a parent window. This functionality is used in evince.
CC @gpooIt currently calls out directly to `org.freedesktop.FileManager1` which doesn't work on sandboxed filesystems.
Ideally, the API would also be adapted to allow passing a parent window. This functionality is used in evince.
CC @gpoohttps://gitlab.gnome.org/GNOME/libdazzle/-/issues/64Friendly fork of data structures proposed2022-03-31T10:34:31ZReuben ThomasFriendly fork of data structures proposedI am developing in Vala, and I found libdazzle when looking for a Trie implementation. Indeed, the implementation seems to be ideal for me.
I see that libdazzle is EOL; also, that the library as a whole is under GPL. Neither of these is...I am developing in Vala, and I found libdazzle when looking for a Trie implementation. Indeed, the implementation seems to be ideal for me.
I see that libdazzle is EOL; also, that the library as a whole is under GPL. Neither of these is ideal for my current project.
However, I also see that much of the code is under LGPL (exactly what I need).
I would be interested in making a new library (or perhaps finding a home in some other existing library) for the data structure code.
I have already mentioned Trie, and a quick scan of the Valadoc web page for libdazzle reveals Heap and Ring, and a bunch of FuzzyIndex classes. Is there anything else you'd recommend?
Any opinions or suggestions you have would be most welcome. My thought is that it would be a shame for the useful and general-purpose data structure code to disappear along with the more special-purpose UI code.https://gitlab.gnome.org/GNOME/libdazzle/-/issues/59Provide screenshots of widgets2021-09-09T16:09:47ZDarkTrickProvide screenshots of widgetsIt would be nice to have a visual overview of what libdazzle brings along.
I think this would help people to decide whether or not to try it.It would be nice to have a visual overview of what libdazzle brings along.
I think this would help people to decide whether or not to try it.https://gitlab.gnome.org/GNOME/libdazzle/-/issues/57dzl_g_date_time_format_for_display code looks odd2020-11-17T13:33:37ZSophie Herolddzl_g_date_time_format_for_display code looks oddEverything that is more then 1½ hours and less then 48 hours ago is displayed as "Yesterday"?
```c
else if (diff < (60 * 90))
return g_strdup (_("An hour ago"));
else if (diff < (60 * 60 * 24 * 2))
return g_strdup (_("Yeste...Everything that is more then 1½ hours and less then 48 hours ago is displayed as "Yesterday"?
```c
else if (diff < (60 * 90))
return g_strdup (_("An hour ago"));
else if (diff < (60 * 60 * 24 * 2))
return g_strdup (_("Yesterday"));
```
https://gitlab.gnome.org/GNOME/libdazzle/-/blob/master/src/util/dzl-date-time.chttps://gitlab.gnome.org/GNOME/libdazzle/-/issues/53How to clear a GraphView?2020-03-02T21:29:24ZStanisławHow to clear a GraphView?How to properly clear a GraphView from all the lines?How to properly clear a GraphView from all the lines?https://gitlab.gnome.org/GNOME/libdazzle/-/issues/48cpu graph for only one core2019-10-01T18:28:08ZJames Zcpu graph for only one corethe cpu graph example was for all cores is it possible for libdazzle to do 1 graph per core? If yes, how do I do this without incurring huge performance?the cpu graph example was for all cores is it possible for libdazzle to do 1 graph per core? If yes, how do I do this without incurring huge performance?https://gitlab.gnome.org/GNOME/libdazzle/-/issues/39DzlApplicationWindow should allow to reveal the header bar with a touchscreen2019-06-11T23:41:21ZAdrien PlazasDzlApplicationWindow should allow to reveal the header bar with a touchscreenIt is currently impossible to reveal the header bar on a touchscreen when `DzlApplicationWindow` is in fullscreen mode: https://gitlab.gnome.org/GNOME/epiphany/issues/814
Either we allow to manually reveal the header bar so the apps can...It is currently impossible to reveal the header bar on a touchscreen when `DzlApplicationWindow` is in fullscreen mode: https://gitlab.gnome.org/GNOME/epiphany/issues/814
Either we allow to manually reveal the header bar so the apps can add the extra cases they want, or we make `DzlApplicationWindow` handle that but it may be a bit too application specific.
If we offer accessors, we kill two birds with one stone as it would fix https://gitlab.gnome.org/GNOME/libdazzle/issues/38 too.https://gitlab.gnome.org/GNOME/libdazzle/-/issues/42Typing in URL bar slows down system2020-05-27T21:27:08ZCarmen Bianca BakkerTyping in URL bar slows down systemThis is a bit of a weird issue. When I type on the URL bar in Web, the rest of the system slows down.
Steps to reproduce:
- Open Firefox or Totem to play a video
- Open Web
- Start typing in the URL bar
- The video begins to stutter...This is a bit of a weird issue. When I type on the URL bar in Web, the rest of the system slows down.
Steps to reproduce:
- Open Firefox or Totem to play a video
- Open Web
- Start typing in the URL bar
- The video begins to stutter
The stuttering is especially noticeable on the first few characters that are typed.
This problem occurs on:
```
System:
Host: thinkpad-a285 Kernel: 5.0.11-300.fc30.x86_64 x86_64 bits: 64
Desktop: Gnome 3.32.1 Distro: Fedora release 30 (Thirty)
Machine:
Type: Laptop System: LENOVO product: 20MWCTO1WW v: ThinkPad A285
serial: <filter>
Mobo: LENOVO model: 20MWCTO1WW v: SDK0J40709 WIN serial: <filter>
UEFI: LENOVO v: R0XET33W (1.10 ) date: 11/07/2018
Battery:
ID-1: BAT0 charge: 21.7 Wh condition: 47.9/47.9 Wh (100%)
CPU:
Quad Core: AMD Ryzen 5 PRO 2500U w/ Radeon Vega Mobile Gfx type: MT MCP
speed: 1597 MHz max: 1600 MHz
Graphics:
Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
driver: amdgpu v: kernel
Display: wayland server: Fedora Project X.org 1.20.4 driver: amdgpu
resolution: 1920x1080~60Hz
OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.11-300.fc30.x86_64 LLVM 8.0.0)
v: 4.5 Mesa 19.0.3
Network:
Device-1: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver: r8822be
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
Drives:
Local Storage: total: 238.47 GiB used: 76.60 GiB (32.1%)
Info:
Processes: 360 Uptime: 17h 45m Memory: 14.62 GiB used: 7.88 GiB (53.9%)
Shell: xonsh inxi: 3.0.32
```https://gitlab.gnome.org/GNOME/libdazzle/-/issues/37DzlSuggestionPopover flickers and pops down unecessarily2019-12-25T18:56:03ZGeorges Basile Stavracas NetoDzlSuggestionPopover flickers and pops down unecessarilyNow that GNOME Calendar is using DzlSuggestion* APIs, it's become increasingly noticeable that https://gitlab.gnome.org/GNOME/libdazzle/issues/32 is affecting the experience.
Same symptoms, under GNOME 3.32 on Wayland.
(This is a track...Now that GNOME Calendar is using DzlSuggestion* APIs, it's become increasingly noticeable that https://gitlab.gnome.org/GNOME/libdazzle/issues/32 is affecting the experience.
Same symptoms, under GNOME 3.32 on Wayland.
(This is a tracker bug for me to not forget to look into it.)https://gitlab.gnome.org/GNOME/libdazzle/-/issues/23dzl_graph_model_iter_set not usable from introspection2018-08-14T19:30:17ZJens Georgdzl_graph_model_iter_set not usable from introspectionI was trying to check whether DzlGraphView is usable for me in a project and while trying to prototype it from python, I noticed that it is not possible to set values on a model from introspection due to the vararg.I was trying to check whether DzlGraphView is usable for me in a project and while trying to prototype it from python, I noticed that it is not possible to set values on a model from introspection due to the vararg.https://gitlab.gnome.org/GNOME/libdazzle/-/issues/18DzlCpuGraph is visually distracting when updating2018-07-09T10:29:43ZRobert AncellDzlCpuGraph is visually distracting when updatingDzlCpuGraph is visually distracting when it adds new data to the right of the graph.
It would work better if the new data faded in.DzlCpuGraph is visually distracting when it adds new data to the right of the graph.
It would work better if the new data faded in.https://gitlab.gnome.org/GNOME/libdazzle/-/issues/12Provide a widget catalog for Glade2018-08-07T23:17:10ZAdrián Pérez de CastroProvide a widget catalog for GladeIt would be great if libdazzle would provide a widget catalog for Glade. [The introduction to catalogs](https://developer.gnome.org/gladeui/stable/catalogintro.html) probably includes enough information to have a basic, working catalog d...It would be great if libdazzle would provide a widget catalog for Glade. [The introduction to catalogs](https://developer.gnome.org/gladeui/stable/catalogintro.html) probably includes enough information to have a basic, working catalog done.https://gitlab.gnome.org/GNOME/libdazzle/-/issues/11Add descriptions to all classes2018-08-07T23:16:50ZnotafileAdd descriptions to all classesBrowsing the docs as someone only vaguely familiar with Gtk, it is very hard to understand what individual classes are for. It would be nice if there was some kind of description for all classes.Browsing the docs as someone only vaguely familiar with Gtk, it is very hard to understand what individual classes are for. It would be nice if there was some kind of description for all classes.https://gitlab.gnome.org/GNOME/libdazzle/-/issues/1libdazzle: user-visible strings are not translatable/translated2022-03-21T13:51:14ZBugzillalibdazzle: user-visible strings are not translatable/translated## Submitted by Piotr Drąg `@piotrdrag`
**[Link to original bug (#785830)](https://bugzilla.gnome.org/show_bug.cgi?id=785830)**
## Description
libdazzle has no i18n infrastructure.
GtkBuilder files with translatable="yes" (exclud...## Submitted by Piotr Drąg `@piotrdrag`
**[Link to original bug (#785830)](https://bugzilla.gnome.org/show_bug.cgi?id=785830)**
## Description
libdazzle has no i18n infrastructure.
GtkBuilder files with translatable="yes" (excluding examples/ and tests/):
https://git.gnome.org/browse/libdazzle/tree/src/prefs/dzl-preferences-font-button.ui
https://git.gnome.org/browse/libdazzle/tree/src/prefs/dzl-preferences-view.ui
https://git.gnome.org/browse/libdazzle/tree/src/widgets/dzl-counters-window.ui
https://git.gnome.org/browse/libdazzle/tree/src/shortcuts/dzl-shortcut-accel-dialog.ui
https://git.gnome.org/browse/libdazzle/tree/src/shortcuts/dzl-shortcut-theme-editor.ui
C files with _(" and ngettext (excluding examples/):
https://git.gnome.org/browse/libdazzle/tree/src/shortcuts/dzl-shortcut-accel-dialog.c#n443 (and #n501)
https://git.gnome.org/browse/libdazzle/tree/src/shortcuts/dzl-shortcuts-shortcut.c#n133
https://git.gnome.org/browse/libdazzle/tree/src/shortcuts/dzl-shortcut-manager.c#n205
https://git.gnome.org/browse/libdazzle/tree/src/shortcuts/dzl-shortcut-theme-editor.c#n198
https://git.gnome.org/browse/libdazzle/tree/src/util/dzl-date-time.c#n55
https://git.gnome.org/browse/libdazzle/tree/src/widgets/dzl-file-chooser-entry.c#n100
https://git.gnome.org/browse/libdazzle/tree/src/widgets/dzl-search-bar.c#n378
C files with translatable properties and journal errors that can *probably* be unmarked from translation:
https://git.gnome.org/browse/libdazzle/tree/src/animation/dzl-animation.c#n732
https://git.gnome.org/browse/libdazzle/tree/src/files/dzl-directory-model.c#n374
https://git.gnome.org/browse/libdazzle/tree/src/search/dzl-trie.c#n792
https://git.gnome.org/browse/libdazzle/tree/src/shortcuts/dzl-shortcuts-group.c
https://git.gnome.org/browse/libdazzle/tree/src/util/dzl-file-manager.c
https://git.gnome.org/browse/libdazzle/tree/src/widgets/dzl-stack-list.c#n408
These have a mixture of the above (“real” strings and prop descriptions):
https://git.gnome.org/browse/libdazzle/tree/src/shortcuts/dzl-shortcuts-window.c
https://git.gnome.org/browse/libdazzle/tree/src/shortcuts/dzl-shortcuts-section.c
Line numbers may be incomplete, I added them just for minor convenience.https://gitlab.gnome.org/GNOME/libdazzle/-/issues/3allow DzlCounter to grow map region for larger numbers of counters2018-01-27T01:57:43ZBugzillaallow DzlCounter to grow map region for larger numbers of counters## Submitted by Christian Hergert `@chergert`
**[Link to original bug (#749280)](https://bugzilla.gnome.org/show_bug.cgi?id=749280)**
## Description
Right now, we don't play well with counters that cause us to overlap our allocated ...## Submitted by Christian Hergert `@chergert`
**[Link to original bug (#749280)](https://bugzilla.gnome.org/show_bug.cgi?id=749280)**
## Description
Right now, we don't play well with counters that cause us to overlap our allocated page size.
Growing the shm_open()'d file-descriptor is easy (using ftruncate to zero things). However, we can't move the mmap regions at runtime, or we could cause faults by running counters.
Therefore, each additional page needs to be allocated individually, and that means we will not have contiguous pages.
To work around that issue, we can just avoid adding counters at locations that would cause them to overlap pages. The local and remove implementations need to be smart enough to avoid this. (Actually, the reader probably doesn't need any help since it does not refresh when new counters are added).