Thank you for this suggestion. I will investigate this and probably will write a KB article or a blog post on how to achieve this in the next few days. Thank you again for your suggestion.
I am still working on this. I hope by the end of the week I will have a blog post about how to use different selectors. I will see to it to have at least the new image selector described.
I'm still on it. I think I will be able to post some posts during the weekend. Stay tuned.
I was thinking about that - about making the dialog with two tabs - one for internal site pages and the other for external pages. The problem is how to store the selected value, since we have only one field and we have to distinguish the value stored in it.
You could also check this blog post by Josh Morales:
I'm still working on the next blog post in the series - an image and multiple image selector.
As for your other question - since the PageSelector is just a FieldControl, like any other field controls it may be included in the definitions of your Edit/View views - the same way as, e.g., TextField - either with the new Fluent definitions API or the classic definitions API. A very good example on the latter may be found in the Products or Locations modules from the SDK.