PLUGIN: Group OPs by purpose (Logical Grouping/Separation of Concerns)

[Danweel]

This is entirely for people coming to the the bpy from outside. Unfortunately it might mess with Fred if he's very used to the order.

Imports & Constants: import bpy, mybrushsize, myshadowsize.

Helper Functions: Small functions that do math or data lookup (e.g., find_layer_by_keyword, set_brush_size). These are pure logic, no bpy.ops calls ideally.

Operator Classes: The bpy.types.Operator classes.

Menu Registration: The register() and unregister() functions at the very bottom.

Blender Add-on convention works like this, so we should stick to that:

1. Metadata

bl_info = {...}

2. Imports

import bpy

3. Constants

MYBRUSHSIZE = 13

4. Helper functions (pure logic)

def find_layer(context, keyword):
    etc

5. Operator classes

class MyOperator(bpy.types.Operator):
    etc

6. Panel/Menu classes

class MyPanel(bpy.types.Panel):
    etc

7. Registration

def register():
    bpy.utils.register_class(MyOperator)
    etc

def unregister():
    bpy.utils.unregister_class(MyOperator)
    etc

8. Entry point

if __name__ == "__main__":
    register()

See #18
https://developer.blender.org/docs/handbook/extensions/addon_guidelines/
https://jlampel.github.io/blender_add-on_guidelines/06_code-structure.html

This will probably look like:

Imports
Constants (Brush names, Layer keywords, Material names)
Helper Functions (The "Tools")

    _find_layer(...)
    _ensure_mode(...)
    _setup_drawing_session(...)
    _apply_noise_step(...)
    _apply_thickness(...)

Operator Classes (The "Recipes")

    SimpleOperatorHIGHLIGHTS3 (Calls helpers)
    SimpleOperatorFRAMES1 (Calls helpers)
    SimpleOperatorOP8 (Calls helpers)
    ...

Registration (register(), unregister())

=investigate=