November 2014 - Pharo-users

Re: [Pharo-users] Memoization Question

by Luc Fabresse

just added you as a contributor. And yes comments are more than welcome ;-) #Luc 2014-11-04 18:03 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Luc, > > Can you add me to the repo so that I can send updates? > > Phil > > On Tue, Nov 4, 2014 at 4:56 PM, Luc Fabresse <luc.fabresse(a)gmail.com> > wrote: > >> Hi Phil, >> >> Ok I missed the details so I've just refreshed my mind. >> >> yes the latest repository is this one: >> http://www.smalltalkhub.com/#!/~CAR/Ghost/ >> I've just tried in Pharo 3.0 and it works now (yes oups I forgot that it >> was for Pharo 2.0 ;-)). >> Ghost is really small so I've just fixed it >> >> Try it: ConfigurationOfGhost load >> Tests are green for me. >> >> No I did not push the config in the right place to have it in the >> ConfigurationBrowser. >> >> You can find infos+examples on how to achieve Method wrapper in Mariano's >> PhD (p116) using Proxies for Methods. >> >> https://tel.archives-ouvertes.fr/tel-00764991/document >> >> and also look at the test case method named >> #testSimpleForwardingForMethodUsingBecome >> >> Cheers, >> >> Luc >> >> 2014-11-04 15:48 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: >> >>> I have been reading on Ghost: >>> >>> >>> http://esug.org/data/ESUG2011/IWST/PRESENTATIONS/23.Mariano_Peck-Ghost-ESUG… >>> http://www.slideshare.net/esug/ghost-9095241 >>> http://rmod.lille.inria.fr/archives/workshops/Mart11a-IWST11-Ghost.pdf >>> >>> This link is dead BTW: >>> http://rmod.inria.fr/web/pier/software/Marea/GhostProxies >>> >>> I found a version here: http://www.smalltalkhub.com/#!/~CAR/Ghost/ >>> >>> It isn't in the ConfigurationBrowser, so I wonder where is the version >>> to use. >>> >>> Phil >>> >>> >>> >>> >>> >>> On Tue, Nov 4, 2014 at 2:09 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> >>> wrote: >>> >>>> >>>> The language you are thinking of is most probably PHANtom: >>>> http://pleiad.cl/phantom But (as author of the language) I think it is >>>> overkill to use it for just a memoization cache. Idem for AspectS (I donât >>>> know if it works on Pharo though). Right now, I would use MethodWrappers >>>> instead, and when Reflectivity is working use that. >>>> >>>> On Nov 4, 2014, at 1:50 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>>> wrote: >>>> >>>> Hi >>>> >>>> There is AspectS package at old squeaksource site. I not know is it >>>> working in Pharo. >>>> And there was presentation at Esug few years ago about another >>>> implementation of aspects in Pharo ( i not remember project name) >>>> 04 Ð½Ð¾ÑÐ±. 2014 Ð³. 9:04 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "phil(a)highoctane.be" < >>>> phil(a)highoctane.be> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: >>>> >>>>> >>>>> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : >>>>> > >>>>> > What's wrong with? >>>>> > >>>>> > myData >>>>> > ^ data ifNil: [data := self computeMe] >>>>> >>>>> That I do have a lot of places like this and do not want these data >>>>> littering the code. >>>>> >>>>> Aspects would solve this but we do not have that. >>>>> >>>>> Also I need the mechanism to be removable. >>>>> >>>>> So, I read something about MethodWrapper, ghost, slots... Can't one >>>>> use any of these things to do this memoization cleanly? >>>>> >>>>> Phil >>>>> >>>>> > >>>>> > >>>>> > >>>>> > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : >>>>> > > How can I do memoization in Pharo? >>>>> > > >>>>> > > I mean, a generic mechanism that will help me wrap the caching >>>>> around >>>>> > > the method invocations / messages. >>>>> > > >>>>> > > I have expensive calls that do not have to refresh their results as >>>>> > > often as they are called. >>>>> > > >>>>> > > TIA >>>>> > > Phil >>>>> > >>>>> > >>>>> > -- >>>>> > Dr. Geo - http://drgeo.eu >>>>> > iStoa - http://istoa.drgeo.eu >>>>> > >>>>> > >>>>> > >>>>> >>>> >>>> >>>> >>>> ---> Save our in-boxes! http://emailcharter.org <--- >>>> >>>> Johan Fabry - http://pleiad.cl/~jfabry >>>> PLEIAD lab - Computer Science Department (DCC) - University of Chile >>>> >>>> >>> >> >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by phil＠highoctane.be

