[gimp-web] News 2.99.6: update.

[Jehan <jehanp src gnome org>]

commit a7945d2d319ab13fcd60a5bef421a9263977e969
Author: Jehan <jehan girinstud io>
Date:   Sun May 2 14:01:24 2021 +0200

    News 2.99.6: update.

 .../2021/2021-04_GIMP-2.99.6_Released/index.md     | 80 +++++++++++++++++-----
 1 file changed, 63 insertions(+), 17 deletions(-)
---
diff --git a/content/news/2021/2021-04_GIMP-2.99.6_Released/index.md 
b/content/news/2021/2021-04_GIMP-2.99.6_Released/index.md
index 622c7368..cb4b40fe 100644
--- a/content/news/2021/2021-04_GIMP-2.99.6_Released/index.md
+++ b/content/news/2021/2021-04_GIMP-2.99.6_Released/index.md
@@ -14,10 +14,10 @@ is evolving quite steadily.
 ⚠️  Many of the third-party plug-ins already ported for GIMP 2.99.2 or
 2.99.4 will end up broken, and there is a high chance they will break
 again in further development releases until we stabilize the API. We
-apologize for this. This is the price of making plug-ins for a program
-in-development, yet we figured it's better to do this now rather than
-ending up stuck with a bad interface for the years to come (as stability
-will be ensured once GIMP 3 will be out).
+apologize for this, though this is the price of making plug-ins for a
+program in-development. We figured it's better to do this now rather
+than ending up stuck with a bad interface for the years to come (as
+stability will be ensured once GIMP 3 will be out).
 
 Release highlights:
 
@@ -40,7 +40,9 @@ Release highlights:
 
 In the continuation of [out-of-canvas area
 visibility](https://www.gimp.org/news/2019/10/31/gimp-2-10-14-released/#out-of-canvas-viewing-and-editing),
-guides can now be placed outside the canvas.
+guides can now be placed outside the canvas. This was deemed useful for
+various use cases when you want to work on bigger areas than your
+canvas.
 
 For people worried of graphical interaction with guides, the workflow to
 delete them (dropping the guides off-canvas) just changed to be about
@@ -77,17 +79,18 @@ the template's dimensions to match the image's density.
 
 This is very fresh news as we merged this code (by Povilas Kanapickas,
 brand new contributor!) only a few days ago: GIMP now has pinch gesture
-support for touchpads and some tablets (it might not work with all
-tablets, in particular touch screens). In other words, if you have a
+support for touchpads, some tablets or touch screens (it might not work
+with all tablets and touch screens). In other words, if you have a
 device with touch support, such as a laptop touchpad (also tested
 successfully with a Wacom Intuos Pro), you can zoom in and out through
 pinching movements with your fingers.
 
-This is known to work on Linux/Wayland and it might work in a few months
-in X11 (after [this
+This is known to work on Linux/Wayland (tested successfully on a laptop
+touchpad and a Wacom Intuos Pro) and it might work in a few months in
+X11 (after [this
 patch](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/530)
 gets merged). Someone reported the feature working on Windows 10 too
-with one's touch display.
+with one's touchpad and integrated laptop's touch display.
 We have not found anyone yet to test the feature on macOS (it relies on
 generic GTK code, but the exact support depends on specific per-platform
 implementation and on the touch device firmware and/or driver
@@ -109,9 +112,9 @@ finished by its contributor, Thomas Manni. Nevertheless it has already
 improved quite a bit and starts getting really interesting.
 
 Several bugs were fixed and selection is now viewport-based which allows
-it to be much faster already depending on the zoom. Yet this is not the
-expected optimization which is planned to make the tool work really fast.
-Expect more to come!
+it to be much faster already depending on the zoom. Yet this is not even
+the expected optimization which is planned to make the tool work really
+fast. Expect more to come!
 
 This work has been happening both on GIMP code base and on our graphics
 engine library's code base, GEGL.
@@ -142,8 +145,8 @@ using such a single gamma value. Yet we wanted to be able to read and
 display such images correctly.
 GIMP's historical workaround was to store the `gAMA` and `cHRM` values
 in a `parasite` on the XCF file, and just put it back when exporting to
-PNG again (which means that the image was wrongly displayed in GIMP
-itself but fine after export).
+PNG again which means that the image was wrongly displayed in GIMP
+itself but fine after export.
 
 Now GIMP will propose creating an actual ICC profile from the `gAMA` and
 `cHRM` chunks, thus the image will be properly displayed. Since we don't
@@ -157,7 +160,7 @@ it](http://www.libpng.org/pub/png/spec/1.2/PNG-Encoders.html#E.Encoder-color-han
 
 ## More plug-in work
 
-Our screenshot plug-ins has several implementations and used to always
+Our screenshot plug-in has several implementations and used to always
 display a dialog. With portals nowadays (especially for Wayland and
 sandbox-style packaging), more of the logics is moved toward the portal
 itself. This is the case in particular for the Freedesktop portal which
@@ -178,7 +181,50 @@ the new API…
 
 # API evolution
 
-TODO
+* Work continued on GUI generation for plug-ins, allowing to generate a
+  GTK dialog in just a few lines of code (options being introspected
+  from the plug-in procedure's arguments).
+
+* Plug-in procedure's default argument used to give a single image and
+  drawable. It was changed to give an image and an array of drawables,
+  since now GIMP has multi-layer selection ability. This is the main
+  reason why most plug-ins out there which used to work on earlier
+  2.99.x versions will break. Sorry about this, it's for the greater
+  good and goes with the new abilities of GIMP for better handling of
+  complex images!
+
+* Some more work is also ingoing on the concept of a plug-in procedure's
+  "sensitivity", i.e.: when is the plug-in usable? Up until GIMP 2.10.x
+  series (and even in the first development releases 2.99.2 and 2.99.4),
+  plug-ins were sensitive when an image is opened with a single drawable
+  selected. Now with the new multi-selection abilities, it became clear
+  that maybe you want a plug-in which works also on several layers at
+  once, or even **only** when several layers are selected! And what if
+  you wanted a plug-in which doesn't care if an image was opened at all?
+  We therefore added a new function to set the sensitivity cases for a
+  plug-in, though we are already thinking on improving this even further
+  (which is why we are not going to name the function here and we don't
+  advise to use it yet if you find it).
+
+* Moreover many functions have been renamed for consistency, and also
+  sometimes avoiding some name clashes on language binding generation,
+  such as `gimp_parasite_name()` becoming `gimp_parasite_get_name()`.
+  Here is the [list of updated function
+  names](https://gitlab.gnome.org/GNOME/gimp/-/blob/master/NEWS#L97) in
+  GIMP 2.99.6.
+
+* "Parasites" (which is the technical name for random data attached to
+  an image, a layer, or to GIMP itself) are now usable as plug-in
+  procedure arguments. While this seems like a weird change, it is
+  useful when you want to store random data (even binary data) between
+  several GIMP runs. We already use this trick in the QBist plug-in from
+  default plug-ins.
+
+Many more changes happened on the API, you may have a better overview by
+checking the
+[NEWS](https://gitlab.gnome.org/GNOME/gimp/-/blob/master/NEWS#L50) file,
+though even this file might not be exhaustive (in case we forgot to note
+some changes!).
 
 # New translation for the installer