This site and SO contain many pages about getters/setters and if they break encapsulation or enforce it. My question is for those developers that agree that getters/setters break encapsulation and should be avoided. Questions:How do you display your data in a GUI if necessary without getters? I found thislink, but to me it seems kind of strange for your class to beaware of components to display.To quote from this link:  It is certainly true that having getters and setters for every field  provides little more encapsulation than having those fields be public,  and it's unfortunate that this kind of design is very widespread.What if you designed a class where all the properties have getters for displaying, now I understand someone could call the getters and use them for calculations and behaviors other than displaying, but my point is, if you find it nessesary to provide getters for all your private variables to display, should you be rethinking your design? if so, how?I'm not talking about if when getters/setters are justified, but rather when display properties of an object, if you're providing getters/setters for all your properties, should you be rethinking your design? 
Encapsulation and Displaying Information
class;encapsulation;setters;getters