Luc, Can you add me to the repo so that I can send updates? Phil On Tue, Nov 4, 2014 at 4:56 PM, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Hi Phil, > > Ok I missed the details so I've just refreshed my mind. > > yes the latest repository is this one: > http://www.smalltalkhub.com/#!/~CAR/Ghost/ > I've just tried in Pharo 3.0 and it works now (yes oups I forgot that it > was for Pharo 2.0 ;-)). > Ghost is really small so I've just fixed it > > Try it: ConfigurationOfGhost load > Tests are green for me. > > No I did not push the config in the right place to have it in the > ConfigurationBrowser. > > You can find infos+examples on how to achieve Method wrapper in Mariano's > PhD (p116) using Proxies for Methods. > > https://tel.archives-ouvertes.fr/tel-00764991/document > > and also look at the test case method named > #testSimpleForwardingForMethodUsingBecome > > Cheers, > > Luc > > 2014-11-04 15:48 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> I have been reading on Ghost: >> >> >> http://esug.org/data/ESUG2011/IWST/PRESENTATIONS/23.Mariano_Peck-Ghost-ESUG… >> http://www.slideshare.net/esug/ghost-9095241 >> http://rmod.lille.inria.fr/archives/workshops/Mart11a-IWST11-Ghost.pdf >> >> This link is dead BTW: >> http://rmod.inria.fr/web/pier/software/Marea/GhostProxies >> >> I found a version here: http://www.smalltalkhub.com/#!/~CAR/Ghost/ >> >> It isn't in the ConfigurationBrowser, so I wonder where is the version to >> use. >> >> Phil >> >> >> >> >> >> On Tue, Nov 4, 2014 at 2:09 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: >> >>> >>> The language you are thinking of is most probably PHANtom: >>> http://pleiad.cl/phantom But (as author of the language) I think it is >>> overkill to use it for just a memoization cache. Idem for AspectS (I donât >>> know if it works on Pharo though). Right now, I would use MethodWrappers >>> instead, and when Reflectivity is working use that. >>> >>> On Nov 4, 2014, at 1:50 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> >>> Hi >>> >>> There is AspectS package at old squeaksource site. I not know is it >>> working in Pharo. >>> And there was presentation at Esug few years ago about another >>> implementation of aspects in Pharo ( i not remember project name) >>> 04 Ð½Ð¾ÑÐ±. 2014 Ð³. 9:04 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "phil(a)highoctane.be" < >>> phil(a)highoctane.be> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: >>> >>>> >>>> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : >>>> > >>>> > What's wrong with? >>>> > >>>> > myData >>>> > ^ data ifNil: [data := self computeMe] >>>> >>>> That I do have a lot of places like this and do not want these data >>>> littering the code. >>>> >>>> Aspects would solve this but we do not have that. >>>> >>>> Also I need the mechanism to be removable. >>>> >>>> So, I read something about MethodWrapper, ghost, slots... Can't one use >>>> any of these things to do this memoization cleanly? >>>> >>>> Phil >>>> >>>> > >>>> > >>>> > >>>> > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : >>>> > > How can I do memoization in Pharo? >>>> > > >>>> > > I mean, a generic mechanism that will help me wrap the caching >>>> around >>>> > > the method invocations / messages. >>>> > > >>>> > > I have expensive calls that do not have to refresh their results as >>>> > > often as they are called. >>>> > > >>>> > > TIA >>>> > > Phil >>>> > >>>> > >>>> > -- >>>> > Dr. Geo - http://drgeo.eu >>>> > iStoa - http://istoa.drgeo.eu >>>> > >>>> > >>>> > >>>> >>> >>> >>> >>> ---> Save our in-boxes! http://emailcharter.org <--- >>> >>> Johan Fabry - http://pleiad.cl/~jfabry >>> PLEIAD lab - Computer Science Department (DCC) - University of Chile >>> >>> >> >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by phil＠highoctane.be

On Tue, Nov 4, 2014 at 4:56 PM, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Hi Phil, > > Ok I missed the details so I've just refreshed my mind. > > yes the latest repository is this one: > http://www.smalltalkhub.com/#!/~CAR/Ghost/ > I've just tried in Pharo 3.0 and it works now (yes oups I forgot that it > was for Pharo 2.0 ;-)). > Ghost is really small so I've just fixed it > Thanks a lot! > > Try it: ConfigurationOfGhost load > Tests are green for me. > I loaded the configuration: Gofer it smalltalkhubUser: 'CAR' project: 'Ghost'; package: 'ConfigurationOfGhost'; load. (#ConfigurationOfGhost asClass project version: #stable) load. Tests are all green. > No I did not push the config in the right place to have it in the > ConfigurationBrowser. > I've put it in the Metarepo for 3.0 > > You can find infos+examples on how to achieve Method wrapper in Mariano's > PhD (p116) using Proxies for Methods. > > https://tel.archives-ouvertes.fr/tel-00764991/document > I didn't had that one, thanks! > > and also look at the test case method named > #testSimpleForwardingForMethodUsingBecome > Yes, seen that. > > Cheers, > Much appreciated! Ghost is quite nice and useful. Could do with some more class comments as there is none. I'll try to put in some as I use it. Phil > > Luc > > 2014-11-04 15:48 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> I have been reading on Ghost: >> >> >> http://esug.org/data/ESUG2011/IWST/PRESENTATIONS/23.Mariano_Peck-Ghost-ESUG… >> http://www.slideshare.net/esug/ghost-9095241 >> http://rmod.lille.inria.fr/archives/workshops/Mart11a-IWST11-Ghost.pdf >> >> This link is dead BTW: >> http://rmod.inria.fr/web/pier/software/Marea/GhostProxies >> >> I found a version here: http://www.smalltalkhub.com/#!/~CAR/Ghost/ >> >> It isn't in the ConfigurationBrowser, so I wonder where is the version to >> use. >> >> Phil >> >> >> >> >> >> On Tue, Nov 4, 2014 at 2:09 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: >> >>> >>> The language you are thinking of is most probably PHANtom: >>> http://pleiad.cl/phantom But (as author of the language) I think it is >>> overkill to use it for just a memoization cache. Idem for AspectS (I donât >>> know if it works on Pharo though). Right now, I would use MethodWrappers >>> instead, and when Reflectivity is working use that. >>> >>> On Nov 4, 2014, at 1:50 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> >>> Hi >>> >>> There is AspectS package at old squeaksource site. I not know is it >>> working in Pharo. >>> And there was presentation at Esug few years ago about another >>> implementation of aspects in Pharo ( i not remember project name) >>> 04 Ð½Ð¾ÑÐ±. 2014 Ð³. 9:04 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "phil(a)highoctane.be" < >>> phil(a)highoctane.be> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: >>> >>>> >>>> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : >>>> > >>>> > What's wrong with? >>>> > >>>> > myData >>>> > ^ data ifNil: [data := self computeMe] >>>> >>>> That I do have a lot of places like this and do not want these data >>>> littering the code. >>>> >>>> Aspects would solve this but we do not have that. >>>> >>>> Also I need the mechanism to be removable. >>>> >>>> So, I read something about MethodWrapper, ghost, slots... Can't one use >>>> any of these things to do this memoization cleanly? >>>> >>>> Phil >>>> >>>> > >>>> > >>>> > >>>> > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : >>>> > > How can I do memoization in Pharo? >>>> > > >>>> > > I mean, a generic mechanism that will help me wrap the caching >>>> around >>>> > > the method invocations / messages. >>>> > > >>>> > > I have expensive calls that do not have to refresh their results as >>>> > > often as they are called. >>>> > > >>>> > > TIA >>>> > > Phil >>>> > >>>> > >>>> > -- >>>> > Dr. Geo - http://drgeo.eu >>>> > iStoa - http://istoa.drgeo.eu >>>> > >>>> > >>>> > >>>> >>> >>> >>> >>> ---> Save our in-boxes! http://emailcharter.org <--- >>> >>> Johan Fabry - http://pleiad.cl/~jfabry >>> PLEIAD lab - Computer Science Department (DCC) - University of Chile >>> >>> >> >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Luc Fabresse

