libcosmic VS cglue

That said, a lot of the things we're working on are still in development within our development fork of iced, so they are not yet published for code review. And COSMIC-specific work is in libcosmic, which depends on that.

GUI frameworks: Iced and Slint can be used for making Cosmic apps. You can pull libcosmic into a project to get the COSMIC integration for Iced.

https://github.com/pop-os/iced/pull/2 https://github.com/pop-os/libcosmic/pull/17 https://github.com/pop-os/libcosmic/pull/16 https://github.com/pop-os/libcosmic/pull/15

You can check out the code here: https://github.com/pop-os/libcosmic

COSMIC will let users customize the desktop in the form of Applets. They wouldn’t work like the very-flexible custom scripting in GNOME though, because it could lead to instabilities when the system updates and collateral damage. Applets would be kind of what they are in Linux Mint: an extension attached to the dock or panel.

Shameless plug - you may want to check out cglue, which lets you mix and match rust versions, and even implement plugins in other languages like C++: https://github.com/h33p/cglue

You can grab CGlue from my GitHub.

I honestly wouldn't say that much has changed during this year. I do see some progress on new libraries like xlang_abi, safer_ffi or cglue, but it's still too early to know, and existing ones like abi_stable move quite slowly.

You might wanna take a look at cglue: https://github.com/h33p/cglue

Importing Rust is the same process as you'd use to import a C library, but there's a lot of people actively invested in this area so there's likely already automated tooling of some sort. Google uses https://cxx.rs for automating C++ bindings to Rust libraries, and lately there's been experiments like cglue to automate C bindings.

I'm proud to announce one final CGlue release for this year, the highlight being ability to use layout_checks feature on non-git builds!

I have just added pre-generated headers, they are now on the repo. Yup, certainly not the cleanest, some whitespaces need fixing, but it wasn't the highest priority as it didn't affect functionality.

Depending on how big your API surface is (and how trait heavy it is), you may want to look into [shameless_plug] automatically generating it with cglue. That's what we did for memflow. [/shameless_plug] It's goals are not much different from abi_stable (in fact, rather a small subset of it focused on traits), but does create C-compatible code.

It seems like we are trying to solve roughly the same problems when it comes to loading plugins and keeping it all ABI safe. Might be worth checking out CGlue (full disclosure: it's my project). While I do not have async trait support, it would be a really interesting challenge to tackle. The ultimate goal for the project is to be a dead simple code generator that would even allow to write plugins in C/C++, and I currently have sweeping changes underway to get it there.