- Pharo-users - lists.pharo.org

Scrollable Spec Model

by Peter UhnÃ¡k

Hi, anyone has any experience with scrollable (arbitrary) Spec Model? e.g. I have a long list of buttons and fixed outer container windowâ¦ â As far as I can see scrolling is only available on morphic side, so I am not sure how to augment itâ¦ (Although we should probably allow scrolling on Spec side in some way) Thanks, Peter

May 18, 2016

Re: [Pharo-users] Retina support in Pharo

by CÃ©drick BÃ©ler

Hereâs a screenshot on a 5K iMac. Reading a Â« retina Â» pdf in background just to compare. Ok itâs a bit pixelated but I can notice it only if Iâm 20cm from the screen (usually Iâm 60cm). So perfectly usable. Of course retina support will give a sharper Â« look Â» but itâs not that important to me (to be honest I just realized it was pixelated when reading the post). Cheers, CÃ©drik

May 18, 2016

StampClient produce only and dealing with heartbeat

by Holger Freyther

Dear Sven, I started to use the StampClient and intend to use it to produce data but for heartbeat and other parts I need to read from the socket as well. I wonder about the best strategy to deal with it. The naive approach. [ | event sendFrame | event := sharedQueue next. sendFrame := self newSendFrameTo: queueName sendFrame text: event convertToText. stampClient write: sendFrame. ] fork. But now the StampClient enforces a non-zero hearbeat.. so I could write something like this [ | event sendFrame | event := sharedQueue nextWaitFor: stampClient timeout * 3. event isNil ifTrue: [stampClient writeHeartBeat] ifFalse: [self convertAndSendEvent: event]. ] fork. But now I face the issue (but maybe I had it before as well) that the server will itself send an empty frame as its heartbeat function and I need to read it. So I could write... [ event := sharedQueue... "try to read all pending events? How often to repeat it read everything??" stampClient readNextFrame. ... ] fork Or to make it more involved? And create a reader and writer? procConsume := [ [stampClient runWith: [:msg | " do nothing " ]] ifCurtailed: [connectionClosed...handling]. ] fork. procProduce := [ [ | event sendFrame | event := sharedQueue next. sendFrame := self newSendFrameTo: queueName sendFrame text: event convertToText. stampClient write: sendFrame. ] ensure: [procConsume... do what exactly? ] fork. So the last options seems to be the best. But how to deal with with re-connects? How to not have have "procConsume" write the heartbeat data in the middle of the produced event? After all How did you solve that? Is the problem space clear enough? holger

May 18, 2016

Re: [Pharo-users] Retina support in Pharo

by J.F. Rick

My guess is that retina support through Athens rendering and 64-bit are critical to greater adoption of Pharo for several reasons: (1) First impressions matter greatly. If I try to get someone into Pharo and the first thing they see is a pixelated screen, they will have an immediate bad reaction. My students believed that Pharo was a toy language because of the pixelated rendering. Even when I explained why, I'm not sure they believed me (sure, prof, we believe you). The interface being slow also gives the impression that the entire system is slow. So, speed improvements from Spur are less tangible. For most newcomers, interface speed = system speed. (2) One of the first things newcomers will want to do with a new system is some sort of graphical user interface. Pharo's morphic is quite nice but the BitBlt rendering is off putting. So, even if newcomers buy that there are reasons for the rendering being not great, they will likely conclude that it isn't a system for them. (3) The vast majority of OSes are 64-bit and 32-bit packages are getting deprecated. So, even if there are nice ways to interface with the outside world, they are being held back. So, very small things, like sound on Ubuntu, don't work. It's not really worth fixing that until Pharo is 64-bit. Again, it looks like Pharo is behind the curve, rather than ahead of it. Now, that stated, I understand why things are the way they are. There are limited resources and there are things that take priority. In addition, there is the tension between Pharo as an engine for research ideas (roughly equates to the things where Pharo is ahead of the curve) and Pharo as a general purpose environment (most notable in places where Pharo is behind the curve). Pharo5 is a major accomplishment and I am excited by it. It is awesome what was accomplished. I have faith in the leadership in setting priorities and great appreciation for those putting in the time. My point in posting this is not to criticize past development or priorities but just to make the case that these two things on the horizon (retina support, 64-bit) are important to my use of Pharo and how newcomers will view the system. I wish I could contribute but the VM things are out of my zone of competence. Cheers, Jeff

May 18, 2016

Re: [Pharo-users] Get a String during the execution

by Julien Delplanque

No problem. :-) ++ Julien On 18/05/16 15:12, Valentin Ryckewaert wrote: > Hello julien, > > cyril helped me i'm using UIManager default textEntry: 'Type something'. > and it's exactly what I was looking for ! > > Thanks you for your answer, i'll check openModal anyway ! :) > > Valentin > > 2016-05-18 15:05 GMT+02:00 Julien Delplanque <julien(a)tamere.eu>: > >> Hello Valentin, >> >> You should check the World>>#openModal: message. >> >> I think this is what you are looking for. :-) >> >> Regards, >> >> Julien >> >> >> On 18/05/16 14:08, Valentin Ryckewaert wrote: >> >>> Hi ! >>> >>> I'm trying to make a method able to ask the user to write something which >>> will be used in the method. >>> During my method execution, a pop up appear on the screen, the user write >>> anything 'test' for exemple, and then the method continue using this >>> string. >>> >>> The code looks like this: >>> MyClass>>dostuff >>> mypopup := MyPopup new. >>> mypopup openDialogWithSpec. >>> mypopup window okAction: [ date := mapop input text. dostuff with the >>> variable date ]." >>> >>> And then I execute this method: >>> MyClass new dostuff. >>> SessionManager default snapshot: false andQuit: true (To close Pharo) >>> >>> The problem is that the method dostuff wait the proc of the popup to make >>> what is in the bloc but continue execution and close Pharo. >>> I would like to be able to stop execution of the code just after mypopup >>> window okAction and to reactivate it in the bloc executed when it's proc. >>> Is it possible? >>> >>> Valentin >>> >>> >>

