Blender Manual: Develop a Script for Automated Screenshots #73397
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information 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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#73397
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, the manual has lots of images however these are very difficult to make (time-consuming) and keep up to date. We want to create a script to automate this as much as possible.
Some work was done to make this work for nodes already but this can be implemented better.
I want this to work for two areas to start with:
For the script, we want to name images by there class name:
.. figure:: /images/BONE_PT_transform.png
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @Blendify
Added subscriber: @ankitm
Automated Screenshotsto Blender Manual: Develop a Script for Automated ScreenshotsAdded subscriber: @JacquesLucke
Related work:
https://gist.github.com/JacquesLucke/65485586a86b2e1de6e3f3b92867947a
rBM5111, rBM5112
Added subscriber: @rdmo
Added subscriber: @HUSCH
Attempt to improve the screenshot-creation process
Problem: the Blender docs contain many (annotated) screenshots. Updating these screenshots because of UI changes is difficult, especially if they are annotated (arrows, text, …). Most of the time, it requires the complete recreating of the Blender model with the specific user interface (zoom level, …), and re-adding the annotations.
Possible solution: each image in the docs has an accompanying blend-file that contains all the info to (re)create the screenshot. So, for each image in the docs, there are two files: xxx.blend and xxx.png.
Steps to (re)create the doc-image
Render final-scene and save the render as a png-file with the same name as the blend-file.
If anything has to be changed/updated later-on:
See attached blend-file for an example with the accopanying png-render output.
editors_vse_sequencer_timeline_sequencer.blend
Questions