Plans for floem 0.3?

[lkdjfhsd]

It's been 1 year since floem 0.2 release and this project is still being actively maintained. Is there any release for 0.3?

[ansarizafar]

I am evaluating Rust UI frameworks for building my next business app. Florem looks perfect for my use case. I don't mind working on the bleeding edge but I want to know the current project status and ETA for v 1.0.

[Third-Thing]

A v0.3 milestone exists, but the issue/PRs appear to be stagnating, and it's not clear to me if @jrmoulton's more recent work is connected or if they have abandoned the milestone.

Several releases worth of work has happened since v0.2: Parley integration, skia as an alternative backend, the performance improvements, and other things warranted releases on their own.

I'd merge the pull requests that are ready, patch known bugs, create a v0.3 branch and publish a release candidate. I'd set any other significant but incomplete projects (e.g. Access Kit integration) as primary goals for v0.4.

I could help with squashing bugs, testing, reviewing, writing release notes, etc - if desired.

[jrmoulton]

@ansarizafar floem is under active development. I am using it personally and plan to continue working on Floem. I would recommend that you use main over v0.2.0 but main will continue to have changes. I'd like to get out a 0.3.0 release and am working on it but personally I need things fixed, not a release so I haven't been able to dedicate time to doing a release. V 1.0.0 is unlikely to happen any time soon. (probably not in the next 2-4 years). Floem is in a good place but GUI in rust is still evolving.

[ansarizafar]

@jrmoulton Thanks for the update. I am using main and I am really impressed. After evaluating every other Rust Ui library, I think, I have found, what I was looking for.
I will also use floem-shadcn and floem-tailwind in my new business app.

[jrmoulton]

floem-shadcn and floem-tailwind probably both need some work. They were never finished to the point of being announced. And I think there are quite a few things that don't work or are not optimal. But the code there is useful and you can use the useful parts

[ansarizafar]

@jrmoulton Is there any plan to make floem-tailwind, floem-shadcn production ready in near future. These projects will greatly help in building polished apps with floem. I request you to please spare sometime for these essential projects from you busy schedule. I am new to Rust/floem and I badly need them for my P2P business app project.

[jrmoulton]

I'm not sure. I wasn't the one building them. And I don't have any time to commit to them

[Third-Thing]

@jrmoulton What do you need fixed and what's your motivation for fixing it? That would help us understand what changes to expect and what needs to be coordinated around.

[jrmoulton]

I'm working on rendering, frame pacing, and compositing. The motivation is correct architecture for performance and usability

[luan-coelho]

Hi! I'd like to contribute. Are there any open issues or areas where help is needed to move toward 0.3? Happy to pick something up.

[leomeinel]

Hello, first of all thanks for this awesome project.

I would recommend that you use main over v0.2.0 but main will continue to have changes. I'd like to get out a 0.3.0 release and am working on it but personally I need things fixed, not a release so I haven't been able to dedicate time to doing a release.

@jrmoulton I do very much understand that and generally think that this is how it should be done.
However with crates.io not allowing published crates to rely on github dependencies but only dependencies on crates.io itself that currently prevents crates that want to publish from using any recent features.

Have you considered this and would maybe just publishing alpha/beta/rc(release candidates) be considered? This would allow me to use this library for a simple app I've published on crates.io.

[panekj]

We have git dependencies so it's not even possible to publish right now

[leomeinel]

We have git dependencies so it's not even possible to publish right now

Thanks for the fast feedback.

Yeah, I wasn't aware of that previously, but all some git dependencies are the following:

• https://github.com/lapce/winit (single package)
• https://github.com/jrmoulton/understory (5 packages)

Since all are either owned by lapce or jrmoulton, it would at least be an option for floem. I do however understand if that's not what contributors here want to prioritize.

Edit

There are also more git dependencies in additional workspace members. But I generally think it would make this much easier to use.

I will most likely use floem anyways and halt publishing until a new version is released since I really like the api and the concept of floem.

[martinsotirov]

@jrmoulton, is there a new Milestone where progress is tracked towards v0.3? How can we support you? What's still open? What's on the roadmap for v0.3?

[jrmoulton]

I've got a lot of things that I thought were going to make it into v3 but now I don't think will. I've made a ton of changes to Floem that I've needed for my project but they are all still experimental and not cross platform. So I think right now I'd be good to just do what needs done to get Floem releasable and to make a release. That means getting off of git dependencies. That should I think just be moving the the crates.io winit beta and switching to upstream understory. There are still a few things that need upstreamed into understory or we need to work around it. I am working on floem every day but not currently doing those things for release. If other people want to drive getting things releasable that would be great. I'll publish a release as soon as it's possible. And I can help with upstreaming things if other people are driving it.