Hi Phil, Ok I missed the details so I've just refreshed my mind. yes the latest repository is this one: http://www.smalltalkhub.com/#!/~CAR/Ghost/ I've just tried in Pharo 3.0 and it works now (yes oups I forgot that it was for Pharo 2.0 ;-)). Ghost is really small so I've just fixed it Try it: ConfigurationOfGhost load Tests are green for me. No I did not push the config in the right place to have it in the ConfigurationBrowser. You can find infos+examples on how to achieve Method wrapper in Mariano's PhD (p116) using Proxies for Methods. https://tel.archives-ouvertes.fr/tel-00764991/document and also look at the test case method named #testSimpleForwardingForMethodUsingBecome Cheers, Luc 2014-11-04 15:48 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > I have been reading on Ghost: > > > http://esug.org/data/ESUG2011/IWST/PRESENTATIONS/23.Mariano_Peck-Ghost-ESUG… > http://www.slideshare.net/esug/ghost-9095241 > http://rmod.lille.inria.fr/archives/workshops/Mart11a-IWST11-Ghost.pdf > > This link is dead BTW: > http://rmod.inria.fr/web/pier/software/Marea/GhostProxies > > I found a version here: http://www.smalltalkhub.com/#!/~CAR/Ghost/ > > It isn't in the ConfigurationBrowser, so I wonder where is the version to > use. > > Phil > > > > > > On Tue, Nov 4, 2014 at 2:09 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > >> >> The language you are thinking of is most probably PHANtom: >> http://pleiad.cl/phantom But (as author of the language) I think it is >> overkill to use it for just a memoization cache. Idem for AspectS (I donât >> know if it works on Pharo though). Right now, I would use MethodWrappers >> instead, and when Reflectivity is working use that. >> >> On Nov 4, 2014, at 1:50 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >> wrote: >> >> Hi >> >> There is AspectS package at old squeaksource site. I not know is it >> working in Pharo. >> And there was presentation at Esug few years ago about another >> implementation of aspects in Pharo ( i not remember project name) >> 04 Ð½Ð¾ÑÐ±. 2014 Ð³. 9:04 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "phil(a)highoctane.be" < >> phil(a)highoctane.be> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: >> >>> >>> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : >>> > >>> > What's wrong with? >>> > >>> > myData >>> > ^ data ifNil: [data := self computeMe] >>> >>> That I do have a lot of places like this and do not want these data >>> littering the code. >>> >>> Aspects would solve this but we do not have that. >>> >>> Also I need the mechanism to be removable. >>> >>> So, I read something about MethodWrapper, ghost, slots... Can't one use >>> any of these things to do this memoization cleanly? >>> >>> Phil >>> >>> > >>> > >>> > >>> > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : >>> > > How can I do memoization in Pharo? >>> > > >>> > > I mean, a generic mechanism that will help me wrap the caching around >>> > > the method invocations / messages. >>> > > >>> > > I have expensive calls that do not have to refresh their results as >>> > > often as they are called. >>> > > >>> > > TIA >>> > > Phil >>> > >>> > >>> > -- >>> > Dr. Geo - http://drgeo.eu >>> > iStoa - http://istoa.drgeo.eu >>> > >>> > >>> > >>> >> >> >> >> ---> Save our in-boxes! http://emailcharter.org <--- >> >> Johan Fabry - http://pleiad.cl/~jfabry >> PLEIAD lab - Computer Science Department (DCC) - University of Chile >> >> >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by phil＠highoctane.be

