All widgets/primitives should take an object

[smithfarm]

mfile-www implements a number of "widgets", or primitives such as dform, dmenu, etc. for displaying "pages of content" and accepting user input.

With the advent of the target stack, there is a need to standardize how the "content" is provided to the widget. It will be good if each widget expects to receive an object. The exact contents of the object will differ from widget to widget, but it will be an object.

The start method of each primitive will take two arguments:

1. the content object, called "state"
2. an optional options object, called "opts"

When stack.push or stack.pop is called, the caller will provide these two arguments, and stack.push/pop will pass them on to the widget's start function.

If no state is given on stack.pop() - i.e. state === undefined - the state will be taken from the stack.

• dmenu
• dform
• dbrowser
• dnotice
• dtable
• drowselect