- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] A taste of bootstrap

by stepharo

> 2016-07-22 15:12 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com > <mailto:pavel.krivanek@gmail.com>>: > > From the Pharo/Squeak point of view this image is very special > because it doesn't contain any object inherited from 70's. Pharo > lost its umbilical cord. > > > Fresh objects tastes good :) I love it :) Excellent quote! I will reuse it. Stef

July 24, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60151 Home: https://github.com/pharo-project/pharo-core

July 24, 2016

[pharo-project/pharo-core] 38eda5: 60151

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 38eda59e2e6cd1af69c8f399c3add62581a703bc https://github.com/pharo-project/pharo-core/commit/38eda59e2e6cd1af69c8f399… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-24 (Sun, 24 Jul 2016) Changed paths: M NautilusRefactoring.package/ChangesBrowserTest.class/instance/tests/testInitializeWidgets.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60150.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60151.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60150.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60151.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Core.package/ComposableModel.class/instance/accessing/focusOrder_.st M Spec-Core.package/RadioButtonGroup.class/definition.st A Spec-Core.package/RadioButtonGroup.class/instance/accessing/buttons.st A Spec-Core.package/RadioButtonGroup.class/instance/accessing/currentlyActivated.st A Spec-Core.package/RadioButtonGroup.class/instance/accessing/currentlyActivated_.st A Spec-Core.package/RadioButtonGroup.class/instance/api-events/whenCanDeselectByClickChanged_.st A Spec-Core.package/RadioButtonGroup.class/instance/api-events/whenCurrentlyActivatedChanged_.st A Spec-Core.package/RadioButtonGroup.class/instance/api/addRadioButton_.st A Spec-Core.package/RadioButtonGroup.class/instance/api/canDeselectByClick.st A Spec-Core.package/RadioButtonGroup.class/instance/api/canDeselectByClick_.st A Spec-Core.package/RadioButtonGroup.class/instance/api/default_.st M Spec-Core.package/RadioButtonGroup.class/instance/initialization/initialize.st R Spec-Core.package/RadioButtonGroup.class/instance/protocol-events/whenCanDeselectByClickChanged_.st R Spec-Core.package/RadioButtonGroup.class/instance/protocol/addRadioButton_.st R Spec-Core.package/RadioButtonGroup.class/instance/protocol/canDeselectByClick.st R Spec-Core.package/RadioButtonGroup.class/instance/protocol/canDeselectByClick_.st R Spec-Core.package/RadioButtonGroup.class/instance/protocol/default_.st A Spec-Core.package/SpecFocusOrder.class/README.md A Spec-Core.package/SpecFocusOrder.class/definition.st A Spec-Core.package/SpecFocusOrder.class/instance/accessing/presenters.st A Spec-Core.package/SpecFocusOrder.class/instance/as yet unclassified/addLast_.st A Spec-Core.package/SpecFocusOrder.class/instance/as yet unclassified/add_.st A Spec-Core.package/SpecFocusOrder.class/instance/as yet unclassified/giveFocusToNextFrom_for_.st A Spec-Core.package/SpecFocusOrder.class/instance/as yet unclassified/giveFocusToPreviousFrom_for_.st A Spec-Core.package/SpecFocusOrder.class/instance/initialization/initialize.st A Spec-Core.package/SpecFocusOrder.class/instance/to clean later/ifEmpty_ifNotEmpty_.st A Spec-Core.package/SpecFocusOrder.class/instance/to clean later/ifNotEmpty_.st A Spec-Core.package/SpecFocusOrder.class/instance/to clean later/removeAll.st A Spec-Tests.package/SpecFocusOrderTest.class/README.md A Spec-Tests.package/SpecFocusOrderTest.class/definition.st A Spec-Tests.package/SpecFocusOrderTest.class/instance/running/setUp.st A Spec-Tests.package/SpecFocusOrderTest.class/instance/tests/testAdd.st A Spec-Tests.package/SpecFocusOrderTest.class/instance/tests/testAddLast.st A Spec-Tests.package/SpecFocusOrderTest.class/instance/tests/testGiveFocusToNextFrom.st A Spec-Tests.package/SpecFocusOrderTest.class/instance/tests/testRemoveAll.st Log Message: ----------- 60151 18747 Improve RadioButtonGroup https://pharo.fogbugz.com/f/cases/18747 18742 add class to manage focusorder https://pharo.fogbugz.com/f/cases/18742 http://files.pharo.org/image/60/60151.zip

