Skip to content
Eddie Antonio Santos edited this page Feb 8, 2015 · 1 revision

User Stories and Requirements

This is part of the "Eddie's Overthinking" series.

This pages lists some user stories that are used to help guide the development of Waterbear. This is not an exhaustive list.

User

As a user, I want to run my program.

As a user, I want to see where blocks will go when I drag them into the editor.

As a user, I want to see how my program affected the state of the screen and variables when I stop my application.

As a user, I want to debug my program.

As a user, I want to step through each block invocation in my program.

As a user, I want to see the current value of variables as I step through my program.


Waterbear Developer

As a developer, I want to avoid using a build system so that the developement cycle is quick and there is a low learning curve for new developers.

Block Writer

As a block writer, I want to organize my blocks into a category.

As a block writer, I want to directly specify a JavaScript function to call for each of my blocks.

As a block writer, I want to write multi-methods.

As a block writer, I want to specify that my blocks require assets or services before the script is run.

As a block writer, I want to write my block UI directly in HTML so that I'm not fiddling around with some awkward JSON format 💩.

As a block writer, I want my blocks to be localizable.

Localizer

As a localizer, I want to localize blocks for my given locale.

As a localizer, I want to change the order of the wb-values in a block so that it translates properly into my loclae without affecting the semantics of the block.