One strategy I found can make a big difference w.r.t. success or failure is to go in smaller steps.
Codex has completely changed the way I work. After less than an hour of design discussion and exploring options, I have agreed with Codex on a detailed, focused plan for how to add syntax highlighting to the new source editor.
Compositor for Windows 0.6
The next prototype of Compositor for Windows, release 0.6 is now available! 🎉
And here's soft line-wrapping in the Windows app.
Soft line-wrapping in the source editor is finally coming together. Took several attempts to get right, tricky stuff. Aiming for the 0.6 release in about a week.
https://github.com/ktraunmueller/Compositor/milestone/96I decided to pull the "Soft line wrapping in source editor" ticket into the Windows 0.6 release, because a lot of documents seem to require it. Sorry for the delay.
https://github.com/ktraunmueller/Compositor/milestone/96And here's source editor warnings & errors in the Windows app:
UI is absolutely my weak spot, I have to say in my defense 😅
Prototyping source editor warnings & errors in the macOS app. I guess that should work for a first iteration. I'll implement the missing UI on the Windows side next, and then call
https://github.com/ktraunmueller/Compositor/issues/659 done.
@stackotter Unrelated to the winrt discussion: if you want to do performance investigation on non-Apple platforms, tracy profiler (
https://compositorapp.com/blog/2026-02-07/Tracy/) may be of interest. I used it on Windows to have a close look at what's happening inside my app:
https://mastodon.online/@compositorapp/115994680723711729 