July 24, 2016

Re: [Pharo-dev] Questions about TextModel in Spec

by Yuriy Tymchuk

> On 24 Jul 2016, at 15:55, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > On Sun, Jul 24, 2016 at 02:35:13PM +0200, Yuriy Tymchuk wrote: >> Iâve found a partial hack: >> >> whenEdited: aBlock >> "Set a block to perform when the text wasEddited & the widget entered hasUnacceptedEdits mode" >> >> hasUnacceptedEdits whenChangedDo: [ :val | >> val ifTrue: aBlock value ] >> >> So now before the text is accepted I can block some other widgets > > wtf is whenEdited: :-o Thing that is called when the text is edited (when the orange triangle appears). I need a way to know that the text in the editor is different on from the excepted. > > There are couple of bugs I've reported last week in regards to this, because it's quite annoying. > https://pharo.fogbugz.com/f/cases/18799/TextModel-whenTextChanged-and-whenT… > https://pharo.fogbugz.com/f/cases/18800/TextModel-has-inconsistent-text-cha… > > I guess whenEdited: should be added to those issues. > > Btw, what are you trying to do? Because I was playing around with custom styling for my DSL (parsed & highlighted by PetitParser), > but got stopped by this same issue. Just RB highlight, but I want it to be switchable i.e. #parseExpression:, #parseMethod:, #parseRewriteExpression:, #parseRewriteMethod: Uko > > Do you use a similar setup? Could we extrapolate something generically useful from this? > > Peter > > >> >> Uko >> >>> On 24 Jul 2016, at 14:17, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>> >>> >>> >>> 2016-07-24 13:45 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >>> There is #pendingText to access it, finally found that. Now I want to detect when someone starts typing and do actions (like disable something until the text is accepted). There is whenTextChanged: but itâs not that useful because it checks if the accepted text has changed. Is there a way to check if pendingCode has changed? Or if the model is entering âhasUnacceptedEditsâ? >>> >>> No :( >>> >>> I don't think this is possible. >>> You could turn autoAccept to true and listen for set a whenTextChanged block, but of course, you can not display "unaccepted" text anymore, because all text is accepted. >>> >>> Uko >>> >>>> On 24 Jul 2016, at 12:48, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >>>> >>>> Cool. Thank you Nicolai. While we are on this, is there an example of how to display the parsing/compilation error as is done in playground? >>>> >>>> Uko >>>> >>>> >>>>> On 24 Jul 2016, at 11:37, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: >>>>> >>>>> >>>>> >>>>> 2016-07-24 11:35 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: >>>>> >>>>> >>>>> 2016-07-24 11:14 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >>>>> Hi, >>>>> >>>>> at some moment I wrote a super angry comment about Spec. But as there is a big effort put into documentation & improving the framework Iâve decided to give it another try. >>>>> >>>>> And guess what, after 10 min I ran into yet one more problem. I was expecting that it will be tough to have a custom styling for code, but no itâs much simpler: how do I get a text from text model? I type something in, sent #getText to the model => nothing. I expect that the problem is that the text is not acceptedâ¦ Why in the first place a basic text model needs this âacceptâ stuff? What if I have just a dialog where someone types something and submits it? I donât need accepts with orange corners for that. >>>>> >>>>> textmodel autoAccept: true. >>>>> >>>>> >>>>> I think that youâve got the idea. I just want to build a simple UI and it looks like itâs easier to do it with Morphicâ¦ >>>>> >>>>> Cheers. >>>>> Uko >>>>> >>>>> >>>>> But I agree, it is not *that* obvious and I think the behavior even changed as we replaced the PluggableTextMorph with Rubric ones - (maybe?) >>>>> >>>>> Anyway, maybe we need a way to distinguish between >>>>> - get visible text (view get text?) >>>>> and >>>>> - get accepted text (model get text?) >>>>> >>>>> nicolai >>>>> >>>> >>> >>> >> >

July 24, 2016

Re: [Pharo-dev] Questions about TextModel in Spec

by Peter Uhnak

