You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Masonry's documentation has only received piecemeal updates since the port to Winit.
Even when the documentation is still accurate, it lacks overall cohesion. There isn't an ordered document explaining the major concepts users need to know to understand Masonry's flow.
Once other major changes are implemented, the documentation should be brought up to date. We should avoid procrastinating on documentation too much just because the architecture is still in progress.
The text was updated successfully, but these errors were encountered:
This is a very messy, very basic skeleton of what Masonry documentation
will eventually look like.
Main points are:
- Dedicated documentation modules.
- Re-using most of the language from the RFCs.
Next steps are:
- Flesh out the Widget documentation.
- Rewrite all those docs in a less placeholder-y way.
- Add chapter about the widget arena.
- Spread out that pass documentation to the respective pass files.
- Rewrite ARCHITECTURE.md.
- Add screenshots.
Fixes#376 and #389.
---------
Co-authored-by: Daniel McNab <[email protected]>
Masonry's documentation has only received piecemeal updates since the port to Winit.
Even when the documentation is still accurate, it lacks overall cohesion. There isn't an ordered document explaining the major concepts users need to know to understand Masonry's flow.
Once other major changes are implemented, the documentation should be brought up to date. We should avoid procrastinating on documentation too much just because the architecture is still in progress.
The text was updated successfully, but these errors were encountered: