June 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Base62/Base36

by Norbert Hartl

Am 19.06.2014 um 21:36 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: > Cool! > > It is a nice companion to my 8 byte "pretty much unique" generator > [1], and could be integrated in my friendly URLs :). > cool > However, I couldn't prove the case insensitivity of Base36, the > #toNumber: ignores characters not present in the Characters array. I > fixed Base36 toNumber: but broke Base62 tests :) > > self assert: (Base36 toNumber: (Base36 fromNumber: 16) asUppercase) > Good catch. It is fixed now. I've uploaded a new version Norbert > will fail. > > Regards, > > -- > Esteban. > > [1] https://gist.github.com/eMaringolo/be973dcf03b0783711f1 > > > > > > > Esteban A. Maringolo > > > 2014-06-12 8:16 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: >> Hmm *cough* >> >> http://smalltalkhub.com/#!/~NorbertHartl/Base62 >> >> >> Norbert >> >> Am 12.06.2014 um 13:12 schrieb Norbert Hartl <norbert(a)hartl.name>: >> >> Just for the record. Iâve uploaded a package to smalltalkhub that contains >> util classes to en-/decode values into/from Base62/Base36. >> >> Base62/Base36 encode numbers in short strings. These are used e.g. by url >> shortener services from google, bit.ly etc. >> >> Base36 uses lowercase letters and numbers to encode, Base62 uses all >> characters from Base36 plus all uppercase letters. Base62 produces smaller >> strings while Base36 produces case insensitive ones. >> >> Example: >> >> Base62 fromNumber: 100000 -> 'q0Uâ >> >> Base36 fromNumber: 100000 -> â255s' >> >> FYI, >> >> Norbert >> >> >> >

June 23, 2014

Re: [Pharo-dev] TaskIT Revealed

by Norbert Hartl

Am 23.06.2014 um 10:02 schrieb Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > btw, with the default plan configuration, it will spawn a thread per independent block (associated by & ), it will rely on the Result mechanism (the sync on demand) to spawn a third thread that is the one that converges both results, and executes the last block with the two previous executions. > Sounds reasonable. As long as the join points (where multiple promises are queued until one/all have a value) can be composed again this is great. Norbert > > > > 2014-06-23 10:00 GMT+02:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > > Ok, i was thinking more for use the same async handler for all the futures, now i read better the handler, for that kind of thing we have something similar,what is PlanIT, you should be able to do something like > > (TKTPlan plan => ( [ 1+1 ] & [ 2+2 ]) => [ : fst :snd | fst + snd ]) run == 6. > > PlanIT is not yet documented and is not fully developed, but it has some nice tests that shows some of the powers > > > > > 2014-06-23 9:07 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>: > Nice! Can you group promises? Like > > ( [ 1 + 1 ] shootIt , [ 2 + 2 ] shootIt ) onSuccess: [ :values | (values first + values second ) = 6 ] > > ? > > Norbert > > Am 23.06.2014 um 00:39 schrieb Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > >> >> Hi all, im glad to announce TaskIT. You may already knew about, after all it's not confidential ;) and it has documentation on-going since some months ago. >> >> Task IT is package that provides a cool way to deal with processes. Even when this version is stable, it still in design and we want to make it consistent and powerfull. >> >> It counts with a chapter in pharo enterprise book and some cool tests. >> >> We have moved the main distribution repo to CAR >> >> http://smalltalkhub.com/#!/~CAR/TaskIT/ >> >> >> The main easy things to do with this revision are: >> >> " closures " >> val := [ 2+2 ] shootIt. >> val isKindOf: TKTFuture. >> val onSuccess: [: rslt | rslt == 4 ] "async" >> val value == 4. " sync " >> >> rslt := [ 2+2 ] shootIt asResult. >> rslt == 4 "sync on demand" >> >> " objects " >> >> val := 2 paralellize + 2. >> val == 4 "sync on demand" >> >> >> " staying in tune " >> >> val := [ "some task" ] shootIt asStickyReference. >> >> val := nil. >> " sticky means that if this future is taken by the GC, it will kill the process" >> >> >> >> " looping " >> >> >> val := server paralellize looping serveOnce: anyParameter asStickyReference. >> >> "this will execute in a new process, in a loop, server serveOnce: anyParameter." >> >> You can stop it by doing >> val:= nil. >> >> "or using a disgusting magic variable, for that check the samples :). But do not rely on that kind of things, because it will not be supported " >> >> >> >> For more advanced and cool usages, check the Doc. >> >> >> FAQ: >> >> 1- Yes, the "sync" on demand is implemented with a proxy and a become. >> 2- Yes, we are changing the API of the processes that persist in time. >> >> CREDITS >> All CAR team in general was great inspiration, particularly, Guille Polito full operational commiter and of course is always a good idea to discuss with him, Nick Papoylias, is also great to discuss with him. Luc, Noury, Jannik: several ideas are discussed with them as well, and they always gave me support. >> >> and from RMOD Esteban Lorenzano, also discussing and proposing. >> >> Thanks all :). >> >> >> OTHERS: >> If you want to go to the darkside (dark because is not documented yet, but in the case of PoolIT, that it has some doc ) you can also add to your combo: >> ActIT: a simple Actor extention for taskit. >> ForkIT: an extention that runs blocks in background image (it adds a nice button to the test runner, letting you run all your tests in a background image and installing the results after the execution) >> PoolIT: it adds a pool of workers, it consumes tasks and ensure you a limited amount of threads. >> PlanIT: a basic and not yet full developed algebra for composing processes. >> >> >> >> I encourage you to use it, it is being used in PhaROS since a lot of time. And please any bug and enhancements, you can contact us. Since we are working on the next version is a good time to define what features are really needed. >> >> >> Salut. >> >> >> Santiago. . >> >> >> >> >> >> > >

