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

Re: [Pharo-dev] [COTDC] 108 - NewValueHolder

by Benjamin

On 21 Jan 2014, at 04:53, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Since nobody looks at it: here are the issue (they contain class comments). > > https://pharo.fogbugz.com/default.asp?12572 is a print case of the following, so will not be checked until the child case is integrated. > > https://pharo.fogbugz.com/default.asp?12486 Resolved (Fixed upstream) aka integrated in Spec So itâs just waiting to be integrated in Pharo. > > Apparently all the work I did around Spec is not reviewed. So this is basically false, and not motivating as a statement. > May be I should push them without waiting from any feedback. â¦ Ben

Jan. 21, 2014

...and load back

by Pavel Krivanek

We can now (again) load and initialize Morphic and tools after unloading it. Main problems to solve: - Multilingual packages are problematic to load - ThemeIcons>>#iconSelectors message finds Object>>#systemIcon too for simplicity we do not load most of the tests and NativeBoost. https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/job/PharoKerne… -- Pavel

Jan. 21, 2014

Re: [Pharo-dev] Pharo on a Raspbian

by Jean Baptiste Arnaud

> Yes it would be good to collaborate. I agree. On 21 Jan 2014, at 09:07, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On 20 Jan 2014, at 23:15, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> Hi Jean-Baptiste, >> >> On Mon, Jan 20, 2014 at 7:25 AM, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> wrote: >> >> On 18 Jan 2014, at 09:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> One of the problem we are thinking about now is the FFI on ARM (alien or not alien)â¦. >> >> +1, we need to think the, best solution is to have NativeBoost on ARM. >> We need an agreement between, time to develop and usage. >> Maybe first I should fix Alien or FFI. Then one day, port Nativeboost on ARM. >> >> >> Did you see the thread on vm-dev about the ARM FFI? When I wrote the FFI-replacement ThreadedFFIPlugin (which is the standard FFI plugin in Cog) I added stubs for ARM and PowerPC. I hope that Doug McPherson is going to be able to fully implement these stubs. If you're interested perhaps you could collaborate? I'm confident that the effort involved in getting this going is a week or two at most. Days for someone who well understands alloca and the ARM ABI. I see it, It is what I speak about when I speak about "fix" FFI, fill the stub. I can collaborate with Doug to fill it, it would be good. > > Yes it would be good to collaborate. > > Stef > >> >>>>> On 17 January 2014 22:59, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> Who is JB ? >>>>> >>>>> >>>>> Jean Baptiste Arnaud. The invaluable asset in any team :) >>>>> The hacker who without any help configuring & compiling VM on raspberry. >> >> Oh, for real, I'm flattered. >> >>>> >>>> Good to know. >>>> >>>> Thanks Jean-Baptiste ! >> >>>> >>> >>> >> >> Best Regards >> Jean Baptiste Arnaud >> jbaptiste.arnaud(a)gmail.com >> >> >> >> >> >> >> >> >> >> >> -- >> best, >> Eliot

Jan. 21, 2014

[help] someone with account on http://pharo.gemtalksystems.com needed

by Marcus Denker

â¦ to delete 5 lines on a page. Marcus

Jan. 21, 2014

Re: [Pharo-dev] NewVersionBrowser

by Nicolai Hess

2014/1/21 Marcus Denker <marcus.denker(a)inria.fr> > > On 21 Jan 2014, at 00:19, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > Hi, > > I finished case "11714 <https://pharo.fogbugz.com/default.asp?11714>NewVersionBrowser needs to be finished". > The changes are integrated and the case is closed. > > Very nice! > > > I omit the Tools registry changes until I have done some more testings > and there are no issues left. > > I have remaining question: > With the side-by-side diff where to put the selected version > and where the prior version? > Currently (Old-)VersionBrowser shows the selected version > on the right and the prior version on the left. > This looks a bit strange. > > > > I would make sure it works the same as the Monticello diffâ¦ > and left original, right change seems to be what it does? > > Marcus > Ok, I take the current version: Left -> Right old Version -> new Version / the changes

Jan. 21, 2014

Re: [Pharo-dev] Pharo on a Raspbian

by StÃ©phane Ducasse

On 20 Jan 2014, at 23:15, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Jean-Baptiste, > > On Mon, Jan 20, 2014 at 7:25 AM, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> wrote: > > On 18 Jan 2014, at 09:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> One of the problem we are thinking about now is the FFI on ARM (alien or not alien)â¦. > > +1, we need to think the, best solution is to have NativeBoost on ARM. > We need an agreement between, time to develop and usage. > Maybe first I should fix Alien or FFI. Then one day, port Nativeboost on ARM. > > > Did you see the thread on vm-dev about the ARM FFI? When I wrote the FFI-replacement ThreadedFFIPlugin (which is the standard FFI plugin in Cog) I added stubs for ARM and PowerPC. I hope that Doug McPherson is going to be able to fully implement these stubs. If you're interested perhaps you could collaborate? I'm confident that the effort involved in getting this going is a week or two at most. Days for someone who well understands alloca and the ARM ABI. Yes it would be good to collaborate. Stef > >>>> On 17 January 2014 22:59, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> Who is JB ? >>>> >>>> >>>> Jean Baptiste Arnaud. The invaluable asset in any team :) >>>> The hacker who without any help configuring & compiling VM on raspberry. > > Oh, for real, I'm flattered. > >>> >>> Good to know. >>> >>> Thanks Jean-Baptiste ! > >>> >> >> > > Best Regards > Jean Baptiste Arnaud > jbaptiste.arnaud(a)gmail.com > > > > > > > > > > > -- > best, > Eliot

