[gnome-builder] update NEWS

[Christian Hergert <chergert src gnome org>]

commit 10b546b8761c445e12dbbc813ec4614a6238abf6
Author: Christian Hergert <chergert redhat com>
Date:   Sat Sep 17 16:57:15 2022 -0700

    update NEWS
    
    This is a preview of 43.0 release notes so that we can start fresh and
    have them both here and on the upcoming branch.

 NEWS | 200 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------
 1 file changed, 175 insertions(+), 25 deletions(-)
---
diff --git a/NEWS b/NEWS
index 93ed8b011..706fd3961 100644
--- a/NEWS
+++ b/NEWS
@@ -1,36 +1,186 @@
-# Builder 43.alpha1
+# GNOME Builder 43.0
 
-This release is not intended for end-users.
+After about 6 months of development, GNOME Builder 43.0 is here!
 
-We're still under heavy development porting to GTK 4 and landing the new
-subsystems for GNOME 43. This release is therefore not yet Beta quality
-and so instead of a beta, we're releasing 43.alpha1.
+This is the truly the largest release of Builder yet, with nearly every
+aspect of the application improved in some way or another this cycle.
 
-It has too many fixes to enumerate since 43.alpha0, so you'll have to
-look through the commit log for the details.
+## Modern and Expressive Theming
 
-# Builder 43.alpha0
+The most noticeable change, of course, is the port to GTK 4. Builder now uses
+WebKit, VTE, libadwaita, libpanel, GtkSourceView, and many other libraries
+recently updated to support GTK 4.
 
-This release is not intended for end-users.
+Like we did for GNOME Text Editor, Builder will restyle the application window
+based on the syntax highlighting scheme. In practice this feels much less
+jarring as you use the application for hours.
 
-This is our first release of the GTK 4 port of GNOME Builder. It contains a
-significantly redesigned interface and foundry.
+## The Foundry
 
-Given the size of the Builder project this port is not yet complete. It is
-far enough along to get testing from distributions and enthusiastic users
-alike. However, expect missing features and please don't overwhelm upstream
-with issue reports on that. First check the GTK 4 port issue to see if it
-is already known at https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1675
+Behind the scenes, the "Foundry" behind Builder has been completely revamped
+to make better use of SDKs and runtimes. This gives precise control over how
+processes are created and run. Such control is important when doing
+development inside container technologies.
 
-Developer builds of Builder now use org.gnome.Builder.Devel as the application
-identifier so that we can allow parallel installing of nightly/stable Flatpaks.
+Users can now define custom "Commands" which are used to run your project
+and can be mapped to keyboard shortcuts. This allows for the use of Builder
+in situations where it traditionally fell short. For example, you can open
+a project without a build system and use commands to emulate a build system.
 
-While Builder still supports plugins written in Python, there are no more
-Python-based plugins bundled with Builder. We've stopped using the bindings
-ourselves due to instability. We may change our scripting language but that
-is for another time.
+Furthermore, those commands can be used to run your application and
+integrate with tooling such as the GNU debugger, Valgrind, Sysprof, and
+more. Controlling how the debugger was spawned has been a long requested
+feature by users.
 
-Thanks to everyone who has contributed to the GTK 4 port, it's been a full out
-scramble to port such a gigantic project in one cycle.
+## Keyboard Shortcuts
 
