docs: add OpenMV IDE user-guide chapter, drop decade-old IDE overview

21-page chapter under tools/ide/ covering the main window (editor,
scripts/examples, connecting, running scripts, preferences), the
frame buffer/histogram/recording views, terminals, firmware and
ROMFS maintenance, the machine-vision tools (threshold, keypoints,
tag generators, model zoo, dataset editor), the code profiler, and
command-line options. All claims verified against the openmv-ide
plugin source. Screenshot placeholders mark images to capture.

Removes openmvcam/tutorial/openmvide_overview.rst and points
software_setup.rst at the new chapter.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: kwagyeman

docs/openmvcam/tutorial/index.rst

@@ -28,7 +28,6 @@ earlier, it links back.
    overview.rst
    software_setup.rst
    hardware_setup.rst
-   openmvide_overview.rst
 
    python/index.rst
    hardware/index.rst

docs/openmvcam/tutorial/openmvide_overview.rst

@@ -2,7 +2,10 @@ Software Setup
 ==============
 
 Before you can start using your OpenMV Cam you'll need to download and install
-`OpenMV IDE <https://openmv.io/pages/download/>`_.
+`OpenMV IDE <https://openmv.io/pages/download/>`_. This page covers getting it
+installed and running on each platform; the IDE itself -- the editor, the frame
+buffer viewer, the camera tools -- has its own :doc:`chapter
+<tools/ide/index>`.
 
 Windows
 -------

docs/openmvcam/tutorial/software_setup.rst

@@ -0,0 +1,82 @@
+Command-line options
+====================
+
+The ``openmvide`` executable takes command-line options
+that automate what the GUI normally does interactively
+-- the basis for kiosk installations, demo machines,
+production test stations, and any setup where the IDE
+should come up connected and running with nobody at the
+keyboard.
+
+Automated startup
+-----------------
+
+The automation flags compose into a launch that needs
+no clicks:
+
+* ``-auto_connect`` -- connect to the camera on
+  startup, and keep reconnecting whenever one appears
+  (the Auto Reconnect option, forced on).
+* ``-auto_update <release|development|path>`` -- on
+  connect, install the bundled release firmware, the
+  latest development firmware, or a specific firmware
+  file, without prompting.
+* ``-auto_erase`` -- erase the internal flash
+  filesystem during the automatic update.
+* ``-auto_run`` -- start the open script as soon as the
+  connection is up.
+* ``-disable_stop`` -- force the Stop Script on
+  Connect/Disconnect option off and lock it, so the
+  IDE attaching or detaching never halts the script
+  already running on the camera.
+* ``-full_screen`` -- start with the main window full
+  screen.
+* ``-serial_number_filter <serial>`` -- only connect to
+  the camera with the given USB serial number; with
+  several cameras attached, each IDE instance can be
+  pinned to one unit.
+
+So ``openmvide -auto_connect -auto_run -full_screen``
+turns a PC and a camera into an appliance: power on,
+IDE appears full screen, camera connects, script runs,
+preview streams.
+
+Viewer mode
+-----------
+
+``-viewer_mode`` starts the application as *OpenMV
+Viewer*: the editor and the run controls are gone, and
+what remains is the frame buffer, the histogram, and
+the serial output of whatever the camera is already
+running. It is the mode for the person who should see
+the camera but not change it -- a monitoring station on
+a line, a demo the audience cannot edit.
+
+Terminal-only windows
+---------------------
+
+The terminal flags skip the main window entirely and
+open a standalone :doc:`terminal window <open-terminal>`
+straight from the command line:
+
+* ``-open_serial_terminal <port:baud>``
+* ``-open_tcp_client_terminal <host:port>`` /
+  ``-open_tcp_server_terminal <port>``
+* ``-open_udp_client_terminal <host:port>`` /
+  ``-open_udp_server_terminal <port>``
+
+In a standalone terminal the run button executes the
+camera's stored ``/main.py``.
+
+Utility flags
+-------------
+
+``-list_ports`` prints one line of key/value fields
+per camera serial port (name, description, vendor and
+product IDs, serial number) to standard output and
+exits -- the hook for scripts that need to discover
+cameras before launching something else.
+``-update_resources`` forces the IDE to rebuild its
+bundled resources (examples, firmware, documentation)
+as it starts, and ``-language <locale>`` overrides the
+user-interface language.

docs/openmvcam/tutorial/tools/ide/command-line.rst

