Personally, and contrary to the article, I <i>do</i> prefer Emacs's plain text widgets over more "GUI-like" ones. Plain text widgets minimize the differences between TUI and GUI Emacs and also inherently offer text selection, searching, copying, and pasting, which nicely integrates with Emacs. I mean, not many GUI frameworks let you place a cursor within a button and select its text, do they? I believe this is a unique advantage of text-based widgets: while other GUI applications require a dedicated mechanism for searching through their settings, text-based widgets allow you to use any text-searching packages to perform these actions.<p>Reading through the article, the author seems to be hoping for a pure GUI approach with Emacs-like navigation mechanisms, but I am not convinced that this can be as flexible as text-based widgets. However, for packages used exclusively within a GUI environment (like el-easydraw [1], which relies quite heavily on SVG-based widgets), it would be nice to have a dedicated GUI widget library.<p>(There was a discussion on Reddit about this a week ago [2], and I saw some comments defending GTK and PGTK that might be worth reading.)<p>[1] <a href="https://github.com/misohena/el-easydraw/">https://github.com/misohena/el-easydraw/</a><p>[2] <a href="https://www.reddit.com/r/emacs/comments/1kcgwme/the_emacs_widget_toolkit/" rel="nofollow">https://www.reddit.com/r/emacs/comments/1kcgwme/the_emacs_wi...</a>
PSA: Use The Lucid Toolkit <a href="https://irreal.org/blog/?p=12672" rel="nofollow">https://irreal.org/blog/?p=12672</a><p><a href="https://old.reddit.com/r/emacs/comments/1hlj04t/emacs_using_the_lucid_toolkit_is_blazingly_fast/" rel="nofollow">https://old.reddit.com/r/emacs/comments/1hlj04t/emacs_using_...</a>
There's also the Emacs Widget Library[1] (which I hoped this posted would be about). It's a plain text widget library that's quite powerful. Unfortunately (and surprisingly for Emacs), the documentation for it could use some love.<p>My understanding of the Widget Library is that it attaches various keywords and plists to a symbol which is considered the "widget". The library otherwise consists of functions that expect certain keywords on the "widget" symbol in order to perform actions or to be drawn on the screen.<p>The challenge is, the documentation doesn't clearly lay out what the keyword API is. This makes it hard to compose widgets in ways beyond what's shown in the docs.<p>[1] <a href="https://www.gnu.org/software/emacs/manual/html_mono/widget.html" rel="nofollow">https://www.gnu.org/software/emacs/manual/html_mono/widget.h...</a>