Questions first: - TxModel class comment - "I don't provide a direct interface for mutating/editing my data (and this is a very important point). Instead I am modified using position(s) (TxTextPosition) and/or selection(s) (TxInterval/TxSelection), providing a rich protocol for various operations over text." That sounds intriguing, but why is that so significant? - TxForeColorAttribute - Why not TxFontColorAttribute? Is the fore/font distinction important? - TxXyzAttribute - can we remove the 'Attribute' from all but the base class? e.g. TxFontAttribute -> TxFont - TxStyle - why both #at: and #get:?
Then a bit of cleaning... Issue 15475: TxText Cleanup for Pharo 5.0 #2 https://pharo.fogbugz.com/default.asp?15475 - TxXyzMorphs - Push up #openInWindowWithString:, #openInWindowWithText:, and #text, which each had two materially-identical implementations - Clean examples - TxModel - enhance class comment - TxStyle - Enhance class comment - Clean #removeAll comment - TxTextStyle - Enhance class comment - Clean #addStyle: comment - Clean #extend:with: comment ----- Cheers, Sean -- View this message in context: http://forum.world.st/TxText-More-Cleaning-and-Questions-tp4823894.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