I have been reading on Ghost: http://esug.org/data/ESUG2011/IWST/PRESENTATIONS/23.Mariano_Peck-Ghost-ESUG… http://www.slideshare.net/esug/ghost-9095241 http://rmod.lille.inria.fr/archives/workshops/Mart11a-IWST11-Ghost.pdf This link is dead BTW: http://rmod.inria.fr/web/pier/software/Marea/GhostProxies I found a version here: http://www.smalltalkhub.com/#!/~CAR/Ghost/ It isn't in the ConfigurationBrowser, so I wonder where is the version to use. Phil On Tue, Nov 4, 2014 at 2:09 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > The language you are thinking of is most probably PHANtom: > http://pleiad.cl/phantom But (as author of the language) I think it is > overkill to use it for just a memoization cache. Idem for AspectS (I donât > know if it works on Pharo though). Right now, I would use MethodWrappers > instead, and when Reflectivity is working use that. > > On Nov 4, 2014, at 1:50 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi > > There is AspectS package at old squeaksource site. I not know is it > working in Pharo. > And there was presentation at Esug few years ago about another > implementation of aspects in Pharo ( i not remember project name) > 04 Ð½Ð¾ÑÐ±. 2014 Ð³. 9:04 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "phil(a)highoctane.be" < > phil(a)highoctane.be> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > >> >> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : >> > >> > What's wrong with? >> > >> > myData >> > ^ data ifNil: [data := self computeMe] >> >> That I do have a lot of places like this and do not want these data >> littering the code. >> >> Aspects would solve this but we do not have that. >> >> Also I need the mechanism to be removable. >> >> So, I read something about MethodWrapper, ghost, slots... Can't one use >> any of these things to do this memoization cleanly? >> >> Phil >> >> > >> > >> > >> > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : >> > > How can I do memoization in Pharo? >> > > >> > > I mean, a generic mechanism that will help me wrap the caching around >> > > the method invocations / messages. >> > > >> > > I have expensive calls that do not have to refresh their results as >> > > often as they are called. >> > > >> > > TIA >> > > Phil >> > >> > >> > -- >> > Dr. Geo - http://drgeo.eu >> > iStoa - http://istoa.drgeo.eu >> > >> > >> > >> > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >

Nov. 4, 2014

Re: [Pharo-users] Porting to a MAC

by garduino

stepharo wrote >> About Dolphin, well, as you point, the ability to generate an exe and >> some >> other features more of the side of publishing a commercial app, make hard >> to >> abandon it (also the UI builder). > > Yes we would love to have the same facilities. > This is why we worked on Fuel because we would like to have a better > deployement (but this is orthogonal to deliver dll). > We would love people to work on that. Even when Dolphin can generate dll's, to my point of view is more important the capacity of generate a standalone executable (for Windows operating systems) and the ability of behave as a native application (multiple windows for example). -- View this message in context: http://forum.world.st/Porting-to-a-MAC-tp4788105p4788374.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Denis Kudriashov

2014-11-04 16:09 GMT+03:00 Johan Fabry <jfabry(a)dcc.uchile.cl>: > The language you are thinking of is most probably PHANtom: > http://pleiad.cl/phantom > Exactly

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Johan Fabry

The language you are thinking of is most probably PHANtom: http://pleiad.cl/phantom But (as author of the language) I think it is overkill to use it for just a memoization cache. Idem for AspectS (I donât know if it works on Pharo though). Right now, I would use MethodWrappers instead, and when Reflectivity is working use that. On Nov 4, 2014, at 1:50 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi > > There is AspectS package at old squeaksource site. I not know is it working in Pharo. > And there was presentation at Esug few years ago about another implementation of aspects in Pharo ( i not remember project name) > > 04 Ð½Ð¾ÑÐ±. 2014 Ð³. 9:04 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "phil(a)highoctane.be" <phil(a)highoctane.be> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > > Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : > > > > What's wrong with? > > > > myData > > ^ data ifNil: [data := self computeMe] > > That I do have a lot of places like this and do not want these data littering the code. > > Aspects would solve this but we do not have that. > > Also I need the mechanism to be removable. > > So, I read something about MethodWrapper, ghost, slots... Can't one use any of these things to do this memoization cleanly? > > Phil > > > > > > > > > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : > > > How can I do memoization in Pharo? > > > > > > I mean, a generic mechanism that will help me wrap the caching around > > > the method invocations / messages. > > > > > > I have expensive calls that do not have to refresh their results as > > > often as they are called. > > > > > > TIA > > > Phil > > > > > > -- > > Dr. Geo - http://drgeo.eu > > iStoa - http://istoa.drgeo.eu > > > > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Nov. 4, 2014

Re: [Pharo-users] How not to serve an AngularJs application from Pharo

by kilon alios

I have welcomed Amber with open arms, but I have failed miserably to wrap my head around it. Is ironic if you think about, Pharo really lacks documentation even in basic areas, libraries are nowhere near as powerful as those offered by javascript yet I have found Pharo way easier to use. Web development looks to me like a big pile of unnecessary mess. Actually Amber is the best part of it :D So the problem for me is not so much the System Browser , but the steep learning curve . Or maybe its just the fact that I dont like many of the web frameworkds, including html / js / css etc. I wish I could make something in pharo and click a button to deploy it as a website but alas thats just a dream. I think however that for the amount of developers Amber has been making some amazing progress. On Tue, Nov 4, 2014 at 4:55 AM, Pierce Ng <pierce(a)samadhiweb.com> wrote: > On Mon, Oct 27, 2014 at 10:21:18PM +0200, kilon alios wrote: > > Even though I always have been a supporter of Amber the IDE has still a > > very long way to go. > > I've been meaning to build a code browser for Amber (and GST) in Pharo with > Omnibrowser using the Shampoo protocol[1], once I get some copious spare > time. > > [1] http://dmitrymatveev.co.uk/shampoo > > Pierce > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Denis Kudriashov

Hi There is AspectS package at old squeaksource site. I not know is it working in Pharo. And there was presentation at Esug few years ago about another implementation of aspects in Pharo ( i not remember project name) 04 Ð½Ð¾ÑÐ±. 2014 Ð³. 9:04 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "phil(a)highoctane.be" <phil(a)highoctane.be> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > > Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : > > > > What's wrong with? > > > > myData > > ^ data ifNil: [data := self computeMe] > > That I do have a lot of places like this and do not want these data > littering the code. > > Aspects would solve this but we do not have that. > > Also I need the mechanism to be removable. > > So, I read something about MethodWrapper, ghost, slots... Can't one use > any of these things to do this memoization cleanly? > > Phil > > > > > > > > > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : > > > How can I do memoization in Pharo? > > > > > > I mean, a generic mechanism that will help me wrap the caching around > > > the method invocations / messages. > > > > > > I have expensive calls that do not have to refresh their results as > > > often as they are called. > > > > > > TIA > > > Phil > > > > > > -- > > Dr. Geo - http://drgeo.eu > > iStoa - http://istoa.drgeo.eu > > > > > > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Norbert Hartl

