splitting the SwipeNavigator

The SwipeNavigator has been commonly criticised as being too monolithic; many applications reimplement random parts of it instead of using the control. Splitting the SwipeNavigator up will make it so that these applications can share code & be more consistent with eachother.

Split One: TopBottomSwitcher

This pattern isn't the most common, but some applications use it. Essentially, it's a bar switching being between above and below a body depending on whether or not the application is running on a mobile device.

Split Two: FixedTab

This is similar to a Tab control, but with some extra APIs for controlling the appearance. May be possible to refactor into Templates.TabButton. Reimplemented by a lot of PlaMo applications that refuse to use the SwipeNavigator.