Gradual Transition to JUCE 8 WebView?

[sonictolfa]

Hi, I am really interested in the new WebView functionality in JUCE 8. I think it could make GUI testing much easier. However, I have a really complicated UI which would take months to refactor. Could I gradually replace existing components with webview components or is it best to transition all components at once so it’s more like a single page web app?

Cheers,

Chris

[ttg]

You should look around the forum there are many topics related such as:

WebView vs JUCE graphics

Now that we have good support for web views in JUCE, and we also have some nice graphics enhancements in JUCE 8, I’ve come back to a question that I’ve had hanging for a while now: What are the pros and cons of creating a plugin UI with web views, and in what situations might one be preferable over the other? I have some thoughts on this myself but I’d like to open it up to the community.

The biggest challenges with “mixing” web views with existing code would be:

• layering: you won’t be able to overlay on WebView with opacity for example.
• keyboard/mouse/touch input - WebViews is also tricky when it comes to mixing user input.

Also,
JUCE8 is getting many welcomed improvements to its own graphics abstraction (re-designed font/text support, Direct2D).

[sonictolfa]

Thanks for the info and cheers for linking that thread.

The biggest challenges with “mixing” web views with existing code would be:

• layering: you won’t be able to overlay on WebView with opacity for example.
• keyboard/mouse/touch input - WebViews is also tricky when it comes to mixing user input.

This would make mixing and matching JUCE UI code with WebViews quite difficult.

JUCE8 is getting many welcomed improvements to its own graphics abstraction (re-designed font/text support, Direct2D).

Good point! I would prob be best off sticking with my current JUCE GUI rather than starting again with WebView. Maybe I will have a play with WebView for my next project.

[Toddler-Boy]

@sonictolfa why did you “like” the previous reply? It’s devoid of all information and is obviously AI generated nonsense.

You already found out that mixing web views and JUCE components is not really possible, so suggesting a “let’s replace a couple of components with webviews” is not really a viable solution. So why like the nonsense AI statement?

[sonictolfa]

I initially liked it because I appreciate it when people take the time to reply (even if it isn’t that helpful). It’s been a long week already, so it took me a second read to realize it was a generic AI response.

I thought about removing it but figured it wouldn’t hurt to leave it. I can’t seem to remove it now but I will try to be less affectionate towards the AI next time.

Cheers for reminding me why I don’t like posting on forums.