As I was drawing various mock-ups it occurred to me that we're going to want a coherent user interface, and we're going to be constantly reinventing the wheel if we don't do this.
Let's write a XAML user control that will set the tone for all RD3 dialogs and prompts. Something like this:
ViewModel would include:
[ ] TitleText
[ ] IconSource
[ ] TitleLabelText
[ ] InstructionsLabelText
[ ] OptionLabelText
[ ] CancelButtonText
[ ] DefaultButtonText
[ ] HasOption: whether or not to display the OptionLabel and bind OptionLabelText
[ ] HasCancelButton: whether or not to display the CancelButton and bind CancelButtonText
[ ] CanResize: whether or not to include minimize/maximize buttons in the control box, and whether the user can drag the border of the control to resize it
[ ] ClientAreaMinHeight: ensures a minimum breathing space for the client area when [re]sizing.
The bare-bones default configuration might look like this:
[ ] Refactor MessageBoxControl and any other existing dialogs as a child component of this new control.
As I was drawing various mock-ups it occurred to me that we're going to want a coherent user interface, and we're going to be constantly reinventing the wheel if we don't do this.
Let's write a XAML user control that will set the tone for all RD3 dialogs and prompts. Something like this:
ViewModel would include:
OptionLabeland bindOptionLabelTextCancelButtonand bindCancelButtonTextThe bare-bones default configuration might look like this:
MessageBoxControland any other existing dialogs as a child component of this new control.