> Am 04.11.2014 um 12:47 schrieb phil(a)highoctane.be: > > On Tue, Nov 4, 2014 at 12:06 PM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > I'm not sure. I thought Spy would use them but it does not load in a fresh pharo3 for me. Did you try > > http://www.squeaksource.com/ObjectsAsMethodsWrap/ <http://www.squeaksource.com/ObjectsAsMethodsWrap/> > > This one loads and tests are green once the "_"s are replaced with ":="s > > Thx for the pointer. I'll see how I can hook a TTLCache into this. > I don't know your exact use case. But if you need one cache for your package with TTLCache then this could be done in one pass. You can have an installer that scans your package for methods containing a special pragma. Then you exchange every compiled method (installing the wrapper) with the wrapper that accesses its value from the same TTLCache having the compiled method as key. So you would have exchanged a lot of methods that share a single cache. As the TTLCache gives the hit rate on printString you get back an effectivity number for free. Norbert > Phil > > ? > > Norbert > >> Am 04.11.2014 um 11:53 schrieb phil(a)highoctane.be <mailto:phil@highoctane.be>: >> >> On Tue, Nov 4, 2014 at 9:59 AM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >> Ghost won't be a big help here. Slots would be a good solution but not if it needs to be removable on runtime. So it seems MethodWrappers is your best bet. I'd try create a caching MethodWrapper, mark all the needed methods with a pragma and then install the MethodWrapper on these. Could be a package wide install/uninstall if you need that. >> >> I loaded MethodWrappers in 3.0 as I saw in http://forum.world.st/MethodWrappers-td3829576.html#a4601624 <http://forum.world.st/MethodWrappers-td3829576.html#a4601624> >> >> Gofer it >> squeaksource: 'MethodWrappers'; >> package: 'MethodWrappers4'; >> load. >> >> It loads. >> >> But no test seems to be fine. >> >> >> <image.png> >> >> What version should I be using? >> >> Phil >> >> Norbert >> >> Am 04.11.2014 um 07:03 schrieb "phil(a)highoctane.be <mailto:phil@highoctane.be>" <phil(a)highoctane.be <mailto:phil@highoctane.be>>: >> >>> >>> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu <mailto:hilaire@drgeo.eu>> a Ã©crit : >>> > >>> > What's wrong with? >>> > >>> > myData >>> > ^ data ifNil: [data := self computeMe] >>> >>> That I do have a lot of places like this and do not want these data littering the code. >>> >>> Aspects would solve this but we do not have that. >>> >>> Also I need the mechanism to be removable. >>> >>> So, I read something about MethodWrapper, ghost, slots... Can't one use any of these things to do this memoization cleanly? >>> >>> Phil >>> >>> > >>> > >>> > >>> > Le 03/11/2014 16:10, phil(a)highoctane.be <mailto:phil@highoctane.be> a Ã©crit : >>> > > How can I do memoization in Pharo? >>> > > >>> > > I mean, a generic mechanism that will help me wrap the caching around >>> > > the method invocations / messages. >>> > > >>> > > I have expensive calls that do not have to refresh their results as >>> > > often as they are called. >>> > > >>> > > TIA >>> > > Phil >>> > >>> > >>> > -- >>> > Dr. Geo - http://drgeo.eu <http://drgeo.eu/> >>> > iStoa - http://istoa.drgeo.eu <http://istoa.drgeo.eu/> >>> > >>> > >>> > >> > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Luc Fabresse

2014-11-04 13:16 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > On 04 Nov 2014, at 09:59, Norbert Hartl <norbert(a)hartl.name> wrote: > > Ghost won't be a big help here. Slots would be a good solution but not if > it needs to be removable on runtime. So it seems MethodWrappers is your > best bet. I'd try create a caching MethodWrapper, mark all the needed > methods with a pragma and then install the MethodWrapper on these. Could be > a package wide install/uninstall if you need that. > > > This would be a nice useless for Reflectivityâ¦ one way of describing it > is âlike method wrappers, but generalizedâ. e.g. you can put a âwrapperâ on > any kind of AST node. > After the breakpoints, we could use that as the next client. > yes Nick's Reflectogram would also be usable for that but it would require a special VM currently. Indeed, it would be better to have at the compiler level. Then, Ghost is also usable for that since Mariano did a MethodWrapper like implementation using Ghost in 5 lines or so. And Ghost should load in Pharo 3 ;-) Luc > > > > Marcus > > Norbert > > Am 04.11.2014 um 07:03 schrieb "phil(a)highoctane.be" <phil(a)highoctane.be>: > > > Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : > > > > What's wrong with? > > > > myData > > ^ data ifNil: [data := self computeMe] > > That I do have a lot of places like this and do not want these data > littering the code. > > Aspects would solve this but we do not have that. > > Also I need the mechanism to be removable. > > So, I read something about MethodWrapper, ghost, slots... Can't one use > any of these things to do this memoization cleanly? > > Phil > > > > > > > > > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : > > > How can I do memoization in Pharo? > > > > > > I mean, a generic mechanism that will help me wrap the caching around > > > the method invocations / messages. > > > > > > I have expensive calls that do not have to refresh their results as > > > often as they are called. > > > > > > TIA > > > Phil > > > > > > -- > > Dr. Geo - http://drgeo.eu > > iStoa - http://istoa.drgeo.eu > > > > > > > > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Norbert Hartl