June 23, 2014

Re: [Pharo-dev] [ANN] LaTeX to Pillar converter

by J.F. Rick

Cool. Jeff On Thu, Jun 19, 2014 at 3:54 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > I'm happy to announce that I wrote a LaTeX to Pillar converter. This > converter should not be considered perfect and proof reading is required. > Still, the converter could automatically convert from: > > > https://github.com/SquareBracketAssociates/PharoByExample-english/blob/mast… > > to: > > > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/blob/maste… > > > This Pillar file is then exported to either > > html: > https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/lastSucces… > > or pdf: > https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/lastSucces… > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing > enthusiasm." > Winston Churchill > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

June 23, 2014

Re: [Pharo-dev] TaskIT Revealed

by Santiago Bragagnolo

btw, with the default plan configuration, it will spawn a thread per independent block (associated by & ), it will rely on the Result mechanism (the sync on demand) to spawn a third thread that is the one that converges both results, and executes the last block with the two previous executions. 2014-06-23 10:00 GMT+02:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com >: > > Ok, i was thinking more for use the same async handler for all the > futures, now i read better the handler, for that kind of thing we have > something similar,what is PlanIT, you should be able to do something like > > (TKTPlan plan => ( [ 1+1 ] & [ 2+2 ]) => [ : fst :snd | fst + snd ]) run > == 6. > > PlanIT is not yet documented and is not fully developed, but it has some > nice tests that shows some of the powers > > > > > 2014-06-23 9:07 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>: > >> Nice! Can you group promises? Like >> >> ( [ 1 + 1 ] shootIt , [ 2 + 2 ] shootIt ) onSuccess: [ :values | (values >> first + values second ) = 6 ] >> >> ? >> >> Norbert >> >> Am 23.06.2014 um 00:39 schrieb Santiago Bragagnolo < >> santiagobragagnolo(a)gmail.com>: >> >> >> Hi all, im glad to announce TaskIT. You may already knew about, after all >> it's not confidential ;) and it has documentation on-going since some >> months ago. >> >> Task IT is package that provides a cool way to deal with processes. Even >> when this version is stable, it still in design and we want to make it >> consistent and powerfull. >> >> It counts with a chapter in pharo enterprise book and some cool tests. >> >> We have moved the main distribution repo to CAR >> >> http://smalltalkhub.com/#!/~CAR/TaskIT/ >> >> >> The main easy things to do with this revision are: >> >> " closures " >> val := [ 2+2 ] shootIt. >> val isKindOf: TKTFuture. >> val onSuccess: [: rslt | rslt == 4 ] "async" >> val value == 4. " sync " >> >> rslt := [ 2+2 ] shootIt asResult. >> rslt == 4 "sync on demand" >> >> " objects " >> >> val := 2 paralellize + 2. >> val == 4 "sync on demand" >> >> >> " staying in tune " >> >> val := [ "some task" ] shootIt asStickyReference. >> >> val := nil. >> " sticky means that if this future is taken by the GC, it will kill the >> process" >> >> >> >> " looping " >> >> >> val := server paralellize looping serveOnce: anyParameter >> asStickyReference. >> >> "this will execute in a new process, in a loop, server serveOnce: >> anyParameter." >> >> You can stop it by doing >> val:= nil. >> >> "or using a disgusting magic variable, for that check the samples :). But >> do not rely on that kind of things, because it will not be supported " >> >> >> >> For more advanced and cool usages, check the Doc. >> >> >> FAQ: >> >> 1- Yes, the "sync" on demand is implemented with a proxy and a become. >> 2- Yes, we are changing the API of the processes that persist in time. >> >> CREDITS >> All CAR team in general was great inspiration, particularly, Guille >> Polito full operational commiter and of course is always a good idea to >> discuss with him, Nick Papoylias, is also great to discuss with him. Luc, >> Noury, Jannik: several ideas are discussed with them as well, and they >> always gave me support. >> >> and from RMOD Esteban Lorenzano, also discussing and proposing. >> >> Thanks all :). >> >> >> OTHERS: >> If you want to go to the darkside (dark because is not documented yet, >> but in the case of PoolIT, that it has some doc ) you can also add to your >> combo: >> ActIT: a simple Actor extention for taskit. >> ForkIT: an extention that runs blocks in background image (it adds a nice >> button to the test runner, letting you run all your tests in a background >> image and installing the results after the execution) >> PoolIT: it adds a pool of workers, it consumes tasks and ensure you a >> limited amount of threads. >> PlanIT: a basic and not yet full developed algebra for composing >> processes. >> >> >> >> I encourage you to use it, it is being used in PhaROS since a lot of >> time. And please any bug and enhancements, you can contact us. Since we are >> working on the next version is a good time to define what features are >> really needed. >> >> >> Salut. >> >> >> Santiago. . >> >> >> >> >> >> >> >

