Skip to content

ROADMAP.md

Latest commit

 

History

History
99 lines (73 loc) · 3.69 KB

ROADMAP.md

File metadata and controls

99 lines (73 loc) · 3.69 KB
Raw

RIONT Roadmap

Mission

RIONT fills a specific gap in the FRC NetworkTables tooling landscape:

  • AdvantageScope owns data analysis — graphs, logging, replay.
  • Elastic owns the pit-side and driver display.
  • RIONT owns fast NetworkTables navigation and topic viewing: find a topic quickly, see its value clearly, right now, without configuring anything.

RIONT should do that one job excellently. It should never try to become the next AdvantageScope or the next Elastic. Features below are filtered through that identity; anything that drifts toward analysis or dashboards belongs in another tool.

Non-goals

RIONT deliberately does not do these. Revisit only with a strong, season-tested reason:

  • Graphs, plots, sparklines of any kind (AdvantageScope's domain)
  • Data recording, log export, log replay (AdvantageScope's domain)
  • Driver/pit display layouts, match-viewing dashboards (Elastic's domain)
  • Alerting, monitoring, threshold watches
  • Robot control beyond lightweight value writes
  • Anything team-specific — RIONT is team-agnostic

On the roadmap

Viewing fidelity — the core investment

  1. Struct decoding expansion. ✅ Done — ChassisSpeeds, Twist2d, and SwerveModuleStates decode to named fields (v0.8.0).
  2. Raw/struct inspector. ✅ Done — the inspector dock shows the parsed structSchema leaves plus a hex view of raw bytes for undecoded structs (v0.8.0).

Viewing — field

  1. Swerve module vectors on the field card. ✅ Done — drawn around the robot rectangle when SwerveModuleStates are available (v0.8.0).

Connection

  1. Connection quality detail in the HUD. Improve what COMM communicates about link health beyond connected/reconnecting — exact metrics to be decided during design.

UX / configuration (config-only by policy)

  1. Tree/watchlist split sizing via config. A config.json key for the left-column width. Deliberately no UI for it — it must not clutter the main interface.
  2. Customizable color themes via config. Hex values for the UI colors (watchlist, borders, HUD, tree) so users can personalize the look. Config-file only, same policy as the split sizing.
  3. Colorblind-safe theme. Far down the line — not urgent.

Mouse tolerance

  1. Mouse support. Click-to-focus, scrolling. Keyboard remains the primary interaction; this exists for users who want it, not for the author.

Infrastructure

  1. CI + release binaries. ✅ Done — .github/workflows/ci.yml (fmt/clippy/tests on Windows/Linux/macOS + the contract harness on Linux) and .github/workflows/release.yml (Windows/Linux/macOS binaries attached to the GitHub release on v* tag push, via scripts/release.sh).
  2. Wide-viewport harness coverage. ✅ Done — the harness runs wide (200x50) and short (90x20) scenarios alongside 120x36.

Parked — revisit after a full season of use

These are not committed. Real usage over a season decides whether they earn a place:

  • Per-card view options (precision, units, compact/expanded). Leans AdvantageScope; if it ever happens it must be a hover + keybinding menu on a watchlist card — never persistent UI.
  • Recently-changed view (topics mutated in the last N seconds). Leans monitoring; may prove its worth as navigation with reps.

Rejected

Recorded so they are not re-proposed every few months:

  • Type-scoped search (/double kP). Collides with Space-to-pin; search stays simple.
  • Quick-jump slots. Overlaps presets; the same "needs season reps" question applies, and the answer today is no.
  • Target auto-discovery. Team-agnostic tool; the Connection Picker is sufficient.