atomic14 / atomic14/web-serial-plotter
[Feature]: Separation of channels & URL query
- Lenguaje dominante
- TypeScript
- Estrellas
- 198
- Forks
- 25
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Problem to solve
Good stuff.
This isn't as much as a request as it's just some ideas off the top of my head.
Just some ideas to keep you going ;)
Regards,
Toon
### Proposed solution
1) I think it would be cool if you had a separate channel for plotting and for terminal messages.
E.g.: messages starting with 0x00 go to the plotter, messages with 0x01 got to the terminal.
You could even allow multiple channels for plotting and multiple terminal channels. A split screen where the left is the scope and the right is the terminal would also be cool.
Example use case:
Imagine an application with 2 motor's being controlled by 2 pid loops. We could split the uart data into 4 channels:
- 0x00 Plotting of PID internals of motor 1
- 0x01 Terminal to tune PID of motor 1
- 0x02 Plotting of PID internals of motor 2
- 0x03 Terminal to tune PID of motor 3
2) Another cool feature would be if you could "configure" the ui through a url query.
E.g: https://web-serial-plotter.atomic14.com/?legend=p_error,i_error,d_error
That way you could always come back to the same setup.
### Alternatives considered
_No response_
### Area of the app
None
### Willingness to contribute
- [ ] I'd be willing to submit a PR for this
- [ ] I can help test and provide feedback
### Additional context, screenshots or mockups
_No response_
Guía de contribución
Línea de trabajo
El issue no nombra archivos, pruebas ni puntos de entrada concretos. Empieza por localizar el flujo de datos de Web Serial, las vistas de gráficos y de terminal, y el manejo de consultas de URL; el trabajo estaría terminado cuando exista un diseño acordado para la separación de canales y una configuración reproducible de la UI, seguido de pruebas para ambas funcionalidades.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- typescript
- Área
- frontend, web-dev
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100