Refactor development workflows and workspace ownership documentation
- Updated the "Development-Workflows.md" to improve clarity and organization of key workflows, including opening and creating workspaces, managing projects, running and canceling renders, and generating templates.
- Enhanced descriptions of the processes involved in workspace management, including file handling, font management, and the implications of workspace locks.
- Revised the "Development-Workspace-Ownership.md" to provide a clearer understanding of workspace exclusivity, file management, and the structure of workspace folders.
- Added detailed explanations of how overlays, assets, and fonts are managed within a workspace, emphasizing the importance of maintaining a single workspace per folder.
- Improved formatting and readability throughout both documents to facilitate better understanding for developers and users.
Move the GUI specification into the wiki, with current names
The former docs/SPECIFICATION.md, word for word, onto the matching
Development pages and five new ones; then its stale class and function
names, region numbers and section references brought up to date.
Strip editor code map; region names instead of numbers
Update documentation: translate bubble comment to English for clarity
Refactor documentation: replace `TextArtifact` with `Artifact`, clarify imported artwork handling, and update status descriptions for the strip editor framework.
Update documentation for strip editor: clarify tool properties, enhance color pair descriptions, and improve multi-selection handling.
Refactor and enhance the strip editor framework
- Updated the status of Development-Anchoring to reflect completed features including anchoring, unanchored state, and render gate functionality.
- Clarified the behavior of file replacement and deletion processes, ensuring user prompts are more informative and consistent.
- Improved the handling of undo operations in the strip editor, ensuring a single history per project and enhancing user experience with clear feedback on actions taken.
- Established a clear structure for property groups and their editors in the strip editor, ensuring that each group is properly defined and associated with its respective editor.
- Enhanced the object state and tool view panels, ensuring they accurately reflect the current selection and provide appropriate editing options.
- Updated documentation to reflect the current state of development, including completed increments and planned future enhancements.
Add the strip editor tool framework specification (T1–T4)
Six Development-* pages covering property groups, the two panels, the
editor's undo stack, advisories and badges, and input anchoring.