Originally posted by Tommy Mato:
Isn't having a single properties file/object breaking the independance of the M V and C? Should I think about having 3 separate properties files? After all, if I want to replace the View with another completly different view, I shouldn't have to 'disentangle' my view properties from the M and C properties.
If I can get away with having one file/object, how should I pass this object to the M, V and C? Is there a 'central' object that acts as the 'conductor' to the M V and C?
I would imagine that this is a common problem that applies to other objects that should be shared between the MVC components.
I hope this makes sense. Solutions and advice will be gratefully received.
"The differential equations that describe dynamic interactions of power generators are similar to that of the gravitational interplay among celestial bodies, which is chaotic in nature."
There will always be people who are ahead of the curve, and people who are behind the curve. But knowledge moves the curve. --Bill James