How kashiyyy/autodartstouch_jules works
Project type and purpose
• AutodartsTouch is a kiosk-style touchscreen application built with Node.js/Electron, targeting a Raspberry Pi. It wraps web content (by default the Autodarts website) in a full-screen interface, provides an on-screen keyboard, toolbar, and settings page, and can switch between up to five configurable web “tabs.”
File structure
• Top-level scripts:
• AutodartsTouchInstall.sh – installation orchestration (system updates, Node.js install, Autodarts + AutodartsTouch fetch, config)
• AutodartsTouch/AutodartsTouch.sh – launch script for the Electron app
• Electron application folder (AutodartsTouch/):
• package.json & package-lock.json – Node.js/Electron dependencies and metadata
• main.js – Electron “main” process, creates BrowserWindow in kiosk mode, sets up IPC
• preload.js – exposes limited Node.js/IPC APIs to renderer pages
• index.html – primary UI shell with toolbar, tab container, WebView or BrowserView for web content
• settings.html – UI for adjusting volume, keyboard size, tab URLs
• keyboard-server.js – lightweight HTTP server serving the on-screen keyboard assets
• keyboard/index.html (plus supporting assets) – the HTML/JS/CSS for the pop-up keyboard
README for additional insights
• Describes kiosk mode behavior, toolbar controls (keyboard toggle, tabs, reload, settings), automatic on-screen keyboard on input focus, settings persistence and restart requirements.
• Indicates external dependency on Autodarts installation and the Autodarts web service.
Components
a. Main components:
• Operating System (Raspbian/Linux)
• Installation Script (AutodartsTouchInstall.sh)
• Electron Main Process (Node.js/Electron runtime)
• Renderer Processes:
– UI Renderer (index.html + toolbar + embedded web content view)
– Settings Renderer (settings.html)
– Keyboard Renderer (served by keyboard-server.js)
• Preload Script (preload.js) – IPC bridge & safe Node APIs
• Local Configuration Store (e.g. JSON file or Electron Store)
• External Services:
– Autodarts Web Service or any configured website URLs
– Optional local service pages
• Hardware Interfaces:
– Touchscreen input
– System volume control
b. Relationships & interactions:
• User taps → UI Renderer → IPC via preload → Main Process
• Main Process launches BrowserWindow (index.html) in kiosk mode, spawns keyboard HTTP server
• Renderer requests keyboard → WebView points to localhost:keyboard-port → keyboard-server responds with keyboard UI
• Settings adjustments → Settings Renderer IPC → Main Process writes config store → Signals renderer to apply or restart
• Tab switch / reload → IPC calls from UI Renderer → Main Process updates BrowserView or reloads WebView
• On boot/autostart → OS runs AutodartsTouch.sh → invokes Electron app
c. Architectural patterns & design principles:
• Electron multi-process model (main vs. renderers)
• IPC for secure separation of UI and privileged operations
• Modular renderer pages: index, settings, keyboard – each isolated
• Service-oriented keyboard server for dynamic injection
d. Key technologies/frameworks:
• Electron (desktop shell)
• Node.js (runtime for main process + keyboard-server.js)
• IPC + preload.js (context isolation)
• HTML/CSS/JS for renderers
• Bash scripts for installation & autostart configuration