Improve "Online Manual" Operator for Tools and Options #37479

Closed
opened 2013-11-15 20:14:43 +01:00 by Jonathan Williamson · 17 comments

The current method to view documentation for specific tools is a bit worthless. There's no explicit lookup happening to direct the user to the exact documentation page, and so generally the user is sent to a generic page and then must find the specific tool/option documentation from there. For anyone that's not familiar with the documentation this leaves them at a lost, unable to find what they need. Effectively making the Online Documentation operator worthless.

For Example
The Knife mesh tool documentation goes to [Modeling/Meshes ]], when it should go to [ http:*wiki.blender.org/index.php/Doc:2.6/Manual/Modeling/Meshes/Editing/Subdividing/Knife_Subdivide | Modeling/Meshes/Editing/Subdividing/Knife_subdivide .

Proposal
Explicitly set the URL for all operators. This gives more burden to the developers of said operator, but ensures accurate documentation links for that operator. This is also something that junior developers (such as myself) can easily maintain.

The current method to view documentation for specific tools is a bit worthless. There's no explicit lookup happening to direct the user to the exact documentation page, and so generally the user is sent to a generic page and then must find the specific tool/option documentation from there. For anyone that's not familiar with the documentation this leaves them at a lost, unable to find what they need. Effectively making the **Online Documentation** operator worthless. **For Example** The Knife mesh tool documentation goes to [Modeling/Meshes ]], when it should go to [[ http:*wiki.blender.org/index.php/Doc:2.6/Manual/Modeling/Meshes/Editing/Subdividing/Knife_Subdivide | Modeling/Meshes/Editing/Subdividing/Knife_subdivide ](http:*wiki.blender.org/index.php/Doc:2.6/Manual/Modeling/Meshes). **Proposal** Explicitly set the URL for all operators. This gives more burden to the developers of said operator, but ensures accurate documentation links for that operator. This is also something that junior developers (such as myself) can easily maintain.
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscribers: @JonathanWilliamson, @brecht

Added subscribers: @JonathanWilliamson, @brecht

Added subscriber: @katsbits

Added subscriber: @katsbits

Aren't tools and operators given unique URL identifiers by default or are they largely generic (how many link to the same page when they should link to specific information)? Are the numbers known?

Aren't tools and operators given unique URL identifiers by default or are they largely generic (how many link to the same page when they should link to specific information)? Are the numbers known?

Removed subscriber: @katsbits

Removed subscriber: @katsbits

Added subscriber: @katsbits

Added subscriber: @katsbits

Added subscriber: @koilz

Added subscriber: @koilz

The operators and properties have a python pointer.
bpy.ops.mesh.knife_tool
So the doc id is 'bpy.ops.mesh.knife_tool'.

http://developer.blender.org/diffusion/BA/browse/master/modules/rna_wiki_reference.py

So here:
line 303: ("bpy.ops.mesh.", "Modeling/Meshes"),
You add:
line 303: ("bpy.ops.mesh.
", "Modeling/Meshes"),
line 304: ("bpy.ops.mesh.knife_tool", "Modeling/Meshes/Editing/Subdividing/Knife_Subdivide"),

303 is generic, 304 is specific.

'(how many link to the same page when they should link to specific information)? Are the numbers known?'

Most at the moment are generic, most mesh operators go to the Modeling/Meshes page without a specific link.

The operators and properties have a python pointer. bpy.ops.mesh.knife_tool So the doc id is 'bpy.ops.mesh.knife_tool'. http://developer.blender.org/diffusion/BA/browse/master/modules/rna_wiki_reference.py So here: line 303: ("bpy.ops.mesh.*", "Modeling/Meshes"), You add: line 303: ("bpy.ops.mesh.*", "Modeling/Meshes"), line 304: ("bpy.ops.mesh.knife_tool", "Modeling/Meshes/Editing/Subdividing/Knife_Subdivide"), 303 is generic, 304 is specific. '(how many link to the same page when they should link to specific information)? Are the numbers known?' Most at the moment are generic, most mesh operators go to the Modeling/Meshes page without a specific link.
Author
Member

@koilz, so it seems to me that we just need to go in and update the rna_wiki_reference.py for each tool that needs a specific entry? Which is most. @brecht, is that correct? If so then this is something I can start doing.

@koilz, so it seems to me that we just need to go in and update the rna_wiki_reference.py for each tool that needs a specific entry? Which is most. @brecht, is that correct? If so then this is something I can start doing.
Author
Member

@koilz, it should be noted that you actually need to reverse line 303 and 304, or else knife_tool will satisfy line 303 first and still just go to Modeling/Meshes.

@koilz, it should be noted that you actually need to reverse line 303 and 304, or else knife_tool will satisfy line 303 first and still just go to Modeling/Meshes.

Yup, it seems there is actually a list but it's in the addons repository so missed that at first. I actually already committed a patch by @koilz to update the shape key operators (D27: wiki manual - shape keys), and I'm happy to commit more.

This is something that's fairly easy for people to start contributing to. Note how using * wildcards you can avoid adding entries for each individual operator, see [how the diff was simplified in D27 ](http://developer.blender.org/D27?vs=56&id=63&whitespace=ignore-all#toc) using wildcards.

Yup, it seems there is actually a list but it's in the addons repository so missed that at first. I actually already committed a patch by @koilz to update the shape key operators ([D27: wiki manual - shape keys](https://archive.blender.org/developer/D27)), and I'm happy to commit more. This is something that's fairly easy for people to start contributing to. Note how using * wildcards you can avoid adding entries for each individual operator, see [how the diff was simplified in [D27](https://archive.blender.org/developer/D27) ](http://developer.blender.org/D27?vs=56&id=63&whitespace=ignore-all#toc) using wildcards.
Author
Member

@brecht okay cool. Then if it's alright I'll start working on manual entires for the mesh operators. I agree wildcards are good, but for somethings they've been too over zealous. For example, a single wild card for all mesh operators is silly :) But for things like each of the various Shapekey operators, it makes good sense.

@brecht okay cool. Then if it's alright I'll start working on manual entires for the mesh operators. I agree wildcards are good, but for somethings they've been too over zealous. For example, a single wild card for all mesh operators is silly :) But for things like each of the various Shapekey operators, it makes good sense.
Author
Member

Some progress on this one. I have begun updating the manual references to point to the correct tool, rather than being general.

First up, the 3D View toolbar mesh operators: blender/blender-addons@8da66b2936

Some progress on this one. I have begun updating the manual references to point to the correct tool, rather than being general. First up, the 3D View toolbar mesh operators: blender/blender-addons@8da66b2936

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Going over User Interface tasks and there's quite a lot of vague "area needs improvement" tasks.

These just stay open and don't have clear conclusion... since this task was opened we've updated and added manual links, yet many more could be added too.

I would like to see tasks like this have a clear scope (list exactly what needs doing), or be closed.

Going over *User Interface* tasks and there's quite a lot of vague *"area needs improvement"* tasks. These just stay open and don't have clear conclusion... since this task was opened we've updated and added manual links, yet many more could be added too. I would like to see tasks like this have a clear scope (list exactly what needs doing), or be closed.
Author
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Jonathan Williamson self-assigned this 2016-03-08 16:29:41 +01:00
Author
Member

Good call @campbellbarton. I'll close and create new, more specific ones as they come up

Good call @campbellbarton. I'll close and create new, more specific ones as they come up
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
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
5 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#37479
No description provided.