@@ -0,0 +1,108 @@
+Connecting a camera
+===================
+
+The connect button -- the plug icon at the bottom of
+the left toolbar, or ``Ctrl+E`` -- is how every session
+starts. Clicking it scans the USB serial ports for
+cameras and connects to the one it finds. With more
+than one camera attached, a dialog asks which serial
+port to use, preselecting the previous pick; with
+none, the IDE says so and offers a recovery path for a
+camera that no longer enumerates (see
+:doc:`firmware`).
+
+What happens on connect
+-----------------------
+
+Connecting is more than opening a serial port. The IDE
+identifies the board, reads its firmware version, and
+compares it against the release bundled with the IDE.
+If the camera's firmware is older, a prompt offers to
+update it -- the normal way cameras get firmware
+updates is exactly this prompt. The update dialog
+includes checkboxes to also erase the internal flash
+filesystem and to reset the ROM file system; they
+start off, remember the last choice made, and neither
+is normally needed for an update. After the first
+successful connect the IDE also shows a one-time
+dialog explaining what the camera's LED blink colours
+mean.
+
+A camera that is attached in bootloader (DFU) mode
+rather than as a normal serial device gets its own
+dialog on connect, with options to install the latest
+release firmware, load a specific firmware file, erase
+the internal flash filesystem, or edit or reset the ROM
+file system.
+
+Two platform notes. On Windows, the IDE checks the
+system device list during connect and reports USB
+driver problems it finds, with the device names
+involved. On Linux, a permission error opening the
+serial port almost always means the user is not in the
+``dialout`` group; the error dialog shows the exact
+``adduser`` command to fix it.
+
+The status bar
+--------------
+
+Once connected, the status bar along the bottom right
+of the window becomes the camera's dashboard:
+
+* *Board* -- the board type reported by the camera.
+* *Sensor* -- the attached camera sensor module.
+* *Firmware Version* -- the running firmware version.
+  Clicking it re-checks the version against the bundled
+  release and offers an update if one is available.
+* *Serial Port* -- the port the connection is using.
+* *Drive* -- the flash-drive mount point associated
+  with the camera. Clicking it opens the drive in the
+  platform's file manager, or -- when several
+  candidate drives are attached -- asks which one
+  belongs to the camera, remembering the answer per
+  serial port. A camera connects and runs scripts fine
+  without a drive association; only the drive-dependent
+  actions, like opening the drive folder and saving a
+  script as ``main.py``, stay disabled until one is
+  set.
+* *FPS* -- the rate at which frames are arriving at the
+  IDE. This is the preview rate, not necessarily the
+  camera's capture rate -- a script can run faster than
+  the USB link can stream its frames.
+
+.. admonition:: Screenshot needed
+
+   ``figures/status-bar.png`` -- the bottom edge of the
+   main window with a camera connected, showing the
+   board, sensor, firmware version, serial port, drive,
+   and FPS entries populated. Crop to the status bar.
+
+An *Unregistered* button also appears in the status
+bar for boards that require a one-time product
+registration, and the IDE offers the registration
+automatically on connect; once the camera is
+registered the button goes away.
+
+Disconnecting is forgiving. Clicking disconnect is the
+tidy way out, but unplugging the cable works too -- the
+IDE notices the camera is gone (or has stopped
+responding) and disconnects on its own.
+
+Auto reconnect
+--------------
+
+Tools → Auto Reconnect to OpenMV Cam makes connection
+fully automatic: whenever a camera is detected on USB
+the IDE connects to it, and the manual connect and
+disconnect buttons are disabled while the option is
+active. With one camera and one IDE this is the
+convenient mode -- plug the camera in and it is
+connected. Turn it off when juggling several cameras or
+sharing the port with another program.
+
+The related Tools → Stop Script on Connect/Disconnect
+option (on by default) halts any running script when
+the IDE attaches or detaches, so a freshly connected
+camera is always in a known idle state. Turning it off
+lets a camera keep executing its stored script while
+the IDE connects to observe it.

docs/openmvcam/tutorial/tools/ide/connecting.rst

