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

Re: [Pharo-dev] [regression reporter]regression occurred

by Andrei Chis

Thanks :) We would still want to do one more update, maybe today or tomorrow, to add the extension for recording user data. Afterwards it's bug fixing mode. On Fri, Feb 27, 2015 at 5:37 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On Fri, Feb 27, 2015 at 10:22 AM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > >> The issue is waiting integration: >> https://pharo.fogbugz.com/f/cases/14993/Integrate-GTools >> There are still some more bugs to fix but we should integrate >> nevertheless. >> > > In 40 update #520 > > Marcus >

Feb. 27, 2015

Re: [Pharo-dev] Slots: and ProcessLocalSlot

by Henrik Johansen

> On 27 Feb 2015, at 5:43 , Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Not yet, but that is a next step we were discussing the other day. > > El Fri Feb 27 2015 at 5:41:50 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no <mailto:henrik.s.johansen@veloxit.no>> escribiÃ³: > >> On 26 Feb 2015, at 6:55 , Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >> >> So I added an example of ProcessLocalSlot (like a thread local from other languages) using the existing ProcessLocalVariable. A variable has different values depending on the process the code is executing. >> >> Example of usage: >> >> Object subclass: #TestLocal >> slots: { #local => ProcessLocalSlot } >> classVariables: { } >> category: 'SlotTestGuille'. >> >> object := TestLocal new. >> object local: 55. >> object local. >> >> [ valueInOtherProcess := object local ] fork. >> >> valueInOtherProcess. "=> nil" >> >> [ object local: 'String'. >> valueInOtherProcess := object local ] fork. >> >> valueInOtherProcess. "=> 'String'" >> object local "=> 55" >> >> Code in issue: https://pharo.fogbugz.com/f/cases/15004/Add-ProcessLocalSlot <https://pharo.fogbugz.com/f/cases/15004/Add-ProcessLocalSlot> >> >> Guille > > Pardon my ignorance, but can Slot definitions be composed like traits? > Because I can imagine wanting, say ProcessLocal + mmm... Static, without having to combine the two properties in a class with a gnarly inheritance tree, or a factorial number of classes combining different defining traits... > > Cheers, > Henry Looking forward to it! Would something like slots: {#x . #y . #area -> (Cache: #calculateArea)) } Meaning :area is a Slot that holds a cached value, calculated when accessed (by calling calculateArea), and nilled whenever slots accessed by it's calculation method takes a new value. be possible as well? Who said cache invalidation has to be hard? ;) Cheers, Henry

Feb. 27, 2015

Re: [Pharo-dev] Easy way to write a proxy?

by Alexandre Bergel

> Alex why ghost is not ok? At that stage, it was more of a mental exercise. > Because you want to have a portable proxy? If our implementation goes above a simple prototype, yes, it will have to work on VisualWorks. Alexandre > > Le 27/2/15 03:43, Alexandre Bergel a Ã©crit : >> Hi! >> >> I have a near-to-be naive question. Maybe there is something obvious, but I cannot see it. Consider the following implementation of a proxy: >> >> -=-=-=-=-=-=-=-=-=-=-=-= >> Object subclass: #MyProxy >> instanceVariableNames: 'object'. >> >> MyProxy >> object: anObject >> object := anObject >> >> MyProxy >> doesNotUnderstand: aMessage >> ^ object perform: aMessage selector withArguments: aMessage arguments >> >> Object >> wrap >> self becomeForward: (MyProxy new object: self; yourself) >> -=-=-=-=-=-=-=-=-=-=-=-= >> >> The problem is with wrap. After the becomeForward:, MyProxy has itself in the object variable. Even self is apparently subject to the #become. >> >> It means that the following code loop indefinitely >> >> -=-=-=-=-=-=-=-=-=-=-=-= >> d := Dictionary new. >> d wrap. >> d add: #foo -> 10 >> -=-=-=-=-=-=-=-=-=-=-=-= >> >> I know there is Marianoâs library to write proxy. But I still wondering whether this could be done simply. >> Any idea how to simply create a proxy? >> >> Cheers, >> Alexandre >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 27, 2015

Re: [Pharo-dev] Easy way to write a proxy?

by Alexandre Bergel

Excellent! Alexandre > On Feb 27, 2015, at 7:10 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > For most cases Ghost is the way to go. > > > We will add a proxy model (based on Ghost or just ghost as is) to Pharo by default in Pharo5. > Then people can just use it. > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 27, 2015

Re: [Pharo-dev] Easy way to write a proxy?

by Alexandre Bergel

