I acknowledged that Prism is great framework that support MVVM (Model View View Model) design pattern. First of all, I am introduced to few terms based on the course I followed on some courses and tutorials (Title : Introduction to Prism for WPF).
Next, I learnt how to perform view injection to allow certain text to be displayed when i run the the program. It is performed simply just by linking instance of region to specific region called as ” NAME” in XAML file. Other than that, I also followed some step to implement View Model Locator and construct property to allow connection between View(XAML file) and View Model(CS file) in prism.
Beside that, I came across to know about delegate command, where it is used to implement ICommand without require an event handler. Delegate command can invoke method defined in ViewModel and let u control the properties on view from ViewModel. Hence, I played around with ICommand provided by prism that bind UI gesture to particular action/event. Along side of that, I also try out composite command, where it is able to invoke multiple view on one touch and IEventAggregator, which is a good implementation when you have lots of objects that are potential event sources.
Lastly, I understood the purpose of Dialog in prism library as it is used to notify user of current system progress or asking for user’s confirmation upon an action. In dialog, it is divided into two type, where one is block interaction with the rest of the application (modal) and one is to allow user to still interact with the other part of application (non-modal).
Conclusion, I do have to admit spend quite some time understanding how prism library works as I am still weak in programming knowledge, but thanks to guidance from my supervisor and going through it several times, I managed to get a grab on my understanding.