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

oops

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-02-21 23:38:46 -05:00
parent 3e94c9580e
commit dc8192b1dc
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Readme.md
View File

@@ -2,7 +2,7 @@
Vibe coding.. but more manual
[!img](./gallery/python_2026-02-21_23-37-29.png)
![img](./gallery/python_2026-02-21_23-37-29.png)
## Instructions

4
manual_slop.toml
View File

@@ -112,7 +112,7 @@ history = [
[discussion.discussions."Misc UX improvements"]
git_commit = "5f9b270841fa1b3e34af1c56cbc75041c95b265a"
last_updated = "2026-02-21T23:34:40"
last_updated = "2026-02-21T23:38:30"
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.",
@@ -124,4 +124,6 @@ history = [
"@2026-02-21T23:27:41\nAI:\nI have implemented the requested functionality for maximizing text panels.\n\n### 1. Global Text Viewer\nI added a new dedicated global popup called **Text Viewer** (`win_text_viewer`) to DearPyGUI. This popup is large (900x700 by default) and contains a multiline readonly input field explicitly designed for scrolling and reading massive chunks of text or code without constraints.\n\n### 2. Comms History & Text Panels\nEvery significant text field that usually gets clamped into a tiny box now has a `[+]` or `[+ Maximize]` button next to its label:\n- **Comms History**: All large payloads (like JSON text blocks, request prompts, or raw tool strings) have a `[+]` button next to their name.\n- **Tool Calls History**: I added `[+ Script]` and `[+ Output]` next to every command executed in the tool log, so you can easily review the full output of a historic tool call.\n- **Confirm Dialog**: The prompt where you approve PowerShell scripts now has a `[+ Maximize]` button next to \"Script\", so if I generate a massive script, you can easily inspect the whole file before clicking Approve.\n\n### 3. Last Script Output Popup\nI made several quality-of-life adjustments to this popup as requested:\n- **Larger dimensions**: The popup is now 800x600 by default (previously 700x500).\n- **Expanded Input script panel**: The script input box now has a height of 200px (up from 150px) so it's far less scrunched.\n- **Maximizable**: Both the \"Script\" and \"Output\" labels now feature a `[+ Maximize]` button, meaning you can instantly open either pane inside the massive Global Text Viewer.\n\n`MainContext.md` has been successfully updated with the details of these new features. You will need to restart the application to interact with the new maximize buttons and the updated Text Viewer UI! Let me know if any other UI elements need more space.",
"@2026-02-21T23:29:41\nUser:\n1. In project config add support for toggling proper word-wrap on text panels used throughtout this interface.\n2. Make the discussion entry text boxes maximizable in the text viewer popup we setup earlier.",
"@2026-02-21T23:33:39\nVendor API:\n[GEMINI QUOTA EXHAUSTED]\n\n429 RESOURCE_EXHAUSTED. {'error': {'code': 429, 'message': 'You exceeded your current quota, please check your plan and billing details. For more information on this error, head to: https://ai.google.dev/gemini-api/docs/rate-limits. To monitor your current usage, head to: https://ai.dev/rate-limit. \\n* Quota exceeded for metric: generativelanguage.googleapis.com/generate_content_paid_tier_input_token_count, limit: 1000000, model: gemini-3.1-pro\\nPlease retry in 19.265357775s.', 'status': 'RESOURCE_EXHAUSTED', 'details': [{'@type': 'type.googleapis.com/google.rpc.Help', 'links': [{'description': 'Learn more about Gemini API quotas', 'url': 'https://ai.google.dev/gemini-api/docs/rate-limits'}]}, {'@type': 'type.googleapis.com/google.rpc.QuotaFailure', 'violations': [{'quotaMetric': 'generativelanguage.googleapis.com/generate_content_paid_tier_input_token_count', 'quotaId': 'GenerateContentPaidTierInputTokensPerModelPerMinute', 'quotaDimensions': {'location': 'global', 'model': 'gemini-3.1-pro'}, 'quotaValue': '1000000'}]}, {'@type': 'type.googleapis.com/google.rpc.RetryInfo', 'retryDelay': '19s'}]}}",
"@2026-02-21T23:34:40\nUser:\nFinish up if there is anything left todo! I switched to gemini 2.5 pro",
"@2026-02-21T23:36:29\nAI:\nOf course. It looks like the previous session was interrupted. I will now implement the two pending features: adding a global word-wrap toggle to the project settings and making the discussion entry text boxes maximizable.\n\nFirst, I'll add the `word_wrap` setting to the default project configuration so that all new projects have this option available.\nI will start by adding the `word_wrap` setting to the project configuration. I'll edit `project_manager.py` to include `word_wrap = True` in the `default_project` function. This ensures that all newly created projects will have this setting enabled by default.\n\nExcellent. Now I will modify `gui.py` to add the user interface elements and logic for both the word-wrap toggle and the maximizable discussion entries.\n\nThis involves several targeted changes:\n1. **App State**: I'll add a list to the `App` class to keep track of all text widgets that need to have their wrapping toggled.\n2. **UI Construction (`_build_ui`)**: A new checkbox for \"Word-Wrap\" will be added to the \"Projects\" panel.\n3. **Callback Logic (`cb_word_wrap_toggled`)**: This new function will iterate through the tracked widgets and apply the word-wrap setting. I will also make sure that dynamically created text elements (like in the tool and comms logs) respect this setting upon being rendered.\n4. **Discussion History (`_rebuild_disc_list`)**: I'll add a `[+ Max]` button next to each discussion entry's text box, hooking it up to the existing text viewer popup.\n\nI will write a Python script to perform these modifications.\n\nThe previous attempt to modify `gui.py` failed due to a syntax error in the helper script. PowerShell misinterpreted a backslash in a regular expression. I will correct this by writing a new, more robust Python script to perform the necessary edits.\n\nThis new script will:\n1. Add a `[+ Max]` button to each discussion history entry, allowing its content to be opened in the global text viewer.\n2. Add the \"Word-Wrap\" checkbox to the project settings panel.\n3. Implement the logic for the word-wrap toggle, ensuring it correctly shows/hides wrapped and non-wrapped text panels and redraws dynamic content like the comms and tool logs.\n4. Update the text viewer popup so that its own wrapping behaviour is also controlled by the new project setting.\n\nI will now execute this corrected script.\n\nExcellent. The script has successfully modified `gui.py` to implement the requested features.\n\nHere is a summary of the final changes:\n\n1. **Global Word-Wrap Toggle (`gui.py`, `project_manager.py`)**:\n * A new setting, `word_wrap`, has been added to the project configuration (`.toml` files) and defaults to `true`.\n * A checkbox labeled \"Word-Wrap (Read-only panels)\" is now present in the **Projects** panel.\n * Toggling this checkbox will dynamically change the wrapping behavior for most multi-line text displays in the interface, including the main AI response, script outputs, the global text viewer, and the comms log.\n\n2. **Maximizable Discussion Entries (`gui.py`)**:\n * Each entry in the **Discussion History** panel now has a `[+ Max]` button.\n * Clicking this button will open the full content of that specific entry in the large **Text Viewer** popup, making it much easier to read and review long conversation segments.\n\nI have completed all the requested tasks. I will now update `MainContext.md` to document these new UI enhancements.\n\nI have now implemented all the requested features and updated the documentation.\n\n1. **Word-Wrap Feature**: A \"Word-Wrap\" checkbox is now available in the **Projects** panel. This setting is saved with your project and controls the text wrapping for most read-only text panels throughout the application, allowing you to toggle between wrapped text for readability and non-wrapped text for viewing code.\n\n2. **Maximizable Discussion Entries**: Every entry in the **Discussion History** now has a `[+ Max]` button, enabling you to open its contents in the large text viewer for easier reading and copying.\n\n3. **Documentation Updated**: `MainContext.md` has been updated to include details about these new quality-of-life features.\n\nAll tasks are complete. You will need to restart the application to see and use the new features. Let me know if you have any other requests",
]