On Sun, Jul 24, 2016 at 02:35:13PM +0200, Yuriy Tymchuk wrote: > Iâve found a partial hack: > > whenEdited: aBlock > "Set a block to perform when the text wasEddited & the widget entered hasUnacceptedEdits mode" > > hasUnacceptedEdits whenChangedDo: [ :val | > val ifTrue: aBlock value ] > > So now before the text is accepted I can block some other widgets wtf is whenEdited: :-o There are couple of bugs I've reported last week in regards to this, because it's quite annoying. https://pharo.fogbugz.com/f/cases/18799/TextModel-whenTextChanged-and-whenT… https://pharo.fogbugz.com/f/cases/18800/TextModel-has-inconsistent-text-cha… I guess whenEdited: should be added to those issues. Btw, what are you trying to do? Because I was playing around with custom styling for my DSL (parsed & highlighted by PetitParser), but got stopped by this same issue. Do you use a similar setup? Could we extrapolate something generically useful from this? Peter > > Uko > > > On 24 Jul 2016, at 14:17, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > > > > > 2016-07-24 13:45 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > > There is #pendingText to access it, finally found that. Now I want to detect when someone starts typing and do actions (like disable something until the text is accepted). There is whenTextChanged: but itâs not that useful because it checks if the accepted text has changed. Is there a way to check if pendingCode has changed? Or if the model is entering âhasUnacceptedEditsâ? > > > > No :( > > > > I don't think this is possible. > > You could turn autoAccept to true and listen for set a whenTextChanged block, but of course, you can not display "unaccepted" text anymore, because all text is accepted. > > > > Uko > > > >> On 24 Jul 2016, at 12:48, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: > >> > >> Cool. Thank you Nicolai. While we are on this, is there an example of how to display the parsing/compilation error as is done in playground? > >> > >> Uko > >> > >> > >>> On 24 Jul 2016, at 11:37, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: > >>> > >>> > >>> > >>> 2016-07-24 11:35 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > >>> > >>> > >>> 2016-07-24 11:14 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > >>> Hi, > >>> > >>> at some moment I wrote a super angry comment about Spec. But as there is a big effort put into documentation & improving the framework Iâve decided to give it another try. > >>> > >>> And guess what, after 10 min I ran into yet one more problem. I was expecting that it will be tough to have a custom styling for code, but no itâs much simpler: how do I get a text from text model? I type something in, sent #getText to the model => nothing. I expect that the problem is that the text is not acceptedâ¦ Why in the first place a basic text model needs this âacceptâ stuff? What if I have just a dialog where someone types something and submits it? I donât need accepts with orange corners for that. > >>> > >>> textmodel autoAccept: true. > >>> > >>> > >>> I think that youâve got the idea. I just want to build a simple UI and it looks like itâs easier to do it with Morphicâ¦ > >>> > >>> Cheers. > >>> Uko > >>> > >>> > >>> But I agree, it is not *that* obvious and I think the behavior even changed as we replaced the PluggableTextMorph with Rubric ones - (maybe?) > >>> > >>> Anyway, maybe we need a way to distinguish between > >>> - get visible text (view get text?) > >>> and > >>> - get accepted text (model get text?) > >>> > >>> nicolai > >>> > >> > > > > >

July 24, 2016

Re: [Pharo-dev] Questions about TextModel in Spec

by Yuriy Tymchuk

