Age | Commit message (Collapse) | Author |
|
this was required when we used ewlsh branch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
it contains several translations update and fixes
|
|
|
|
|
|
This is needed to make the extension work with gnome 3.34
|
|
|
|
|
|
|
|
|
|
|
|
simplified PKGBUILD
|
|
Multi-monitor-support further improved and the window previews are now
assorted into a separate menu, bindable to any click option. The usual
bug fixes and translation updates accompany these new features.
|
|
Besides the usual bug fixes and translation updates, docks can now be
placed on multiple monitors. A new click option was also added.
Version 58 introduced a regression and was thus skipped.
|
|
Apart from minor bugfixes and translation updates, the hotkey numbers of
the panel icons can now be displayed. Compatibility to the upcoming
gnome shell version 3.24 is also already included.
|
|
This version improved Wayland compatibility and added new features: The
windows can now be previewed from the dock icons which can also be
scrolled through with the mouse wheel, keyboard shortcuts can be
defined, and the border of the dock gained more customizability.
|
|
Some extensions authors introduce build steps required before
installing. Their execution normally produces a completed variant of the
extension code in a subdirectory, difficult to tell apart from the
original source. The find condition introduced herein proves the process
against such cases to come. It always chooses the files created last,
ensuring that a build which occurred after mere unpacking will always
take precedence.
|
|
This release only fixes a few bugs.
|
|
Apart from translation updates and improvements in configuration
options, the upcoming gnome-shell version 3.22 is already supported.
|
|
According to the Arch Packaging Standards [1], lines in a PKGBUILD
should be no longer than 100 characters and package descriptions should
cap at 80.
This does not change the contents of the built package, so the pkgver
stays unchanged.
[1]: https://wiki.archlinux.org/index.php/Arch_packaging_standards
|
|
As an extension consists of both the metadata description and a
JavaScript entry point always named extension.js, searching for both
hardens the locating process against changes to the directory structure.
This does not change the contents of the built package, so the pkgver
stays unchanged.
|