JavaFX WebView

[vsquared]

Demonstrates a JavaFX WebView in the default Processing window.

# Uses Imported mode for py5

from javafx.scene.web import WebView

def setup():
    global pane,webView
    
    size(900, 600, FX2D)
    window_title('JavaFX WebView')
    canvas = get_surface().get_native()
    pane = canvas.getParent()
    webView = WebView()
    webView.getEngine().load('https://py5coding.org')    
    pane.getChildren().add(webView)

Output:

[hx2A]

I like this! Thank you, glad you are experimenting with this.

And this reminds me that I should update the homepage. I don't think it should still say that py5 is a "new version of Processing", as it has been publicly available for a few years now.

[vsquared]

I intend to continue using this technique. I did not realize that PSurfaceFX already had a root pane that could be accessed. It makes good sense to just use that pane in the default window instead of creating a separate new window with its own pane. The only downside that I see is that the Processing author chose to use a StackPane and I personally prefer just a 'regular' Pane so that I can position controls wherever I want with setLayoutX() and setLayoutY(). It remains to be seen if I can convince the new authors to allow the user to choose their own layout pane rather than being constrained to the StackPane with CENTER alignment. The 'pro' to most of the layout panes (there are several available) is that they dynamically reposition the controls with window resizing whereas the 'regular' layout Pane is static and the controls stay wherever they were positioned. The 'con' to the dynamic panes is the user is stuck with whatever the engineers coded for.
Addendum:
A regular Pane (or presumably any other type of layout pane) may be added to the StackPane to allow static control placement and therefore the type of root pane is not a problem. It will not be necessary to change the runtime.

[GoToLoop]

import javafx.scene.web.WebView

That import can be better targeted to just Webview: from javafx.scene.web import WebView
So webView = javafx.scene.web.WebView() can be shortened to just: webView = WebView():

# Uses Imported mode for py5
from javafx.scene.web import WebView

def setup():
    size(900, 600, FX2D)
    window_title('JavaFX WebView')

    global pane, webView
    pane = get_surface().get_native().getParent()
    webView = WebView()

    webView.getEngine().load('https://py5coding.org')
    pane.getChildren().add(webView)

[vsquared]

Thanks, I wondered about that; I tried webView = WebView(), but it didn't work the way I had the import syntax. After changing to from...import syntax it works as expected. Not sure why that's a better import technique (looks like the same thing to me), but it does work and I will edit the original post. I appreciate your help.

[GoToLoop]

Not sure why that's a better import technique

B/c after we do from pack.path... import class, we just need class(), rather than pack.path.class()

[vsquared]

I've had problems with javafx Button in the past. Do you have any idea why this fails:

Doesn't run in Thonny:

# Uses Imported mode for py5

from javafx.scene.control import Button

def setup():
    global pane,btn
    
    size(300, 200, FX2D)
    window_title('JavaFX Button')
    canvas = get_surface().get_native()
    pane = canvas.getParent()
    btn = Button('Push Me')
    pane.getChildren().add(btn)

ErrorMsg:

This runs ok:

# Uses Imported mode for py5

# Need something up here to load javafx
import javafx.scene.Scene

def setup():
    global pane,btn
    
    size(300, 200, FX2D)
    window_title('JavaFX Button')
    canvas = get_surface().get_native()
    pane = canvas.getParent()
    btn = javafx.scene.control.Button('Push Me')
    pane.getChildren().add(btn)

[GoToLoop]

#653 (comment)