Is there a good CMP code editor component? RSyntax...

# jewel

[fishy]

Is there a good CMP code editor component? RSyntaxArea works nearly perfectly but SwingPanel causes it to layout a frame delayed, which causes gaps in the layout, KodeMirror is buggy and complicated, SyntaxMP only does highlighting, and net.akehurst.kotlin.compose:code-editor is too bare-bones and not really what I want

[seb]

Not currently, no

[seb]

Best bet is embedding one of the Swing ones

[seb]

Second best bet is pointing Fable or Sol at one of the good Swing ones and asking it to replicate it in Compose, then hope for the best

[seb]

BTW Swing interop is better if you enable a few flags — I forget exactly which ones lol but the main one is the one we use everywhere we use Jewel in IJ — I think it was kotlinlang.org/docs/multiplatform/compose-desktop-swing…#…

[fishy]

It seems like compose.interop.blending is only supported on Windows and Mac, is that correct?

[fishy]

My main problem with embedding the Swing components is that they leave this slight gap in the layout when resizing (the one on the window edge is unfixable on my end, I think it's a skiko issue)

Screencast_20260827_141433.webm

[seb]

I know @Alexander Maryanovsky was working on improving the window edge artefacts for CMP 1.13, so that should be better

[seb]

And my bad, it's compose.swing.render.on.graphics not compose.interop.blending I was referring to

[seb]

The flag has one downside: on Windows and Linux (and macOS if not running on JBR) then redrawing is expensive because there's a texture copy GPU -> CPU -> GPU

[seb]

I'd like to improve that eventually, I know exactly how and have a working almost-prod-quality prototype, but it would require a lot of work — it needs a bunch of work in the JBR, but I am not sure they'd wanna do it. There's a stopgap solution, which is to implement the same shared textures mechanism the JBR shipped for macOS, to Windows and Linux too. Again, it depends on JBR being willing to do it, or at least take the contribution

[Alexander Maryanovsky]

My resizing fixes won't help with Swing interop. That's a direction @Ivan Matkov is working on.

[seb]

Yeah I meant they'd be useful for the window resizing, not for Swing interop :)

[fishy]

Doesn't compose.swing.render.on.graphics only apply to embedding Compose inside of Swing, not the other way around?

[seb]

As I said that helps with the window resizing issues

[אליהו הדס]

Why not klibs.io/project/SnipMeDev/Highlights ?

[seb]

I did not know it exists

[אליהו הדס]

I use it, it works very well

[seb]

But it doesn't seem to be an editor component?

[אליהו הדס]

github.com/SnipMeDev/KodeView they have that too, but it hasn't been updated in 2 years but I understood that he only needed highlight

[seb]

Yeah that'd not be enough for a proper editor component

[seb]

It's a part of it for sure tho

[אליהו הדס]

It's a very large library, it seems complicated for Fable or Sol to rewrite it directly in Compose, but forking KodeView seems much more realistic.

[seb]

It would be a fun experiment to put Fable/Sol to take one of the fully featured Swing editors and rewrite them in Compose but I think it would be difficult because a) tons of tokens, and b) swing UI usually has no test coverage and as such there's no solid ground truth to tdd off of

[אליהו הדס]

LLMs do a good job when they already have a good code base to work on and are supervised, because they tend to want to cheat or duplicate code, but in principle, from scratch, in my experience, it's not really great, especially since Swing doesn't resemble Compose at all.

[Alexander Maryanovsky]

Text editor sounds like it would be fun to write yourself.

[אליהו הדס]

the next benchmark for AI agents in 2028, rewrite intellig in compose 🙃

[seb]

Maybe Astra will be able to XD

[seb]

Everyone focusing on models doing 3D models now, next silly benchmark is porting Swing libraries to Compose XD

[אליהו הדס]

yes it's probably harder to rewrite swing in compose than to do 3d

[seb]

Tell me about that lol

[fishy]

KodeView just wasn't great to use, the documentation was incomplete, didn't match the actual behavior, and felt entirely AI generated, and it itself was complicated to use and very laggy. It seemed to lose a lot of usability in making itself extensible, so I think whatever I make would have a more monolithic architecture. I do want a full editor component that I can turn read-only, since I a. want to keep the possibility of editing decompiled class files and b. it feels better to navigate with shortcuts and stuff.

I was actually thinking about writing a code editor component yesterday. You know, how hard could it possibly be? (also I need an excuse to learn about ropes)

[fishy]

RSTA seems to work okay for now, so it'll wait until I finish the rest of the functionality of the app (assuming I do)