Design Document: Command History HUD

Status: Idea and mock

This is a 50 points implementation! :)

Overview

Right now when you run a command, the output is thrown into the infobar. There is no way to get back to it if time has moved on, and if two events happen quickly you can lose the information.

We want to migrate to a world where you send output events to the system and they are all saved away (both locally, and synced up to BespinSettings/commandhistory).

Here is a mockup (just look at the history piece):

Implementation

• When you have a showinfo / command event, save that info (again: use local storage and / or save to BespinSettings)
• Quick key / history button opens the HUD that shows the past output, and toggles it off

This fits in with the desire to have this feel more like a shell, where when open, it feels like a shell with commands and output. This makes "ls" make sense.

Questions

• Should it be a translucent HUD that comes over the editor? Or should it be more like the mockup, and have the editor move up?