> Am 04.11.2014 um 13:16 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > > >> On 04 Nov 2014, at 09:59, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >> >> Ghost won't be a big help here. Slots would be a good solution but not if it needs to be removable on runtime. So it seems MethodWrappers is your best bet. I'd try create a caching MethodWrapper, mark all the needed methods with a pragma and then install the MethodWrapper on these. Could be a package wide install/uninstall if you need that. >> > > This would be a nice useless for Reflectivityâ¦ one way of describing it is âlike method wrappers, but generalizedâ. e.g. you can put a âwrapperâ on any kind of AST node. > After the breakpoints, we could use that as the next client. > > Sure, I forgot. If I would have the need to implement it I would try solving it with meta-links. Basically it does the same as the method wrapper without having the need to exchange the compiled method. Norbert > > Marcus > >> Norbert >> >> Am 04.11.2014 um 07:03 schrieb "phil(a)highoctane.be <mailto:phil@highoctane.be>" <phil(a)highoctane.be <mailto:phil@highoctane.be>>: >> >>> >>> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu <mailto:hilaire@drgeo.eu>> a Ã©crit : >>> > >>> > What's wrong with? >>> > >>> > myData >>> > ^ data ifNil: [data := self computeMe] >>> >>> That I do have a lot of places like this and do not want these data littering the code. >>> >>> Aspects would solve this but we do not have that. >>> >>> Also I need the mechanism to be removable. >>> >>> So, I read something about MethodWrapper, ghost, slots... Can't one use any of these things to do this memoization cleanly? >>> >>> Phil >>> >>> > >>> > >>> > >>> > Le 03/11/2014 16:10, phil(a)highoctane.be <mailto:phil@highoctane.be> a Ã©crit : >>> > > How can I do memoization in Pharo? >>> > > >>> > > I mean, a generic mechanism that will help me wrap the caching around >>> > > the method invocations / messages. >>> > > >>> > > I have expensive calls that do not have to refresh their results as >>> > > often as they are called. >>> > > >>> > > TIA >>> > > Phil >>> > >>> > >>> > -- >>> > Dr. Geo - http://drgeo.eu <http://drgeo.eu/> >>> > iStoa - http://istoa.drgeo.eu <http://istoa.drgeo.eu/> >>> > >>> > >>> > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Marcus Denker

> On 04 Nov 2014, at 09:59, Norbert Hartl <norbert(a)hartl.name> wrote: > > Ghost won't be a big help here. Slots would be a good solution but not if it needs to be removable on runtime. So it seems MethodWrappers is your best bet. I'd try create a caching MethodWrapper, mark all the needed methods with a pragma and then install the MethodWrapper on these. Could be a package wide install/uninstall if you need that. > This would be a nice useless for Reflectivityâ¦ one way of describing it is âlike method wrappers, but generalizedâ. e.g. you can put a âwrapperâ on any kind of AST node. After the breakpoints, we could use that as the next client. Marcus > Norbert > > Am 04.11.2014 um 07:03 schrieb "phil(a)highoctane.be <mailto:phil@highoctane.be>" <phil(a)highoctane.be <mailto:phil@highoctane.be>>: > >> >> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu <mailto:hilaire@drgeo.eu>> a Ã©crit : >> > >> > What's wrong with? >> > >> > myData >> > ^ data ifNil: [data := self computeMe] >> >> That I do have a lot of places like this and do not want these data littering the code. >> >> Aspects would solve this but we do not have that. >> >> Also I need the mechanism to be removable. >> >> So, I read something about MethodWrapper, ghost, slots... Can't one use any of these things to do this memoization cleanly? >> >> Phil >> >> > >> > >> > >> > Le 03/11/2014 16:10, phil(a)highoctane.be <mailto:phil@highoctane.be> a Ã©crit : >> > > How can I do memoization in Pharo? >> > > >> > > I mean, a generic mechanism that will help me wrap the caching around >> > > the method invocations / messages. >> > > >> > > I have expensive calls that do not have to refresh their results as >> > > often as they are called. >> > > >> > > TIA >> > > Phil >> > >> > >> > -- >> > Dr. Geo - http://drgeo.eu <http://drgeo.eu/> >> > iStoa - http://istoa.drgeo.eu <http://istoa.drgeo.eu/> >> > >> > >> >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by phil＠highoctane.be

On Tue, Nov 4, 2014 at 12:06 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > I'm not sure. I thought Spy would use them but it does not load in a fresh > pharo3 for me. Did you try > > http://www.squeaksource.com/ObjectsAsMethodsWrap/ > This one loads and tests are green once the "_"s are replaced with ":="s Thx for the pointer. I'll see how I can hook a TTLCache into this. Phil > > ? > > Norbert > > Am 04.11.2014 um 11:53 schrieb phil(a)highoctane.be: > > On Tue, Nov 4, 2014 at 9:59 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Ghost won't be a big help here. Slots would be a good solution but not if >> it needs to be removable on runtime. So it seems MethodWrappers is your >> best bet. I'd try create a caching MethodWrapper, mark all the needed >> methods with a pragma and then install the MethodWrapper on these. Could be >> a package wide install/uninstall if you need that. >> > > I loaded MethodWrappers in 3.0 as I saw in > http://forum.world.st/MethodWrappers-td3829576.html#a4601624 > > Gofer it > squeaksource: 'MethodWrappers'; > package: 'MethodWrappers4'; > load. > > It loads. > > But no test seems to be fine. > > > <image.png> > > What version should I be using? > > Phil > > >> Norbert >> >> Am 04.11.2014 um 07:03 schrieb "phil(a)highoctane.be" <phil(a)highoctane.be>: >> >> >> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : >> > >> > What's wrong with? >> > >> > myData >> > ^ data ifNil: [data := self computeMe] >> >> That I do have a lot of places like this and do not want these data >> littering the code. >> >> Aspects would solve this but we do not have that. >> >> Also I need the mechanism to be removable. >> >> So, I read something about MethodWrapper, ghost, slots... Can't one use >> any of these things to do this memoization cleanly? >> >> Phil >> >> > >> > >> > >> > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : >> > > How can I do memoization in Pharo? >> > > >> > > I mean, a generic mechanism that will help me wrap the caching around >> > > the method invocations / messages. >> > > >> > > I have expensive calls that do not have to refresh their results as >> > > often as they are called. >> > > >> > > TIA >> > > Phil >> > >> > >> > -- >> > Dr. Geo - http://drgeo.eu >> > iStoa - http://istoa.drgeo.eu >> > >> > >> > >> >> > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Norbert Hartl