May 18, 2016

Re: [Pharo-users] Get a String during the execution

by Valentin Ryckewaert

Hello julien, cyril helped me i'm using UIManager default textEntry: 'Type something'. and it's exactly what I was looking for ! Thanks you for your answer, i'll check openModal anyway ! :) Valentin 2016-05-18 15:05 GMT+02:00 Julien Delplanque <julien(a)tamere.eu>: > Hello Valentin, > > You should check the World>>#openModal: message. > > I think this is what you are looking for. :-) > > Regards, > > Julien > > > On 18/05/16 14:08, Valentin Ryckewaert wrote: > >> Hi ! >> >> I'm trying to make a method able to ask the user to write something which >> will be used in the method. >> During my method execution, a pop up appear on the screen, the user write >> anything 'test' for exemple, and then the method continue using this >> string. >> >> The code looks like this: >> MyClass>>dostuff >> mypopup := MyPopup new. >> mypopup openDialogWithSpec. >> mypopup window okAction: [ date := mapop input text. dostuff with the >> variable date ]." >> >> And then I execute this method: >> MyClass new dostuff. >> SessionManager default snapshot: false andQuit: true (To close Pharo) >> >> The problem is that the method dostuff wait the proc of the popup to make >> what is in the bloc but continue execution and close Pharo. >> I would like to be able to stop execution of the code just after mypopup >> window okAction and to reactivate it in the bloc executed when it's proc. >> Is it possible? >> >> Valentin >> >> > >

May 18, 2016

Re: [Pharo-users] Get a String during the execution

by Julien Delplanque

Hello Valentin, You should check the World>>#openModal: message. I think this is what you are looking for. :-) Regards, Julien On 18/05/16 14:08, Valentin Ryckewaert wrote: > Hi ! > > I'm trying to make a method able to ask the user to write something which > will be used in the method. > During my method execution, a pop up appear on the screen, the user write > anything 'test' for exemple, and then the method continue using this string. > > The code looks like this: > MyClass>>dostuff > mypopup := MyPopup new. > mypopup openDialogWithSpec. > mypopup window okAction: [ date := mapop input text. dostuff with the > variable date ]." > > And then I execute this method: > MyClass new dostuff. > SessionManager default snapshot: false andQuit: true (To close Pharo) > > The problem is that the method dostuff wait the proc of the popup to make > what is in the bloc but continue execution and close Pharo. > I would like to be able to stop execution of the code just after mypopup > window okAction and to reactivate it in the bloc executed when it's proc. > Is it possible? > > Valentin >

May 18, 2016

