How oldchong98/tcp-simulator works
This is an Electron TCP simulator: the user configures a connection, starts a TCP server or connects as a client, then exchanges and inspects messages. The renderer owns navigation, socket handling, message conversion and display; the Electron main process creates the window. The tree also identifies message setup and ISO configuration views, and the renderer excerpt shows ISO-config IPC requests. Those view-specific details and any persistence behavior are not fully sampled, so links beyond the shown calls are omitted.
Main entry points: renderer.js Renderer · index.html App shell · index.js Electron main · connection_setup.html Connection setup
Components 14
Electron app
- Electron main
index.js - App shell
index.html - Renderer
renderer.js
TCP connections
- Connection setup
connection_setup.html - TCP server
renderer.js - TCP client
renderer.js
Message tools
- Run view
run.html - Message setup
message_setup.html - Message tools
renderer.js - Traffic display
renderer.js
Configuration
- ISO config view
iso_config.html - ISO config tools
renderer.js
Other components
- User
- TCP peer
Connections 18
- User → App shell: opens app
- Electron main → App shell: loads window
index.js - App shell → Renderer: runs interface
- User → Renderer: uses controls
renderer.js - Renderer → Connection setup: loads view
renderer.js - Renderer → Run view: loads view
renderer.js - Renderer → Message setup: loads view
- Renderer → ISO config view: loads view
- Renderer → TCP server: starts server
renderer.js - Renderer → TCP client: connects client
renderer.js - TCP server → TCP peer: accepts connection
renderer.js - TCP client → TCP peer: connects to
renderer.js - Renderer → Message tools: handles input
renderer.js - Message tools → TCP client: writes bytes
renderer.js - Message tools → TCP server: writes bytes
renderer.js - TCP client → Traffic display: logs traffic
renderer.js - TCP server → Traffic display: logs traffic
renderer.js - Renderer → Electron main: requests ISO configs
renderer.js