New button-styles:
- `change-view`: Highlighted like `special`,
but with a border at the bottom.
- `character-group`: Like `change-view`, but with less highlighting.
- `placeholder`: Less contrast to the background and does not visually
change when pressed.
- `subtle-highlight`: For highlighting commonly used characters
in accent-views, for example.
New layouts:
- Portuguese
- Slovenian
- Turkish (F-layout)
- Turkish (Q-layout)
Remade layout:
- Portuguese (Brazil): A view for accents has been added.
Changes:
- The new button-styles are used in the available layouts,
where appropriate.
- The top rows of the terminal-layouts are a little taller.
- Squeekboard will choose the wide shape of layouts, for more displays
in horizontal orientation.
- Highlighted buttons now show visual feedback too, when pressed.
- Many layouts have been adjusted,
so that those change their form less when switching views.
- Various small issues have been fixed, to make layouts more consistent.
Development:
- Scaling-tests for many display-types have been added.
Part-of: <https://gitlab.gnome.org/World/Phosh/squeekboard/-/merge_requests/655>
Changes:
- 25 wide shapes have been added,
so that every available layout now has a wide shape
- "PgUp" and "PgDn" on the terminal-layouts have been relabeled
to "Page ↑" and "Page ↓"
- The Spanish and French terminal-layouts now have translated key-names
- The Spanish terminal-layout has been updated with the additional
keys that are already available on the US-terminal-layout.
- The wide and base shapes of the German layout had a different
key-arrangement and the wide shape did not have a button to access
additional characters; this has been fixed.
Development:
- Squeekboard's versioning now follows Phosh's versioning
(for example: Squeekboard 1.38 was released in time for Phosh 0.38)
- The build-system has been simplified
- A single Cargo.toml file is used,
instead of assembling it from multiple parts
- Newer dependencies are now used for building Squeekboard by default
- Squeekboard's main development-platform is now Debian Testing
- The layout-files have been cleaned up,
so that those are easier to understand and edit
Part-of: <https://gitlab.gnome.org/World/Phosh/squeekboard/-/merge_requests/631>
The `eek/layersurface.c` file should be excluded because it's an imported, "foreign" source, but clang-tidy doesn't seem to have an annotation for that.
An alternative would have been to exclude it in Meson and do the check there, but that requires clang-tidy, raising the barrier to contribute of Squeekboard even more (it already requires libfeedback, which isn't packaged widely).
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.
This commit is a bit bigger than it could have: Meson changes could have gone in separately from CI and Debian.
This commit looks more complicated than it should reasonably be. Alas, Cargo is a piece of work, and it doesn't let honest people just choose different versions of dependencies, leading to a cascade of misery. Several things were tried to curb the disaster:
- Cargo [feature] supports choosing dependencies, but doesn't support specifying dependency versions
- Cargo has a cfg() syntax in sections for choosing dependencies by build options, but it explicitly doesn't support selecting on features…
- Cargo allows choosing different dependencies based on features, so perhaps dependencies with different versions could live in stub crates pulled in as needed? Nope! If a dependency doesn't exist in the repo (and that's the point here), Cargo throws up its hands.
This means Cargo.toml needs to be generated based on the build type. More misery:
- we lose the simplicity of just doing `cargo.sh` for simple housekeeping like deps updates. HACKING.md was updated to reflect that. Perhaps that's inevitable - build options need to be like this.
- Some flaky adjustments needed in `cargo.sh` because of an additional argument that can be mistaken for an argument to the exec in `cargo run`.
- Specifying a custom `Cargo.toml` means Cargo can no longer find any tests, examples, benchmarks, or binaries, because it searches relative to the directory of `Cargo.toml`, which is now the build dir. Extra care needed to not forget about them now.
As soon as Cargo allows anything better for managing deps versions, the above should be undone in its favor.
Good side is that a couple bugs went away:
- build flags not always making it to Cargo
- arm64 builds were optional while they shouldn't
- test layouts in unit tests are loaded from an explicit directory now
The Bullseye versions of dependencies are canonical now, Buster considered legacy.
