'''Introduction to interface:'''

This interface is used to program a LEGO Mindstorms robot. Building blocks (Programming components) are always available at the left side of the screen. Images are iconic (which is less intimidating). Multiple pages of programs can overlap each other (notice the “Untitled-5” tab in the “Programming 3” screenshot). A window, to change preferences for an action, is always available at the bottom of the screen.

'''Application to personal research:'''

A page could consist of time-lines connected together by decision branches (i.e. it would be a “tree” [in the computer science sense of the term] of time-lines). A branch could lead to another time-line on the same page, or to an icon that would tell the user what page contains the time-line that the branch leads to (clicking on that icon would take the user to that page and time-line).

If we made a list of programming components, it could consist of:

  • Animate (to play any animation/sound)
  • Wait (to wait for remote control, sensory input, or time)

After a Wait, control could change over to somewhere new in the script.

Perhaps Animates and Waits could exist on two separate lines of a time-line.


  • Would it be better to have a “loop” programming component, or have looping a variable of an animation block?
  • Would it be better to show more information about a programming component ON the block instead of in the window at the bottom of the screen?

'''Additional notes:'''

  • LEGO Mindstorms robots can also be programmed using Microsoft's Robotics Developer Studio

« User Interface Design

ar/alan-s-thoughts-on-the-lego-programming-interface.txt · Last modified: 2014/08/11 16:02 (external edit)
Back to top
CC Attribution-Share Alike 4.0 International
chimeric.de = chi`s home Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0