I'm not sure. I thought Spy would use them but it does not load in a fresh pharo3 for me. Did you try http://www.squeaksource.com/ObjectsAsMethodsWrap/ <http://www.squeaksource.com/ObjectsAsMethodsWrap/> ? Norbert > Am 04.11.2014 um 11:53 schrieb phil(a)highoctane.be: > > On Tue, Nov 4, 2014 at 9:59 AM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > Ghost won't be a big help here. Slots would be a good solution but not if it needs to be removable on runtime. So it seems MethodWrappers is your best bet. I'd try create a caching MethodWrapper, mark all the needed methods with a pragma and then install the MethodWrapper on these. Could be a package wide install/uninstall if you need that. > > I loaded MethodWrappers in 3.0 as I saw in http://forum.world.st/MethodWrappers-td3829576.html#a4601624 <http://forum.world.st/MethodWrappers-td3829576.html#a4601624> > > Gofer it > squeaksource: 'MethodWrappers'; > package: 'MethodWrappers4'; > load. > > It loads. > > But no test seems to be fine. > > > <image.png> > > What version should I be using? > > Phil > > Norbert > > Am 04.11.2014 um 07:03 schrieb "phil(a)highoctane.be <mailto:phil@highoctane.be>" <phil(a)highoctane.be <mailto:phil@highoctane.be>>: > >> >> Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu <mailto:hilaire@drgeo.eu>> a Ã©crit : >> > >> > What's wrong with? >> > >> > myData >> > ^ data ifNil: [data := self computeMe] >> >> That I do have a lot of places like this and do not want these data littering the code. >> >> Aspects would solve this but we do not have that. >> >> Also I need the mechanism to be removable. >> >> So, I read something about MethodWrapper, ghost, slots... Can't one use any of these things to do this memoization cleanly? >> >> Phil >> >> > >> > >> > >> > Le 03/11/2014 16:10, phil(a)highoctane.be <mailto:phil@highoctane.be> a Ã©crit : >> > > How can I do memoization in Pharo? >> > > >> > > I mean, a generic mechanism that will help me wrap the caching around >> > > the method invocations / messages. >> > > >> > > I have expensive calls that do not have to refresh their results as >> > > often as they are called. >> > > >> > > TIA >> > > Phil >> > >> > >> > -- >> > Dr. Geo - http://drgeo.eu <http://drgeo.eu/> >> > iStoa - http://istoa.drgeo.eu <http://istoa.drgeo.eu/> >> > >> > >> > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by phil＠highoctane.be

On Tue, Nov 4, 2014 at 9:59 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Ghost won't be a big help here. Slots would be a good solution but not if > it needs to be removable on runtime. So it seems MethodWrappers is your > best bet. I'd try create a caching MethodWrapper, mark all the needed > methods with a pragma and then install the MethodWrapper on these. Could be > a package wide install/uninstall if you need that. > I loaded MethodWrappers in 3.0 as I saw in http://forum.world.st/MethodWrappers-td3829576.html#a4601624 Gofer it squeaksource: 'MethodWrappers'; package: 'MethodWrappers4'; load. It loads. But no test seems to be fine. [image: Inline image 1] What version should I be using? Phil > Norbert > > Am 04.11.2014 um 07:03 schrieb "phil(a)highoctane.be" <phil(a)highoctane.be>: > > > Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : > > > > What's wrong with? > > > > myData > > ^ data ifNil: [data := self computeMe] > > That I do have a lot of places like this and do not want these data > littering the code. > > Aspects would solve this but we do not have that. > > Also I need the mechanism to be removable. > > So, I read something about MethodWrapper, ghost, slots... Can't one use > any of these things to do this memoization cleanly? > > Phil > > > > > > > > > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : > > > How can I do memoization in Pharo? > > > > > > I mean, a generic mechanism that will help me wrap the caching around > > > the method invocations / messages. > > > > > > I have expensive calls that do not have to refresh their results as > > > often as they are called. > > > > > > TIA > > > Phil > > > > > > -- > > Dr. Geo - http://drgeo.eu > > iStoa - http://istoa.drgeo.eu > > > > > > > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Damien Pollet

mutate a literal array ? :D On 3 November 2014 16:10, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > How can I do memoization in Pharo? > > I mean, a generic mechanism that will help me wrap the caching around the > method invocations / messages. > > I have expensive calls that do not have to refresh their results as often as > they are called. > > TIA > Phil

Nov. 4, 2014

Re: [Pharo-users] Porting to a MAC

by stepharo

> Yes, it was a sad news of Bill's death, I read the list of Dolphin. yes sad! > > About Dolphin, well, as you point, the ability to generate an exe and some > other features more of the side of publishing a commercial app, make hard to > abandon it (also the UI builder). Yes we would love to have the same facilities. This is why we worked on Fuel because we would like to have a better deployement (but this is orthogonal to deliver dll). We would love people to work on that. > My password manager PasswordsPro is still in Dolphin and will stay there for > some time yet ... >

