Rework User interface workflow

[bastianilso]

The current user interface is informative, but it lacks a general flow. Students were confused about what to do after connecting the arduino and when the arduino connection finished. Also, it wasnt clear whether you could repeat the exercise consecutively without closing and opening the RTIIArduinoLogger first.

• [ ] It would be helpful to separate it into several pages, rather than showing all elements at once.
• [ ] There should also be much more clear feedback once the arduino rtii logger is done logging.
• [ ] Show a button from which you can start a new logging session.

[bastianilso]

Here are some initial UI mockups for revamping the workflow.

Behavioral remarks:

• Everything is now in several pages, like a wizard.
• First we ask people to insert their e-mail and Arduino system path.
• We then switch to a page, where we attempt to connect the system. Show this page for minimum 2 seconds and time-out the MySQL connection after 5 seconds.
• We then show a blank Arduino output window on the right side (currently not showing Arduino messages), and a record button on the left side.
• When pressing the record button, we start to show Arduino Output in the window and the button is changed to Stop Logging. For now, we dont save anything to disk, instead we just create the LogCollection and keep it in memory.
• When the stop button is pressed, we stop the recording, and offer people to either save the logs to disk, or restart the logging.
• The mockups might miss some details that the current interface has - feel free to keep those interface details - the main idea is to rework the flow here.

[bastianilso]

here is a mockup for some error handling:

and assets: assets-new-navigation-flow.zip checkmark-icon.zip