- Sep 15, 2005
- 3,622
- 1
- 0
I understand, you can have a model..you can use the model to feed multiple views..ok..
But I have ALWAYS been able to do this just by using a data structure
lets say i have an array of "profiles"
If someone right clicks on the gui and selects "delete" for a certain profile, I remove it from that item in the GUI and then remove it from the datastructure...
I really don't see the benefit of models. It just seems like a huge pain.
I know I probably sound stupid, but I just don't see the point.
What I am having difficulty understanding is: If I already have the data in a structure and can access its pieces (say strings), why would I want to add another layer of objects into the mess loading the information into a model?
When I was using Ruby on Rails, it all made sense. It FORCED you to do it that way. I am having great difficulty imaginging how to do something similar with c++.
But I have ALWAYS been able to do this just by using a data structure
lets say i have an array of "profiles"
If someone right clicks on the gui and selects "delete" for a certain profile, I remove it from that item in the GUI and then remove it from the datastructure...
I really don't see the benefit of models. It just seems like a huge pain.
I know I probably sound stupid, but I just don't see the point.
What I am having difficulty understanding is: If I already have the data in a structure and can access its pieces (say strings), why would I want to add another layer of objects into the mess loading the information into a model?
When I was using Ruby on Rails, it all made sense. It FORCED you to do it that way. I am having great difficulty imaginging how to do something similar with c++.
Last edited: