Wiring Up Communication

Thu, 10 Oct 2019 22:58:00 +0800

As we mentioned in the last AiMC post , the next task is to wire up communications between the simulator’s backend and frontend.

As a general rule, our frontend will have two communication regimes:

When something happens (e.g. a button is pressed or a job starts sending), the frontend will send a batch of messages to the backend and interpret the response
The frontend will continually poll the backend’s state in the background (e.g. at 10Hz)

As it is, the Browser in our WASM code already provides a method for sending data to the frontend (Browser::send_data() ) and receiving data from the frontend (App::on_data_received() ) so we shouldn’t need to write any Rust code.

A Better Frontend

Fri, 27 Sep 2019 03:47:00 +0800

Now we’ve got a half-usable motion controller, we need a graphical way for humans to interact with it. The controller runs in a browser, which makes Vue a perfect candidate for the UI.

Adding Vue to the Frontend Link to heading

Now, we don’t actually have much frontend code (47 lines of JavaScript to be exact) so it’s actually easier to delete the existing frontend and use the vue CLI tool to create a new one.

Vue.js on Michael-F-Bryan

Wiring Up Communication

A Better Frontend

Adding Vue to the Frontend Link to heading