Process terminal view

[sgmunn]

• Refactoring of Terminal View
  • move the scroller from TerminalControl into TerminalView
  • added visual padding around the terminal content
  • added ability to change fonts and recalculate the terminal dimensions
  • fixed a couple is miscellaneous layout issues
  • reduced some of the duplicated layout logic to a class to track cell dimensions
  • added ability to change fonts and recalculate the terminal dimensions
  • added ability to change font colors
  • changed caret view to use a mask so I can reuse location calculations. also allows some other options for how to draw carets.
• Rename TerminalControl to ProcessTerminalView
• Introduce a LocalProcess class that sends and receives data from a process

Fixes #53 #54 #52

• Fixes an issue where changes are not shown because of a mismatch between the UpdateRange and where the caret is on screen. (add content to the view so that it scrolls, 'clear', then scroll back. The caret will be visibly down the view but the update range will be row 0. this results in invisible text and output on the view).
• Implements "userScrolling" in Terminal
• Implements SelectedRange (but not 100% sure how to test this)

[sgmunn]

The thought occurs to me that LocalProcess could have an abstract ancestor "TerminalProcess" (?) and remote / connections could derive from that. LocalProcessTerminalView could be ProcessTerminalView (? ugh) or something nicer sounding. LocalProcessTerminalView.Process could even be just "Connection" and we could loosely describe a terminal view being connected to something (a local process, a remote process, etc).

~Maybe even just fold what's in LocalProcessTerminalView into terminal view altogether. Wasn't sure if welcome / exit text ought to be a part of TerminalView or not.~

edit: I looked briefly at making ProcessTerminalView a subclass of TerminalView but I wasn't happy with how I had to rewire events. I think this can be done but I need to take another look at what events need to be hooked up and how that can be done sanely and still allow for others to subclass / extend without breaking functionality.

[sgmunn]

Might need to come back and take another look at text selection. We also need to implement double click to select word etc