RenderClientAdapter is now CefBrowserWrapper, and RenderClientAdapterInternal has been freed of the quite pointless "Internal" suffix.
Settings.h is now CefSettings.h
Renamed the class also, since "Settings" isn't really clear enough IMHO.
Sorted the properties alphabetically, to make it more maintainable.
Added the RemoteDebuggingPort, which is needed to get the DevTools working w/ CEF3.
Made the OnLostFocus a bit safer when shutting down the app and cefBrowserWrapper may be null.
Started working on the DevTools stuff, which is seemingly non-trivial since we can no longer just call a method but need to open up the devtools URL ourselves.
Let's try to do things in a more MVVM-orthodox way. This is one of the first steps on a quite long journey I believe… The previous CefSharp.Wpf.Example was (in my opinion) slightly badly designed in that it too much tried to "reuse" code between the WPF and WinForms examples. Now, this is good from a CefSharp maintainability standpoint, but it really means that you will "dumb down" the WPF one in a way that feels very unnatural to me. WPF is WPF and should be done in a certain way (to take advantage of the platform), and WinForms is an entirely different beast. So, I feel that it is very much OK if these sample apps diverge much more, so that we demonstrate CefSharp usage in a more realistic, close-to-real-life way than has been the case before.
Need to set the RemoteDebuggingPort when initializing CEF, to be able to use the devtools. This code will have to be slightly refactored if/when we skip the Presenter approach entirely for the WPF example.
Improved the reliability of the code to better handle cases when things happen "out of order", or at least in another order than we are expecting. (which is often the case when using data binding etc)