Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Can anyone explain to me how NSAttributedString correctly follows the MVC paradigm? I know it doesn’t inherit from NSString, but it still is a string, so I would say that’s part of my model. However, setting UI attributes such as underline, font, shadow, etc. clearly are part of the View when talking MVC, so I’m not really sure how this follows the rules.
NSAttributedString is a model class.
It just has the representation of the attributed string.
Just because it stores the attributes, that doesn’t make it responsible for the display of the attribute.
Imagine you had a custom class for shapes. If you had a square shape and stored it’s colour, it would still be a model object, because it’s up to the presenting view to draw the square and fill it with the colour, the model object is just a place to store the attributes.