PyBreeze-dev 1.0.19__tar.gz → 1.0.21__tar.gz

{pybreeze_dev-1.0.19 → pybreeze_dev-1.0.21}/PKG-INFO

@@ -1,11 +1,10 @@
 Metadata-Version: 2.4
 Name: pybreeze_dev
-Version: 1.0.19
+Version: 1.0.21
 Summary: IDE for multi automation
 Author-email: JE-Chen <jechenmailman@gmail.com>
 Project-URL: Homepage, https://github.com/Integration-Automation/PyBreeze
 Project-URL: Code, https://github.com/Integration-Automation/PyBreeze
-Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
@@ -15,7 +14,7 @@ Classifier: Environment :: Win32 (MS Windows)
 Classifier: Environment :: MacOS X
 Classifier: Environment :: X11 Applications
 Classifier: Operating System :: OS Independent
-Requires-Python: >=3.10
+Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: je-editor>=1.0.27
@@ -33,7 +32,7 @@ Dynamic: license-file
 
 # PyBreeze: The Automation-First IDE
 
-[![Python 3.10–3.14](https://img.shields.io/badge/python-3.10--3.14-blue.svg)](https://www.python.org/downloads/)
+[![Python 3.11–3.14](https://img.shields.io/badge/python-3.11--3.14-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![PySide6](https://img.shields.io/badge/GUI-PySide6-green.svg)](https://doc.qt.io/qtforpython/)
 [![Documentation](https://readthedocs.org/projects/pybreeze/badge/?version=latest)](https://pybreeze.readthedocs.io/en/latest/index.html)
@@ -44,7 +43,11 @@ Dynamic: license-file
 
 ![PyBreeze main window](images/main_window.png)
 
-*The main window: an APITestka action file open in the editor, project tree on the left, run/format/debug/terminal panes below.*
+*The main window in the default theme: an APITestka action file open in the editor, the Navigation view in the side bar with the activity bar at its left, and the output, problems, terminal and debug panes below.*
+
+![PyBreeze main window, light theme](images/main_window_light.png)
+
+*The same window in JEditor Light, with the Explorer in the side bar.*
 
 ---
 
@@ -108,7 +111,7 @@ Each module gets the same menu shape: **Run** (single script, batch directory, w
 
 - **Automation keyword sets** — the `AT_*` / GUI / Web / Load keyword sets are registered for `.json`, and TestPioneer's schema for `.yml` and `.yaml`, on top of JEditor's language support. JEditor does not colour them yet: it highlights those files with its own rules for the suffix, which leave registered keywords out
 - **Code editor** — built on [JEditor](https://github.com/Integration-Automation/JEDITOR): tabs, project tree, format checker, debugger, terminal and a git client pane
-- **Navigation panel** — a dock at the left lists what the menus hold as one tree (Automation, Tools, Settings): type in its box to find a tool or a command by name, then press Enter or double-click to open it. **Dock ▸ Navigation** shows and hides it, and a panel closed on purpose stays closed at the next start
+- **Navigation panel** — a view of the side bar, with its own icon in the activity bar, lists what the menus hold as one tree (Automation, Tools, Settings): type in its box to find a tool or a command by name, then press Enter or double-click to open it. It is the view shown on a first start; the activity bar or **View ▸ Navigation** switches to it, and the view left open is the one shown at the next start
 - **Fits a small screen** — a tool tab never asks for more than 60 font heights of width: a row of buttons too long for the tab wraps onto the next line instead of pushing the window wider than the display
 - **Script execution** — single or batch, each run in a window of its own with a Stop button (Run ▸ Stop All Program stops them all), which asks whether to stop the run when it is closed while the run goes on; action files are passed by path, and a script from the tab in front that is too long for a Windows command line (~32 KB) goes through a temporary file
 - **Report generation** — HTML / JSON / XML after a run, with optional email delivery
@@ -413,7 +416,7 @@ pip install -r requirements.txt
 
 ### System requirements
 
-- **Python**: 3.10 – 3.14
+- **Python**: 3.11 – 3.14
 - **OS**: Windows, macOS, Linux
 - **GUI**: PySide6 6.11.2 (installed automatically)
 
@@ -429,8 +432,8 @@ python exe/start_pybreeze.py      # from the exe directory
 ```python
 from pybreeze import start_editor
 
-start_editor()                              # the theme picked from UI Style (dark_amber until one is)
-start_editor(theme="dark_teal.xml")         # any qt_material theme; it becomes the picked one
+start_editor()                              # the theme picked from UI Style (JEditor Dark until one is)
+start_editor(theme="jeditor_light")         # a JEditor theme, or any qt_material one such as "dark_teal.xml"; it becomes the picked one
 ```
 
 Once launched:
@@ -548,7 +551,7 @@ python -m pytest test/test_utils/ -v --tb=short
 
 - **Unit tests** — `test/test_utils/`, covering the pure-logic layer (curl and HAR parsing, header analysis, SSRF validation, JWT, hashing, timestamps, diffing) plus headless Qt widget tests via `QT_QPA_PLATFORM=offscreen`, with Hypothesis property tests over the parsers. The SSH terminal and the SFTP file tree also log in to an SSH server the tests start on the loopback address, which serves a temporary folder over SFTP
 - **Startup tests** — `test/unit_test/start_automation/` launches the IDE in debug mode and verifies it comes up and exits cleanly
-- **CI** — GitHub Actions: the whole suite on Windows across Python 3.10 – 3.14, and a short set of platform smoke tests on Linux and macOS, on every push and PR plus a nightly run; a push to `dev` that passes the suite also publishes `pybreeze_dev` when the package changed
+- **CI** — GitHub Actions: the whole suite on Windows across Python 3.11 – 3.14, and a short set of platform smoke tests on Linux and macOS, on every push and PR plus a nightly run; a push to `dev` that passes the suite also publishes `pybreeze_dev` when the package changed
 - **Static analysis** — SonarCloud, Codacy and Bandit
 
 ---
@@ -572,4 +575,4 @@ MIT — see [LICENSE](LICENSE). Copyright (c) 2022 JE-Chen
 
 ---
 
-<sub>Screenshots are rendered from the actual PyBreeze widgets on Windows 11 with the default `dark_amber` theme; the sample data in each tool is real input processed by the real code path.</sub>
+<sub>Screenshots are rendered from the actual PyBreeze widgets on Windows 11: the main window and the menus in the default JEditor Dark theme, the tool tabs in `dark_amber`, the default when those were taken; the sample data in each tool is real input processed by the real code path.</sub>

{pybreeze_dev-1.0.19 → pybreeze_dev-1.0.21}/README.md

@@ -1,6 +1,6 @@
 # PyBreeze: The Automation-First IDE
 
-[![Python 3.10–3.14](https://img.shields.io/badge/python-3.10--3.14-blue.svg)](https://www.python.org/downloads/)
+[![Python 3.11–3.14](https://img.shields.io/badge/python-3.11--3.14-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![PySide6](https://img.shields.io/badge/GUI-PySide6-green.svg)](https://doc.qt.io/qtforpython/)
 [![Documentation](https://readthedocs.org/projects/pybreeze/badge/?version=latest)](https://pybreeze.readthedocs.io/en/latest/index.html)
@@ -11,7 +11,11 @@
 
 ![PyBreeze main window](images/main_window.png)
 
-*The main window: an APITestka action file open in the editor, project tree on the left, run/format/debug/terminal panes below.*
+*The main window in the default theme: an APITestka action file open in the editor, the Navigation view in the side bar with the activity bar at its left, and the output, problems, terminal and debug panes below.*
+
+![PyBreeze main window, light theme](images/main_window_light.png)
+
+*The same window in JEditor Light, with the Explorer in the side bar.*
 
 ---
 
@@ -75,7 +79,7 @@ Each module gets the same menu shape: **Run** (single script, batch directory, w
 
 - **Automation keyword sets** — the `AT_*` / GUI / Web / Load keyword sets are registered for `.json`, and TestPioneer's schema for `.yml` and `.yaml`, on top of JEditor's language support. JEditor does not colour them yet: it highlights those files with its own rules for the suffix, which leave registered keywords out
 - **Code editor** — built on [JEditor](https://github.com/Integration-Automation/JEDITOR): tabs, project tree, format checker, debugger, terminal and a git client pane
-- **Navigation panel** — a dock at the left lists what the menus hold as one tree (Automation, Tools, Settings): type in its box to find a tool or a command by name, then press Enter or double-click to open it. **Dock ▸ Navigation** shows and hides it, and a panel closed on purpose stays closed at the next start
+- **Navigation panel** — a view of the side bar, with its own icon in the activity bar, lists what the menus hold as one tree (Automation, Tools, Settings): type in its box to find a tool or a command by name, then press Enter or double-click to open it. It is the view shown on a first start; the activity bar or **View ▸ Navigation** switches to it, and the view left open is the one shown at the next start
 - **Fits a small screen** — a tool tab never asks for more than 60 font heights of width: a row of buttons too long for the tab wraps onto the next line instead of pushing the window wider than the display
 - **Script execution** — single or batch, each run in a window of its own with a Stop button (Run ▸ Stop All Program stops them all), which asks whether to stop the run when it is closed while the run goes on; action files are passed by path, and a script from the tab in front that is too long for a Windows command line (~32 KB) goes through a temporary file
 - **Report generation** — HTML / JSON / XML after a run, with optional email delivery
@@ -380,7 +384,7 @@ pip install -r requirements.txt
 
 ### System requirements
 
-- **Python**: 3.10 – 3.14
+- **Python**: 3.11 – 3.14
 - **OS**: Windows, macOS, Linux
 - **GUI**: PySide6 6.11.2 (installed automatically)
 
@@ -396,8 +400,8 @@ python exe/start_pybreeze.py      # from the exe directory
 ```python
 from pybreeze import start_editor
 
-start_editor()                              # the theme picked from UI Style (dark_amber until one is)
-start_editor(theme="dark_teal.xml")         # any qt_material theme; it becomes the picked one
+start_editor()                              # the theme picked from UI Style (JEditor Dark until one is)
+start_editor(theme="jeditor_light")         # a JEditor theme, or any qt_material one such as "dark_teal.xml"; it becomes the picked one
 ```
 
 Once launched:
@@ -515,7 +519,7 @@ python -m pytest test/test_utils/ -v --tb=short
 
 - **Unit tests** — `test/test_utils/`, covering the pure-logic layer (curl and HAR parsing, header analysis, SSRF validation, JWT, hashing, timestamps, diffing) plus headless Qt widget tests via `QT_QPA_PLATFORM=offscreen`, with Hypothesis property tests over the parsers. The SSH terminal and the SFTP file tree also log in to an SSH server the tests start on the loopback address, which serves a temporary folder over SFTP
 - **Startup tests** — `test/unit_test/start_automation/` launches the IDE in debug mode and verifies it comes up and exits cleanly
-- **CI** — GitHub Actions: the whole suite on Windows across Python 3.10 – 3.14, and a short set of platform smoke tests on Linux and macOS, on every push and PR plus a nightly run; a push to `dev` that passes the suite also publishes `pybreeze_dev` when the package changed
+- **CI** — GitHub Actions: the whole suite on Windows across Python 3.11 – 3.14, and a short set of platform smoke tests on Linux and macOS, on every push and PR plus a nightly run; a push to `dev` that passes the suite also publishes `pybreeze_dev` when the package changed
 - **Static analysis** — SonarCloud, Codacy and Bandit
 
 ---
@@ -539,4 +543,4 @@ MIT — see [LICENSE](LICENSE). Copyright (c) 2022 JE-Chen
 
 ---
 
-<sub>Screenshots are rendered from the actual PyBreeze widgets on Windows 11 with the default `dark_amber` theme; the sample data in each tool is real input processed by the real code path.</sub>
+<sub>Screenshots are rendered from the actual PyBreeze widgets on Windows 11: the main window and the menus in the default JEditor Dark theme, the tool tabs in `dark_amber`, the default when those were taken; the sample data in each tool is real input processed by the real code path.</sub>

{pybreeze_dev-1.0.19 → pybreeze_dev-1.0.21}/pybreeze/pybreeze_ui/editor_main/main_ui.py

@@ -30,7 +30,12 @@ from pybreeze.pybreeze_ui.closing import AskingDock, may_close
 from pybreeze.pybreeze_ui.editor_main.file_tree_context_menu import setup_file_tree_context_menu
 from pybreeze.pybreeze_ui.gui_thread_gc import collect_garbage_on_gui_thread
 from pybreeze.pybreeze_ui.menu.build_menubar import add_menu_to_menubar
-from pybreeze.pybreeze_ui.navigation.navigation_dock import VISIBLE_STATE, NavigationDock
+from pybreeze.pybreeze_ui.navigation.navigation_dock import (
+    NAVIGATION_VIEW,
+    VISIBLE_STATE,
+    NavigationDock,
+    NavigationPanel,
+)
 from pybreeze.pybreeze_ui.navigation.navigation_model import build_navigation
 from pybreeze.pybreeze_ui.show_code_window.code_window import CodeWindow
 from pybreeze.pybreeze_ui.syntax.syntax_extend import \
@@ -115,7 +120,7 @@ class PyBreezeMainWindow(EditorMain):
         self.run_menu.stop_all_program_action.triggered.connect(self.stop_all_runs)
 
         # Navigation: what the menus hold, as a tree that stays in view
-        self._add_navigation_dock()
+        self._add_navigation()
 
         # Action scripts are completed and checked from the installed frameworks' keywords
         self._offer_language_server()
@@ -132,15 +137,43 @@ class PyBreezeMainWindow(EditorMain):
             close_timer.timeout.connect(self.debug_close)
             close_timer.start()
 
-    def _add_navigation_dock(self) -> None:
-        """Add the navigation panel at the left, shown unless the user closed it last time.
+    def _add_navigation(self) -> None:
+        """Add the navigation panel: a view of the side bar where the window has a shell.
 
-        Built after the menus: each of its lines is one of their actions. Its
-        entry in the Dock menu shows and hides it. Whether it is shown is
+        Built after the menus: each of its lines is one of their actions.
+        JEditor's shell gives it an icon in the activity bar and an entry in
+        the View menu, and remembers with its own layout whether it is the
+        view shown. JEditor restored that layout while it was building the
+        window, before this view existed, so it is restored again here; on a
+        first start, with nothing saved, the panel is the view shown. A JEditor
+        from before its window had a shell gets the panel in a dock instead.
+        """
+        navigation = build_navigation(self)
+        workbench = getattr(self, "workbench", None)
+        if workbench is None:
+            self._add_navigation_dock(navigation)
+            return
+        self.navigation_dock = None
+        self.navigation_panel = NavigationPanel(navigation)
+        workbench.add_view(
+            NAVIGATION_VIEW, "side", widget=self.navigation_panel,
+            title_key="navigation_dock_title", icon="navigation")
+        if workbench.has_saved_layout():
+            workbench.restore_layout()
+        else:
+            workbench.show_view(NAVIGATION_VIEW)
+
+    def _add_navigation_dock(self, navigation: dict) -> None:
+        """Add the navigation panel in a dock at the left, shown unless the user closed it last time.
+
+        Its entry in the Dock menu shows and hides it. Whether it is shown is
         remembered only when the user says so (that entry, or the panel's own
         close button): the entry's checked state also changes as the IDE closes.
+
+        :param navigation: what each category holds (``build_navigation``)
         """
-        self.navigation_dock = NavigationDock(build_navigation(self), self)
+        self.navigation_dock = NavigationDock(navigation, self)
+        self.navigation_panel = self.navigation_dock.panel
         self.addDockWidget(Qt.DockWidgetArea.LeftDockWidgetArea, self.navigation_dock)
         self.navigation_dock.setVisible(read_ui_state().get(VISIBLE_STATE) is not False)
         toggle = self.navigation_dock.toggleViewAction()
@@ -268,9 +301,10 @@ def start_editor(debug_mode: bool = False, theme: str | None = None, **kwargs) -
     """
     Start editor instance
     :param debug_mode: enable debug mode with auto-close timer
-    :param theme: qt_material theme name (e.g. "dark_teal.xml", "light_blue.xml"). It replaces
-        the theme picked from UI Style, and is kept as the picked one. ``None`` starts with the
-        picked theme, ``dark_amber.xml`` until one is picked
+    :param theme: a theme of JEditor's own ("jeditor_dark", "jeditor_light") or a qt_material
+        theme name (e.g. "dark_teal.xml", "light_blue.xml"). It replaces the theme picked from
+        UI Style, and is kept as the picked one. ``None`` starts with the picked theme, JEditor's
+        default until one is picked
     :return: None
     """
     new_ide = QCoreApplication.instance()
@@ -297,8 +331,8 @@ def open_main_window(app: QApplication, debug_mode: bool = False, theme: str | N
 
     :param app: the running application, which the theme is applied to
     :param debug_mode: close by itself after a while, as the startup tests need
-    :param theme: qt_material theme name, which replaces the one picked from UI Style and is
-        kept as the picked one; ``None`` keeps the picked one
+    :param theme: a JEditor or qt_material theme name, which replaces the one picked from UI
+        Style and is kept as the picked one; ``None`` keeps the picked one
     :return: the window, which the caller keeps for as long as the IDE runs
     """
     window = PyBreezeMainWindow(debug_mode=debug_mode, **kwargs)
@@ -322,4 +356,9 @@ def _apply_given_theme(app: QApplication, window: PyBreezeMainWindow, theme: str
     # a bad one is logged, and the theme is still applied.
     except (OSError, ValueError, TypeError, KeyError, RuntimeError) as error:
         pybreeze_logger.error("Startup setting error: %r", error)
-        apply_stylesheet(app, theme=theme)
+        apply_style = getattr(window, "apply_style", None)
+        if callable(apply_style):
+            # JEditor applies its own themes and qt_material's alike, with the editor's colours
+            apply_style(theme)
+        else:
+            apply_stylesheet(app, theme=theme)

{pybreeze_dev-1.0.19 → pybreeze_dev-1.0.21}/pybreeze/pybreeze_ui/navigation/navigation_dock.py

@@ -1,8 +1,13 @@
 """The navigation panel: PyBreeze's areas as a tree that stays in view and can be searched.
 
-It is a dock at the left of the main window. Typing in its box keeps the lines
-that hold the text, and Enter or a double click on a line does what the menu
-entry it stands for does. What it lists is decided by ``navigation_model``.
+Typing in its box keeps the lines that hold the text, and Enter or a double
+click on a line does what the menu entry it stands for does. What it lists is
+decided by ``navigation_model``.
+
+``NavigationPanel`` is the panel itself. Where JEditor's window has a shell it
+is a view of the side bar, with an icon in the activity bar; ``NavigationDock``
+holds one in a dock at the left of the main window, for a JEditor from before
+its window had a shell.
 """
 from __future__ import annotations
 
@@ -16,26 +21,27 @@ from pybreeze.pybreeze_ui.navigation.navigation_model import CATEGORIES, Navigat
 from pybreeze.utils.logging.logger import pybreeze_logger
 from pybreeze.utils.ui_state import remember
 
-# The name the panel's visibility is remembered under (utils/ui_state.py)
+# The name the dock's visibility is remembered under (utils/ui_state.py)
 VISIBLE_STATE = "navigation_visible"
+# The panel's ID as a view of JEditor's shell, which its saved layout names
+NAVIGATION_VIEW = "pybreeze_navigation"
 # The least width the panel asks for, in ems: room for a tool's name
 _MIN_WIDTH_EMS = 14
 # Where an item keeps the entry it stands for
 _ENTRY_ROLE = Qt.ItemDataRole.UserRole
 
 
-class NavigationDock(QDockWidget):
+class NavigationPanel(QWidget):
     """The navigation tree with its search box.
 
     :param navigation: what each category holds, by the category's key
         (``navigation_model.build_navigation``)
-    :param parent: the main window
+    :param parent: the Qt parent
     """
 
     def __init__(self, navigation: dict[str, list[NavigationEntry]], parent: QWidget | None = None) -> None:
         word = language_wrapper.language_word_dict
-        super().__init__(word.get("navigation_dock_title"), parent)
-        self.setObjectName("pybreeze_navigation")
+        super().__init__(parent)
 
         self.filter_edit = QLineEdit()
         self.filter_edit.setPlaceholderText(word.get("navigation_filter_placeholder"))
@@ -49,14 +55,12 @@ class NavigationDock(QDockWidget):
         self.status = StatusLine()
         self.status.hide()
 
-        body = QWidget()
-        layout = QVBoxLayout(body)
+        layout = QVBoxLayout(self)
         apply_spacing(layout, around=Space.TIGHT)
         layout.addWidget(self.filter_edit)
         layout.addWidget(self.tree)
         layout.addWidget(self.status)
-        body.setMinimumWidth(_MIN_WIDTH_EMS * em(body))
-        self.setWidget(body)
+        self.setMinimumWidth(_MIN_WIDTH_EMS * em(self))
 
         self._fill(navigation)
 
@@ -121,6 +125,30 @@ class NavigationDock(QDockWidget):
             item.setExpanded(True)
         return shown
 
+
+
+class NavigationDock(QDockWidget):
+    """The navigation panel in a dock at the left of the main window.
+
+    :param navigation: what each category holds, by the category's key
+        (``navigation_model.build_navigation``)
+    :param parent: the main window
+    """
+
+    def __init__(self, navigation: dict[str, list[NavigationEntry]], parent: QWidget | None = None) -> None:
+        super().__init__(language_wrapper.language_word_dict.get("navigation_dock_title"), parent)
+        self.setObjectName("pybreeze_navigation")
+        self.panel = NavigationPanel(navigation)
+        # The panel's parts under the names the dock always had them
+        self.filter_edit = self.panel.filter_edit
+        self.tree = self.panel.tree
+        self.status = self.panel.status
+        self.setWidget(self.panel)
+
+    def apply_filter(self, text: str) -> None:
+        """Keep the lines that hold *text* (``NavigationPanel.apply_filter``)."""
+        self.panel.apply_filter(text)
+
     def closeEvent(self, event) -> None:
         # Closed with its own button: stay closed next time. The Dock menu's
         # entry remembers the same when it is used (main_ui.py).

{pybreeze_dev-1.0.19 → pybreeze_dev-1.0.21}/pybreeze_dev.egg-info/PKG-INFO

@@ -1,11 +1,10 @@
 Metadata-Version: 2.4
 Name: pybreeze_dev
-Version: 1.0.19
+Version: 1.0.21
 Summary: IDE for multi automation
 Author-email: JE-Chen <jechenmailman@gmail.com>
 Project-URL: Homepage, https://github.com/Integration-Automation/PyBreeze
 Project-URL: Code, https://github.com/Integration-Automation/PyBreeze
-Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
@@ -15,7 +14,7 @@ Classifier: Environment :: Win32 (MS Windows)
 Classifier: Environment :: MacOS X
 Classifier: Environment :: X11 Applications
 Classifier: Operating System :: OS Independent
-Requires-Python: >=3.10
+Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: je-editor>=1.0.27
@@ -33,7 +32,7 @@ Dynamic: license-file
 
 # PyBreeze: The Automation-First IDE
 
-[![Python 3.10–3.14](https://img.shields.io/badge/python-3.10--3.14-blue.svg)](https://www.python.org/downloads/)
+[![Python 3.11–3.14](https://img.shields.io/badge/python-3.11--3.14-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![PySide6](https://img.shields.io/badge/GUI-PySide6-green.svg)](https://doc.qt.io/qtforpython/)
 [![Documentation](https://readthedocs.org/projects/pybreeze/badge/?version=latest)](https://pybreeze.readthedocs.io/en/latest/index.html)
@@ -44,7 +43,11 @@ Dynamic: license-file
 
 ![PyBreeze main window](images/main_window.png)
 
-*The main window: an APITestka action file open in the editor, project tree on the left, run/format/debug/terminal panes below.*
+*The main window in the default theme: an APITestka action file open in the editor, the Navigation view in the side bar with the activity bar at its left, and the output, problems, terminal and debug panes below.*
+
+![PyBreeze main window, light theme](images/main_window_light.png)
+
+*The same window in JEditor Light, with the Explorer in the side bar.*
 
 ---
 
@@ -108,7 +111,7 @@ Each module gets the same menu shape: **Run** (single script, batch directory, w
 
 - **Automation keyword sets** — the `AT_*` / GUI / Web / Load keyword sets are registered for `.json`, and TestPioneer's schema for `.yml` and `.yaml`, on top of JEditor's language support. JEditor does not colour them yet: it highlights those files with its own rules for the suffix, which leave registered keywords out
 - **Code editor** — built on [JEditor](https://github.com/Integration-Automation/JEDITOR): tabs, project tree, format checker, debugger, terminal and a git client pane
-- **Navigation panel** — a dock at the left lists what the menus hold as one tree (Automation, Tools, Settings): type in its box to find a tool or a command by name, then press Enter or double-click to open it. **Dock ▸ Navigation** shows and hides it, and a panel closed on purpose stays closed at the next start
+- **Navigation panel** — a view of the side bar, with its own icon in the activity bar, lists what the menus hold as one tree (Automation, Tools, Settings): type in its box to find a tool or a command by name, then press Enter or double-click to open it. It is the view shown on a first start; the activity bar or **View ▸ Navigation** switches to it, and the view left open is the one shown at the next start
 - **Fits a small screen** — a tool tab never asks for more than 60 font heights of width: a row of buttons too long for the tab wraps onto the next line instead of pushing the window wider than the display
 - **Script execution** — single or batch, each run in a window of its own with a Stop button (Run ▸ Stop All Program stops them all), which asks whether to stop the run when it is closed while the run goes on; action files are passed by path, and a script from the tab in front that is too long for a Windows command line (~32 KB) goes through a temporary file
 - **Report generation** — HTML / JSON / XML after a run, with optional email delivery
@@ -413,7 +416,7 @@ pip install -r requirements.txt
 
 ### System requirements
 
-- **Python**: 3.10 – 3.14
+- **Python**: 3.11 – 3.14
 - **OS**: Windows, macOS, Linux
 - **GUI**: PySide6 6.11.2 (installed automatically)
 
@@ -429,8 +432,8 @@ python exe/start_pybreeze.py      # from the exe directory
 ```python
 from pybreeze import start_editor
 
-start_editor()                              # the theme picked from UI Style (dark_amber until one is)
-start_editor(theme="dark_teal.xml")         # any qt_material theme; it becomes the picked one
+start_editor()                              # the theme picked from UI Style (JEditor Dark until one is)
+start_editor(theme="jeditor_light")         # a JEditor theme, or any qt_material one such as "dark_teal.xml"; it becomes the picked one
 ```
 
 Once launched:
@@ -548,7 +551,7 @@ python -m pytest test/test_utils/ -v --tb=short
 
 - **Unit tests** — `test/test_utils/`, covering the pure-logic layer (curl and HAR parsing, header analysis, SSRF validation, JWT, hashing, timestamps, diffing) plus headless Qt widget tests via `QT_QPA_PLATFORM=offscreen`, with Hypothesis property tests over the parsers. The SSH terminal and the SFTP file tree also log in to an SSH server the tests start on the loopback address, which serves a temporary folder over SFTP
 - **Startup tests** — `test/unit_test/start_automation/` launches the IDE in debug mode and verifies it comes up and exits cleanly
-- **CI** — GitHub Actions: the whole suite on Windows across Python 3.10 – 3.14, and a short set of platform smoke tests on Linux and macOS, on every push and PR plus a nightly run; a push to `dev` that passes the suite also publishes `pybreeze_dev` when the package changed
+- **CI** — GitHub Actions: the whole suite on Windows across Python 3.11 – 3.14, and a short set of platform smoke tests on Linux and macOS, on every push and PR plus a nightly run; a push to `dev` that passes the suite also publishes `pybreeze_dev` when the package changed
 - **Static analysis** — SonarCloud, Codacy and Bandit
 
 ---
@@ -572,4 +575,4 @@ MIT — see [LICENSE](LICENSE). Copyright (c) 2022 JE-Chen
 
 ---
 
-<sub>Screenshots are rendered from the actual PyBreeze widgets on Windows 11 with the default `dark_amber` theme; the sample data in each tool is real input processed by the real code path.</sub>
+<sub>Screenshots are rendered from the actual PyBreeze widgets on Windows 11: the main window and the menus in the default JEditor Dark theme, the tool tabs in `dark_amber`, the default when those were taken; the sample data in each tool is real input processed by the real code path.</sub>

{pybreeze_dev-1.0.19 → pybreeze_dev-1.0.21}/pyproject.toml

@@ -7,12 +7,12 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pybreeze_dev"
-version = "1.0.19"
+version = "1.0.21"
 authors = [
     { name = "JE-Chen", email = "jechenmailman@gmail.com" },
 ]
 description = "IDE for multi automation"
-requires-python = ">=3.10"
+requires-python = ">=3.11"
 license-files = ["LICENSE"]
 dependencies = [
     "je-editor>=1.0.27", "je_auto_control", "je_web_runner",
@@ -21,7 +21,6 @@ dependencies = [
     "jupyterlab",
 ]
 classifiers = [
-    "Programming Language :: Python :: 3.10",
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
     "Programming Language :: Python :: 3.13",