Iâve found a partial hack: whenEdited: aBlock "Set a block to perform when the text wasEddited & the widget entered hasUnacceptedEdits mode" hasUnacceptedEdits whenChangedDo: [ :val | val ifTrue: aBlock value ] So now before the text is accepted I can block some other widgets Uko > On 24 Jul 2016, at 14:17, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-07-24 13:45 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > There is #pendingText to access it, finally found that. Now I want to detect when someone starts typing and do actions (like disable something until the text is accepted). There is whenTextChanged: but itâs not that useful because it checks if the accepted text has changed. Is there a way to check if pendingCode has changed? Or if the model is entering âhasUnacceptedEditsâ? > > No :( > > I don't think this is possible. > You could turn autoAccept to true and listen for set a whenTextChanged block, but of course, you can not display "unaccepted" text anymore, because all text is accepted. > > Uko > >> On 24 Jul 2016, at 12:48, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >> >> Cool. Thank you Nicolai. While we are on this, is there an example of how to display the parsing/compilation error as is done in playground? >> >> Uko >> >> >>> On 24 Jul 2016, at 11:37, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: >>> >>> >>> >>> 2016-07-24 11:35 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: >>> >>> >>> 2016-07-24 11:14 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >>> Hi, >>> >>> at some moment I wrote a super angry comment about Spec. But as there is a big effort put into documentation & improving the framework Iâve decided to give it another try. >>> >>> And guess what, after 10 min I ran into yet one more problem. I was expecting that it will be tough to have a custom styling for code, but no itâs much simpler: how do I get a text from text model? I type something in, sent #getText to the model => nothing. I expect that the problem is that the text is not acceptedâ¦ Why in the first place a basic text model needs this âacceptâ stuff? What if I have just a dialog where someone types something and submits it? I donât need accepts with orange corners for that. >>> >>> textmodel autoAccept: true. >>> >>> >>> I think that youâve got the idea. I just want to build a simple UI and it looks like itâs easier to do it with Morphicâ¦ >>> >>> Cheers. >>> Uko >>> >>> >>> But I agree, it is not *that* obvious and I think the behavior even changed as we replaced the PluggableTextMorph with Rubric ones - (maybe?) >>> >>> Anyway, maybe we need a way to distinguish between >>> - get visible text (view get text?) >>> and >>> - get accepted text (model get text?) >>> >>> nicolai >>> >> > >

July 24, 2016

Re: [Pharo-dev] Questions about TextModel in Spec

by Nicolai Hess

2016-07-24 13:45 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > There is #pendingText to access it, finally found that. Now I want to > detect when someone starts typing and do actions (like disable something > until the text is accepted). There is whenTextChanged: but itâs not that > useful because it checks if the accepted text has changed. Is there a way > to check if pendingCode has changed? Or if the model is entering > âhasUnacceptedEditsâ? > No :( I don't think this is possible. You could turn autoAccept to true and listen for set a whenTextChanged block, but of course, you can not display "unaccepted" text anymore, because all text is accepted. > > Uko > > On 24 Jul 2016, at 12:48, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Cool. Thank you Nicolai. While we are on this, is there an example of how > to display the parsing/compilation error as is done in playground? > > Uko > > > On 24 Jul 2016, at 11:37, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-07-24 11:35 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2016-07-24 11:14 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> >>> Hi, >>> >>> at some moment I wrote a super angry comment about Spec. But as there is >>> a big effort put into documentation & improving the framework Iâve decided >>> to give it another try. >>> >>> And guess what, after 10 min I ran into yet one more problem. I was >>> expecting that it will be tough to have a custom styling for code, but no >>> itâs much simpler: how do I get a text from text model? I type something >>> in, sent #getText to the model => nothing. I expect that the problem is >>> that the text is not acceptedâ¦ Why in the first place a basic text model >>> needs this âacceptâ stuff? What if I have just a dialog where someone types >>> something and submits it? I donât need accepts with orange corners for that. >>> >> >> textmodel autoAccept: true. >> >> >>> >>> I think that youâve got the idea. I just want to build a simple UI and >>> it looks like itâs easier to do it with Morphicâ¦ >>> >>> Cheers. >>> Uko >>> >> >> > But I agree, it is not *that* obvious and I think the behavior even > changed as we replaced the PluggableTextMorph with Rubric ones - (maybe?) > > Anyway, maybe we need a way to distinguish between > - get visible text (view get text?) > and > - get accepted text (model get text?) > > nicolai > > > >

July 24, 2016

Re: [Pharo-dev] Questions about TextModel in Spec

by Nicolai Hess

