[Transition to WPF] ServerSharingView & ServerSharingViewModel

[database64128]

Please follow the guide below

• You will be asked some questions, please read them carefully and answer honestly

• Put an x into all the boxes [ ] relevant to your pull request (like that [x])

• Use Preview tab to see how your pull request will actually look like

• Searched for similar pull requests

• Compiled the code with Visual Studio

• Require translation update

• Require document update (readme.md, wikipage, etc)

What is the purpose of your pull request?

• Bug fix
• Improvement
• New feature

---

Description of your pull request and other information

This is a series of attempts that aims to modernize shadowsocks-windows by rewriting most UI components using WPF and standard MVVM patterns, and eventually make it a highly-maintainable WPF MVVM project.

This PR adds the ReactiveUI.WPF package as the MVVM framework. The old server sharing form is replaced with a new one implemented in XAML.

[Stzx]

If I use WPF technology, I actually prefer to open a new WPF UI project directly in v5, and then gradually convert the old project into a library.

[database64128]

If I use WPF technology, I actually prefer to open a new WPF UI project directly in v5, and then gradually convert the old project into a library.

It's certainly more clean to start a new WPF UI project from scratch. And it's definitely a good idea if you have quite a bit of time dedicated to the project.

However, given the condition of the project, I'm not confident if I can accomplish all these goals on my own. For now, I'd rather take baby steps: convert to WPF incrementally.

BTW, I feel the Shadowsocks organization is rather fragmented, compared to other similar organizations like V2Fly. The communication between maintainers at Shadowsocks is rather rare, with mostly infrequent exchanges in issues and emails. It would help a lot if we could have some kind of group chat between maintainers and contributors for more direct communication.

[Stzx]

Yes, this is indeed a problem. There are not many developers currently active in the project. Most of the existing developers are busy with things in real life, so the cost of communicating with each other is high.

BTW, It has not yet been determined whether the UI will be rewritten in v5 and what technology will be used. .NET 5 will be released soon, I think it’s time to determine this problem.

[ghost]

IMO add a WPF window (not WPF control in WinForms window) is better.

[database64128]

Are we cleared to merge now? 😃

[database64128]

Note that the current placement of ServerSharingWindow in the project root directory is intentional and was only decided after careful consideration. The ServerSharingWindow, along with some other WPF windows coming in future PRs, is intended to hold the related control as a temporary replacement of previous forms. Eventually the new main interface will include all these controls and the windows will be removed. These windows are definitely not views. After examining some similar projects' directory layout, it's my opinion that the project root directory is the best place to hold them for now.

Thanks @studentmain for reminding me of this situation.

[database64128]

Although we will be mostly targeting v5/master for the new WPF interface, we won't have a usable build for a long while. I think it's not a bad idea to bring some new stuff back to master for more coverage. If no one is opposing this, I'm merging the PR in 24 hours.