--- Christian
+Keyboard shortcuts were always a sore spot in GTK 3. With the move to GTK 4
+we redesigned the whole system to give incredible control to users and
+plugin authors. Similar to VS Code, Builder has gained support for a
+format similar to "keybindings.json" which allows for embedding GObject
+Introspection API scripting. The syntax matches the template engine in
+Builder which can also call into GObject Introspection.
+
+## Command Bar and Project Search
+
+We've unified the Command Bar and Project Search into one feature. Use
+Ctrl+Enter to display the new Global Search popover.
+
+We do expect this feature to be improved and expanded upon in upcoming releases
+as some features necessary are still to land within a future GTK release.
+
+## Movable Panels and Sessions
+
+Panels can be dragged around the workspace window and placed according
+to user desire. The panel position will persist across future openings
+of the project.
+
+Additionally, Builder will try to save the state of various pages including
+editors, terminals, web browsers, directory listings, and more. When you re-open
+your project with Builder, you can expect to get back reasonably close to where
+you left off.
+
+## GtkSourceView
+
+Core editing features have been polished considerably as part of my
+upstream work on maintaining GtkSourceView. Completion feels as smooth
+as ever. Interactive tooltips are polished and working nicely. Snippets too
+have been refined and performance improved greatly.
+
+Not all of our semantic auto-indenters have been ported to GtkSourceIndenter,
+but we expect them (and more) to come back in time.
+
+## Redesigned Preferences
+
+Preferences have been completely redesigned and integrated throughout
+Builder. Many settings can be tweaked at either the application-level as
+a default, or on a per-project basis. See "Configure Project" in the new
+"Build Menu" to see some of those settings. Many new settings were added
+to allow for more expressive control and others improved open.
+
+Use Ctrl+, to open application preferences, and Alt+, to open your project's
+preferences and configurations.
+
+## Document Navigation
+
+Since the early versions of Builder, users have been requested tabs to
+navigate documents. Now that we're on GTK 4 supporting that in a
+maintainable fashion is trivial and so you can choose between tabs or the
+legacy "drop down" selector. Navigation tabs are enabled by default.
+
+Some of the UI elements that were previously embedded in the document
+frame can be found in the new workspace statusbar on the bottom right.
+Additionally, controls for toggling indentation, syntax, and encoding
+have been added.
+
+Switching between similar files is easy with Ctrl+Shift+O. You'll be
+displayed a popover with similarly named files to the open document.
+
+The symbol tree is also still available, but moved to the statusbar.
+Ctrl+Shift+K will bring it up and allow for quick searching.
+
+## WebKit
+
+A new web browser plugin was added allowing you to create new browser
+tabs using Ctrl+Shift+B. It is minimal in features but can be useful
+for quick viewing of information or documentation.
+
+Additionally, the html-preview, markdown-preview, and sphinx-preview plugins
+have been rewritten to build upon this WebKit integration.
+
+## Plugin Removals
+
+Some features have been removed from Builder due to the complexity and
+time necessary for a proper redesign or port. The Glade plugin (which
+targets GTK 3 only) has been removed or obvious reasons. A new designer
+replace it and is expected as part of GNOME 44.
+
+Devhelp has also been removed but may return after it moves to supporting
+GTK 4. Additionally, other tooling may supersede this plugin in time.
+
+The code beautifier and color-picker were also removed and will likely
+return in a different form in future releases.
+
+## Project Templates
+
+Project templates have been simplified and improved for GTK 4 along with
+a new look and feel for creating them. You'll see the new project template
+workflow from the application greeter by clicking on "Create New Project".
+
+## Top Matches
+
+Heavy users of code completion will notice a new completion result which
+contains a large star (★) next to it. This indicates that the proposal is a
+very close match for the typed text and is getting resorted to the top of
+the completion results. This serves as an alternative to sorting among
+completion providers which is problematic due to lack of common scoring
+algorithms across different data sources. 
+
+## Sysprof Integration
+
+Tooling such as Sysprof went through a lot of revamp too. As part of this
+process I had to port Sysprof to GTK 4. Additionally, I created new tooling
+in the form of `sysprof-agent` which allows us to have more control when
+profiling across container boundaries. Tools which need to inject LD_PRELOAD
+(such as memory profilers) now work when combined with an appropriate SDK.
+
+## Language Servers
+
+Language servers have become a part of nearly everyone's development
+toolbox at this point. Builder is no different. We've added support for a
+number of new language servers including jdtls (Java), bash-language-server
+(Bash), gopls (Golang) and improved many others such as clangd (C/C++),
+jedi-language-server (Python), ts-language-server (JavaScript/Typescript),
+vls (Vala), rust-analyzer (Rust), blueprint, and intelephense (PHP).
+
+Many language servers are easier to install and run given the new design
+for how cross-container processes are spawned.
+
+## Plugins
+
+We have been struggling with our use of PyGObject for sometime. It's a
+complex and difficult integration project and I felt like I spent more time
+debugging issues than I was comfortable with. So this port also included a
+rewrite of every Python-based plugin to C. We still enable the Python 3
+plugin loader from libpeas (for third-party plugins), but in the future we
+may switch to another plugin language.
+
+## Maintainers Corner
+
+So...
+
+A special thanks to all those that sent me merge requests, modernized bits
+of software I maintain, fixed bugs, or sent words of encouragement.
+
+I'm very proud of where we've gotten. However, it's been an immense amount of
+work. Builder could be so much more than it is today with your help with triage
+of bugs, designing and writing features, project and product management, writing
+documentation, maintaining plugins, improving GNOME OS, and everything
+in-between.
+
+The biggest lesson of this cycle is how a strong design language is
+transformative. I hope Builder's transformation serves as an example for
+other GNOME applications and the ecosystem at large. We can make big leaps
+in short time if we have the right tooling and vision.
+
+-- Christian Hergert