September 2015 - Pharo-dev - lists.pharo.org

To Detent Or Not To Detentâ¦

by Sean P. DeNigris

Can anyone explain the purpose of sending #detentBy:atMultiplesOf:snap: in the method below? The problem is that, if you resize programatically below a factor of 0.1, you enter a black hole from which many scale attempts become effectively ignored. If the send is removed, everything works for my use case, but I don't understand its purpose and so don't know if it's a bug or feature! TransformationMorph>>#extent: newExtent self adjustAfter: [ | scaleFactor |scaleFactor := (self scale * newExtent r / self fullBounds extent r) max: 0.1. self scale: (scaleFactor detentBy: 0.1 atMultiplesOf: 1.0 snap: false)] ----- Cheers, Sean -- View this message in context: http://forum.world.st/To-Detent-Or-Not-To-Detent-tp4847682.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2015

Re: [Pharo-dev] Widget choice list

by Franck Warlouzet

Yes arrows up/down handling in fast table is not perfect. Esteban told me there is a way to have this kind of filtering direclty in the small rectangle but I did not take the time to see how. I like the search field but maybe someone prefers filtering directly in the list items area Franck > To: pharo-dev(a)lists.pharo.org > From: stephan(a)stack.nl > Date: Wed, 2 Sep 2015 16:35:39 +0200 > Subject: Re: [Pharo-dev] Widget choice list > CC: pharo-users(a)lists.pharo.org > > On 02-09-15 14:22, Franck Warlouzet wrote: > > Hi, > > > > Some of you showed interest in a widget as the one which pops up to add protocol in Nautilus, but using FastTable. We started to build such one, it allows to bind specific action on click on a item, to have icon for items, to filter items etc. Examples show how to use it. > > It is still a beginning so there is probably some strange points or improvements to do, but if it appears to be useful to replace some widgets we can enhance it. Or it can simply show you how easy it is to build a fast table with a more complex data source, which would already be a good point. > > > > You can find the code in this repo : > > > > MCHttpRepository > > location: 'http://www.smalltalkhub.com/mc/FranckW/WidgetChoiceList/main' > > user: '' > > password: '' > > > > Feel free to contact me if you have questions. > > Nice. I've fixed example4 > In the interaction between the search field and the table, you'll want > to change the focus behaviour. Starting to type should enter the text in > the search field while filtering the table and selecting the first > element that filters. Arrow up and down should move the selection of the > table. You'll also want a key combination to move up and down to the > next position where the strings start to differ again. > > I took a look at reacting to a keystroke in the text field, but there > is an announcement that is not exposed in the model. > > Stephan > > > >

Sept. 2, 2015

Re: [Pharo-dev] Widget choice list

by Stephan Eggermont

On 02-09-15 14:22, Franck Warlouzet wrote: > Hi, > > Some of you showed interest in a widget as the one which pops up to add protocol in Nautilus, but using FastTable. We started to build such one, it allows to bind specific action on click on a item, to have icon for items, to filter items etc. Examples show how to use it. > It is still a beginning so there is probably some strange points or improvements to do, but if it appears to be useful to replace some widgets we can enhance it. Or it can simply show you how easy it is to build a fast table with a more complex data source, which would already be a good point. > > You can find the code in this repo : > > MCHttpRepository > location: 'http://www.smalltalkhub.com/mc/FranckW/WidgetChoiceList/main' > user: '' > password: '' > > Feel free to contact me if you have questions. Nice. I've fixed example4 In the interaction between the search field and the table, you'll want to change the focus behaviour. Starting to type should enter the text in the search field while filtering the table and selecting the first element that filters. Arrow up and down should move the selection of the table. You'll also want a key combination to move up and down to the next position where the strings start to differ again. I took a look at reacting to a keystroke in the text field, but there is an announcement that is not exposed in the model. Stephan

Sept. 2, 2015

Re: [Pharo-dev] Pharo CI Validation Timeout

by Nicolai Hess

