@d-healey JUCE 7 only added official support for LV2. CLAP support is not yet official. They also have yet to add any support for Wayland, which will become a problem soon - Linux DAWs are starting to consider Wayland support, as evidenced by PreSonus' beta release. VST3 GUIs straight up do not show up as of right now.

@tobante Interesting, I didn't know HISE made any modifications to JUCE. Is there any developer documentation, for would-be contributors?
LV2 or CLAP, anything to get away from Steinberg is a welcome change; I don't really care which one takes precedence, but official JUCE support tends to work way better than any third-party patches anyone makes.
The Linux world is starting to make the final strides of a really big change from X11 to Wayland, too, so keeping up to date is an absolute necessity in my eyes. I'm even aware of one DAW that has made the move to Wayland, which is REALLY unusual.

I'll be waiting for that blog post.

It has been around (or over, I didn't count exactly) a year since this was last mentioned.
JUCE 7 adds support for a plugin format that has some wider adoption lately; this was one of the main reasons it finally got added.
Christoph appears to believe CLAP will be the format that wins out, which is fine, but JUCE themselves would have to add support for that too - which would again mean updating to a newer version of the framework. I think it would cause less technical debt to keep up-to-date with JUCE in the meantime.
In addition, I believe they have been slowly working towards Wayland support on Linux, such as decoupling X11 windowing code - this WILL have to happen eventually.
Is there any reason there's not been much movement here?

@d-healey
Interesting. Is there no way to access data from the extension's host?

@d-healey
I'm afraid that doesn't exactly clear up my confusion - is that from within the full extension or from the plugin hosting the extension? As in, does the extension have to have the feature to unload itself with a button, or does the plugin have to provide that?

My understanding so far is that it overrides EVERYTHING that was originally in the project.

Just had another thought - if a full expansion essentially replaces everything else going on in the project, how do you 'reset' things? For example, if you want to load a different expansion?

@d-healey
This begs the question whether full expansions can have smaller sub-expansions.

@d-healey
https://docs.hise.audio/working-with-hise/project-management/expansions/index.html#features
Under 'active expansion'
It's the first result after searching 'expansion' in the documentation

@d-healey
'no different than any other expansion'
The documentation on expansions implies otherwise - what's the deal with that?
It explicitly states multiple can be loaded, but there is the concept of an 'active expansion'.

There's documentation on expansions, but nothing about 'full instrument' expansions - how they work, whether you can load multiple at a time, how that works with saving parameters (as in when the project in the DAW is saved)

Do they just override everything already present, or load in a new container, or what? Somewhere on D. Healey's channel I read he planned on releasing a video about this, but that doesn't seem to have happened yet.