WIP: updated code-layout diagram #106475

Draft
Campbell Barton wants to merge 1 commits from ideasman42/blender:pr-code-layout-diagram into main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.

Add a utility to generate a diagram showing an overview of Blender's code-base, updating the old code-layout diagram from: https://www.blender.org/bf/codelayout.jpg


See: updated image

Rationale

The original diagram was a quick way to get an overview of a large code-base, wile not entire accurate (bad level calls for e.g.), it's helpful to show a top-level view of the code-base.

TODO

  • Support validating the diagram against Blender's code-base for completeness.
  • Some descriptions should be improved (this is a first pass).
  • Add command line argument parsing (to set the output file).
  • Minor code-cleanup.

Open Topics

  • We might want to list ../lib/ elsewhere as it's now quite large and not something users will encounter when navigating the code-base.

Further Work

We might consider having a README in each of these directories which is used as a data-source. It's convenient to update, useful for anyone navigating the code-base and means this information doesn't have to be copied between this diagram & https://wiki.blender.org/wiki/Source/File_Structure
Although we would most likely have to use a convention to support extracting a summary for the purpose of the diagram.

Add a utility to generate a diagram showing an overview of Blender's code-base, updating the old code-layout diagram from: https://www.blender.org/bf/codelayout.jpg ---- See: ![updated image](https://download.blender.org/ftp/ideasman42/pics/code_layout.webp) #### Rationale The original diagram was a quick way to get an overview of a large code-base, wile not entire accurate (bad level calls for e.g.), it's helpful to show a top-level view of the code-base. #### TODO - Support validating the diagram against Blender's code-base for completeness. - Some descriptions should be improved (this is a first pass). - Add command line argument parsing (to set the output file). - Minor code-cleanup. #### Open Topics - We might want to list `../lib/` elsewhere as it's now quite large and not something users will encounter when navigating the code-base. #### Further Work We might consider having a README in each of these directories which is used as a data-source. It's convenient to update, useful for anyone navigating the code-base and means this information doesn't have to be copied between this diagram & https://wiki.blender.org/wiki/Source/File_Structure Although we would most likely have to use a convention to support extracting a summary for the purpose of the diagram.
Campbell Barton force-pushed pr-code-layout-diagram from ad0a888f96 to 6c861e8f5f 2023-04-03 04:07:29 +02:00 Compare
Member

I did some work mapping out the deps between libs for D12122

It's probably better to make this new updated graph logical or how we want it to be rather than trying to base it on reality, which is.... yeah.....

https://archive.blender.org/developer/file/10266/10266294/full.png

red lines are circular dependencies, dependencies are modeled upon the import/exports out of the static libs.

I did some work mapping out the deps between libs for [D12122](https://archive.blender.org/developer/D12122) It's probably better to make this new updated graph logical or how we want it to be rather than trying to base it on reality, which is.... yeah..... https://archive.blender.org/developer/file/10266/10266294/full.png red lines are circular dependencies, dependencies are modeled upon the import/exports out of the static libs.
Campbell Barton force-pushed pr-code-layout-diagram from 6c861e8f5f to 4653173ed7 2023-04-03 12:51:47 +02:00 Compare
Campbell Barton force-pushed pr-code-layout-diagram from 4653173ed7 to b5969df65e 2023-04-05 05:53:56 +02:00 Compare
This pull request is marked as a work in progress.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u pr-code-layout-diagram:ideasman42-pr-code-layout-diagram
git checkout ideasman42-pr-code-layout-diagram
Sign in to join this conversation.
No reviewers
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#106475
No description provided.