一键在 Manus 中运行任何 Skill

开始使用

javafx-web-maps-embedded-integration

星标1

分支0

更新时间2026年6月6日 09:58

Integrate JavaFX with JavaScript bridges, embedded browsers, maps, and browser-delivered JavaFX strategies.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

JohannesRabauer

JohannesRabauer/javafx-skills

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

JavaFX Web, Maps, and Embedded Integration

Use this skill when the app must bridge JavaFX state to JavaScript, embed browser-centric features, show maps with overlays, or evaluate browser-delivered JavaFX technologies.

Example

import netscape.javascript.JSObject;
import javafx.concurrent.Worker;
import javafx.scene.web.WebView;

public class BrowserBridge {

    public WebView createView() {
        var webView = new WebView();
        var engine = webView.getEngine();

        engine.getLoadWorker().stateProperty().addListener((obs, oldState, newState) -> {
            if (newState == Worker.State.SUCCEEDED) {
                JSObject window = (JSObject) engine.executeScript("window");
                window.setMember("javaBridge", this);
            }
        });

        engine.loadContent("""
                <html>
                <body>
                    <button onclick="window.javaBridge.log('clicked')">Call Java</button>
                </body>
                </html>
                """);

        return webView;
    }

    public void log(String message) {
        System.out.println(message);
    }
}

Setup notes

Keep core WebView or WebEngine setup in javafx-media-webview-3d; use this skill for bridge logic, embedded-browser workflows, maps, and web delivery decisions.
Decide early whether a map or browser feature is central enough to justify browser-centric packaging or debugging constraints.
Treat JavaScript bridges as an API surface with explicit ownership, not as a grab bag of callbacks.

Gotchas

Browser integration changes security, debugging, and packaging assumptions significantly.
Maps need stable ownership of layers, projection, markers, and overlay refresh timing.
Browser-delivered JavaFX and native desktop JavaFX are different deployment models, not skin-deep variants.

同仓库更多 Skills

同仓库

javafx-3d-modeling-printing

JohannesRabauer/javafx-skills

Build JavaFX 3D modeling tools and print/export workflows with isolated geometry generation and preview rendering.

2026-06-061

javafx-ecosystem-controls-productivity

JohannesRabauer/javafx-skills

Choose and integrate mature third-party JavaFX control libraries for forms, productivity widgets, theming, and developer workflow support.

2026-06-061

javafx-terminal-emulators

JohannesRabauer/javafx-skills

Build JavaFX terminal emulators or shell-style console panes with background process I/O, ANSI handling, and safe FX-thread updates.

2026-06-061

javafx-workflow-graph-editors

JohannesRabauer/javafx-skills

Build node-based JavaFX workflow editors, graph canvases, and visual programming surfaces with clean model separation.

2026-06-061

javafx-animation-canvas-render-loop

JohannesRabauer/javafx-skills

Animate JavaFX UIs with Timeline, Transition, Canvas, and AnimationTimer-based render loops.

2026-06-061

javafx-application-lifecycle

JohannesRabauer/javafx-skills

Manage the JavaFX Application lifecycle, primary stage setup, startup sequencing, and shutdown behavior.

2026-06-061

name	javafx-web-maps-embedded-integration
description	Integrate JavaFX with JavaScript bridges, embedded browsers, maps, and browser-delivered JavaFX strategies.
triggers	["webview javascript bridge javafx","javafx map view","jxbrowser javafx","webfx jpro javafx"]
compatibility	{"java":"17+","javafx":"21+"}
category	platform-integration
tags	["webview","javascript","maps","browser","integration"]
metadata	{"scope":"repository","maturity":"starter"}
allowed-tools	["view","rg","apply_patch"]

JavaFX Web, Maps, and Embedded Integration

Use this skill when the app must bridge JavaFX state to JavaScript, embed browser-centric features, show maps with overlays, or evaluate browser-delivered JavaFX technologies.

Example

import netscape.javascript.JSObject;
import javafx.concurrent.Worker;
import javafx.scene.web.WebView;

public class BrowserBridge {

    public WebView createView() {
        var webView = new WebView();
        var engine = webView.getEngine();

        engine.getLoadWorker().stateProperty().addListener((obs, oldState, newState) -> {
            if (newState == Worker.State.SUCCEEDED) {
                JSObject window = (JSObject) engine.executeScript("window");
                window.setMember("javaBridge", this);
            }
        });

        engine.loadContent("""
                <html>
                <body>
                    <button onclick="window.javaBridge.log('clicked')">Call Java</button>
                </body>
                </html>
                """);

        return webView;
    }

    public void log(String message) {
        System.out.println(message);
    }
}

Setup notes

Keep core WebView or WebEngine setup in javafx-media-webview-3d; use this skill for bridge logic, embedded-browser workflows, maps, and web delivery decisions.
Decide early whether a map or browser feature is central enough to justify browser-centric packaging or debugging constraints.
Treat JavaScript bridges as an API surface with explicit ownership, not as a grab bag of callbacks.

Gotchas

Browser integration changes security, debugging, and packaging assumptions significantly.
Maps need stable ownership of layers, projection, markers, and overlay refresh timing.
Browser-delivered JavaFX and native desktop JavaFX are different deployment models, not skin-deep variants.