Private
Public Access
conductor(archive): move 39 completed tracks (2026-05 to 2026-06) to archive/
This commit is contained in:
@@ -0,0 +1,5 @@
|
||||
# Track gui_2_cleanup_20260513 Context
|
||||
|
||||
- [Specification](./spec.md)
|
||||
- [Implementation Plan](./plan.md)
|
||||
- [Metadata](./metadata.json)
|
||||
@@ -0,0 +1,8 @@
|
||||
{
|
||||
"track_id": "gui_2_cleanup_20260513",
|
||||
"type": "chore",
|
||||
"status": "new",
|
||||
"created_at": "2026-05-13T00:00:00Z",
|
||||
"updated_at": "2026-05-13T00:00:00Z",
|
||||
"description": "I started to do a large cleanup to ./src/gui_2.py. I want you to study it and derive more information on how to maintain and write code for the python codebase. Please update product guidlines or the python code_styleguidleines based on what you discover. Also we may need to make some changes the mcp_tools for better structural awareness of annotations or other conventions with these python files. There is still more orgnaizatoin to be done like annotation/organizing the __init__ method's declarations, among other nitpicks."
|
||||
}
|
||||
@@ -0,0 +1,26 @@
|
||||
# Implementation Plan: GUI 2.py Cleanup & Structural Awareness
|
||||
|
||||
## Phase 1: `gui_2.py` Structural Analysis & Init Cleanup
|
||||
- [x] Task: Audit `gui_2.py` state variables and `__init__` declarations to identify redundancies or disorganization.
|
||||
- [x] Task: Refactor `gui_2.py`'s `__init__` method to group related state variables and improve clarity.
|
||||
- [x] Task: Verify GUI initialization functionality and ensure no regressions using manual/test hooks.
|
||||
- [x] Task: Conductor - User Manual Verification 'Phase 1: `gui_2.py` Structural Analysis & Init Cleanup' (Protocol in workflow.md)
|
||||
|
||||
## Phase 2: Study & Document Codebase Conventions
|
||||
- [x] Task: Study recent changes to `gui_2.py` (via git diffs and current file state) to identify established conventions for type hints, layout logic, and ImGui scoping.
|
||||
- [x] Task: Synthesize learnings to update `conductor/code_styleguides/python.md` with specific, explicit coding conventions.
|
||||
- [x] Task: Update `conductor/product-guidelines.md` with high-level structural and maintenance strategies derived from the codebase study.
|
||||
- [x] Task: Conductor - User Manual Verification 'Phase 2: Study & Document Codebase Conventions' (Protocol in workflow.md)
|
||||
|
||||
## Phase 3: Apply Conventions & Finalize `gui_2.py` Nitpicks
|
||||
- [x] Task: Audit `gui_2.py` against the newly documented conventions to identify remaining structural nitpicks.
|
||||
- [x] Task: Apply formatting, type hint corrections, and layout refactoring to bring the rest of `gui_2.py` into alignment.
|
||||
- [x] Task: Run automated test suite to ensure structural changes haven't broken the rendering pipeline.
|
||||
- [x] Task: Conductor - User Manual Verification 'Phase 3: Apply Conventions & Finalize `gui_2.py` Nitpicks' (Protocol in workflow.md)
|
||||
|
||||
## Phase 4: MCP Tool Enhancements for Structural Awareness
|
||||
- [x] Task: Investigate existing Python MCP tool scripts (e.g., `py_get_skeleton`, `py_get_code_outline` implementations) for AST parsing logic.
|
||||
- [x] Task: Enhance AST parsing logic to better extract and expose type annotations from Python source files.
|
||||
- [x] Task: Modify structural extraction tools to recognize and highlight common ImGui/Dear PyGui patterns.
|
||||
- [x] Task: Write/update tests for MCP tools to verify accurate annotation and pattern parsing.
|
||||
- [~] Task: Conductor - User Manual Verification 'Phase 4: MCP Tool Enhancements for Structural Awareness' (Protocol in workflow.md)
|
||||
@@ -0,0 +1,30 @@
|
||||
# Specification: GUI 2.py Cleanup & Structural Awareness
|
||||
|
||||
## Overview
|
||||
This track focuses on studying recent manual cleanups performed on `src/gui_2.py` to derive best practices for maintaining the Python codebase. It aims to document these extracted conventions, apply them to remaining nitpicks, and significantly enhance the MCP tools' structural awareness of annotations and Python/ImGui conventions.
|
||||
|
||||
## Functional Requirements
|
||||
1. **Study & Documentation**:
|
||||
- Study the recent changes made to `gui_2.py` to identify conventions regarding type hints, state organization, and ImGui rendering patterns.
|
||||
- Update `conductor/product-guidelines.md` with high-level maintenance strategies derived from the study.
|
||||
- Update `conductor/code_styleguides/python.md` with explicit coding conventions discovered (e.g., annotation formatting, class layout).
|
||||
2. **`gui_2.py` Cleanup (Nitpicks)**:
|
||||
- Apply the formalized conventions to any remaining unorganized sections of `gui_2.py` (e.g., finishing `__init__` refactoring or scattered state).
|
||||
3. **MCP Tools Enhancements**:
|
||||
- Enhance AST parsing logic (e.g., in Python outline/skeleton extraction) to properly parse and expose type annotations.
|
||||
- Modify structural tools to recognize common ImGui/Dear PyGui patterns for better structural awareness and token efficiency.
|
||||
|
||||
## Non-Functional Requirements
|
||||
- Ensure changes do not break existing functionality or introduce regressions.
|
||||
- Maintain the "1-space indentation" rule as strictly defined in the Python code styleguide.
|
||||
- All refactoring should aim to reduce token consumption when analyzing files with AI.
|
||||
|
||||
## Acceptance Criteria
|
||||
- Both `conductor/product-guidelines.md` and `conductor/code_styleguides/python.md` are updated with the newly derived insights.
|
||||
- `gui_2.py` is successfully refactored according to the formalized conventions.
|
||||
- MCP tools exhibit improved awareness of annotations and GUI patterns.
|
||||
- Automated tests pass and manual GUI verification confirms no regressions.
|
||||
|
||||
## Out of Scope
|
||||
- Major architectural changes to the underlying `AppController` or DAG Engine logic.
|
||||
- Rewriting `gui_2.py` in a different UI framework.
|
||||
Reference in New Issue
Block a user