What's the approach for sharable and reusable component library in Slint?

[Apollo-Roboto]

So far I haven't found any community made component library for Slint. And that makes me wonder, how do I even compile and share my own Slint component for reuse across different projects?

I could always copy paste, but complex component sometimes have associated Rust code, which can be many files to handle, and obviously you can't push updates this way.

So, how have developers been approaching component reuse?

[Vadoola]

There are a couple that I'm aware of, but not many. If i recall they added support a while backing for importing a collection of widgets from another folder, I don't recall the details at the moment. Only one of the apps I've created with Slint required some more complex custom widgets, but they were fairly specific to the app. While they are somewhat reusable they are all within in that one app and I never extracted them into anything else.

https://codeberg.org/flovansl/co_sl/src/branch/main/widgets/coop/

https://lib.rs/crates/vivi_ui

https://github.com/Surrealism-All/SurrealismUI

Edit here is a link about the Component Library support: https://docs.slint.dev/latest/docs/slint/guide/language/coding/file/#component-libraries

[hunger]

Feel free to contribute well working widgets straight to upstream slint :-) We could definitely use some more of those.

Pure slint widgets are pretty straight forward to do. It does get tricky once you need backend code in rust for parts of the implementation though. We have no good story for how to consume that yet.