JUCE Roadmap Updates

News and Announcements
21

This is being worked on.

3 Likes
22

Very happy to see your plans laid out like this!

1 Like
23

I had to laugh at this because Microsoft has been trying and failing to force touch interfaces onto Windows users since at least 2012.

4 Likes
24

.. and one of the reasons they keep failing (imho) is that they continue to try to maintain a ‘backwards compatability’ with the window/sub-window parent/child relationship in the touch interface, and nobody wants to have to switch paradigms when they’re trying to get things done.

I believe iOS designers learned from that negative experience.

1 Like
25

We have just added another roadmap update:

There haven’t been many changes to the big ticket items, but we have finished off better Windows windowing, and we have started work on the JUCE marketplace. We’re also working hard on improving the Direct2D renderer.

However, there have also been some additional useful things added to JUCE 8:

  • Windows Arm support for applications and plug-ins
  • Local notifications (particularly useful for accessibility)
  • VST3 parameter migration
  • MIDI note names
2 Likes
26

What is the JUCE Marketplace all about? That sounds neat!

27

What does this include? I don’t see it on the roadmap.

28

Somewhere where we can showcase all the third-party JUCE modules, tools and JUCE-based projects. It’ll be along the same lines as the Visual Studio Marketplace.

29

We removed it from the roadmap as it was finished.

From the previous roadmap update:

Support for Windows 11 snap layouts is coming. Snap layouts are accessed by hovering the mouse over a window’s maximize button to bring up a set of options for positioning that window in relation to others.

354×203 24.4 KB

1 Like
30

When you have a chance, can we have more details about this? This sounds like an important change.

Also, is there “an official/supported method” to disable Direct2D and revert to JUCE7 rendering if it causes issues(see relevant thread)? I don’t see it in the roadmap and I’m not migrating to JUCE8 because I can’t risk those problems in production. I wonder if I am alone with this.

Thanks much!

3 Likes
31

If you ever get a moment, we could use a wiki :wink:

32

It would be great if PowerToys “FancyZones” would work as well. Not sure why JUCE windows don’t work currently.

33

I haven’t tested this, but I wonder whether you’re using a recent JUCE 8 release, or something older. We made some significant changes to window handling on Windows, including adding support for the “Snap Window” feature, shortly after the initial release of JUCE 8. If you haven’t already, please check the current develop branch.

34

I’m on 7.0.12, will likely upgrade on the next release. Thx

35

This is the most important commit related to this work.

See the VST3ClientExtensions::getCompatibleParameterIds() function for more details.

1 Like
36

Here’s another update:

6 Likes
37

You could also mention the many improvements to the Android platform added to JUCE 8 post-launch: support for floating windows and split-view, correct reporting of safe-area insets, ability to change the app style, support for virtual MIDI devices (within the MIDI 2.0 preview branch). These are all extremely useful additions!

4 Likes
38

In successive JUCE releases we have improved the GUI rendering performance on both macOS/iOS and Windows, and we’re now turning our attention to embedded platforms and Linux. JUCE is used in flagship hardware products and the ability to render increasingly complex UIs more efficiently is becoming more important.

It seems to something new in JUCE 9 roadmap :laughing: Would you like to share some details on this? Does JUCE plan to switch to hardware rendering on Linux desktop (such as Vulkan)? Or it is something else?

39

Part of the work will be investigating the possibilities. Given the constraints of popular embedded devices running Linux, it seems very unlikely Vulkan is always going to be available, add on top of that the amount of effort required for a Vulkan renderer (just look at the effort required for the recent Direct2D renderer) it seems unlikely this is where we will focus our attention. However, maybe there is merit in improving our OpenGL renderer, adding support for something like OpenGL ES, or just improving the performance of the software renderer for these platforms. It would be hard to say anything definitive without first doing some more investigative work.

3 Likes
40

Any estimated timeline for MIDI 2.0 making it to the main/stable JUCE branch? Just hope it’s not something dependant on Window’s implementation because Microsoft has been dragging their feet for 2 years already.