Alain is rewriting textMorph so it will get better. Then sean did you look at the new debugger model?
Stef On Apr 10, 2013, at 8:38 PM, Igor Stasenko <siguc...@gmail.com> wrote: > On 10 April 2013 20:08, Sean P. DeNigris <s...@clipperadams.com> wrote: >> I'm writing a little debugger extension and I want to replace the entire >> method source with another string. >> >> I thought of two ways: >> >> aDebugger getTextMorph textMorph editor selectAll. >> aDebugger getTextMorph textMorph editor zapSelectionWith: aString. >> >> or >> >> aDebugger getTextMorph textMorph contents: 'meaning: aString >> meaning := aString.' >> aDebugger getTextMorph textMorph editor userHasEdited >> >> They both work, but what is the best/correct way to do something like this? >> >> Thanks! >> > > + 1 i wanna know that too. > the problem with it, that the model is so diverse that you have no > clue, which object is actually > true holder (owner) of text, while others using it just for quick access. > > and also i don't like the expression length: > aDebugger getTextMorph textMorph editor userHasEdited > > (poor guy, Demeter, and his law ;) ) > it should not be like that.. (maybe we need to think about proper api there?) > > > -- > Best regards, > Igor Stasenko. >