June 23, 2014

Re: [Pharo-dev] TaskIT Revealed

by Santiago Bragagnolo

Ok, i was thinking more for use the same async handler for all the futures, now i read better the handler, for that kind of thing we have something similar,what is PlanIT, you should be able to do something like (TKTPlan plan => ( [ 1+1 ] & [ 2+2 ]) => [ : fst :snd | fst + snd ]) run == 6. PlanIT is not yet documented and is not fully developed, but it has some nice tests that shows some of the powers 2014-06-23 9:07 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>: > Nice! Can you group promises? Like > > ( [ 1 + 1 ] shootIt , [ 2 + 2 ] shootIt ) onSuccess: [ :values | (values > first + values second ) = 6 ] > > ? > > Norbert > > Am 23.06.2014 um 00:39 schrieb Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > > > Hi all, im glad to announce TaskIT. You may already knew about, after all > it's not confidential ;) and it has documentation on-going since some > months ago. > > Task IT is package that provides a cool way to deal with processes. Even > when this version is stable, it still in design and we want to make it > consistent and powerfull. > > It counts with a chapter in pharo enterprise book and some cool tests. > > We have moved the main distribution repo to CAR > > http://smalltalkhub.com/#!/~CAR/TaskIT/ > > > The main easy things to do with this revision are: > > " closures " > val := [ 2+2 ] shootIt. > val isKindOf: TKTFuture. > val onSuccess: [: rslt | rslt == 4 ] "async" > val value == 4. " sync " > > rslt := [ 2+2 ] shootIt asResult. > rslt == 4 "sync on demand" > > " objects " > > val := 2 paralellize + 2. > val == 4 "sync on demand" > > > " staying in tune " > > val := [ "some task" ] shootIt asStickyReference. > > val := nil. > " sticky means that if this future is taken by the GC, it will kill the > process" > > > > " looping " > > > val := server paralellize looping serveOnce: anyParameter > asStickyReference. > > "this will execute in a new process, in a loop, server serveOnce: > anyParameter." > > You can stop it by doing > val:= nil. > > "or using a disgusting magic variable, for that check the samples :). But > do not rely on that kind of things, because it will not be supported " > > > > For more advanced and cool usages, check the Doc. > > > FAQ: > > 1- Yes, the "sync" on demand is implemented with a proxy and a become. > 2- Yes, we are changing the API of the processes that persist in time. > > CREDITS > All CAR team in general was great inspiration, particularly, Guille > Polito full operational commiter and of course is always a good idea to > discuss with him, Nick Papoylias, is also great to discuss with him. Luc, > Noury, Jannik: several ideas are discussed with them as well, and they > always gave me support. > > and from RMOD Esteban Lorenzano, also discussing and proposing. > > Thanks all :). > > > OTHERS: > If you want to go to the darkside (dark because is not documented yet, but > in the case of PoolIT, that it has some doc ) you can also add to your > combo: > ActIT: a simple Actor extention for taskit. > ForkIT: an extention that runs blocks in background image (it adds a nice > button to the test runner, letting you run all your tests in a background > image and installing the results after the execution) > PoolIT: it adds a pool of workers, it consumes tasks and ensure you a > limited amount of threads. > PlanIT: a basic and not yet full developed algebra for composing > processes. > > > > I encourage you to use it, it is being used in PhaROS since a lot of > time. And please any bug and enhancements, you can contact us. Since we are > working on the next version is a good time to define what features are > really needed. > > > Salut. > > > Santiago. . > > > > > > >

