Group: Vaadin Swingbridge

Sort by:Popular▼

✓Popular✓Newest

Runtime emulation of the Swing API on top of Vaadin: the vaadinx.awt and vaadinx.swing classes a Swing application compiles against after rewriting its javax.swing imports, each storing Swing state, firing Swing events and driving a ...

IntentionallyStatic, the allowlist marker a migrated application's own source carries for the static-field gate. Zero dependencies by contract, so a UI-free service module can annotate its statics without acquiring a Vaadin ...

Vaadin components extended directly to reproduce one Swing component's behaviour in full. Used as the peers the emulators drive, and as the API a migrated view rewrites onto once it is ready to become Vaadin-shaped.

The tools run over a Swing application while following the Swing-to-emulators migration guide: a hazard scan, an import rewriter, and a static-field sweep, one per mechanical phase. Also published under the "dist" classifier as a ...

JCalendar 1.4's JDateChooser API on top of SwingBridge Emulators, so a migrated application keeps compiling after rewriting its com.toedter imports to vaadinx.toedter. A clean reimplementation over a Vaadin date picker, not a fork of ...

JGoodies Forms 1.2.1's FormLayout API on top of SwingBridge Emulators, so a migrated application keeps compiling after rewriting its com.jgoodies imports to vaadinx.jgoodies. A BSD-licensed fork of the upstream sources with the pixel ...

SwingBridge Emulators: a runtime emulation library of the Swing API running on top of Vaadin 25

Optional SwingBridge Emulators add-on: a virtual PDF printer implementing vaadinx.awt.print.PrinterJob, rendering a hand-crafted Printable to a PDF the browser downloads. A separate artifact so its PDFBox dependency stays off the ...

Optional SwingBridge Emulators add-on: the host-app wiring a migrated app needs on Spring Boot — a SpringServlet with a virtual-thread-aware session lock, and an auto-configuration that registers it and SwingBridgeEmulatorsBootstrap. ...

MigrationGuardrails: the three post-migration build gates — every static field provably immutable or explicitly allowlisted, no UI component in a static field, no JVM exit — as one class a migrated application calls from its own test ...