we were discussing this in irc yesterday.
LOOPTOOLS_OT_my_operator_name seems a good solution.
i’m really thinking of external devs here also, such a change will mean external devs that call the old name will need to update.
given the addon is currently broken in master, we need to fix. it’s easy fix.
my current proposal is to leave everything as is in 2.79rc2 and 2.79 release.
as far as looptools and any addons that call looptools/other potential conflicts, it’s all working and no change needed for 2.79 release. safe!
issues as i see are this:
2.79 is ok.
master/nightly builds some addons no longer work.
if we fix master and add new class names to individual classes, this will not harm most external addons unless they call the specific class.
using loop tools as an example, if we fix the “Curve” class, it will be still safe if your addon calls the main ui class, but if your addon reuses the classes individually the “Curve” class will need to be changed in your addon too.
thus the paradox begins…
We will end up with different class names in 2.79 release and 2.79 master, basically forking our own addons.
this is ok as long as external addons devs don’t fix their addons too early.
I would say if your developing addons for Blender 2.79 you Should use 2.79rc2 (blender tagged rc builds) as your test/working build atm, if your using classes from other activated addons. we have kept this working for the 2.79 release branch, but will be changing the class names in several addons in the master branch, so your addons will work with 2.79, but maybe not with 2.79 master.
some solutions i have done in the past to prevent duplicate class names:
I duplicated the internal space_view3d.py, all the menus/classes and reused them here:
dynamic spacebar menu addon:
in blender the class is: VIEW3D_MT_view_align
in the addon it’s: VIEW3D_MT_View_Align
to take this further, i duplicated the spacebar menu and made it a panel:
contrib addon “Dynamic Toolshelf”
by this time i’m deep in dupliclassville, so i added a prefix “2” to all the classes to make them unique.
not talking about within the same addon, but this should be avoided too i guess.
this example: https://github.com/meta-androcto/blenderpython/tree/master/scripts/addons_extern/AF_view3d_mod
run it as an addon in the addons folder, enable it and disable it and watch the ui vanish.