Class name / bl_idname about animation_nodes HOT 4 CLOSED

ah yes. you're right!

do you think another prefix for every node is necessery to avoid conflicts?
bpy.types.mn_FloatInputNode

from animation_nodes.

In Sverchok we have been using the Sv prefix, sadly we have some horribly generic names, AreaNode and LineNode for example from before we started to use it. I will work to resolve the ones we have left.
Right now we don't have any conflicts but sooner or later with more nodes system it will happen.

What prefix you use is up to you but you might as well use one for the whole addon to make it simpler to see where it belongs.

from animation_nodes.

Ok. thanks for your suggestion. I will change that for every node when I'm back from school :D
I'm planning a few changes that concerns every node anyway, so I can do that all at the same time. Great timing

from animation_nodes.

it say to me - we should all integrate to one system as soon as possible to reduce conflicts. naming is not complete solution. That is reason to talk Lukas Ton on bconf2014.
universal sockets and collective regimes or collective nodes or scheme to interact with cross checking of custom nodes...

from animation_nodes.