[Core] Experimental Core API (?) #493
Open
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.
Ignore the
CLAY_NAMEDstuff, that is a duplicate implementation of #492 and will get removed once it's merged.In my experience rolling out my own immediate mode UI libraries, I have gravitated towards having a core layout engine which you can hook into to do things at different times in the pipeline. Be it rendering, input and whatnot.
I don't expect this to be merged in as it's incomplete first of all, but I believe this kind of API could allow the debug visualization, rendering, input and more to be separated from the core. I believe you are working towards that and here are my two cents on that.
I would love feedback on this, especially regarding how it would interact with floating elements. I am almost 100% sure that, as it is, it won't work in some corner cases.
Stripped down input example: