roadmap, future and breaking changes ?

[moolight-seashell]

After experimenting quite a bit with Slint, I must say I’m genuinely impressed by this technology
both in terms of its capabilities and tooling.

That said, even without considering some of the missing features, there seem to be two major pain points at the moment:

1. Layout inconsistencies
   Layouting behavior can be somewhat unpredictable and has known issues, such as:
   • the "if true” issue (layouting constraints not respected for items in if or for #407)
   • the Inconsitant layouting (Inconsitant and unexplicit backward sizing overwrite #9134)
2. Scalability and dynamic composition
   The need to re-export all APIs in the main Slint file, combined with the inability to dynamically modify the DOM, makes it difficult to design large-scale or modular UIs.
   Dynamic composition of application parts #959

Given that these issues are already known and discussed, I’m wondering about the long-term roadmap:

Can we expect a major new version at some point that might address these issues (by bringing, I suppose, quite a few breaking changes)?

If so do we have any idea of a time frame for these changes ?

Because these two points are currently reasons for me not to use slint in my projects, and I think that's too bad.

[tronical]

Thanks for the feedback :)

Can we expect a major new version at some point that might address these issues (by bringing, I suppose, quite a few breaking changes)?

At this point we're not planning for breaking changes, or rather: We're trying to maintain compatibility.

Eventually we'll need to making some breaking changes, but I don't think we're there yet. (as a side-note, we've got a breaking changes label in the issue tracker)

The need to re-export all APIs in the main Slint file, combined with the inability to dynamically modify the DOM, makes it difficult to design large-scale or modular UIs.

There are two areas where we intend to invest time in next year: Our Rust API that results from .slint files (that includes the way of interacting with it), as well as modularity in general (the ability to invoke the slint compiler multiple times). We will do experiments and implementation along the way in the repo, and it will of course be visible and public.