c# - Is it normal practice to have intermediate type(s) just for data binding purposes? (WPF) -
i have collection of types model system. want show functionality of system in gui (wpf). relationship between actual types isn't databindable is.
is normal practice have intermediate type(s) data binding purposes?
say like:
public class effectuielement { .name <string> .type <enum> .usage <string> }
where these values aren't in 1 place several, has pulled seperately.
is normal practice have intermediate type(s) data binding purposes?
yes. "viewmodel" in mvvm (model-view-viewmodel). mvvm pattern allows create viewmodel used expose model (your original data, can come 1 or more sources) view via data binding.
Comments
Post a Comment