[gimp-web] Fill a bit 2.99.4 news.

[Jehan <jehanp src gnome org>]

commit 762bb99aab51359d56d346cd6693ec37b89a7bb7
Author: Jehan <jehan girinstud io>
Date:   Fri Dec 18 13:31:16 2020 +0100

    Fill a bit 2.99.4 news.

 .../2020/2020-12_GIMP-2.99.4_Released/index.md     | 105 ++++++++++++++++++++-
 1 file changed, 103 insertions(+), 2 deletions(-)
---
diff --git a/content/news/2020/2020-12_GIMP-2.99.4_Released/index.md 
b/content/news/2020/2020-12_GIMP-2.99.4_Released/index.md
index 55349f0d..c95b0ab6 100644
--- a/content/news/2020/2020-12_GIMP-2.99.4_Released/index.md
+++ b/content/news/2020/2020-12_GIMP-2.99.4_Released/index.md
@@ -27,7 +27,34 @@ Release highlights:
 # Usability fixes
 ## Slider widget
 
-FIXME
+The new (more compact) slider widget came with a few discoverability
+issues, which we tried to fix in this version. This was mostly the
+result of usability tests and tweak-design by Aryeom after extensive
+usage.
+
+The first issue was the ability to edit the scale value numerically
+(i.e. by inputting numbers on keyboard) without also triggering a value
+change (with main button click). This was actually possible with a
+middle click which was hardly discoverable. Therefore it is now possible
+to pinpoint-click the displayed numbers. This action will only focus the
+text input (by default entirely selecting the existing value as is
+common when focusing text entries). You can still click-edit the value
+from everywhere in the widget, except exactly on the numbers.
+
+The second issue was providing cursor change, meant to help feature
+discovery:
+* The top-arrow cursor came from a time where this widget had 2 areas, a
+  top and bottom area, and doesn't really mean anything anymore on the
+  current interaction. We replaced it by a common "*grab*" cursor as
+  specified in the CSS specification. This becomes a "*grabbing*" cursor
+  when a click'n drag is in progress.
+* When the pointer is hovering the text area, it becomes a "*text*"
+  cursor instead, hence advertizing the fact that a click here would
+  produce a different action.
+* Finally when holding the `Shift` modifier key, the cursor will become
+  an horizontal resize cursor ("*col-resize*" in CSS specification),
+  hence advertizing the ability for smaller relative resizing (an action
+  also available with the third button, usually `right-click`).
 
 ## Multi-layer selection
 
@@ -35,7 +62,81 @@ FIXME
 
 ## Input Devices dialog
 
-FIXME
+The infamous "Input Devices" dialog has always felt packed with arcane
+features and devices. With GIMP 3, many features will be working
+out-of-the-box and it felt like the right time to clean a bit this
+dialog. This is a work we started earlier and continued for GIMP 2.99.4.
+
+* We now only show entries for actual physical devices attached to your
+  computers. Indeed this dialog also used to list "virtual devices", a
+  concept which was very confusing to everyone. Similarly we now hide
+  the `XTEST` device, some kind of test device generated by the X11
+  server (Linux).
+* We used to show all possible axes for all devices, including some axes
+  like "Rotation" or "Slider" which are actually only available very
+  rarely (only on some specific drawing styluses in the market, even
+  uncommon among professionals). The dialog will now only list the axes
+  returned by the driver (note that even this list may still show more
+  than a specific device actually has because drivers are sometimes
+  over-listing, but it is still much closer to reality).
+* When a device is connected, the names of the axes will also be the
+  ones as listed by the backend, which will get us closer-to-reality
+  names. Typically the `X` axis for a graphics tablet will be `Abs. X`
+  because these devices are usually meant for absolute pointer
+  positionning.
+* Curve editing for the tablet pressure response was one of the most
+  interesting configuration option in this dialog, even more now that we
+  don't need to enable or disable specific devices. This is why when a
+  device has a "Pressure" axis, it will be selected by default, hence
+  allowing you to directly work on the curve, without unecessarily
+  clicks.
+
+**Call for inputs**:
+
+There are a few puzzling settings in this dialog and we would welcome
+input from anyone who had actual needs for it. How were you using this
+feature? Which OS? What was the goal?
+
+* There used to be a "Keys" list for every device in the dialog. We
+  actually removed this list back in 2.99.2. Based on tests, code
+  research and discussion with Carlos Garnacho, we came to the
+  conclusion that the "Keys" concept was tied to "keyboard" devices
+  (a type of devices specifically which has always been filtered out of
+  this listing, at least since 2.8 and probably before) and is
+  meaningless on "pointer" devices (mice, touchpads, graphics tablets…).
+  Yet here was the option! Maybe it actually had a hidden usage to
+  someone, someday? If this is your case, please explain us so that we
+  can think of a way to restablish the feature with an understandabble
+  interface.
+* The "Axes" list has the ability to set the "axis use" for a given
+  axis (the little numbers next to each axis). Yet we never managed to
+  do anything with it. This looks mostly either broken or meaningless.
+  Has anyone a usage for this axis use settings?
+* Each device has 3 "modes": Disabled, Screen and Window. "Disabled"
+  simply means that the device will share the main virtual device
+  pointer while "Screen" will make it look independant. The "Window"
+  mode on the other hand is a concept only meaningful for "floating"
+  devices (a concept maybe not even valid on all platforms?) and even
+  then it looks broken, as far as our tests went. Is there anyone in the
+  world who actually use the "Window" mode and sees a difference with
+  "Screen"?
+
+If anyone gets a usage of these features, we would definitely welcome
+inputs because we are as puzzled as many on actual usage for these. On
+one hand, if we don't actually find any usage, we are tempted to remove
+the settings. Because it is only a waste of time and efforts to show
+non-working configuration, and it is confusing for everyone. On the
+other hand, we don't want to remove actual features if it turns out
+these can actually be used somehow. This is your time to shine and tell
+us how these are used!
+
+Note that if we finally understand how a feature is useful, we might
+actually even be able to improve the settings interface to make it more
+understandable hence useful to more people.
+
+## Better device defaults
+
+FIXME.
 
 # New experimental Paint Select tool