API: images, use external image with sphinx 1.6 #51473

Closed
opened 2017-05-11 18:45:56 +02:00 by Aaron Carlisle · 8 comments
Member

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

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
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Author
Member

Added subscribers: @mont29, @ideasman42

Added subscribers: @mont29, @ideasman42
  • What are the benefits / whats this solve?
  • What are the down-sides?
  • What will the figure/image URL look like before/after?
  • How would this impact building PDF?

I'd assume remote images adds some complications to managing images (adding / removing / checking what images from some spesific revision looks like).

* What are the benefits / whats this solve? * What are the down-sides? * What will the figure/image URL look like before/after? * How would this impact building PDF? I'd assume remote images adds some complications to managing images (adding / removing / checking what images from some spesific revision looks like).
Author
Member

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.

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.

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.
Author
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Aaron Carlisle self-assigned this 2017-06-16 05:17:28 +02:00
Author
Member

We decided to host this doc on the manual instead.

We decided to host this doc on the manual instead.
Sign in to join this conversation.
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-addons#51473
No description provided.