[dev docs] Created the first pass at demystifying the layout system for debuggers and developers #1557
Conversation
This file contains 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
|
|
|
🚫 CI failed with log |
mikezucc
force-pushed
the
mz/layout-specs
branch
from
0f5d687
to
eb8f382
Compare
nguyenhuy
approved these changes
Jun 24, 2019
mikezucc
force-pushed
the
mz/layout-specs
branch
from
7c5f8e3
to
b3d924d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I took a first pass at getting this Layout Specs for developing doc together.
It uses the Layout Specs example project to show two sides of the layout process:
-[CALayer layout]Let me know what is wrong or should use some deeper dive here.