- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About inspectors

by Tudor Girba

Thanks. I was looking for something like that! I will check it and get back to you. Doru On Tue, Mar 11, 2014 at 10:42 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Doru, for the DBXTalk inspector, maybe it is useful for you this package: > > http://www.smalltalkhub.com/#!/~DBXTalk/DBXDatabaseModel/ > > That allows to retrieve database schema metadata in a polymorphic way :) > > > On Tue, Mar 11, 2014 at 7:43 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Thank you. >> >> In this case yes, it blurs the line between an SQL Editor and the >> inspector. And between a table and an Excel code editor. But, here is >> another blurred line between the file browser and the inspector: >> >> http://www.humane-assessment.com/blog/browsing-files-with-gtinspector-video/ >> >> The GTInspector blurs all sorts of lines and it even empowers you to blur >> your own lines :). >> >> Just a note: the GToolkit is also the work of Andrei. >> >> Doru >> >> >> On Mon, Mar 10, 2014 at 8:01 PM, Esteban A. Maringolo < >> emaringolo(a)gmail.com> wrote: >> >>> Excellent Tudor! >>> >>> Very impressive. It blurs the line between a the Smalltalk tools and >>> an SQL Editor. >>> Esteban A. Maringolo >>> >>> >>> 2014-03-10 12:15 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >>> > Yes! >>> > >>> > We have Roassal 2 which is pretty well advanced already. We would like >>> to announce Roassal2 the way its deserve: with fireworks and a big fanfare. >>> > >>> > The coming months will be full of surprises. >>> > >>> > Alexandre >>> > >>> > >>> > On Mar 10, 2014, at 9:59 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >>> wrote: >>> > >>> >> Alex, >>> >> >>> >> On 10 Mar 2014, at 13:54, Alexandre Bergel <alexandre.bergel(a)me.com> >>> wrote: >>> >> >>> >>> Yesterday evening I watched the Wolfram video. I think we can >>> produce Pharo-based video as impressive as what this strange guy did. >>> >> >>> >> Please do ! Visualization and marketing is important indeed. >>> >> >>> >> Sven >>> > >>> > -- >>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > Alexandre Bergel http://www.bergel.eu >>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > >>> > >>> > >>> > >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

March 11, 2014

Re: [Pharo-dev] Bug in valueWithin:onTimeout: ?

by Stefan Marr

Hi ClÃ©ment: On 11 Mar 2014, at 09:58, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Yesterday I had this problem that at startup a pharo image has several process running at priority 40. The problem is that my tests (run from command line) trigger #valueWithin:onTimeout: and the protected block (the block calling #valueWithin:onTimeout:) would always timed out for the first test as resuming the watchdog in #valueWithin:onTimeout: allows another runnable process at the same priority as the active process to be run. > > I'm not very familiar with Pharo's process framework nor with processes in general so I would like to discuss the problem. > > Question 1: Is it a bug ? Just a brief answer: Processes on the same priority are scheduled cooperatively. So, no, it is not a bug. Only processes of different priority are scheduled preemptively. So, it is âby designâ and the expected behavior (which some parts of the system rely on). Best regards Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/

March 11, 2014

Re: [Pharo-dev] Sort by property

by Yuriy Tymchuk