Re: [Pharo-users] Spec layout

by Marion Noirbent

Ok, I wait your answer. Thanks for your help. Marion, Le 18/05/2016 12:04, Peter UhnÃ¡k a Ã©crit : > Yes but someone must call rebuildWidgetâ¦ I will try to take a look at this > today and give a better/more comprehensive example. > > Peter > > On Wed, May 18, 2016 at 1:01 PM, stepharo <stepharo(a)free.fr> wrote: > >> I do not get it. >> >> I still think that the solution of peter is the one to implement >> >> rebuildWidget >> self widgets removeAll. >> self createWidgets. >> self needFullRebuild: false. >> self buildWithSpecLayout: self dynamicLayout. >> self alignButtons >> >> >> dynamicLayout >> | keys | >> keys := self widgets keys. >> ^ SpecLayout composed >> newColumn: [ :c | >> keys do: [ :key | c newRow: key height: self class >> buttonHeight ]. >> c newRow: [ :r | ] ]; >> yourself >> >> >> >> Le 18/5/16 Ã 12:46, Marion Noirbent a Ã©crit : >> >> Because I would use "openWithSpec" to build only when the widget is ready, >>> but it call a method (with the good pragma) on the class side. >>> >>> In the example i use i have add RadioButtonModel with addRadioButton: in >>> the collection buttons, it's not empty but RadioButtonModel is a >>> ComposableModel and layout: is define in the subclass >>> DynamicComposableModel . >>> >>> Le 18/05/2016 10:22, stepharo a Ã©crit : >>> >>>> But why from the class side. >>>> >>>> buttons >>>> ^ buttons >>>> >>>> returns an empty collection >>>> >>>> and >>>> >>>> rebuildWidget >>>> self widgets removeAll. >>>> self createWidgets. >>>> self needFullRebuild: false. >>>> self buildWithSpecLayout: self dynamicLayout. >>>> self alignButtons >>>> >>>> >>>> >>>> Le 18/5/16 Ã 11:31, Marion Noirbent a Ã©crit : >>>> >>>>> I was trying to use it but i have still the problem to call the >>>>> instance method from the class side, so i call the >>>>> buildWithSpecLayout: in the method to add buttons in the collection, >>>>> it seems work but i have an "MessageNotUnderstood" RadioButton>>layout: >>>>> >>>>> Le 18/05/2016 09:20, stepharo a Ã©crit : >>>>> >>>>>> marion the solution is what peter proposes. >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> Le 18/5/16 Ã 11:14, Marion Noirbent a Ã©crit : >>>>>> >>>>>>> In fact i was trying to modify RadioButtonGroup to turn it into a >>>>>>> widget, #buttons is not a widget but its collection of widget. >>>>>>> >>>>>>> May you have confused RadioButtonGroup with the MenuModel / >>>>>>> MenuGroupModel / MenuItemModel which are widgets. I take inspiration >>>>>>> from them and I would got the same kind of behaviour. >>>>>>> >>>>>>> Le 17/05/2016 21:11, stepharo a Ã©crit : >>>>>>> >>>>>>>> Thanks Johan >>>>>>>> >>>>>>>> >>>>>>>> We looked at >>>>>>>> >>>>>>>> RadioButtonGroupExample >>>>>>>> >>>>>>>> but you see we cannot have a RadioButtonGroupPresenter having 2, 3 >>>>>>>> or 4 >>>>>>>> radioButton. >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>>> >>>>>>>> Le 17/5/16 Ã 18:52, Johan Fabry a Ã©crit : >>>>>>>> >>>>>>>>> Hi Marion, >>>>>>>>> >>>>>>>>> the class side message of defaultSpec is generally meant to be >>>>>>>>> used if >>>>>>>>> you use a fixed number of widgets, so you can put the reference to >>>>>>>>> the >>>>>>>>> name of each widget there (in cour case #buttons). For variable >>>>>>>>> number >>>>>>>>> of widgets you should have a look at the dynamic features of Spec. >>>>>>>>> >>>>>>>>> That being said, It looks like what you really want to use is a >>>>>>>>> Radio >>>>>>>>> Button Group. Have a look at RadioButtonGroupExample. >>>>>>>>> >>>>>>>>> HTH >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Does this mail seem too brief? Sorry for that, I donât mean to be >>>>>>>>> rude! Please see http://emailcharter.org . >>>>>>>>> >>>>>>>>> Johan Fabry - http://pleiad.cl/~jfabry >>>>>>>>> PLEIAD and RyCh labs - Computer Science Department (DCC) - >>>>>>>>> University of Chile >>>>>>>>> >>>>>>>>> On May 17, 2016, at 13:48, Marion Noirbent >>>>>>>>>> <ms.noirbent(a)etudiant.univ-lille1.fr> wrote: >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> I'm trying to create a widget whith Spec, managing a collection of >>>>>>>>>> RadioButton. But I have a problem with defaultSpec (the accessor of >>>>>>>>>> the collection is the methods "buttons") : >>>>>>>>>> >>>>>>>>>> If i put defaultSpec on class side, i can't acces the collection of >>>>>>>>>> the instance. (the following code iterate on the string) >>>>>>>>>> >>>>>>>>>> defaultSpec >>>>>>>>>> <spec: #default> >>>>>>>>>> ^ SpecLayout composed >>>>>>>>>> newColumn: [ :column | #buttons do: [ :item | column add: >>>>>>>>>> item ] ]; >>>>>>>>>> yourself >>>>>>>>>> >>>>>>>>>> If i put it on instance side, the lookup don't find it (in the book >>>>>>>>>> Building UI with Spec, it said the lookup begin by the instance >>>>>>>>>> side >>>>>>>>>> and it allow to have specific UI, in part about layout) >>>>>>>>>> >>>>>>>>>> defaultSpec >>>>>>>>>> <spec: #default> >>>>>>>>>> ^ SpecLayout composed >>>>>>>>>> newColumn: [ :column | self buttons do: [ :item | column >>>>>>>>>> add: >>>>>>>>>> item ] ]; >>>>>>>>>> yourself >>>>>>>>>> >>>>>>>>>> Any idea ? >>>>>>>>>> >>>>>>>>>> Marion Noirbent, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> > -- Ma clÃ© publique sur pgp.mit.edu

