📐 Add layout constraint system #64
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
heytherewill
force-pushed
the
will/constraint-layout
branch
from
41e3814 to
2562964
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements a pretty basic, but extensible, layout constraint system.
Right now one can snap the UI on any of the four sides of the screen, center it vertically or horizontally and also force a width or height. We can implement relative layout and other constraints on future iterations.
I'm using the
CollisionComponentas the way of indicating the size while using aPositionComponentto indicate where on the screen the UI will be rendered. Do let me know if there are better candidates for either.Needless to say, this assumes the target batch is a UI batch, since values are based on the size of the screen and are ignoring the camera (though one could make it work by wrapping all components in a parent component that is aware of the camera and moves along with it).