Right now, a lot of the logic for creating and maintaining a number of terminals lives in the TerminalApp::App singleton. That's not exactly correct by "xaml application" standards (nor is it correct by normal application standards.)

Pull request #XXX introduced a new xaml page that hosts the UI for the terminal. It should be tasked with maintaining the state of a number of terminal controls and connections so that ti becomes a reusable component. This may even be a step on the path to having multiple top-level windows hosting terminals -- if App can be the singleton in charge of settings and profile management, and a window can host a page instead of an App, we're in a better position to spawn more than one. 😄