May 18, 2016

Get a String during the execution

by Valentin Ryckewaert

Hi ! I'm trying to make a method able to ask the user to write something which will be used in the method. During my method execution, a pop up appear on the screen, the user write anything 'test' for exemple, and then the method continue using this string. The code looks like this: MyClass>>dostuff mypopup := MyPopup new. mypopup openDialogWithSpec. mypopup window okAction: [ date := mapop input text. dostuff with the variable date ]." And then I execute this method: MyClass new dostuff. SessionManager default snapshot: false andQuit: true (To close Pharo) The problem is that the method dostuff wait the proc of the popup to make what is in the bloc but continue execution and close Pharo. I would like to be able to stop execution of the code just after mypopup window okAction and to reactivate it in the bloc executed when it's proc. Is it possible? Valentin

May 18, 2016

Re: [Pharo-users] Spec layout

by Peter UhnÃ¡k

Yes but someone must call rebuildWidgetâ¦ I will try to take a look at this today and give a better/more comprehensive example. Peter On Wed, May 18, 2016 at 1:01 PM, stepharo <stepharo(a)free.fr> wrote: > I do not get it. > > I still think that the solution of peter is the one to implement > > rebuildWidget > self widgets removeAll. > self createWidgets. > self needFullRebuild: false. > self buildWithSpecLayout: self dynamicLayout. > self alignButtons > > > dynamicLayout > | keys | > keys := self widgets keys. > ^ SpecLayout composed > newColumn: [ :c | > keys do: [ :key | c newRow: key height: self class > buttonHeight ]. > c newRow: [ :r | ] ]; > yourself > > > > Le 18/5/16 Ã 12:46, Marion Noirbent a Ã©crit : > > Because I would use "openWithSpec" to build only when the widget is ready, >> but it call a method (with the good pragma) on the class side. >> >> In the example i use i have add RadioButtonModel with addRadioButton: in >> the collection buttons, it's not empty but RadioButtonModel is a >> ComposableModel and layout: is define in the subclass >> DynamicComposableModel . >> >> Le 18/05/2016 10:22, stepharo a Ã©crit : >> >>> But why from the class side. >>> >>> buttons >>> ^ buttons >>> >>> returns an empty collection >>> >>> and >>> >>> rebuildWidget >>> self widgets removeAll. >>> self createWidgets. >>> self needFullRebuild: false. >>> self buildWithSpecLayout: self dynamicLayout. >>> self alignButtons >>> >>> >>> >>> Le 18/5/16 Ã 11:31, Marion Noirbent a Ã©crit : >>> >>>> I was trying to use it but i have still the problem to call the >>>> instance method from the class side, so i call the >>>> buildWithSpecLayout: in the method to add buttons in the collection, >>>> it seems work but i have an "MessageNotUnderstood" RadioButton>>layout: >>>> >>>> Le 18/05/2016 09:20, stepharo a Ã©crit : >>>> >>>>> marion the solution is what peter proposes. >>>>> >>>>> Stef >>>>> >>>>> >>>>> Le 18/5/16 Ã 11:14, Marion Noirbent a Ã©crit : >>>>> >>>>>> In fact i was trying to modify RadioButtonGroup to turn it into a >>>>>> widget, #buttons is not a widget but its collection of widget. >>>>>> >>>>>> May you have confused RadioButtonGroup with the MenuModel / >>>>>> MenuGroupModel / MenuItemModel which are widgets. I take inspiration >>>>>> from them and I would got the same kind of behaviour. >>>>>> >>>>>> Le 17/05/2016 21:11, stepharo a Ã©crit : >>>>>> >>>>>>> Thanks Johan >>>>>>> >>>>>>> >>>>>>> We looked at >>>>>>> >>>>>>> RadioButtonGroupExample >>>>>>> >>>>>>> but you see we cannot have a RadioButtonGroupPresenter having 2, 3 >>>>>>> or 4 >>>>>>> radioButton. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> >>>>>>> Le 17/5/16 Ã 18:52, Johan Fabry a Ã©crit : >>>>>>> >>>>>>>> Hi Marion, >>>>>>>> >>>>>>>> the class side message of defaultSpec is generally meant to be >>>>>>>> used if >>>>>>>> you use a fixed number of widgets, so you can put the reference to >>>>>>>> the >>>>>>>> name of each widget there (in cour case #buttons). For variable >>>>>>>> number >>>>>>>> of widgets you should have a look at the dynamic features of Spec. >>>>>>>> >>>>>>>> That being said, It looks like what you really want to use is a >>>>>>>> Radio >>>>>>>> Button Group. Have a look at RadioButtonGroupExample. >>>>>>>> >>>>>>>> HTH >>>>>>>> >>>>>>>> -- >>>>>>>> Does this mail seem too brief? Sorry for that, I donât mean to be >>>>>>>> rude! Please see http://emailcharter.org . >>>>>>>> >>>>>>>> Johan Fabry - http://pleiad.cl/~jfabry >>>>>>>> PLEIAD and RyCh labs - Computer Science Department (DCC) - >>>>>>>> University of Chile >>>>>>>> >>>>>>>> On May 17, 2016, at 13:48, Marion Noirbent >>>>>>>>> <ms.noirbent(a)etudiant.univ-lille1.fr> wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> I'm trying to create a widget whith Spec, managing a collection of >>>>>>>>> RadioButton. But I have a problem with defaultSpec (the accessor of >>>>>>>>> the collection is the methods "buttons") : >>>>>>>>> >>>>>>>>> If i put defaultSpec on class side, i can't acces the collection of >>>>>>>>> the instance. (the following code iterate on the string) >>>>>>>>> >>>>>>>>> defaultSpec >>>>>>>>> <spec: #default> >>>>>>>>> ^ SpecLayout composed >>>>>>>>> newColumn: [ :column | #buttons do: [ :item | column add: >>>>>>>>> item ] ]; >>>>>>>>> yourself >>>>>>>>> >>>>>>>>> If i put it on instance side, the lookup don't find it (in the book >>>>>>>>> Building UI with Spec, it said the lookup begin by the instance >>>>>>>>> side >>>>>>>>> and it allow to have specific UI, in part about layout) >>>>>>>>> >>>>>>>>> defaultSpec >>>>>>>>> <spec: #default> >>>>>>>>> ^ SpecLayout composed >>>>>>>>> newColumn: [ :column | self buttons do: [ :item | column >>>>>>>>> add: >>>>>>>>> item ] ]; >>>>>>>>> yourself >>>>>>>>> >>>>>>>>> Any idea ? >>>>>>>>> >>>>>>>>> Marion Noirbent, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> > >

May 18, 2016