Export UV Layout is an add-on document it as such? #54429

Closed
opened 2018-03-26 22:19:51 +02:00 by Aaron Carlisle · 8 comments
Member

https://docs.blender.org/manual/en/dev/editors/uv_image/uv/editing/layout.html#export-uv-layout

is actually an addon but we document it like it is an eternal feature.

This might be a larger question but how do we document add-ons enabled by default.

https://docs.blender.org/manual/en/dev/editors/uv_image/uv/editing/layout.html#export-uv-layout is actually an addon but we document it like it is an eternal feature. This might be a larger question but how do we document add-ons enabled by default.
Author
Member

Added subscriber: @Blendify

Added subscriber: @Blendify

Added subscriber: @brecht

Added subscriber: @brecht

I think addons that are enabled by default should be documented as builtin features. It's basically an implementation detail if it's an addon or not, why should the user care?

The fact that it's an addon only matters in that it can be disabled, but that's not important I think.

I think addons that are enabled by default should be documented as builtin features. It's basically an implementation detail if it's an addon or not, why should the user care? The fact that it's an addon only matters in that it can be disabled, but that's not important I think.
Author
Member

Added subscribers: @VukGardasevic, @ideasman42

Added subscribers: @VukGardasevic, @ideasman42
Author
Member

I do not have a strong opinion here but I think we should keep this information in the manual. Having it elsewhere can make it harder to find. This, however, would also mean that we should port all the import/export add-ons to the manual. @VukGardasevic @ideasman42 Any thoughts here?

I do not have a strong opinion here but I think we should keep this information in the manual. Having it elsewhere can make it harder to find. This, however, would also mean that we should port all the import/export add-ons to the manual. @VukGardasevic @ideasman42 Any thoughts here?

I think that adding a notice box about it being an add-on with the default name / category could be enough. Just in case if for some reason, the user has disabled it.
The inclusion of documenting all the default start-up add-ons could be postponed until the 2.8 finalization.

I think that adding a notice box about it being an add-on with the default name / category could be enough. Just in case if for some reason, the user has disabled it. The inclusion of documenting all the default start-up add-ons could be postponed until the 2.8 finalization.
Author
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Aaron Carlisle self-assigned this 2018-08-02 19:35:35 +02:00
Author
Member

Fixed

Fixed
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 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#54429
No description provided.