"The font is then responsible for providing the drawing commands and metrics for the particular glyph when it's drawn."
sounds like Cocoa delegates rendering to the font. On Nov 20, 2012, at 10:09 PM, Camillo Bruni wrote: > > On 2012-11-20, at 17:30, Denis Kudriashov <[email protected]> wrote: > >> Hello. >> >> Can you add me as project contributor. I try to upload version with >> detailed comment from my first mail but can't. >> >> 2012/11/18 Camillo Bruni <[email protected]> >> >>> I don't think the basic model should know about the visual lines. We >>> discussed >>> that for a while, but in the end that's purely a view on the basic model. >>> >> >> If such behaviour will be at view simple Cursor>>moveUp/moveDown will never >> work right from user perspective. So why you need cursor at text model >> which will never reflect state of visual cursor at screen? > > it depends, I think the model should not take the view into account. > First we implement the cursor movement as simple as possible, and that is > for now on the model-base. > > If it will work properly or not depends on the view implementation. > >> To me text model should completly represent what user see at text view. >> Otherwise why you call it model? Otherwise it is just raw data like Text in >> current TextMorph > > Model IS the raw base model, the view is what you see, that are definitely > two different things. > For instance where would you deal with hyphenation? dynamic layouts? > > I don't think they belong in the model and I think we should stick to > existing implementation schemes (M VC) and existing implementations > like Cocoa... > >
