on-screen-keyboard: Add extra feedback on problems with using a widget

https://phabricator.apertis.org/T8305



Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>

content/concepts/on-screen-keyboard.md

@@ -114,14 +114,25 @@ application](https://gitlab.apertis.org/pkg/mildenhall/-/blob/apertis/v2021/widg
 was used for spell checking. This widget was built to exclusively target the legacy
 Mildenhall platform, and thus it brings several problems:
 
-- It is exclusively tied to Mildenhall applications; no other GUI frameworks are supported
+- It is exclusively tied to Mildenhall applications; no other GUI frameworks are supported.
 - Each app has their own instance of the widget, thus the application side is also
   responsible for tasks such as positioning the keyboard on the screen, while not actually
-  knowing the full screen layout as a compositor does
+  knowing the full screen layout as a compositor does.
 
 Attempting to migrate it away from being dependent on Mildenhall would essentially amount
 to a full rewrite, resulting in little advantage versus an alternative solution.
 
+## Using a New Widget
+
+Even if a new in-application widget were created, both of these points would
+still apply:
+
+- There would need to be a widget for every graphical application framework, and every
+  application using the framework would need to explicitly include the widget.
+- The problems and inefficiency with having the application position the keyboard on the
+  screen without full knowledge of the entire screen persist outside of Mildenhall, as it
+  is purely an architectural problem.
+
 # Implementations in Other Systems
 
 Qt uses a framework-specific, client-side plugin,