From f9e6283c5b0337b11a6115153ef7703cfbd9e3c0 Mon Sep 17 00:00:00 2001 From: jimgoog Date: Mon, 15 Mar 2021 09:33:11 -0700 Subject: [PATCH] Wordsmith swing interop API description (#500) We've been seeing an antipattern where people are literally "passing a view/jcomponent" into the interop API by merely referencing the native object in the factory lambda. This usage is very much an antipattern. Wordsmithing a bit to avoid putting that idea into people's minds. --- tutorials/Swing_Integration/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorials/Swing_Integration/README.md b/tutorials/Swing_Integration/README.md index efd32125c8..732e919504 100644 --- a/tutorials/Swing_Integration/README.md +++ b/tutorials/Swing_Integration/README.md @@ -149,7 +149,7 @@ fun Counter(text: String, counter: MutableState) { ## Adding a Swing component to CFD composition using SwingPanel. -SwingPanel lets you create a UI using Swing components in a Compose-based UI. To achieve this you need to create Swing component and pass it as a parameter to SwingPanel. +SwingPanel lets you create a UI using Swing in a Compose-based UI. To achieve this you need to create Swing `JComponent` in the `factory` parameter of `SwingPanel`. ```kotlin import androidx.compose.desktop.SwingPanel