dashboard design

[Geal]

there is none :D
Just an accumulation of graphs. Let's find a way to make it look nice! I'm open to any idea and pull requests here. There's only one thing that will stay for now: using chartjs to display the data (for performance reasons). But any graphical changes to the graphs are fair game :)

[Vengarioth]

Hey @Geal, i'd love to contribute to the frontend. But i'd rather put it into it's own repository, make a webpack/babeljs pipeline and use reactjs.

[Geal]

why in another repository? I'm not really attached to the current frontend code (I mean, look at it :D), so it should be fine.
A few things that I'd care about though:

• I'd like a way to embed the frontend inside the executable, to avoid carrying assets in folders everywhere (right now it's done with include_str)
• the interface should feel fast, and the current way of downloading all the new points and updating all the charts at once will not work well once we get a lot of points, so maybe there's something to do with promises and async requests?

[Vengarioth]

Another repository because it would come with it's own unit tests and build steps.

The produced artifact would be a single js file with all needed ressources embedded into it. just <script src="..."> it into an html page and it works (i would not add dependencies over the web since dashboards often run on boxes without web access). So yes, this file can be embedded into the executable. It should also be possible to directly embed it into an html wrapper.

About the data management, it absolutely should be async and at best should use the same API accessible to everyone using it. My usual aproach is axios and redux, if data changes come in too frequent for redux then build something new with the react context api.

[Vengarioth]

started building it at https://github.com/Vengarioth/grad-frontend can transfer the repo to you if you like

[Geal]

it can live there for now, it's fine. How would you integrate that with the cargo build? Considering that the file should be integrated when building, even in a cargo install

[Vengarioth]

i would commit the compiled js file into this repo, it should only be updated with new releases of the frontend project, at some point we can publish the frontend on either npm or cargo(packaged in a rust lib).

Edit: but the heavy lifting / build process into a rust accessible project should be in the other repo.

[Geal]

alright then :)