[Bf-docboard] Getting a start

[Aaron Carlisle]

Hi Glen,

You should now have commit rights. The usernames and passwords are synced
with whatever you use on developer.blender.org

Aaron Carlisle

Picture taker | Bit cruncher | Pixel pusher | Document writer | Artist
Project administrator for the Blender 3D Documentation Project

On Tue, Oct 3, 2017 at 2:29 AM, Glen Larsen <glenl.glx at gmail.com> wrote:

> @Francesco, I've posed a question on bf-funboard with some scenario
> descriptions
>
> @Tobias, the notion of input and output node preservation answers the
> question I posted bf-funboard. (I'm sure this won't be the first time this
> will happen.) Apparently, when you have a single node *all* input and
> output is "preserved", if you insert two nodes that are connected together
> (no input or output connections), there is nothing to preserve so the new
> group input/output nodes are detached.
>
> Thanks for the input. I should [solve] this on bf-funboard.
>
> On Mon, Oct 2, 2017 at 8:36 PM, Aaron Carlisle <carlisle.b3d at gmail.com>
> wrote:
>
>> Hey sorry I was unable to get to your stuff over the weekend I was busier
>> than I thought I would be.
>> I will have a look soon though!
>>
>> Aaron Carlisle
>>
>> Picture taker | Bit cruncher | Pixel pusher | Document writer | Artist
>> Project administrator for the Blender 3D Documentation Project
>>
>> On Mon, Oct 2, 2017 at 7:06 PM, Tobias Heinke <heinke.tobias at t-online.de>
>> wrote:
>>
>>> Hi Glen,
>>>
>>> Hello and welcome. :)
>>> Fixing a todo is always a good start.
>>>
>>> On the node group page
>>> <https://docs.blender.org/manual/en/dev/editors/node_editor/nodes/groups.html>
>>> :
>>> I would suggest to add a proper paragraph about group in-/output nodes
>>> first.
>>> E.g. multiple outputs: the last selected node will be used. (currently
>>> at Interface > Panel).
>>> This can then be refer to in Group Insert.
>>>
>>> The reason why the in/out nodes are created is to preserve the outer
>>> links of the nodes.
>>> IMO it's better to simply start with a description how it is.
>>> Because later you might notice things you missed, like UI conventions
>>> (multiple in-/output nodes for both materials and in groups), hidden
>>> code related constraints & limitations...
>>>
>>> Tobias
>>> Am 30.09.2017 um 22:58 schrieb Glen Larsen:
>>>
>>> First: As a start to my Blender documentation career I would like to
>>> fill out missing sections relating to material node editing. I don't see a
>>> list of section owners so is it sufficient to replace a "Todo" with
>>> relevant text and submit a patch? Any other coordination I should do?
>>>
>>> Second: While quite familiar with node editing, I have come across an
>>> operation that I've never used ("Group Insert") and its functionality seems
>>> clumsy. It does what it says --- move one or more nodes into an existing
>>> group --- but it adds additional input and output nodes which forces
>>> further editing. Certainly I could ask the module owners but are there more
>>> appropriate discussion areas? Here?
>>>
>>> Thanks for any input.
>>>
>>> -glen
>>>
>>>
>>> _______________________________________________
>>> Bf-docboard mailing listBf-docboard at blender.orghttps://lists.blender.org/mailman/listinfo/bf-docboard
>>>
>>>
>>>
>>> _______________________________________________
>>> Bf-docboard mailing list
>>> Bf-docboard at blender.org
>>> https://lists.blender.org/mailman/listinfo/bf-docboard
>>>
>>>
>>
>> _______________________________________________
>> Bf-docboard mailing list
>> Bf-docboard at blender.org
>> https://lists.blender.org/mailman/listinfo/bf-docboard
>>
>>
>
> _______________________________________________
> Bf-docboard mailing list
> Bf-docboard at blender.org
> https://lists.blender.org/mailman/listinfo/bf-docboard
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.blender.org/pipermail/bf-docboard/attachments/20171006/e5b50d80/attachment.html>