So roughly 11k lines of "legacy" is load-bearing for the primary editor, and professional mode cannot be deleted without moving them first. The naming actively misleads: a reasonable reading of CLAUDE.md is that professional/ is safe to ignore or bin, and it is neither.
This is not urgent and does not need doing today. Filing it because the current arrangement means the cost of the legacy surfaces is invisible, and because anybody acting on "professional mode is legacy" would break Blender mode.
Cheapest honest fix is probably moving the shared panels somewhere neutral - they are not professional-mode-specific in any real sense - and letting professional/ shrink to just its shell. The tracking issue for Blender mode UX is the natural parent.
Found during the roadmap audit on 2026-09-05.
CLAUDE.md calls `lib/pages/professional/` legacy weight and says Blender mode is what matters. That is not what the imports say.
`lib/pages/blender/blender_editor.dart` and `blender_lines_panel.dart` pull five panels straight out of `lib/pages/professional/widgets/`:
- `explorer_panel.dart` (2,616 lines)
- `object_properties_panel.dart` (3,582 lines)
- `properties_panel.dart` (2,556 lines, reached transitively)
- `script_editor_panel.dart`
- `prefab_params_editor.dart`
- `blender_slots_list.dart`
So roughly 11k lines of "legacy" is load-bearing for the primary editor, and professional mode cannot be deleted without moving them first. The naming actively misleads: a reasonable reading of CLAUDE.md is that `professional/` is safe to ignore or bin, and it is neither.
This is not urgent and does not need doing today. Filing it because the current arrangement means the cost of the legacy surfaces is invisible, and because anybody acting on "professional mode is legacy" would break Blender mode.
Cheapest honest fix is probably moving the shared panels somewhere neutral - they are not professional-mode-specific in any real sense - and letting `professional/` shrink to just its shell. The tracking issue for Blender mode UX is the natural parent.
Found during the roadmap audit on 2026-09-05.
ImBenji
added this to the Arcs & Angles project 2026-09-05 15:12:35 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
CLAUDE.md calls
lib/pages/professional/legacy weight and says Blender mode is what matters. That is not what the imports say.lib/pages/blender/blender_editor.dartandblender_lines_panel.dartpull five panels straight out oflib/pages/professional/widgets/:explorer_panel.dart(2,616 lines)object_properties_panel.dart(3,582 lines)properties_panel.dart(2,556 lines, reached transitively)script_editor_panel.dartprefab_params_editor.dartblender_slots_list.dartSo roughly 11k lines of "legacy" is load-bearing for the primary editor, and professional mode cannot be deleted without moving them first. The naming actively misleads: a reasonable reading of CLAUDE.md is that
professional/is safe to ignore or bin, and it is neither.This is not urgent and does not need doing today. Filing it because the current arrangement means the cost of the legacy surfaces is invisible, and because anybody acting on "professional mode is legacy" would break Blender mode.
Cheapest honest fix is probably moving the shared panels somewhere neutral - they are not professional-mode-specific in any real sense - and letting
professional/shrink to just its shell. The tracking issue for Blender mode UX is the natural parent.Found during the roadmap audit on 2026-09-05.