On Wed, Oct 26, 2011 at 3:35 PM, Harley Acheson
harley.ache...@gmail.com wrote:
we don't want one doc for bpy.ops.texture.slot_move, better glob
bpy.ops.texture.slot_*, or bpy.ops.texture.* and then link to a
page explaining about blender texture system.
I'd say we do. And I'd say that
I thought of this a long time ago. I am really in favor of this. If there is
a concern with increased traffic, maybe a local copy of the wiki can be
downloaded and updated, but that sounds like a solution that may be harder
to implemt than the feature is worse.
+1 on this!
Sean Olson seanol...@gmail.com wrote:
Additionally, we would have to decide on exactly how to do this UI wise.
There are a number of options.
1. Additional Menu Item - So we would have 'View User Docs' and
'View API Docs'
2. Tie User Docs and API docs together in wiki. So if you go to
+1, but I agree with Martin regarding laying off on tying the API doc with
the Wiki User Manual.
I would be willing to help with the mapping.
Benjy
On Oct 25, 2011 9:10 AM, Martin Bürbaum martin.buerb...@gmx.at wrote:
Sean Olson seanol...@gmail.com wrote:
Additionally, we would have to
big +1
2011/10/25 Benjy Cook benjytc...@gmail.com
+1, but I agree with Martin regarding laying off on tying the API doc with
the Wiki User Manual.
I would be willing to help with the mapping.
Benjy
On Oct 25, 2011 9:10 AM, Martin Bürbaum martin.buerb...@gmx.at wrote:
Sean Olson
Sounds good but is the many to one mapping really required or wanted?
It sounds like more work than necessary, and would result in ongoing
maintenance.
Instead just have a separate page for each operator based on their
identifiers. For those
that are part of some larger group, we can just add
Id be concerned that a lot of api things that are wiki-able are used all
over the place, not just in a few operators. Are we talking about clicking
on buttons only, or also settings and values used in operators? If you click
for help on a slider that does something in a modifier, but the same kind
@Harley - The many to one relationship was actually Campbell's idea, but I
agree with it. As a user, the user experience would not be very good to
click on 'view user docs' and get some info that is not very relevant to
what you were looking for and then have to click another link. We really
Sean,
I don't necessarily disagree with you at all. The way you are proposing
things might be ideal
I just find that when you start any job of grouping a large number of things
you inevitably find
all sorts of funny exceptions. Items that need to belong to more than one
group. Or you just
On Wed, Oct 26, 2011 at 3:14 AM, Harley Acheson
harley.ache...@gmail.com wrote:
Sounds good but is the many to one mapping really required or wanted?
It sounds like more work than necessary, and would result in ongoing
maintenance.
I think this is manageable, we can fallback on wildcards/regex
Hi,
On Wed, Oct 26, 2011 at 12:04 AM, Campbell Barton ideasma...@gmail.com wrote:
On Wed, Oct 26, 2011 at 3:14 AM, Harley Acheson
harley.ache...@gmail.com wrote:
Sounds good but is the many to one mapping really required or wanted?
It sounds like more work than necessary, and would result in
we don't want one doc for bpy.ops.texture.slot_move, better glob
bpy.ops.texture.slot_*, or bpy.ops.texture.* and then link to a
page explaining about blender texture system.
I'd say we do. And I'd say that trying to figure out whether to use
bpy.ops.texture.slot_*, or bpy.ops.texture.*
On Wed, Oct 26, 2011 at 12:40 PM, Brecht Van Lommel
brechtvanlom...@pandora.be wrote:
Hi,
On Wed, Oct 26, 2011 at 12:04 AM, Campbell Barton ideasma...@gmail.com
wrote:
On Wed, Oct 26, 2011 at 3:14 AM, Harley Acheson
harley.ache...@gmail.com wrote:
Sounds good but is the many to one mapping
Hi All,
Occasionally I try and step back from Blender and attempt to see it the way
a brand new user would. I recently did this and saw a glaring problem.
The 'View Docs' on Right click does not help Users.
Currently in Blender if you right click on 'almost' any button you will get
a menu like
14 matches
Mail list logo