> So the idea is that the reference to self in MyProxy becomes the wrapped object using the become. Yes, for some reason, I did not see this. Well spotted! I am getting old apparently :-) > The main problem of this kind of implementation is that self is bounded to the proxy, so all the internal calls of self are not going to be intercepted and the return self is going to expose the original object. Yes. Maybe the doesNotUnderstand: can be improved to take this into account. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 27, 2015

Re: [Pharo-dev] Easy way to write a proxy?

by Alexandre Bergel

> Object >> wrap > | proxyThenTarget | > proxyThenTarget := MyProxy new. > self become: proxyThenTarget. > âNow self is the proxy" > self object: proxyThenTarget. > ^ self Tshuuâ¦. I did not think about this. Well spotted!!! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 27, 2015

Re: [Pharo-dev] Slots: and ProcessLocalSlot

by Guillermo Polito

Not yet, but that is a next step we were discussing the other day. El Fri Feb 27 2015 at 5:41:50 PM, Henrik Johansen < henrik.s.johansen(a)veloxit.no> escribiÃ³: > > On 26 Feb 2015, at 6:55 , Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > So I added an example of ProcessLocalSlot (like a thread local from other > languages) using the existing ProcessLocalVariable. A variable has > different values depending on the process the code is executing. > > Example of usage: > > Object subclass: #TestLocal > slots: { #local => ProcessLocalSlot } > classVariables: { } > category: 'SlotTestGuille'. > > object := TestLocal new. > object local: 55. > object local. > > [ valueInOtherProcess := object local ] fork. > > valueInOtherProcess. "=> nil" > > [ object local: 'String'. > valueInOtherProcess := object local ] fork. > > valueInOtherProcess. "=> 'String'" > object local "=> 55" > > Code in issue: > https://pharo.fogbugz.com/f/cases/15004/Add-ProcessLocalSlot > > Guille > > > Pardon my ignorance, but can Slot definitions be composed like traits? > Because I can imagine wanting, say ProcessLocal + mmm... Static, without > having to combine the two properties in a class with a gnarly inheritance > tree, or a factorial number of classes combining different defining > traits... > > Cheers, > Henry >

Feb. 27, 2015

Re: [Pharo-dev] Recording user actions in GTools

by kilon alios

no objection from me, whatever help you guys improve the tools, helps me ;) On Thu, Feb 26, 2015 at 5:10 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > In order to better understand how people use the GT tools we would like to > integrate, before the Pharo code freeze, a small extension to GT tools (300 > lines of code) that records and sends usage data. > > The recording of data will be opt-out: *you have to explicitly agree with > sending usage data*. > The first time you open a GT tool, that tool will embed a small UI asking > you if you want to enable data submission. > We will save the setting in the your preference directory so it will be > shared between all your local images. > You can change this setting at any time from the Settings Browser. > > For now we will only like to collect data about Spotter. > *By default we will only collect anonymous data *about various actions > you do in spotter (open, close, search, dive-in, dive-out, select element, > etc) without collecting any data what about what query you enter or what > search results you get. > We would also add an optional setting for sending the query text and > selected elements. > > We will send then the data periodically to our server and when you close > the image. > > The data that will be send is rather small: 1000 actions require 7kb of > data. > Thus sending an entire day worth of recordings, if all you did that day > was searching, should be around 1MB of data. > > The recording does not influence the performance of Spotter. Spotter > already generates all events of interest as announcements. > To enable recording we just register a subscriber with the Spotter > announcer and store the events of interest. > > We would like to get your opinion on this. > > > Cheers, > GT team > >

Feb. 27, 2015

Re: [Pharo-dev] Slots: and ProcessLocalSlot

by Henrik Johansen

> On 26 Feb 2015, at 6:55 , Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > So I added an example of ProcessLocalSlot (like a thread local from other languages) using the existing ProcessLocalVariable. A variable has different values depending on the process the code is executing. > > Example of usage: > > Object subclass: #TestLocal > slots: { #local => ProcessLocalSlot } > classVariables: { } > category: 'SlotTestGuille'. > > object := TestLocal new. > object local: 55. > object local. > > [ valueInOtherProcess := object local ] fork. > > valueInOtherProcess. "=> nil" > > [ object local: 'String'. > valueInOtherProcess := object local ] fork. > > valueInOtherProcess. "=> 'String'" > object local "=> 55" > > Code in issue: https://pharo.fogbugz.com/f/cases/15004/Add-ProcessLocalSlot <https://pharo.fogbugz.com/f/cases/15004/Add-ProcessLocalSlot> > > Guille Pardon my ignorance, but can Slot definitions be composed like traits? Because I can imagine wanting, say ProcessLocal + mmm... Static, without having to combine the two properties in a class with a gnarly inheritance tree, or a factorial number of classes combining different defining traits... Cheers, Henry

Feb. 27, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40520 Home: https://github.com/pharo-project/pharo-core

Feb. 27, 2015