Timeline for MVC like design with interfaces: How to handle basic objects?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 2, 2015 at 22:55 | comment | added | Gunnar Bernstein | I followed your advice. I removed all interfaces from the objects and moved the mutable objects into the controller package, making the setters package-private (default). I then made a new package with all immutable objects for clarity. I kept the interfaces for controller and display, because it enables me to use a different output and is a clear definition of the communication ways. | |
| Mar 2, 2015 at 20:44 | comment | added | Patrick Peer | Hi Gunnar! You are right, my explanation was a bit lacking. I guess I got lazy towards the end :) Anyway, I added some thoughts to my original answer. Hope it helps ;) | |
| Mar 2, 2015 at 20:41 | history | edited | Patrick Peer | CC BY-SA 3.0 | Elaborated more on the interface approaches |
| Mar 1, 2015 at 19:42 | vote | accept | Gunnar Bernstein | ||
| Mar 1, 2015 at 18:00 | comment | added | Gunnar Bernstein | Thanks for this, it is helping. What do you mean you do not recomment interfaces at all? I like the interface approach to the controller as it gives a strict definition of what methods are used outside the inner logic. If I change one of the these I have better awareness. | |
| Mar 1, 2015 at 10:38 | review | First posts | |||
| Mar 1, 2015 at 13:10 | |||||
| Mar 1, 2015 at 10:36 | history | answered | Patrick Peer | CC BY-SA 3.0 |