swift-cross-ui

> Apple's on-device models for the AI? no. Apple on-device models are not suitable for such a task. It uses a different model (I don't stick to one model in particular, as it may change) > Does Swift have UI capabilities on Linux? No. there are projects inspired by SwiftUI: https://github.com/stackotter/swift-cross-ui or https://git.aparoksha.dev/aparoksha/adwaita-swift (GNOME)

As with other languages, you’d need bindings to another UI framework. In that sense, I wish SwiftUI had a different name because it seems intrinsic to Swift when it’s really no different than UIKit. There’s stuff like SwiftCrossUI that does multiple backend bindings https://github.com/stackotter/swift-cross-ui And Qt was exploring some bindings using the new C++ interoperability.

C++ isn't a text editor. Why would one want to use a non-lisp language within emacs? Zed[4] is fairly new. Swift as wrapper/unix io cli pipe feed around sed for interactive editing or pre/post process input/output to sed without the need to use/understand c++ just requires an understanding of unix cli, swift and just enough sed. Pretty easiy to add swift as an extension language to bashed[3]. Off the cuff guess: insufficient demand within main editor project for swift as language extension. Demand/use for supported extension languages within framework/ IDE / office suite (open office) does require significant/continuous time/effort to be supported within the main editor project. But why an extension language for text editor instead of using editor plugins / text transform dls? (where can insert call to swift program(s) to do transform wor

There's a couple: https://github.com/stackotter/swift-cross-ui (Linux + Windows) https://github.com/TokamakUI/Tokamak (WASM + MacOS + some Ubuntu support) They both had to rewrite the entire backend from scratch, because SwiftUI is very, very closed source. But Tokamak does have an import that just forwards to SwiftUI on Apple platforms.

There's not a consistent story but there are a bunch of options, principally divided into wrappers around existing libraries (SwiftGTK [1], Qlift [2], LVGLSwift [3]) and SwiftUI workalikes (Tokamak [4], SwiftCrossUI [5], AdwaitaSwit [6], there are others too). After exploring most of these for my use case (something that needs to run on an "embedded" RPi CM4 as well as iOS), I wrote a Swift bridge/runner for Flutter [7] which is working well. That enables me to write the UI in Dart and the business logic in Swift. I looked at all the other options below (that's how I know about them, indeed [3] I wrote as part of my research), in the end I felt that none of them were at the time of investigating sufficiently mature to base a product around. [1] https://github.com/rhx/SwiftGtk [2] https://github.com/Longhanks/qlift [3] https://github.com/

For another SwiftUI-like wrapper, see also https://github.com/stackotter/swift-cross-ui (used by Adawaita to generate widgets, and mentioned in other comments). The key premise of this approach is to provide a SwiftUI-like declarative wrapper around Gnome functionality. It's unclear what it adds over swift-cross-ui. SwiftUI itself has growing pains mainly around being on the right thread for processing/updates and getting data binding right. Blog entries on swift.org or from Apple tend to be little demos that show the happy path, but when discussing new frameworks (like a Gnome wrapper) or platforms (like the recent embedded), I'd like more demonstration that the authors understand and address key issues and will sustain development. Cross-platform UI frameworks get complicated quickly and have a long tail of issues (cf Flutter, Java/Ec

Other things worth checking: https://github.com/stackotter/swift-cross-ui https://github.com/TokamakUI/Tokamak I’m also working (slowly) on native Flutter channels: https://github.com/PADL/FlutterSwift But this is really targeted at embedded use cases.

Some interesting stuff happening here [1] and here [2] too. [1] https://github.com/stackotter/swift-cross-ui/tree/main [2] https://github.com/TokamakUI/Tokamak