Have Geek Brain

MCV / MVP templates and applications that interact with hardware (DAQ / PLC / etc)

I've read a lot about MCV and MVP patterns for use with UI and this seems like a really good powerful way to handle UIs. However, I am having a hard time figuring out how this can be integrated into a system where the data in the model is generated using a data acquisition system or serial / Ethernet devices. There is also an added step that 70% of the application interaction is done by the PLC instead of the live user.

It looks like this works great for applications that just read / write and manipulate information from the database, but how does hardware and automation fit into these patterns? Is it as simple as another controller (for lack of a better term) that interacts with hardware that manipulates data and writes to a model?

I may have changed my mind or thought too much, so any advice would be great. I'm not entirely sure where I'm going with this, so if something doesn't make sense or I'm too vague leave me a comment.

Thanks!

+2


a source to share


2 answers


The hardware state is your model. How it updates is not part of the pattern, just how updating the state affects your view.



+1


a source


Just adding to what Hans said. Your data is collected into the data model of your application.



(Using MVVM / WPF / Silverlight context) This in turn should result in a NotifyPropertyChanged event on your ViewModel (aka Presentation Model), which is then automatically propagated to your view via data binding.

0


a source






More articles:


All Articles