Some moves towards UI isolation

[sorsarre]

Trying to jumpstart decoupling the Razor's functional guts from WinForms specifically and UI side of things in general.

Why bother?

• In order to enable changing the frontend Running headless, making an alternative UI in case MS kicks WF to the curb; @markdwags mentioned ditching it all in favour of gump-based UI, which would be absolutely wicked.
• Enable unit/auto tests for core stuff Mixing UI code with engine guts in a global static object managing a pile of its own instances effectively kills any prospect of unit/automated testing, aside from causing a literal headache if meditated upon for long enough.

What's in?

Not much compared to the whole workload necessary to run headless, but I hope it's a start.

Dragged some UI code from obviously domain stuff:

• Filters
• TextFilterManager
• WaypointManager
• OverheadManager
• TargetFilterManager
• SoundMusicManager

On WinForms front:

• Fencing off some of the MessageBox calls behind a separate class — far from complete, but it's mostly straightforward, will do a more extensive overhaul in a separate PR;
• Same for most clipboard calls except ones that deal with images — will have to take a better look af them.

What's next?

Specific plans are part 1, parts 2 & 3 are more in the vague far-off milestones department for now.

1. Continue UI split
   • Remaining object managers (friends, counters, etc)
   • Agents
   • Macros
   • Hotkeys
   • Scripts
   • Deal with MessageBox infestation
   • Direct WinForms Clipboard calls
2. Move core stuff into a separate assembly
3. Fence core-to-UI interactions behind a set of interfaces

[mythril]

I have written a RunUO gump script that fairly well emulates a tabbed interface. It's a bit huge and knobby because of the constraints of gumps, but I would happily share the code and some screenshots if it will help.

[mythril]

If I can get Razor building on my system I might also port the idea to Razor just to contribute.

Looking for detailed build instructions on Linux if anyone has them.

Or command line (I don't have Visual Studio) instructions for Windows 10.