Re: [Pharo-users] [pharo8-api-change] newTextEditor

2020-03-01 Thread Hilaire
Ok, never mind I figure out. Announcement framework is neat. They were a couple of errors with the Rub** related to the change of #contents to #text message, which is more meaningful. Le 01/03/2020 à 11:44, Hilaire a écrit : > *Question.* > > In RubPluggableTextMorph why the access to the announ

Re: [Pharo-users] [pharo8-api-change] newTextEditor

2020-03-01 Thread Hilaire
*Question.* In RubPluggableTextMorph why the access to the announcer instance is different in this two methods (quoted message of mine below) *self textArea announcer* ... and in the other place *self announcer* ... >From my understanding the former is the announcer attached as a property of the

[Pharo-users] [pharo8-api-change] newTextEditor

2020-02-29 Thread Hilaire
Hi, RubPluggableTextMorph replaced the old PluggableTextMorph. acceptOnCR: and changedAction: are not valid any more. For the former never mind. For the latter how should it be rewritten? I read these self textArea announcer when: RubTextChanged send: #whenTextChangedInTextArea: to: self. and