Jan. 21, 2014

Re: [Pharo-dev] Anyone with the passwd to edit http://book.pharo-project.org/book/PharoTools/

by Marcus Denker

On 21 Jan 2014, at 08:46, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On 21 Jan 2014, at 07:59, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 18 Jan 2014, at 11:26, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> 10231 collaboractive Book: Page about Pharo Tools is out of date >>> https://pharo.fogbugz.com/f/cases/10231 >>> >>> â> the action needed to close this issue tracker entry is to remove the "Other Pharo Non Core Packagesâ >>> section. >>> >> >> If this issue is not fixed until Feb1, I will close it and replace it with âremove DNS entry book.pharo-project.orgâ. > > Marcus why donât you say that this is a bit updated. To whom? Where? What? What I want is that someone closes the issue tracker entry with âDONEâ. > How do you think that we can manage it? Someone with the password need to *do it*. I do not know how things can happen if nobody does it. Especially simple things. (I do not have the pass, so I can not do anything) > It is not possible. Now do you that there is tokyoTyrant? No, isnât that a database? I have no idea even what it could mean in the context of this discussion... Marcus

Jan. 21, 2014

Re: [Pharo-dev] [Moose-dev] you spin me around...

by StÃ©phane Ducasse

> > > -=-=-=-=-=-=-=-=-=-= > | v shape | > v := RTView new. > shape := RTRotatedLabel new. > > why you need separate class for 'rotated' label? > i suppose you also need RTRotatedAndScaledLabel, > RTRotatedAndScewedLabel > .. as well as other (infinite) number of permutations with 'something-ed' and 'Label'. > > or its just a prototype? I asked myself the same. Why Label can not do everyhing? Stef > > shape angleInDegree: [ :cls | cls numberOfMethods negated / 1.5 ]. > shape text: [ :cls | ' ', cls name ]. > shape color: (Color black alpha: 0.2). > v addAll: (shape elementsOn: Collection withAllSubclasses). > > v canvas color: Color white. > v open > -=-=-=-=-=-=-=-=-=-= > > More screenshots and more examples on: > https://www.facebook.com/media/set/?set=a.573528479400420.1073741841.340543… > > Excellent job Juraj! > > Before the end of January, we will make a big big announcement. We, the profilers, are working hard these days on a fantastic infrastructure for a better and stronger visual experience. > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- > Best regards, > Igor Stasenko. > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Jan. 21, 2014

Re: [Pharo-dev] [COTDC] 108 - NewValueHolder

by StÃ©phane Ducasse

Since nobody looks at it: here are the issue (they contain class comments). https://pharo.fogbugz.com/default.asp?12572 https://pharo.fogbugz.com/default.asp?12486 Apparently all the work I did around Spec is not reviewed. May be I should push them without waiting from any feedback. Stef

Jan. 21, 2014

Re: [Pharo-dev] [COTDC] 108 - NewValueHolder

by StÃ©phane Ducasse

Hi nicolas. I do not remember but it seems that I did a slice to move NewValueHolder out of Spec inside their own package. Then we should rename and remove the old one but it takes time and if somebody does it will go faster. Stef > NewValueHolder? the name sounds like a Squeak strategy: keep backward compatibility as long as possible. > > Since Pharo values cleanlyDesigned > backwardCompatible, I would expect ValueHolder->LegacyValueHolder and NewValueHolder->ValueHolder. > > We had too many NewParagraph, etc... in the past, history does not necessarily have to repeat itself ;) > > > 2014/1/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > I commented the code in a slice that apparently was not integrated. > But yes this is a good idea. > - to have more code review > - to revive the COTDC!!!! > > > > I had some questions about NewValueHolder and I figured, why not revive > > COTDC?! > > > > The current comment is: "A NewValueHolder is a new implementation of > > ValueHolder based on Announcements". Of course, ValueHolder doesn't have a > > class comment. Wikipedia claims a value holder is "a generic object that > > handles the lazy loading behavior, and appears in place of the object's data > > fields" [1]. So: > > - what is a NewValueHolder? > > - is the "Value Holder" part of the name accurate in light of [1]. Obviously > > repurposing a term people may already be familiar with is a bad idea. In > > fact the important part here seems not the holding of the value, but the > > notification of changes. It seems more like an event in FRP. How about > > ReactiveVariable or AnnouncingVariable, since it combines the storage of a > > variable with announcing of changes? I like Reactive a bit better because > > those familiar with FRP will get the idea that it's notifying dependents, > > Announcing maybe begs the question "announcing what?" > > - should it replace ValueHolder, which is used only by > > ExclusiveWeakMessageSend and WidgetExamples > > > > [1] http://en.wikipedia.org/wiki/Lazy_loading > > > > p.s. [OT] valueChanged: oldValue to: newValue seems fishy. It is only used > > in one place in the image in this weird way "pickedItemsHolder valueChanged: > > true to: item" > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: http://forum.world.st/COTDC-108-NewValueHolder-tp4738066.html > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > >

Jan. 21, 2014