Keep Morphorm or swap over to Taffy?

[StarArawn]

Should we keep the current Morphorm layout integration or should we move over to taffy for layouts? I'm hoping the community can help make a decision here. Morphorm hasn't been updated recently but Taffy is being actively developed.

[Hellzbellz123]

i dont really understand much, i just know i really don't like the current css style uis in bevy, with that said, taffy intending to support other layout algorithms and are currently implementing "css grid" while refactoring to make it easier to add new layouts and use multiple layout types in the same app DioxusLabs/taffy#28

[Commander-lol]

My £0.02, if this is still being considered - It would make sense to me to choose whichever would allow the most focus on the cool things that make Kayak different to other UI frameworks (Reactive bindings, a neat RSX impl, etc)

With Morphorm, it's looking like there will need to be a fork to fix some pretty important issues (E.g. #115 ). Using Taffy would guarantee some level of stability (or at least continuity), since it's being used for Bevy UI proper.

If the short term pain of switching to Taffy beats out the long term pain of forking/maintaining/patching Morphorm, I'd give it a thumbs up and be willing to pitch in to help with the transition, busy calendar allowing

[nicoburns]

I've just put together a write up on integrating Morphorm into Taffy: DioxusLabs/taffy#308. Obviously it hasn't been implemented yet, but hopefully in a few months time you will be able to depend on Taffy and get Flexbox, CSS Grid, and Morphorm layout under a single API and configured to interoperate with each other.