On 11 Mar 2014, at 10:19, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hello, > > [ Note: So in the default Pharo the method is named #sort: not #sortByProp: or #sortBy: but it's a detail ] Yes, my mistake, I was misguided by #isSortedBy: Now #sortByProp: is my own example method that accepts a block and executes it for each sortable item and then the result is compared. I donât like the idea to implement #value:value: for a symbol because it caries a bit of a logic inside it. Uko > > I like this idea because I also have always the problem. So I would like to be able to do: > > projects sort: #creationDate > > The implementation would be, in a similar fashion to how Symbol>>value: is implemented for aCollection collect: #isPlague : > > Symbol>>value: val1 value: val2 > ^ (val1 perform: self) <= (val2 perform: self) > > Then : > > (#( 10 42 31 23 90 87 65) collect: #asValueHolder) sort: #value > > Answers: > > an Array(a NewValueHolder[ 10 ] a NewValueHolder[ 23 ] a NewValueHolder[ 31 ] a NewValueHolder[ 42 ] a NewValueHolder[ 65 ] a NewValueHolder[ 87 ] a NewValueHolder[ 90 ]) > > which is correct :-). > > However I do not like: > > projects sort: [ :proj | proj author birthDate ] > > If you allow that where is the limit to the thing you want to allow ? In addition, I do not see any nice implementation and you could just implement in project > > Project>>authorBirthDate > ^ self author birthDate > > Best, > > Clement > > > > 2014-03-11 9:19 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi guys. > > This is a thing that I encounter quite often. > > Eg I have a collection of projects and I want to sort them by creation date. It would be nice to be able to do something like: > > projects sortByProp: #creationDate > > or by birth date of the author > > projects sortByProp: [ :proj | proj author birthDate ] > > Maybe Iâm wrong, but as Iâve told already I encounter it quite often and writing something like > > projects sortBy: [ :prev :next | prev creationDate <= next creationDate ] > > is boring for me. > > Cheers. > Uko >

March 11, 2014

Re: [Pharo-dev] About inspectors

by Guillermo Polito

Doru, for the DBXTalk inspector, maybe it is useful for you this package: http://www.smalltalkhub.com/#!/~DBXTalk/DBXDatabaseModel/ That allows to retrieve database schema metadata in a polymorphic way :) On Tue, Mar 11, 2014 at 7:43 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thank you. > > In this case yes, it blurs the line between an SQL Editor and the > inspector. And between a table and an Excel code editor. But, here is > another blurred line between the file browser and the inspector: > > http://www.humane-assessment.com/blog/browsing-files-with-gtinspector-video/ > > The GTInspector blurs all sorts of lines and it even empowers you to blur > your own lines :). > > Just a note: the GToolkit is also the work of Andrei. > > Doru > > > On Mon, Mar 10, 2014 at 8:01 PM, Esteban A. Maringolo < > emaringolo(a)gmail.com> wrote: > >> Excellent Tudor! >> >> Very impressive. It blurs the line between a the Smalltalk tools and >> an SQL Editor. >> Esteban A. Maringolo >> >> >> 2014-03-10 12:15 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >> > Yes! >> > >> > We have Roassal 2 which is pretty well advanced already. We would like >> to announce Roassal2 the way its deserve: with fireworks and a big fanfare. >> > >> > The coming months will be full of surprises. >> > >> > Alexandre >> > >> > >> > On Mar 10, 2014, at 9:59 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> > >> >> Alex, >> >> >> >> On 10 Mar 2014, at 13:54, Alexandre Bergel <alexandre.bergel(a)me.com> >> wrote: >> >> >> >>> Yesterday evening I watched the Wolfram video. I think we can produce >> Pharo-based video as impressive as what this strange guy did. >> >> >> >> Please do ! Visualization and marketing is important indeed. >> >> >> >> Sven >> > >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

March 11, 2014

Re: [Pharo-dev] About a Spec dedicated mailing-list

by Nicolai Hess

Are those "+1" meant for "yes a dedicated mailling list" or for sven's " I don't think that makes much sense" comment ? even if you don't want to do something directly with spec (and so, you wouldn't follow that mailinglist), many changes done for spec have an influence on common tools or morphic components. +1 (for svens comment). 2014-03-11 9:02 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > +1 > > > Gesendet: Dienstag, 11. MÃ¤rz 2014 um 03:46 Uhr > > Von: "Alexandre Bergel" <alexandre.bergel(a)me.com> > > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Betreff: Re: [Pharo-dev] About a Spec dedicated mailing-list > > > > + 1 > > > > > Le 10-03-2014 Ã 16:48, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > > > > > > Ben, > > > > > > I don't think that makes that much sense (right now): > > > > > > - there is not that much spec specific traffic > > > - spec is a fundamental and critical part of pharo > > > - pharo is a fundamental and critical part of spec > > > - we have to make spec better all together > > > > > > ;-) > > > > > > My 2c, > > > > > > Sven > > > > > >> On 10 Mar 2014, at 18:23, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> wrote: > > >> > > >> Hello guys :) > > >> > > >> I was wondering if it will make sense to have a spec dedicated > mailing list :) > > >> As I have pros and cons, I am asking for your opinion :) > > >> > > >> Thanks in advance, > > >> Ben > > > > > > > > > > > >

March 11, 2014

Re: [Pharo-dev] Sort by property

by ClÃ©ment Bera

Hello, [ Note: So in the default Pharo the method is named #sort: not #sortByProp: or #sortBy: but it's a detail ] I like this idea because I also have always the problem. So I would like to be able to do: projects sort: #creationDate The implementation would be, in a similar fashion to how Symbol>>value: is implemented for aCollection collect: #isPlague : Symbol>>value: val1 value: val2 ^ (val1 perform: self) <= (val2 perform: self) Then : (#( 10 42 31 23 90 87 65) collect: #asValueHolder) sort: #value Answers: an Array(a NewValueHolder[ 10 ] a NewValueHolder[ 23 ] a NewValueHolder[ 31 ] a NewValueHolder[ 42 ] a NewValueHolder[ 65 ] a NewValueHolder[ 87 ] a NewValueHolder[ 90 ]) which is correct :-). However I do not like: projects sort: [ :proj | proj author birthDate ] If you allow that where is the limit to the thing you want to allow ? In addition, I do not see any nice implementation and you could just implement in project Project>>authorBirthDate ^ self author birthDate Best, Clement 2014-03-11 9:19 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi guys. > > This is a thing that I encounter quite often. > > Eg I have a collection of projects and I want to sort them by creation > date. It would be nice to be able to do something like: > > projects sortByProp: #creationDate > > or by birth date of the author > > projects sortByProp: [ :proj | proj author birthDate ] > > Maybe I'm wrong, but as I've told already I encounter it quite often and > writing something like > > projects sortBy: [ :prev :next | prev creationDate <= next creationDate ] > > is boring for me. > > Cheers. > Uko >

March 11, 2014

Re: [Pharo-dev] Sort by property

by Camille Teruel

Hi Yuriy, I though the same. There is a similar situation with pluggable collections where you have to specify two blocks: one for the hash the other for equality. So you have to repeat three times the property you're interested in: PluggableSet new hashBlock: [ :each | each name hash ]; equalBlock: [ :a :b | a name = b name ]; yourself. Where I would like to be able to write: PluggableSet by: #name. On 11 mars 2014, at 09:19, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi guys. > > This is a thing that I encounter quite often. > > Eg I have a collection of projects and I want to sort them by creation date. It would be nice to be able to do something like: > > projects sortByProp: #creationDate > > or by birth date of the author > > projects sortByProp: [ :proj | proj author birthDate ] > > Maybe Iâm wrong, but as Iâve told already I encounter it quite often and writing something like > > projects sortBy: [ :prev :next | prev creationDate <= next creationDate ] > > is boring for me. > > Cheers. > Uko

March 11, 2014

Bug in valueWithin:onTimeout: ?

by ClÃ©ment Bera

Hello guys, Yesterday I had this problem that at startup a pharo image has several process running at priority 40. The problem is that my tests (run from command line) trigger #valueWithin:onTimeout: and the protected block (the block calling #valueWithin:onTimeout:) would always timed out for the first test as resuming the watchdog in #valueWithin:onTimeout: allows another runnable process at the same priority as the active process to be run. Example: Here we have two process at the activePriority, the second process takes 100ms to be run and as the transcript shows, the protected block always times out because this other process is started after the watchdog so during the protected block activation. | p endTime | p := Processor activeProcess priority. [ 'Process2Start' logCr. endTime := Time millisecondClockValue + 100. [ Time millisecondClockValue > endTime ] whileFalse: [ 1 + 2 + 3 ]. 'Process2End' logCr. ] forkAt: p. [ 'protected' logCr] valueWithin: 0.05 second onTimeout: [ 'timeout' logCr ]. Transcript displays: 'Process2Start' 'Process2End' 'timeout' I'm not very familiar with Pharo's process framework nor with processes in general so I would like to discuss the problem. *Question 1: Is it a bug ?* I fixed it by adding a Processor yield just before resuming the watchdog in #valueWithin:onTimeout: to allow other runnable process at the activePriority to be run before the protected block and therefore forbidding other process started outside of the protected block to trigger the time out. No process can be started in between the Processor yield and watchdog resume. *Question 2: Can someone tell me if this code looks ok ? I've just added Processor yield.* valueWithin: aDuration onTimeout: timeoutBlock "Evaluate the receiver. If the evaluation does not complete in less than aDuration evaluate the timeoutBlock instead" | theProcess delay watchdog tag | aDuration <= Duration zero ifTrue: [^ timeoutBlock value ]. "the block will be executed in the current process" theProcess := Processor activeProcess. delay := aDuration asDelay. tag := self. "make a watchdog process" watchdog := [ delay wait. "wait for timeout or completion" theProcess ifNotNil:[ theProcess signalException: (TimedOut new tag: tag)] ] newProcess. "Watchdog needs to run at high priority to do its job (but not at timing priority)" watchdog priority: Processor timingPriority-1. *Processor yield.* "catch the timeout signal" ^ [ watchdog resume. "start up the watchdog" self ensure:[ "evaluate the receiver" theProcess := nil. "it has completed, so ..." delay delaySemaphore signal. "arrange for the watchdog to exit" ]] on: TimedOut do: [ :e | e tag == tag ifTrue:[ timeoutBlock value ] ifFalse:[ e pass]].

March 11, 2014

Sort by property

by Yuriy Tymchuk

Hi guys. This is a thing that I encounter quite often. Eg I have a collection of projects and I want to sort them by creation date. It would be nice to be able to do something like: projects sortByProp: #creationDate or by birth date of the author projects sortByProp: [ :proj | proj author birthDate ] Maybe Iâm wrong, but as Iâve told already I encounter it quite often and writing something like projects sortBy: [ :prev :next | prev creationDate <= next creationDate ] is boring for me. Cheers. Uko

March 11, 2014

Re: [Pharo-dev] About a Spec dedicated mailing-list

by Torsten Bergmann

+1 > Gesendet: Dienstag, 11. MÃ¤rz 2014 um 03:46 Uhr > Von: "Alexandre Bergel" <alexandre.bergel(a)me.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] About a Spec dedicated mailing-list > > + 1 > > > Le 10-03-2014 Ã 16:48, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > > > > Ben, > > > > I don't think that makes that much sense (right now): > > > > - there is not that much spec specific traffic > > - spec is a fundamental and critical part of pharo > > - pharo is a fundamental and critical part of spec > > - we have to make spec better all together > > > > ;-) > > > > My 2c, > > > > Sven > > > >> On 10 Mar 2014, at 18:23, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> > >> Hello guys :) > >> > >> I was wondering if it will make sense to have a spec dedicated mailing list :) > >> As I have pros and cons, I am asking for your opinion :) > >> > >> Thanks in advance, > >> Ben > > > > > >

March 11, 2014