June 23, 2014

Re: [Pharo-dev] TaskIT Revealed

by Santiago Bragagnolo

Ea, not, but i like that :D. 2014-06-23 9:07 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>: > Nice! Can you group promises? Like > > ( [ 1 + 1 ] shootIt , [ 2 + 2 ] shootIt ) onSuccess: [ :values | (values > first + values second ) = 6 ] > > ? > > Norbert > > Am 23.06.2014 um 00:39 schrieb Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com>: > > > Hi all, im glad to announce TaskIT. You may already knew about, after all > it's not confidential ;) and it has documentation on-going since some > months ago. > > Task IT is package that provides a cool way to deal with processes. Even > when this version is stable, it still in design and we want to make it > consistent and powerfull. > > It counts with a chapter in pharo enterprise book and some cool tests. > > We have moved the main distribution repo to CAR > > http://smalltalkhub.com/#!/~CAR/TaskIT/ > > > The main easy things to do with this revision are: > > " closures " > val := [ 2+2 ] shootIt. > val isKindOf: TKTFuture. > val onSuccess: [: rslt | rslt == 4 ] "async" > val value == 4. " sync " > > rslt := [ 2+2 ] shootIt asResult. > rslt == 4 "sync on demand" > > " objects " > > val := 2 paralellize + 2. > val == 4 "sync on demand" > > > " staying in tune " > > val := [ "some task" ] shootIt asStickyReference. > > val := nil. > " sticky means that if this future is taken by the GC, it will kill the > process" > > > > " looping " > > > val := server paralellize looping serveOnce: anyParameter > asStickyReference. > > "this will execute in a new process, in a loop, server serveOnce: > anyParameter." > > You can stop it by doing > val:= nil. > > "or using a disgusting magic variable, for that check the samples :). But > do not rely on that kind of things, because it will not be supported " > > > > For more advanced and cool usages, check the Doc. > > > FAQ: > > 1- Yes, the "sync" on demand is implemented with a proxy and a become. > 2- Yes, we are changing the API of the processes that persist in time. > > CREDITS > All CAR team in general was great inspiration, particularly, Guille > Polito full operational commiter and of course is always a good idea to > discuss with him, Nick Papoylias, is also great to discuss with him. Luc, > Noury, Jannik: several ideas are discussed with them as well, and they > always gave me support. > > and from RMOD Esteban Lorenzano, also discussing and proposing. > > Thanks all :). > > > OTHERS: > If you want to go to the darkside (dark because is not documented yet, but > in the case of PoolIT, that it has some doc ) you can also add to your > combo: > ActIT: a simple Actor extention for taskit. > ForkIT: an extention that runs blocks in background image (it adds a nice > button to the test runner, letting you run all your tests in a background > image and installing the results after the execution) > PoolIT: it adds a pool of workers, it consumes tasks and ensure you a > limited amount of threads. > PlanIT: a basic and not yet full developed algebra for composing > processes. > > > > I encourage you to use it, it is being used in PhaROS since a lot of > time. And please any bug and enhancements, you can contact us. Since we are > working on the next version is a good time to define what features are > really needed. > > > Salut. > > > Santiago. . > > > > > > >

June 23, 2014

English Dr. Geo user guide

by Hilaire Fernandes

Hello, It has been a very long task to produce a good quality English user guide (and a French one, but it was easier for me), but we did it. Of course it talks about Pharo programming as well! Read, speak about, forward from http://forum.drgeo.eu/New-user-guides-tt4024325.html Thanks to read. Hilaire -- Dr. Geo - http://drgeo.eu iStoa - https://launchpad.net/istoa

June 23, 2014

Re: [Pharo-dev] [ANN] DrGeo 14.07b

by phil＠highoctane.be

