libhandy issueshttps://source.puri.sm/Librem5/libhandy/-/issues2020-04-14T09:52:53Zhttps://source.puri.sm/Librem5/libhandy/-/issues/246Documentation Request: Discoverability Coverage2020-04-14T09:52:53ZOliver KennedyDocumentation Request: Discoverability CoverageEspecially for someone just starting out with GTK, it can be difficult to find the right widget for a given interaction effect. For example, I almost gave up on trying to figure out how to get HdySqueezer to transition between a side-ba...Especially for someone just starting out with GTK, it can be difficult to find the right widget for a given interaction effect. For example, I almost gave up on trying to figure out how to get HdySqueezer to transition between a side-bar on the right until I looked through the example apps and came across HdyLeaflet.
Something that would have helped a lot is to have more screenshot coverage in the documentation -- prose descriptions of the widgets aren't always sufficient to make it clear what the widget's role is. (btw, the visual index is a fantastic feature!) Here's a quick survey of pages without screenshots that could use one:
* [ ] https://developer.puri.sm/projects/libhandy/unstable/HdyCarousel.html
* [ ] https://developer.puri.sm/projects/libhandy/unstable/HdyColumn.html
* [ ] https://developer.puri.sm/projects/libhandy/unstable/HdyLeaflet.html
* [ ] https://developer.puri.sm/projects/libhandy/unstable/HdyPreferencesGroup.html
* [ ] https://developer.puri.sm/projects/libhandy/unstable/HdyPreferencesPage.html
* [ ] https://developer.puri.sm/projects/libhandy/unstable/HdySqueezer.htmlhttps://source.puri.sm/Librem5/libhandy/-/issues/219Drop hdy_list_box_separator_header()?2020-03-03T08:22:51ZAdrien PlazasDrop hdy_list_box_separator_header()?Should we drop `hdy_list_box_separator_header()`? Some CSS could do the trick just as well as long as the list don't use headers at all, we could offer such style classes, and if apps want something more complex they will have to impleme...Should we drop `hdy_list_box_separator_header()`? Some CSS could do the trick just as well as long as the list don't use headers at all, we could offer such style classes, and if apps want something more complex they will have to implement their own headers function anyway.1.0https://source.puri.sm/Librem5/libhandy/-/issues/183Add HdyPasswordEntry2020-03-06T17:42:08ZGuido GuntherAdd HdyPasswordEntryA password entry that
- (toggleable globally) shows the entered character for 2 seconds before switching to the invisible char
- shows 'the eye' to enable showing the entered text (as in https://source.puri.sm/Librem5/phosh/merge_requ...A password entry that
- (toggleable globally) shows the entered character for 2 seconds before switching to the invisible char
- shows 'the eye' to enable showing the entered text (as in https://source.puri.sm/Librem5/phosh/merge_requests/413)
would be nice since passwords are way harder to type on mobilehttps://source.puri.sm/Librem5/libhandy/-/issues/177Don't export symbols form private API2020-03-03T07:31:53ZGuido GuntherDon't export symbols form private API@exalm discovered that we're exporting symbols from private API (https://source.puri.sm/Librem5/libhandy/merge_requests/355#note_74373). We should drop these e.g. by prefixing with `_` and then bump the ABI version for the next release. ...@exalm discovered that we're exporting symbols from private API (https://source.puri.sm/Librem5/libhandy/merge_requests/355#note_74373). We should drop these e.g. by prefixing with `_` and then bump the ABI version for the next release. This does not affect API.1.0https://source.puri.sm/Librem5/libhandy/-/issues/149Ensure minimum spacing around view switcher2020-03-11T06:01:00ZTobias BernardEnsure minimum spacing around view switcherHaving seen the view switcher used in real apps, I've noticed that it really needs a bit of breathing space around it when it's placed next to other controls in the headerbar, because it can look very cramped:
![image](/uploads/fec0aa82...Having seen the view switcher used in real apps, I've noticed that it really needs a bit of breathing space around it when it's placed next to other controls in the headerbar, because it can look very cramped:
![image](/uploads/fec0aa827dcea241b5e336f08f1d9eaf/image.png)
Something like this still looks fine, but less margin than this and it starts looking weird:
![image](/uploads/6c42377ebb2c9b10aceaa834f309e632/image.png)
I wonder if we could just have horizontal margins of e.g. 50-100px on each side when the widget is in the headerbar?https://source.puri.sm/Librem5/libhandy/-/issues/146HdyCarousel should support keynav2020-04-01T14:57:18ZAlexander MikhaylenkoHdyCarousel should support keynavI thought there was already an issue about it, seems not.
I guess: pgup/pgdown/home/end, and maybe arrows, but maybe arrows can be done by autoscrolling to the focused child.I thought there was already an issue about it, seems not.
I guess: pgup/pgdown/home/end, and maybe arrows, but maybe arrows can be done by autoscrolling to the focused child.https://source.puri.sm/Librem5/libhandy/-/issues/138New widget: Empty State2020-03-09T19:03:00ZTobias BernardNew widget: Empty StateThere are a lot of empty states across GNOME, which are all custom implementations of the same pattern. This could be a nice area where a Libhandy widget would make things easier for new developers, and more consistent across apps.
Exam...There are a lot of empty states across GNOME, which are all custom implementations of the same pattern. This could be a nice area where a Libhandy widget would make things easier for new developers, and more consistent across apps.
Example:
![image](/uploads/a489d44e20eb40589faf425896db15b1/image.png)1.xhttps://source.puri.sm/Librem5/libhandy/-/issues/125Add some padding to public structs to not break ABI on adding members2020-03-10T12:22:46ZMohammed SadiqAdd some padding to public structs to not break ABI on adding membersCurrently there are no additional slots added into public class structs of any widget. This will make it impossible to add additional signal handlers without ABI break. I would suggest to have at least 4 dummy pointer variables to be ad...Currently there are no additional slots added into public class structs of any widget. This will make it impossible to add additional signal handlers without ABI break. I would suggest to have at least 4 dummy pointer variables to be added to the end of public structs.1.0https://source.puri.sm/Librem5/libhandy/-/issues/116Allow to wrap the HdyActionRow subtitle2020-03-03T08:17:01ZAdrien PlazasAllow to wrap the HdyActionRow subtitleAllow to wrap the `HdyActionRow` subtitle instead of ellipsizing it for when it is important to deliver the full message to the user.Allow to wrap the `HdyActionRow` subtitle instead of ellipsizing it for when it is important to deliver the full message to the user.https://source.puri.sm/Librem5/libhandy/-/issues/110hdy_list_box_separator_header() has wrong signature in Vala2020-03-03T08:22:45ZAlexander Mikhaylenkohdy_list_box_separator_header() has wrong signature in Vala```vala
public static void list_box_separator_header (Gtk.ListBoxRow row, Gtk.ListBoxRow? before, void* unused_user_data);
```
```
../../../../../../../../../Projects/sidebar-example/src/window.vala:32.26-32.54: error: Argument 1: Can...```vala
public static void list_box_separator_header (Gtk.ListBoxRow row, Gtk.ListBoxRow? before, void* unused_user_data);
```
```
../../../../../../../../../Projects/sidebar-example/src/window.vala:32.26-32.54: error: Argument 1: Cannot convert from `void Hdy.list_box_separator_header (Gtk.ListBoxRow, Gtk.ListBoxRow?, void*)' to `void Gtk.ListBoxUpdateHeaderFunc? (Gtk.ListBoxRow, Gtk.ListBoxRow?)'
list.set_header_func (Hdy.list_box_separator_header);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```
That `void* unused_user_data` shouldn't be there.1.0https://source.puri.sm/Librem5/libhandy/-/issues/96column: Rename linear-growth-width2020-03-03T08:17:08ZAdrien Plazascolumn: Rename linear-growth-widthThe name is hard to understand, renaming to something like `natural-width-request` (if fitting) could help.The name is hard to understand, renaming to something like `natural-width-request` (if fitting) could help.1.0