RedEye’s configuration system is entirely file-based: every shell behavior, window layout, hotkey binding, and visual theme is controlled by a set of XML files on disk. There is no GUI settings panel — you edit the files directly, then restart the shell to apply your changes. This design makes configuration reproducible, version-controllable, and straightforward to share or deploy across machines.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/ryzhpolsos/redeye/llms.txt
Use this file to discover all available pages before exploring further.
Root file: config.xml
The entry point for all configuration is config.xml in the RedEye application directory. When RedEye starts, it parses this file first and follows every <import> directive it encounters to build a complete configuration tree in memory.
What each import does
| Import path | Purpose |
|---|---|
config/core.xml | Core shell behavior: Explorer integration, window manager, transparency key |
config/ui/theme.xml | Shared color, font, and spacing variables used everywhere |
config/workArea.xml | Calls setWorkArea(...) to reserve screen space below the taskbar |
config/ui/desktop.xml | Creates the background window with the wallpaper image |
config/ui/startMenu.xml | Creates the start menu popup window |
config/ui/taskbar.xml | Creates the taskbar window with the app list and tray |
config/ui/configUtil.xml | Creates the configuration utility window |
config/ui/shutdownOptions.xml | Creates the shutdown/lock/logoff dialog window |
config/keyBindings.xml | Registers global keyboard shortcuts |
Directory structure
Core settings (core.xml)
The <core> block controls foundational shell behaviors.
explorerIntegration
| Field | Type | Default | Description |
|---|---|---|---|
enable | bool | true | Launches a hidden explorer.exe process on startup so shell integrations (file associations, COM objects, etc.) remain functional |
timeout | int (ms) | 2000 | How long RedEye waits for Explorer to initialize before continuing startup |
windowManager
| Field | Type | Default | Description |
|---|---|---|---|
enable | bool | false | Enables RedEye’s experimental window manager, which tracks and manages all open application windows |
ui.transparencyKey
The hex color used as the transparency chroma key for shell windows that have allowTransparency="true". Any pixel painted in this exact color will be rendered fully transparent. The default value #ff00ff (magenta) is chosen because it rarely appears in real UI content.
Applying configuration changes
RedEye does not hot-reload configuration. After editing any config file you must restart the shell. The built-in expression functionshell.restart() terminates the current process and immediately relaunches redeye.exe, so you can wire it to a button or hotkey:
cmd.exe command that kills the current process by PID and then starts a fresh instance from the same directory.
Explore the configuration system
Layout Markup (RWML)
The full reference for the XML markup language used to define windows and widgets.
Variables
How to define, reference, and compute variables across config files.
Hotkeys
Binding global keyboard shortcuts to shell actions and programs.
Built-in Widgets
The panel, image, label, button, and other widgets you can place inside windows.