Develop detailed requirements for split screen viewer

[torrin47]

This ticket is to spend time thinking through the workflow for using the split screen functionality in a detailed way and capturing those requirements so we can work through individual tickets.

[torrin47]

Here's a brainstorm of splitscreen requirements...

• User needs to be able to start working in one frame, then switch to two-frame mode without losing session in first frame (added layers, widgets, etc.)
• Is it possible to create a clone of the first, with all the same session elements (layers added, community selected, etc) chosen? Would it be equivalent to the Save Session widget?
• What about when switching back from 2 to 1? Do we need to save the second frame session choices (selected layers, etc) in case a user toggles back again to 2, or does closing the second window torpedo that session and start a new one with a cloned first frame again?
• Choice to switch between 1 and 2 frames should be incorporated into main UI, which might mean that we switch from the current WAB layout (which includes the header) to one of the ones without a header (launchpad or dart?) to get more screen space, and then we move the header elements (title, icons, etc) to the external frame.
• We're going to have to pay a lot more attention to responsive design, as we will be more likely to encounter limited screen space when using split screen.
• Synchronized map extent (with ability to toggle on and off) seems perfect. Because intent of split screen functionality is to enable comparisons between communities, though, we can't synchronize or couple other session elements (like added/selected layers or selected community) following the initial clone, or can we? Are there specific elements we want to be able to synchronize? Like adding layers?
• Anything else?

[torrin47]

This issue was moved to USEPA/EnviroAtlas_JSApp#21