Allow for insertion of both info and interaction modules into main page

[AdamVig]

Currently, there is an ng-repeat that iterates over the list of selected modules and, for each selected module, creates and <info-module> element that it populates with all of the data from the selected module.

To add interaction modules, there will have to be a check of what type of module the selected module is, then the view will have to conditionally render either an <info-module> or an <interaction-module>.

[AdamVig]

Alternatively, the current method of rendering modules in the main view could be kept in place and interaction modules could be rendered exclusively at the end of the list. Arguments for this:

• Interaction modules could ruin the aesthetics of the app if mixed with info modules. Now that the app automatically loads all info modules every time the app is opened, it is a nice effect to see the ripple of data loading down the list of info modules. There is a slight delay between each module making its data request. Having interaction modules interrupting this flow of data loading may ruin the effect or at least make it more difficult to discern.
• Interaction modules do not need to be at the top or middle of the list because they will be less commonly used. The majority of modules represent simple data that can be represented by numbers. With auto loading, the user can open the app, set it down on a table, and watch all of the data pop up. If the user has interaction modules at the top of their list for some reason, the user may have to scroll down to see all of the data he or she has requested.

Arguments against this:

• This is the first limitation that will be enforced on the user. Up until now, the user had complete control over the order of modules in the list. Users will still be able to move info modules as they desire, but they will be forced to keep interaction modules at the bottom of the list.
• It is difficult to communicate to the user that they cannot move interaction modules to wherever they want in the list. It could create friction and therefore frustration as the user fails to move the modules. A possible solution would be to split info modules and interaction modules into separate sections in the selection list so that they are clearly shown as being separate categories.

Options:

1. Allow interaction modules to be reordered with info modules so that the two types of module can be interspersed in the list.
2. Separate info and interaction modules into two sections in the selection list so that the user can understand why the interaction modules show up at the bottom of the list.

[AdamVig]

The Solution

1. Maintain the current module list view and selection options view.
2. Combine infoModule and interactionModule directives into dataModule to allow for ng-repeat behavior in the main view.
3. Standardize parameters on new hybrid module to allow for different behavior but consistent markup.