Low memory ? Running the rules fill up the ast cache with nearly one entry per compiled method instance. (this are thousands instances of Array/OrderedCollections/RB and OC classes) My pharo images runs from ~ 50 MB to ~ 350-400 MB after running all rules for all classes! 2015-09-02 13:42 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > I have the feeling that is is an artefact of the virtualisation somehow. > > On 02 Sep 2015, at 10:24, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > I saw also that one of the linux slaves is much much slower than the > others. Just check this: > > https://ci.inria.fr/pharo/job/30-Bootstrap/buildTimeTrend > > In one of the slaves the build takes one hour. In the other it takes 6. > > El miÃ©., 2 de sept. de 2015 a la(s) 9:11 a. m., Marcus Denker < > marcus.denker(a)inria.fr> escribiÃ³: > >> I donât think soâ¦ the job used to run in 15 minutes. But we added more >> tests, >> Rules got slowerâ¦ >> >> On 02 Sep 2015, at 08:34, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> It is possible to see from the console output which rule or test takes a >> lot time? >> >> 2015-09-02 8:09 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: >> >>> >>> On 01 Sep 2015, at 19:15, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> Do you want to try a post-load... >>> Delay delaySchedulerClass: DelayExperimentalSemaphoreScheduler >>> >>> which fixes the "super fast delay" on virtual machines reported here... >>> http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873 >>> >>> Its named "experimental" only since it was integrated just before >>> Pharo 4 release and did not have wide spread community testing, but >>> its complete and working. There is some further overall streamlining >>> of the DelayScheduler hierarchy I'd like to do later, but it would be >>> good to give this one a run as the default for a while to see how it >>> impacts the issue. (It would be good to get rough "CIAndRule: Timeout" >>> before and after statistics.) >>> >>> btw, is that CI error indicating it times out after one hour? Are >>> there any other timestamps present in the log that indicate if 1 hour >>> really passed? >>> >>> >>> Yes, I think soâ¦ >>> >>> https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/buildTimeTrend >>> >>> Now looking at it (no idea why it is chinese), it seems that we have some >>> slowdown recently and all runs take 40-50 minutes, a slowdown to 60 can >>> happen >>> just by having less compute power available (or running multiple things >>> in parallel). >>> >>> We should >>> >>> -> do a pass over slow tests >>> -> do a pass over slow rules >>> >>> I will put the limit higher than 60 min for now. >>> >>> Marcus >>> >>> >>> >> >> >

Sept. 2, 2015

Re: [Pharo-dev] Broken GTSpotter in #50298

by Andrei Chis

https://pharo.fogbugz.com/f/cases/16455/Spotter-dying-on-not-understanding-… On Wed, Sep 2, 2015 at 2:41 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > Thanks! > > Juraj > > On Sep 2, 2015, at 09:40, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Making an issue now. > > Cheers, > Andrei > > On Wed, Sep 2, 2015 at 2:04 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com> > wrote: > >> Hi, >> >> I have fixed it yesterday. Maybe some integration is necessary to do. >> >> Cheers, >> Juraj >> >> -- >> Juraj Kubelka >> >> 2. 9. 2015 v 8:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >> >> > Hi, >> > >> > is Spotter working for you in latest Pharo? (#50298) >> > I downloaded fresh image and its dying on not understanding >> #canUnderstand: >> > >> > Peter >> >> > >

Sept. 2, 2015

Re: [Pharo-dev] Broken GTSpotter in #50298

by Juraj Kubelka

Thanks! Juraj > On Sep 2, 2015, at 09:40, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Making an issue now. > > Cheers, > Andrei > > On Wed, Sep 2, 2015 at 2:04 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com <mailto:juraj.kubelka@gmail.com>> wrote: > Hi, > > I have fixed it yesterday. Maybe some integration is necessary to do. > > Cheers, > Juraj > > -- > Juraj Kubelka > > 2. 9. 2015 v 8:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>>: > > > Hi, > > > > is Spotter working for you in latest Pharo? (#50298) > > I downloaded fresh image and its dying on not understanding #canUnderstand: > > > > Peter > >

Sept. 2, 2015

Re: [Pharo-dev] Broken GTSpotter in #50298

by Andrei Chis

Making an issue now. Cheers, Andrei On Wed, Sep 2, 2015 at 2:04 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > Hi, > > I have fixed it yesterday. Maybe some integration is necessary to do. > > Cheers, > Juraj > > -- > Juraj Kubelka > > 2. 9. 2015 v 8:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > > > Hi, > > > > is Spotter working for you in latest Pharo? (#50298) > > I downloaded fresh image and its dying on not understanding > #canUnderstand: > > > > Peter > >

Sept. 2, 2015

Widget choice list

by Franck Warlouzet

Hi, Some of you showed interest in a widget as the one which pops up to add protocol in Nautilus, but using FastTable. We started to build such one, it allows to bind specific action on click on a item, to have icon for items, to filter items etc. Examples show how to use it. It is still a beginning so there is probably some strange points or improvements to do, but if it appears to be useful to replace some widgets we can enhance it. Or it can simply show you how easy it is to build a fast table with a more complex data source, which would already be a good point. You can find the code in this repo : MCHttpRepository location: 'http://www.smalltalkhub.com/mc/FranckW/WidgetChoiceList/main' user: '' password: '' Feel free to contact me if you have questions. Cheers, Franck

Sept. 2, 2015

Re: [Pharo-dev] Removing name from Object

by Peter UhnÃ¡k

> > Off the top of my head, in the worst case implementing #name on the > class-side can be fatal. > TBH using generic names (for both variables and methods) on class side is like running through a mine field. I blew up my image more than once. >From UX perspective the system should warn the user if he is trying to override some system method or variable, but that is perhaps issue of its own. Peter

Sept. 2, 2015

Re: [Pharo-dev] Broken GTSpotter in #50298

by Juraj Kubelka

Hi, I have fixed it yesterday. Maybe some integration is necessary to do. Cheers, Juraj -- Juraj Kubelka 2. 9. 2015 v 8:50, Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > Hi, > > is Spotter working for you in latest Pharo? (#50298) > I downloaded fresh image and its dying on not understanding #canUnderstand: > > Peter

Sept. 2, 2015