[gimp-web/testing] Change the wording in the GTK+3 section a little
- From: Alexandre Prokoudine <aprokoudine src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gimp-web/testing] Change the wording in the GTK+3 section a little
- Date: Thu, 5 May 2016 15:30:03 +0000 (UTC)
commit 699e9cfe21cc6b1a9f3e011b0d2ac5cfc80822ae
Author: Alexandre Prokoudine <alexandre prokoudine gmail com>
Date: Thu May 5 18:26:20 2016 +0300
Change the wording in the GTK+3 section a little
content/docs/userfaq.md | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
---
diff --git a/content/docs/userfaq.md b/content/docs/userfaq.md
index bcf25ab..99493f7 100644
--- a/content/docs/userfaq.md
+++ b/content/docs/userfaq.md
@@ -182,7 +182,9 @@ We made a preliminary port of GIMP to GTK+3 a few years ago and intend to comple
The reason we prioritize it that way is that users who don't make a heavy use of Wacom tablets on Windows
can live with GTK+2 based GIMP another year or so. However not providing high bit depth precision for editing
makes GIMP unusable in professional workflows involving color grading and retouching.
-The completion of the GTK+3 port will coincide with API/ABI changes: we intend to break a few things to make
GIMP's architecture cleaner and prepare it for non-destructive editing (a feature currently planned for v3.2).
+The completion of the GTK+3 port will lead to API/ABI changes: we intend to break a few things to make
GIMP's architecture cleaner and prepare it for non-destructive editing (a feature currently planned for
v3.2), and we **have** to break ABI it to make GIMP's custom widgets work with GTK+3.
+
+While completing the GTK+3 port, we shall have to break API/ABI compatibility to make GIMP's custom widgets
work with GTK+3. Moreover, we intend to break a few more things to make GIMP's architecture cleaner and
prepare it for non-destructive editing (a feature currently planned for v3.2).
## Tips
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]