Nov. 4, 2014

Re: [Pharo-users] How not to serve an AngularJs application from Pharo

by stepharo

I'm really interested to see how we could develop amber inside pharo and generate JS/amber code. May be you should look at spec instead of OB. On 4/11/14 03:55, Pierce Ng wrote: > On Mon, Oct 27, 2014 at 10:21:18PM +0200, kilon alios wrote: >> Even though I always have been a supporter of Amber the IDE has still a >> very long way to go. > I've been meaning to build a code browser for Amber (and GST) in Pharo with > Omnibrowser using the Shampoo protocol[1], once I get some copious spare time. > > [1] http://dmitrymatveev.co.uk/shampoo > > Pierce > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Norbert Hartl

Ghost won't be a big help here. Slots would be a good solution but not if it needs to be removable on runtime. So it seems MethodWrappers is your best bet. I'd try create a caching MethodWrapper, mark all the needed methods with a pragma and then install the MethodWrapper on these. Could be a package wide install/uninstall if you need that. Norbert > Am 04.11.2014 um 07:03 schrieb "phil(a)highoctane.be" <phil(a)highoctane.be>: > > > Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : > > > > What's wrong with? > > > > myData > > ^ data ifNil: [data := self computeMe] > > That I do have a lot of places like this and do not want these data littering the code. > > Aspects would solve this but we do not have that. > > Also I need the mechanism to be removable. > > So, I read something about MethodWrapper, ghost, slots... Can't one use any of these things to do this memoization cleanly? > > Phil > > > > > > > > > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : > > > How can I do memoization in Pharo? > > > > > > I mean, a generic mechanism that will help me wrap the caching around > > > the method invocations / messages. > > > > > > I have expensive calls that do not have to refresh their results as > > > often as they are called. > > > > > > TIA > > > Phil > > > > > > -- > > Dr. Geo - http://drgeo.eu > > iStoa - http://istoa.drgeo.eu > > > > > >

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by phil＠highoctane.be

Le 3 nov. 2014 22:13, "Hilaire" <hilaire(a)drgeo.eu> a Ã©crit : > > What's wrong with? > > myData > ^ data ifNil: [data := self computeMe] That I do have a lot of places like this and do not want these data littering the code. Aspects would solve this but we do not have that. Also I need the mechanism to be removable. So, I read something about MethodWrapper, ghost, slots... Can't one use any of these things to do this memoization cleanly? Phil > > > > Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : > > How can I do memoization in Pharo? > > > > I mean, a generic mechanism that will help me wrap the caching around > > the method invocations / messages. > > > > I have expensive calls that do not have to refresh their results as > > often as they are called. > > > > TIA > > Phil > > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > >

Nov. 4, 2014

Re: [Pharo-users] OSProcess command never ends

by Offray Vladimir Luna CÃ¡rdenas

Hi, Thanks Dave. Your detailed explanation helped me to understand what was going in. The problem was that I don't use /bin/sh as my default shell, so there was no process associated to it (/bin/zsh was the parent of all shell process including launching Pharo). Now I have changed the way I use to launch pharo from my zsh shell. It goes something like this: /bin/sh ~/Programas/Pharo/pharo-ui ~/Programas/Moose/5.0/moose-5.0.image Now is working well. The only thing is that the last process is always running, so I put an 'echo "something"' as the last argument of the OSProcess command: to get all previous commands working instead of making all but the last one (which waits forever and exec doesn't work). Cheers, Offray On 11/02/2014 08:17 PM, David T. Lewis wrote: > On Sun, Nov 02, 2014 at 07:28:44PM -0500, Offray Vladimir Luna C??rdenas wrote: >> Thanks David and Juan, >> >> I was trying to run a pandoc conversion from markdown to html and I had >> an error inside my command. Once corrected it works without any problem >> and generates the desired file. One note on adding "exec" is that I get >> this message on the playground: >> >> "an ExternalUnixOSProcess with pid 21552 on /bin/sh (complete, normal >> termination with status 0)" >> >> which seems better. Despite of both working I will use the exec >> suggestion to have a better message from external process. >> > > Using the exec shell command is a good idea. Just for information, the > ExternalUnixOSProcess object is a proxy for the real external OS process, > which started by running the /bin/sh program. When you use exec to run > your pandoc program, the pandoc program will begin running in the same > external OS process that was originally running the /bin/sh program. > The ExternalUnixOSProcess object does not know that you did this, so it > still displays itself as "an ExternalUnixOSProcess ... on /bin/sh" even > though the OS process is now actually running your pandoc program instead. > But the exit status 0 came from your pandoc program, which is exactly > what you wanted. > > Dave > > >

Nov. 4, 2014

Re: [Pharo-users] How not to serve an AngularJs application from Pharo

by Pierce Ng

On Mon, Oct 27, 2014 at 10:21:18PM +0200, kilon alios wrote: > Even though I always have been a supporter of Amber the IDE has still a > very long way to go. I've been meaning to build a code browser for Amber (and GST) in Pharo with Omnibrowser using the Shampoo protocol[1], once I get some copious spare time. [1] http://dmitrymatveev.co.uk/shampoo Pierce

Nov. 4, 2014

Re: [Pharo-users] Memoization Question

by Hilaire

What's wrong with? myData ^ data ifNil: [data := self computeMe] Le 03/11/2014 16:10, phil(a)highoctane.be a Ã©crit : > How can I do memoization in Pharo? > > I mean, a generic mechanism that will help me wrap the caching around > the method invocations / messages. > > I have expensive calls that do not have to refresh their results as > often as they are called. > > TIA > Phil -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Nov. 3, 2014