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

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

by Hilaire Fernandes

Yeah! Another API changes to make a happy life. I met toons like that. Thanks to mention it. Hilaire Le 22/06/2014 23:38, MartinW a Ã©crit : > I found another one, concerning a deprecated Method: > The method UITheme>>questionIcon has been deprecated. It occurs when I use > the âWrench-Buttonâ.. > > M. -- Dr. Geo http://drgeo.eu iStoa - https://launchpad.net/istoa

June 23, 2014

Re: [Pharo-dev] TaskIT Revealed

by Serge Stinckwich

Terrific ! EnvoyÃ© de mon iPhone > Le 23 juin 2014 Ã 00:39, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> a Ã©crit : > > > 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 stepharo

Thanks for your contributions. I will read the chapter :) Stef On 23/6/14 00:39, Santiago Bragagnolo wrote: > > 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/ > <http://smalltalkhub.com/#%21/%7ECAR/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

In general terms there are pharo processes. val := [2+2] shooitIt. val := [2+2] scheduleIt. val := [2+2] forkIt. All of this snippets will give you a future, all will be related with a pharo process, but each process has different meaning. the firstone is a common 2+2 block opened in a pharo process. the second one is a block assigned to one of the by-default two worker pharo processes from the thread pool. ( in this case the pharo processes do not run directly the task, but run a process that run tasks. Then, the first one is applied just there, the second one when is its turn. Finally the third one will use osprocess to open the same image (so, by now, this will work without anyproblem if you have saved the image just before, or if you didnt change any of the code to be executed) with the same vm and it will give the block to be executed. In our local image, there will be spawned a watch pharo process that will check if the third image has finished, and deploy the future for it. In the behind the scenes, each of this convenient methods is implemented with a different kind of runner and process reification. 2014-06-23 0:54 GMT+02:00 kilon alios <kilon.alios(a)gmail.com>: > are those OS processes or Pharo processes ? > > > On Mon, Jun 23, 2014 at 1:39 AM, Santiago Bragagnolo < > santiagobragagnolo(a)gmail.com> wrote: > >> >> 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

EyeTreeInspector yellow crossed red rectangles

by HernÃ¡n Morales Durand

(Matrix rows: 10 columns: 10) explore. Do you get yellow crossed red rectangles on items? There is any fix for this one? HernÃ¡n

June 23, 2014

Re: [Pharo-dev] TaskIT Revealed

by kilon alios

are those OS processes or Pharo processes ? On Mon, Jun 23, 2014 at 1:39 AM, Santiago Bragagnolo < santiagobragagnolo(a)gmail.com> wrote: > > 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 22, 2014

TaskIT Revealed

by Santiago Bragagnolo

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 22, 2014

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

by phil＠highoctane.be

Le 22 juin 2014 22:19, "kilon alios" <kilon.alios(a)gmail.com> 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 > > > On Sun, Jun 22, 2014 at 6:55 PM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: >> >> Le 22/06/2014 14:31, kilon alios a Ã©crit : >> > the bug is annoying but not very. I really like Dr Geo you have done an >> >> For DrGeo this the kind of bug that prevent to release to public if you >> don't want to look ridicule. >> So I hope we can have a fixed VM for Mac OS X soon. >> >> > amazing job with it. >> > >> > I am also interested to know how you work with launchpad, what is your >> > workflow ? how you commit and push , pull ? >> >> Sourcecode is managed in SmalltalkHub, I know you can now save code in >> filesystem, then commit in Launchpad, I have not explored it yet. >> >> >> > Yes I am definitely going to explore Dr Geo because I want to write >> > documentation about Morphic and I think your app will provide a good >> > example to learn. I may "steal" some code for my projects too, Morphic + >> > Athens is something that interests me as well and of course Spec and >> > Roassal. But there is so much I don't understand will take me time >> > before I feel comfortable coding. I am getting there though :) >> >> A lot of the UI design is over Morphic, I mean morphic is used for some >> basic stuff, then the UI is handled with subtle details in the way to >> interact with the canvas: DrGBuilder and DrGTool class categories. >> >> >> > I see the Dr Geo could be easily turned into a design application if its >> > not already, I see a lot of potential , will definitely need to take a >> > closer look at the code to see how I can exploit it. Its apps like this >> > that make me love Pharo , more and more and of course all the available >> >> Sure, explore and learn. >> >> Hilaire >> >> >> -- >> Dr. Geo http://drgeo.eu >> iStoa - https://launchpad.net/istoa >> >> >

June 22, 2014

Re: [Pharo-dev] is STHUB slow?

by Tudor Girba

Indeed, I confirm that the speed is back as it was. Thanks! Doru On Sun, Jun 22, 2014 at 9:40 AM, stepharo <stepharo(a)free.fr> wrote: > apparently nicolas did something and now it is up to speed. > > Stef > > > On 21/6/14 20:27, stepharo wrote: > >> Hi >> >> I'm experience strange speed problem when even loading packages. >> Does any of you get the same? >> >> Stef >> >> >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

June 22, 2014

Re: [Pharo-dev] vm over android

by Esteban A. Maringolo

2014-06-20 5:06 GMT-03:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > 2014-06-19 18:35 GMT+02:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: >> What kind of applications? Is there an business interest of running on >> ARM processors? Is there a sale advantage of having this? I don't want >> to sound too inquisitive nor pedantic, those are real questions. > Yes there is a business interest of running on ARM processors. Some of the > big companies use smalltalk on their own hardware for very specific tasks, > and they are now constraint to use x86 processor due to smalltalk. > > In addition for some big projects management checks how the environment is > compatible to other platforms, and they can check "running on ARM, Android, > iOS, ..." I don't know about other PMs. But of the two companies I know that evaluated Pharo to develop "big projects" (10+ current smalltalk developers) one discarded it not because OS support, but rather because of simpler, mundane, library related, things. (However this is a different topic). >> As stated in previous mails, running on the platform is a technical >> challenge per se (I couldn't make it if I wanted), but it's just a >> very small part of "deploying to Android". And I'm not talking about >> app stores. > I agree. I want to run on ARM, not necessarily and Android. Fair enough. IMO, and from the PR point of view, saying it "runs on Android" and then finding out it is an alien process in the platform is not a good sales point. >> But how I see this, the advantage of Pharo running on Android for >> devices other than phones/tablets, more kind of "internet of things" >> devices. The advantage is also that the image is an asset of the vm, >> so you can update your app without having to reinstall it through the >> platform app management. > There is also this direction. Running on ARM is very important to be cross > platform. That includes connected objects, the raspberry pie, and many other > devices. That's totally reasonable, and a platform where something like a self contained platform like Pharo can do "magical" things. Regards!

June 22, 2014