ed/manual_slop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Agent scripting ux improvements

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-02-21 23:15:48 -05:00
parent caa67206fa
commit d7d0583b4e
3 changed files with 106 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
manual_slop.toml
View File

@@ -111,9 +111,11 @@ history = [
]
[discussion.discussions."Misc UX improvements"]
git_commit = ""
last_updated = "2026-02-21T23:08:11"
git_commit = "caa67206faea0b3a0732761e44ca6afc3bafc7f5"
last_updated = "2026-02-21T23:15:02"
history = [
"@2026-02-21T23:03:51\nUser:\nMake the namespace for the generated markdown file the projet name instead of that specific namespace in the config panel.\nThe ouptut dir can be in the project panel spec (that way we can just remove config panel entirely).",
"@2026-02-21T23:04:55\nAI:\nI have applied the changes to streamline the project settings and remove the old Config panel completely:\n\n1. **GUI Layout Changes (`gui.py`)**:\n - The `Config` panel has been completely removed.\n - The **Output Dir** field has been moved into the **Projects** panel (right above the Project Files list).\n - The **Auto-add history** checkbox has been moved to the top of the **Discussion History** panel (directly under the entry toolbar buttons).\n - The **Files** panel was shifted upward to reclaim the space left behind by the old Config panel.\n\n2. **Namespace Management (`aggregate.py` & `project_manager.py`)**:\n - The explicitly defined `namespace` field is gone.\n - Instead, `aggregate.py` now directly infers the output markdown file namespace from the active project's `name` property. (e.g., saving under the `manual_slop` project will just prefix the markdown with `manual_slop_001.md`).\n - `project_manager.py` was updated to no longer scaffold out `namespace` strings into new `.toml` files, and `flat_config` now injects the core `project` dictionary segment so the generators can access the internal name.\n\n3. **`MainContext.md` Updated**:\n - I have updated the markdown file with the latest layout structures and explained that `namespace` is no longer a configurable setting but dynamically determined by the project profile.\n\nYou'll need to restart the application for the GUI layout and DearPyGUI state changes to take effect! Let me know how it looks.",
"@2026-02-21T23:10:45\nUser:\n1. Make a popup so we can see scripts that were run and their script output more clearly. have that popup stay up and open autoamtically for the last run script by the ai.\n a. Make it blink blue when it runs (very dim).\n2. Adjust the blink green strenght to a dimmer value, or more transparent, its too bright (for the reponse notif).",
"@2026-02-21T23:13:12\nAI:\nI have implemented both requests to improve the feedback you receive from the application:\n\n1. **Script Output Popup (`gui.py`)**: \n - I added a new `Last Script Output` window. \n - Whenever the AI runs a PowerShell tool (after you approve it), this window will automatically pop up (or come to the front if it's already open).\n - It contains two scrollable text boxes: one showing the exact script that was executed, and the other showing the stdout/stderr result.\n - The text boxes within this popup will flash a **dim blue** colour a few times to visually alert you that a background script execution just completed.\n\n2. **Dimmer Green Blink (`gui.py`)**: \n - I modified the retro arcade blink effect for the main AI response notification. \n - The alpha (transparency) of the green overlay has been reduced significantly (from `120` down to `50`), making it much softer and less glaring on the eyes.\n\nI have also updated `MainContext.md` to document these new UI feedback features! You will need to restart the application to see the new popup and the updated blink intensities. Let me know if the colours need any further tweaking.",
]