2016-07-24 12:48 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Cool. Thank you Nicolai. While we are on this, is there an example of how > to display the parsing/compilation error as is done in playground? > I think MessageBrowser must set some handling for accepting modified code and react on compilation/parsing errors. Look at caller for #accept:notifying: a simple example for reacting on parsing errors: textmodel := TextModel new. textmodel beForCode. textmodel openWithSpec. textmodel acceptBlock:[:text :notifier | [RBParser parseExpression:text] on:SyntaxErrorNotification do:[:ex | notifier notify: ex errorMessage at: ex location in: ex errorCode] ]. > > Uko > > > On 24 Jul 2016, at 11:37, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-07-24 11:35 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2016-07-24 11:14 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> >>> Hi, >>> >>> at some moment I wrote a super angry comment about Spec. But as there is >>> a big effort put into documentation & improving the framework Iâve decided >>> to give it another try. >>> >>> And guess what, after 10 min I ran into yet one more problem. I was >>> expecting that it will be tough to have a custom styling for code, but no >>> itâs much simpler: how do I get a text from text model? I type something >>> in, sent #getText to the model => nothing. I expect that the problem is >>> that the text is not acceptedâ¦ Why in the first place a basic text model >>> needs this âacceptâ stuff? What if I have just a dialog where someone types >>> something and submits it? I donât need accepts with orange corners for that. >>> >> >> textmodel autoAccept: true. >> >> >>> >>> I think that youâve got the idea. I just want to build a simple UI and >>> it looks like itâs easier to do it with Morphicâ¦ >>> >>> Cheers. >>> Uko >>> >> >> > But I agree, it is not *that* obvious and I think the behavior even > changed as we replaced the PluggableTextMorph with Rubric ones - (maybe?) > > Anyway, maybe we need a way to distinguish between > - get visible text (view get text?) > and > - get accepted text (model get text?) > > nicolai > > >

July 24, 2016

Re: [Pharo-dev] Questions about TextModel in Spec

by Yuriy Tymchuk

There is #pendingText to access it, finally found that. Now I want to detect when someone starts typing and do actions (like disable something until the text is accepted). There is whenTextChanged: but itâs not that useful because it checks if the accepted text has changed. Is there a way to check if pendingCode has changed? Or if the model is entering âhasUnacceptedEditsâ? Uko > On 24 Jul 2016, at 12:48, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Cool. Thank you Nicolai. While we are on this, is there an example of how to display the parsing/compilation error as is done in playground? > > Uko > > >> On 24 Jul 2016, at 11:37, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: >> >> >> >> 2016-07-24 11:35 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: >> >> >> 2016-07-24 11:14 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >> Hi, >> >> at some moment I wrote a super angry comment about Spec. But as there is a big effort put into documentation & improving the framework Iâve decided to give it another try. >> >> And guess what, after 10 min I ran into yet one more problem. I was expecting that it will be tough to have a custom styling for code, but no itâs much simpler: how do I get a text from text model? I type something in, sent #getText to the model => nothing. I expect that the problem is that the text is not acceptedâ¦ Why in the first place a basic text model needs this âacceptâ stuff? What if I have just a dialog where someone types something and submits it? I donât need accepts with orange corners for that. >> >> textmodel autoAccept: true. >> >> >> I think that youâve got the idea. I just want to build a simple UI and it looks like itâs easier to do it with Morphicâ¦ >> >> Cheers. >> Uko >> >> >> But I agree, it is not *that* obvious and I think the behavior even changed as we replaced the PluggableTextMorph with Rubric ones - (maybe?) >> >> Anyway, maybe we need a way to distinguish between >> - get visible text (view get text?) >> and >> - get accepted text (model get text?) >> >> nicolai >> >

July 24, 2016

Re: [Pharo-dev] Questions about TextModel in Spec

by Yuriy Tymchuk

Cool. Thank you Nicolai. While we are on this, is there an example of how to display the parsing/compilation error as is done in playground? Uko > On 24 Jul 2016, at 11:37, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-07-24 11:35 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > > > 2016-07-24 11:14 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > Hi, > > at some moment I wrote a super angry comment about Spec. But as there is a big effort put into documentation & improving the framework Iâve decided to give it another try. > > And guess what, after 10 min I ran into yet one more problem. I was expecting that it will be tough to have a custom styling for code, but no itâs much simpler: how do I get a text from text model? I type something in, sent #getText to the model => nothing. I expect that the problem is that the text is not acceptedâ¦ Why in the first place a basic text model needs this âacceptâ stuff? What if I have just a dialog where someone types something and submits it? I donât need accepts with orange corners for that. > > textmodel autoAccept: true. > > > I think that youâve got the idea. I just want to build a simple UI and it looks like itâs easier to do it with Morphicâ¦ > > Cheers. > Uko > > > But I agree, it is not *that* obvious and I think the behavior even changed as we replaced the PluggableTextMorph with Rubric ones - (maybe?) > > Anyway, maybe we need a way to distinguish between > - get visible text (view get text?) > and > - get accepted text (model get text?) > > nicolai >

July 24, 2016