GitLab

Key maps are switched on key press whenever needed.

Cleanups leading to Xwayland compatibility

See merge request !389

At the same time, reduce the distance between this and the Xwayland handling branch.

Improve generation of key maps

See merge request !388

debian: Insert a "breaks" for librem5-base < 24

See merge request !392

Optimize sizing

See merge request !390

Librem5-base sets the GNOME a11y to true, which solves the invisibility of the keyboard on the phone.

Add wide keyboards

See merge request !391

Expand key press detection to the edges of the view's bounding box

Closes #191

See merge request !379

This is a copy of the `terminal` layout with modified key dimensions to 
fit a wide arrangement.

This is a copy of the `be` layout with modified key dimensions to fit a 
wide arrangement.

This is a copy of the `fr` layout with modified key dimensions to fit a 
wide arrangement.

Even though proper size management is being worked on, this patch
proposes a simple and easily revertable solution to device-dependent
sizing issues.

First, it provides different calculations based on the display
orientation. In landscape mode, this allows us to have a sensible
keyboard size while leaving enough screen estate for apps to be able to
display useful information.

Then, it gets rid of the weird calculation for display widths between
360 and 540px. While having some continuity is a pleasant idea, in the
real world in doesn't work, as shown by port attempts to other devices:
a 480x800 display (scale 1) would show an unusable 190px-high keyboard
(about half the size of the Librem 5 on-screen keyboard on a device I
own).

Finally, this commit makes sure we never use a hardcoded size.

Tested on the PinePhone, PineTab and Librem 5.

Note: Current behavior is preserved on the L5 in portrait mode, but
keyboard is a bit smaller in landscape mode; this is deliberate, as it
was previously using too much space (causing some apps, such as chatty,
to be unusable).

Using the actual monitor width in pixels can lead to unsatisfying
results, depending on the display orientation and physical size: on a
10" tablet with a 1280x800 resolution (scale 1), portrait orientation
will be using the narrow layout.

If the keyboard is sized in an optimal way (i.e. so the layout fills the
whole area, with no blanks on the sides) this would result in an
unnecessarily huge keyboard being displayed, therefore wasting screen
estate.

Using the virtual display size gives a hint about the physical size of
the device, and can be used to select wide layouts even in portrait
mode, while still preserving current behavior on HiDPI devices.

This has been tested on PineTab, PinePhone and Librem 5.

Add settings option to popover

Closes #154

See merge request !385

Fixes #154

Sort layouts by type before sorting by name

Closes #176

See merge request !384

build: Error on repeating declarations

See merge request !387

Includes changes to the keymap string without which Xwayland won't work.

docs: Tutorial syntax cleanups, reorganization

See merge request !381

Fix 2 leaks

Closes #148

See merge request !386

xkb_keymap_get_as_string requires that the string it returns is freed by
the caller.

This makes it such that local layouts like emoji and terminal appear
below language layouts.

Fixes #176

proposal for belgian layout (copy of fr)

See merge request !382

People still ignore adding layouts to builtins and to tests. To unbury that information, and add a sort of checklist, the more interesting info has been moved upwards nd together.

Promoted bolded "headings" into actual headings, so that they can be linked to.

Expand the development documentation in the readme

Closes #227

See merge request !377

If you have a keyboard layout like the following:

A B C D
 E F G
H I J K

The E and G keys here should be pressed when clicking in the empty space
next to them. This is achieved by not checking the bounding boxes of
each key and instead just using the button and row offset to extend
buttons/rows to the edges of the view. Caching for the size and
position of rows is introduced to simplify implementation and possibly
improve performance.

Fixes #191

Fixes #227

Fix spelling mistakes in doc/hacking.md

Closes #217

See merge request !378

Fixes #217