July 2016 - Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] Stack trying to use Pier 3 with Pharo 5

by Max Leske

Looks like youâre loading Pier onto an incompatible version of Seaside. Have you posted this to the Seaside mailing list? They may be better able to help. Cheers, Max > On 23 Jul 2016, at 20:14, Sean Glazier <sglazier456(a)gmail.com> wrote: > > Hi, > > After loading the configurations of Pier and checking for the lastest and loading them as well. I still get the following when I go to the peir setup off the seaside browse applications. > WABidirectionalCache(Object)>>doesNotUnderstand: #associationsDo: > PRAdminSetup class>>recursiveHandersOn:path:do: > PRAdminSetup class>>recursiveDispatcherHandersDo: > PRAdminKernelPathPair class>>kernelPathPairs > PRAdminSetupChooseDistribution>>pierKernelNames > PRAdminSetupChooseDistribution>>suggestKernelNameFrom: > PRAdminSetupChooseDistribution>>kernelName > MASelectorAccessor>>read: > PRAdminSetupChooseDistribution(Object)>>readUsing: > [ :each | result at: each put: (self model readUsing: each) ] in MACheckedMemento(MAMemento)>>pullRaw in Block: [ :each | result at: each put: (self model readUsi...etc... > SortedCollection(OrderedCollection)>>do: > MAPriorityContainer(MAContainer)>>do: > MACheckedMemento(MAMemento)>>pullRaw > MACheckedMemento(MAMemento)>>pull > MACheckedMemento(MACachedMemento)>>reset > MACheckedMemento>>reset > MACheckedMemento class(MAMemento class)>>model:description: > MAPriorityContainer(MAContainer)>>asComponentOn: > PRAdminSetupChooseDistribution(Object)>>asComponent > PRAdminSetupChooseDistribution>>selectDistributionComponent > PRAdminSetupChooseDistribution>>children > PRAdminSetupChooseDistribution(WAPresenter)>>childrenDo: > WAVisiblePresenterGuide>>visitPresenter: > WAVisiblePresenterGuide(WAPainterVisitor)>>visitComponent: > PRAdminSetupChooseDistribution(WAComponent)>>accept: > WAVisiblePresenterGuide>>visitDecoration: > WAAnswerHandler(WADecoration)>>accept: > WAVisiblePresenterGuide(WAPainterVisitor)>>visitDecorationsOfComponent: > PRAdminSetupChooseDistribution(WAComponent)>>acceptDecorated: > WAVisiblePresenterGuide(WAPresenterGuide)>>visit: > > > Any help is appreciated :-) > > Kind Regards, > > Sean Glazier >

July 24, 2016

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

by Nicolai Hess

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 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 >

July 24, 2016

Questions about TextModel in Spec

by Yuriy Tymchuk

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. 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

July 24, 2016

Stack trying to use Pier 3 with Pharo 5

by Sean Glazier

Hi, After loading the configurations of Pier and checking for the lastest and loading them as well. I still get the following when I go to the peir setup off the seaside browse applications. WABidirectionalCache(Object)>>doesNotUnderstand: #associationsDo: PRAdminSetup class>>recursiveHandersOn:path:do: PRAdminSetup class>>recursiveDispatcherHandersDo: PRAdminKernelPathPair class>>kernelPathPairs PRAdminSetupChooseDistribution>>pierKernelNames PRAdminSetupChooseDistribution>>suggestKernelNameFrom: PRAdminSetupChooseDistribution>>kernelName MASelectorAccessor>>read: PRAdminSetupChooseDistribution(Object)>>readUsing: [ :each | result at: each put: (self model readUsing: each) ] in MACheckedMemento(MAMemento)>>pullRaw in Block: [ :each | result at: each put: (self model readUsi...etc... SortedCollection(OrderedCollection)>>do: MAPriorityContainer(MAContainer)>>do: MACheckedMemento(MAMemento)>>pullRaw MACheckedMemento(MAMemento)>>pull MACheckedMemento(MACachedMemento)>>reset MACheckedMemento>>reset MACheckedMemento class(MAMemento class)>>model:description: MAPriorityContainer(MAContainer)>>asComponentOn: PRAdminSetupChooseDistribution(Object)>>asComponent PRAdminSetupChooseDistribution>>selectDistributionComponent PRAdminSetupChooseDistribution>>children PRAdminSetupChooseDistribution(WAPresenter)>>childrenDo: WAVisiblePresenterGuide>>visitPresenter: WAVisiblePresenterGuide(WAPainterVisitor)>>visitComponent: PRAdminSetupChooseDistribution(WAComponent)>>accept: WAVisiblePresenterGuide>>visitDecoration: WAAnswerHandler(WADecoration)>>accept: WAVisiblePresenterGuide(WAPainterVisitor)>>visitDecorationsOfComponent: PRAdminSetupChooseDistribution(WAComponent)>>acceptDecorated: WAVisiblePresenterGuide(WAPresenterGuide)>>visit: Any help is appreciated :-) Kind Regards, Sean Glazier

July 23, 2016