On Mon, Jun 23, 2014 at 8:50 AM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > Not at chance with Pharo, part of balloon canvas is broken (see a post > of mine about 2 years ago). > If you are serious about using it you should fix it or use Squeak. > Maybe broken but works for me when it comes to lines in a 2.0 image. Get a form canvas and do: c := aCanvas asBalloonCanvas. c aaLevel: 5. "Or whatever" Lines are then draw with antialias. So, what is broken? Phil > > > Hilaire > > Le 23/06/2014 00:11, phil(a)highoctane.be a Ã©crit : > >> Ah ok I thought you managed your code on launchpad. > >> > >> Is Athens the only way to have anti-aliased vector graphics in Pharo ? > > > > I got antialiased graphics with the balloon engine without Athens. > > > > I'll dig for how. It is somewhere in my first Pharo experiments on > > Smalltalkhub. > > > > Phil > > > > -- > Dr. Geo http://drgeo.eu > iStoa - https://launchpad.net/istoa > > >

June 23, 2014

Re: [Pharo-dev] TaskIT Revealed

by Norbert Hartl

Nice! Can you group promises? Like ( [ 1 + 1 ] shootIt , [ 2 + 2 ] shootIt ) onSuccess: [ :values | (values first + values second ) = 6 ] ? Norbert > Am 23.06.2014 um 00:39 schrieb Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > > > Hi all, im glad to announce TaskIT. You may already knew about, after all it's not confidential ;) and it has documentation on-going since some months ago. > > Task IT is package that provides a cool way to deal with processes. Even when this version is stable, it still in design and we want to make it consistent and powerfull. > > It counts with a chapter in pharo enterprise book and some cool tests. > > We have moved the main distribution repo to CAR > > http://smalltalkhub.com/#!/~CAR/TaskIT/ > > > The main easy things to do with this revision are: > > " closures " > val := [ 2+2 ] shootIt. > val isKindOf: TKTFuture. > val onSuccess: [: rslt | rslt == 4 ] "async" > val value == 4. " sync " > > rslt := [ 2+2 ] shootIt asResult. > rslt == 4 "sync on demand" > > " objects " > > val := 2 paralellize + 2. > val == 4 "sync on demand" > > > " staying in tune " > > val := [ "some task" ] shootIt asStickyReference. > > val := nil. > " sticky means that if this future is taken by the GC, it will kill the process" > > > > " looping " > > > val := server paralellize looping serveOnce: anyParameter asStickyReference. > > "this will execute in a new process, in a loop, server serveOnce: anyParameter." > > You can stop it by doing > val:= nil. > > "or using a disgusting magic variable, for that check the samples :). But do not rely on that kind of things, because it will not be supported " > > > > For more advanced and cool usages, check the Doc. > > > FAQ: > > 1- Yes, the "sync" on demand is implemented with a proxy and a become. > 2- Yes, we are changing the API of the processes that persist in time. > > CREDITS > All CAR team in general was great inspiration, particularly, Guille Polito full operational commiter and of course is always a good idea to discuss with him, Nick Papoylias, is also great to discuss with him. Luc, Noury, Jannik: several ideas are discussed with them as well, and they always gave me support. > > and from RMOD Esteban Lorenzano, also discussing and proposing. > > Thanks all :). > > > OTHERS: > If you want to go to the darkside (dark because is not documented yet, but in the case of PoolIT, that it has some doc ) you can also add to your combo: > ActIT: a simple Actor extention for taskit. > ForkIT: an extention that runs blocks in background image (it adds a nice button to the test runner, letting you run all your tests in a background image and installing the results after the execution) > PoolIT: it adds a pool of workers, it consumes tasks and ensure you a limited amount of threads. > PlanIT: a basic and not yet full developed algebra for composing processes. > > > > I encourage you to use it, it is being used in PhaROS since a lot of time. And please any bug and enhancements, you can contact us. Since we are working on the next version is a good time to define what features are really needed. > > > Salut. > > > Santiago. . > > > > > >

June 23, 2014

Re: [Pharo-dev] [ANN] DrGeo 14.07b

by Hilaire Fernandes

Not at chance with Pharo, part of balloon canvas is broken (see a post of mine about 2 years ago). If you are serious about using it you should fix it or use Squeak. Hilaire Le 23/06/2014 00:11, phil(a)highoctane.be a Ã©crit : >> Ah ok I thought you managed your code on launchpad. >> >> Is Athens the only way to have anti-aliased vector graphics in Pharo ? > > I got antialiased graphics with the balloon engine without Athens. > > I'll dig for how. It is somewhere in my first Pharo experiments on > Smalltalkhub. > > Phil > -- Dr. Geo http://drgeo.eu iStoa - https://launchpad.net/istoa

June 23, 2014