@@ -0,0 +1,77 @@
+The dataset editor
+==================
+
+Training a custom classifier starts with a labelled
+dataset -- hundreds of images of each thing the model
+should recognise, captured by the camera that will run
+it, sorted into one folder per class. The dataset
+editor is the IDE's capture workflow for building one.
+
+Tools → Dataset Editor → New Dataset asks for a folder
+to build the dataset in -- warning that a non-empty
+folder's contents will be deleted -- and sets it up: a
+file browser pane docks on the left of the main
+window, and a capture script
+(``dataset_capture_script.py``) opens in the editor.
+The script is a plain capture loop, and it is meant to
+be edited -- apply the
+same lens correction, cropping, or filtering the
+deployed application will use, so the model trains on
+the images it will actually see. Open Dataset reopens
+an existing dataset folder later, and Close Dataset
+puts the window back to normal.
+
+.. admonition:: Screenshot needed
+
+   ``figures/dataset-editor.png`` -- the main window
+   with a dataset open: the dataset pane on the left
+   showing two or three class folders with a few
+   captured images, the image preview below it, and the
+   capture script in the editor. Crop to show the
+   dataset pane and part of the editor.
+
+Capturing
+---------
+
+While a dataset is open, two buttons join the toolbar
+on the window's left edge, below the run controls.
+*New Class Folder* (``Ctrl+Shift+N``) creates a class
+-- one per category the model should learn, named for
+the label.
+With the capture script running and a class folder
+selected, *Capture Data* (``Ctrl+Shift+S``) saves the
+current frame buffer image into that class, and the
+preview pane under the file browser shows each capture
+as it lands.
+
+The capture rhythm is: select a class, point the camera
+at an example of it, capture; move the object, vary the
+angle, the distance, the background, the lighting,
+capture again -- variation in the dataset is what buys
+robustness in the model. Repeat per class, including a
+background class of scenes containing none of the
+targets if the application needs to know when nothing
+is there.
+
+Exporting and training
+----------------------
+
+The Export submenu sends the finished dataset to
+training. Export Dataset to Zip File packs it into an
+archive with class-prefixed file names -- the neutral
+format every training service and framework accepts.
+For Edge Impulse, the IDE integrates directly: log in
+to an Edge Impulse account from the same submenu, and
+Upload to Edge Impulse Project pushes the dataset
+straight into a project (an API-key upload exists for
+accounts where the email-and-password login is not an
+option).
+Train there, export the model, and the :doc:`NPU
+converter <model-zoo>` makes it camera-ready when the
+board needs it.
+
+.. seealso::
+
+   The :doc:`machine learning chapter
+   <../../ml/index>` for the training workflow the
+   dataset feeds into.

docs/openmvcam/tutorial/tools/ide/dataset-editor.rst

@@ -0,0 +1,98 @@
+The script editor
+=================
+
+The editor is a full professional text editor -- the
+same Qt Creator core that ships in commercial IDEs --
+trimmed to a tabbed, single-window layout so that the
+script about to run is always the one in front. Most of
+it needs no explanation: tabs along the top switch
+between open files, and the usual file and edit
+operations live in the File and Edit menus and on the
+toolbar buttons along the left edge. The features below
+are the ones worth knowing about specifically for
+MicroPython work.
+
+Whitespace and undo
+-------------------
+
+Indentation is syntax in Python, so the editor can
+render whitespace visibly -- toggle Visualize
+Whitespace under Edit → Advanced when a script fails
+with an ``IndentationError`` that is invisible in the
+source. Undo and redo are unlimited and tracked per
+file across all open files.
+
+Find and replace
+----------------
+
+The find and replace bar (``Ctrl+F``) supports plain
+text, whole-word, and regular-expression matching, with
+capture groups available in the replacement text and an
+option to preserve the case of each replaced match.
+*Advanced Find* (``Ctrl+Shift+F``) widens the scope
+from the current file to all open files or to every
+file under a folder on disk, and presents the matches
+as a clickable result list.
+
+Code completion and call tips
+-----------------------------
+
+The editor knows the camera's Python API. Typing ``.``
+after a module or object name opens a completion list
+of its functions, methods, and constants; once a name
+is chosen, a call tip walks through the arguments.
+Hovering over any API name shows its documentation in a
+tooltip -- the same text as the library reference,
+without leaving the editor. Completion covers the
+camera-specific modules (:mod:`csi`, :mod:`image`,
+:mod:`machine`, and the rest of the library reference)
+in addition to the Python language itself.
+
+A bundled Python language server checks the code as it
+is typed, underlining undefined names, unused imports,
+and syntax errors in the editor before the script ever
+runs -- a whole class of typo crashes caught at the
+desk instead of on the camera.
+
+Threshold tuples get the same treatment in reverse:
+select a grayscale or LAB threshold tuple in a script,
+right-click it, and the context menu offers to open it
+in the threshold editor, which writes the tuned values
+back into the script when confirmed with OK.
+
+.. admonition:: Screenshot needed
+
+   ``figures/editor-completion.png`` -- the editor with
+   a completion popup open after typing ``img.`` in a
+   script, showing the method list and one entry's
+   documentation tooltip. Crop to the editor pane.
+
+GitHub Copilot
+--------------
+
+The editor ships with GitHub Copilot support for inline
+AI code suggestions. It stays dormant until a GitHub
+account with a Copilot subscription is signed in, under
+the Copilot section of the preferences dialog; sign out
+or untick its enable box to switch it off.
+
+Beyond Python files
+-------------------
+
+The editor opens more than scripts. An image file
+opens in an image viewer with zoom and fit-to-screen
+controls -- handy for inspecting saved snapshots and
+templates without leaving the IDE -- and a binary file
+opens in a hex editor, useful for a quick look inside
+a recording or a descriptor file.
+
+Editing outside the IDE
+-----------------------
+
+Scripts are plain ``.py`` files, and nothing requires
+them to be edited in the IDE. When a file open in the
+editor changes on disk -- saved from another editor,
+pulled from version control -- the IDE picks the
+change up when its window regains focus and reloads
+the file, asking first only when the copy in the
+editor has unsaved changes of its own.