We’re already working on some JUCE 8 features that were highlighted in the survey.
The most prominent of these is a new way of creating GUIs based on the built-in webviews provided by each platform we support. The intention here is that by providing infrastructure around the creation of the webview and bindings to the javascript running inside it, the development of UI elements can take place entirely within the webview. Not only does this enable interoperability with industry-standard design tools, it also removes the requirement for GUIs to be written in C++.
We’re also working on adding much broader text rendering and shaping support. This would be text that runs in different directions, the ability to handle all different character sets, better fallback font support, emojis and more. It’s a huge bit of work, but one that makes JUCE much more flexible.
Support for MIDI 2.0 is another thing currently underway. We’re aiming to add the ability to communicate with MIDI 2.0 devices and parse capability inquiry messages to JUCE “soon” as part of JUCE 7, but the schedule depends on our progress.
There are also some upcoming bits of work, the most exciting of which is a thorough evaluation of the work @matt has been doing on a new Direct2D-based Windows renderer. You can see more detail here:
We will also be investigating sample-accurate plug-in parameter automation as part of the work of adding new MIDI 2.0 compatibility with plug-in APIs.
In addition to having webviews-within-JUCE we will also look at JUCE-within-webviews. A large part of the framework is already compatible with WebAssembly and we will work to make web browsers an officially supported deployment target.