API: images, use external image with sphinx 1.6 #51473
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#51473
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?
Once sphinx 1.6 is out we should consider using remote images. The downside is they will not be available if the user downloads the zip and has not internet connection. We can then host the images in rBM
Changed status to: 'Open'
Added subscriber: @Blendify
Added subscribers: @mont29, @ideasman42
I'd assume remote images adds some complications to managing images (adding / removing / checking what images from some spesific revision looks like).
Currently, the only images in use are on this page: https://docs.blender.org/api/current/info_tutorial_addon.html
Another solution would to simply remove all images from the API docs.
The benefits: gives everyone easy access to the images apposed to right now we get compiling warnings about missing images unless we download them from a previously build of the docs
The downsides: The downside is they will not be available if the user downloads the zip and has no internet connection. Another issue would be that we need to keep images URL the same after that build is up (no renaming images). Images must also live in svn forever.
What will the figure/image URL look like before/after: Before: https:*docs.blender.org/api/current/_images/spacebar.png After: https:*svn.blender.org/svnroot/bf-blender/2.78/images/spacebar.png
How would this impact building PDF: unknown but should work just the same. If not we report the bug to sphinx.
Tsk, my bad was thinking this was related to the manual. +1.
Since we have so few images or so, and they aren't really essential for the API docs so prefer keeping them remove instead of putting images in Blender's git repo.
Changed status from 'Open' to: 'Archived'
We decided to host this doc on the manual instead.