cuicui_layout has now grown a lot. There is indeed several unrelated features under the same umbrella. We need to find a new home for them.
What to do
The cuicui book
Describes what each crate does, why you would want to use them
Identify the features they want to use and know how to use them
Get started quickly
Know where to learn more about the features they need.
Less inter-dependency
cuicui_layout should only optionally depend on cuicui_dsl and cuicui_chirp
the ui/sprite integration crates should split off the content_sized modules (probably into cuicui_layout as feature flags) so that they can be used independently of the dsl/chirp I've no idea what this means.
the ui/sprite crates should only depend optionally on cuicui_chirp
cuicui_dsl should probably only depend on bevy_ecs (depends on hierarchy)
Other considerations
It might also be wise to split out the crates into their own repo, so that they have more visibility individually.
cuicui_layout has now grown a lot. There is indeed several unrelated features under the same umbrella. We need to find a new home for them.
What to do
The
cuicuibookDescribes what each crate does, why you would want to use them
Less inter-dependency
cuicui_layoutshould only optionally depend oncuicui_dslandcuicui_chirptheI've no idea what this means.ui/spriteintegration crates should split off thecontent_sizedmodules (probably intocuicui_layoutas feature flags) so that they can be used independently of the dsl/chirpui/spritecrates should only depend optionally oncuicui_chirpcuicui_dslshould probably only depend onbevy_ecsOther considerations
It might also be wise to split out the crates into their own repo, so that they have more visibility individually.