Culture

Culture is a role that determines your user interface. It defines what your users see on the page. Culture includes a lot of predefined behaviors, like what happens when a user clicks on a button. Cultures are extremely dummy, in that they have no memory, or state, of their own. They know how to draw a user interface and how to handle user input; which they delegate to the Representatives.

Cultures can contain other Cultures, in which case the children would be called subCultures. A list of clickable items in an application would be an instance of a Culture List, and individual items would each be instances of another Culture ListItem. Here, List has a number of ListItems as its subcultures. Obviously, both Cultures have different behaviors and responsibilities. You see where we are getting at.

Every Culture has a Representative of its own. Some Cultures are broad and generic, while others present Stereotypes to the end user. In the above example, Cultures List and ListItem are responsible for presenting respective Stereotypes to the user.

Cultures may welcome other, arbitrary Cultures as immigrant subCultures. These are commonly used as placeholders, as in modal presentations, whose content may vary greatly and therefore separated from a modal implementation.