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

[Pharo-project] Call for Pharo Support **important**

by StÃ©phane Ducasse

Please distribute this message around Dear Pharoers We are pursuing an effort to bring Pharo to the next level: we will set up a consortium of pharo users and industrial partners. Our goal is to build a legal infrastructure that will be able to sustain the development of Pharo and improve its future. As an example, we would like to be able to collect funds (ways as to be determined - we foresee a membership model or moral license) to pay engineering tasks to be performed such as improving the virtual machine, network libraries, better JIT support. To make it short we would like to give a chance to our community to grow and structure itself so that Pharo can get stronger and that risk (truck factor) gets minimized. We are contacting you to know if your company/research group would be interested to support such effort. Showing such interest is strategically important for us and INRIA which could also support such effort. Attached is the letter of support that we will collect once signed and scanned ( stephane.ducasse(a)inria.fr / faxed at: 00 33 (0)3 59 57 78 50) Thanks for your support The Pharo Board M. Denker, S. Ducasse, and A. Lienhard

Feb. 15, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by Igor Stasenko

On 15 February 2011 12:50, David T. Lewis <lewis(a)mail.msen.com> wrote: > On Tue, Feb 15, 2011 at 08:00:18AM +0100, St?phane Ducasse wrote: >> Eliot >> >> you use caseOf: for the generation of C in Slang and VM maker. >> Now this means that >> Â Â Â - it does not need to be inlined >> Â Â Â - it could be packaged with VMMaker >> >> Are these two points correct? > > No. > > VMMaker is used in many images, not just Pharo. And #caseOf: > is used in packages other than VMMaker. So moving it into the > VMMaker package would be a Bad Thing To Do. > I agree. Then probably, Pharo should move it to separate 'Crap-compat' package. ;-P You don't need to remove #caseOf: implementation. I can stay. Just remove a compiler hacks for it :) P.S. i patched MessageNode class>>initialize to test if VMMaker can work without compiler support of caseof: and as it was expected it works quite well. I recompiled VMMaker package and then generated full source code of everything, and then built VM. No any errors. > Dave > > > -- Best regards, Igor Stasenko AKA sig.

Feb. 15, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #71 on issue 3583 by Benjamin...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Here two cs that fix this problem. It's different in 1.2 and 1.3 because now Workspace superclass is Object :) Here it works, so I cross fingers ^^ Attachments: FixWorkspace1.2.1.cs 567 bytes FixWorkspace1.3.1.cs 2.2 KB

Feb. 15, 2011

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

by David T. Lewis

On Tue, Feb 15, 2011 at 08:00:18AM +0100, St?phane Ducasse wrote: > Eliot > > you use caseOf: for the generation of C in Slang and VM maker. > Now this means that > - it does not need to be inlined > - it could be packaged with VMMaker > > Are these two points correct? No. VMMaker is used in many images, not just Pharo. And #caseOf: is used in packages other than VMMaker. So moving it into the VMMaker package would be a Bad Thing To Do. Dave

Feb. 15, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #70 on issue 3583 by Benjamin...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 I think it comes from the workspace, I'll take a look at the fix proposed to fix the declaration of new variables ... Moreover, by default, the item "Automatically create temporary variables" is unselected (the square is blank), but variables created, and if you select it (the square is grayed), variables aren't created anymore ...

Feb. 15, 2011

Re: [Pharo-project] RPackage images

by Tudor Girba

On 15 Feb 2011, at 12:25, Torsten Bergmann wrote: >>> Is there any documentation available on RPackage already? >>> Or a help book? >> >> There is some comments in the classes RPackage and RPackageOrganizer. > > OK, and now there is also a help book ;) > > One can try the package stuff and read the docu using: > > ------------------------------------------------------------------- > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'ConfigurationOfRPackage'; > load. > > ((Smalltalk at: #ConfigurationOfRPackage) project version: 'default') load. > HelpBrowser open > ------------------------------------------------------------------- > > BTW: I still wonder why the classes are called RPackage and RPackageOrganizer instead of "Package" and "PackageOrganizer". Because of name clashes. Cheers, Doru > Keep on talking small > T. > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > -- www.tudorgirba.com "Don't give to get. Just give."

Feb. 15, 2011

[Pharo-project] RPackage images

by Torsten Bergmann

>> Is there any documentation available on RPackage already? >> Or a help book? > >There is some comments in the classes RPackage and RPackageOrganizer. OK, and now there is also a help book ;) One can try the package stuff and read the docu using: ------------------------------------------------------------------- Gofer new squeaksource: 'PharoTaskForces'; package: 'ConfigurationOfRPackage'; load. ((Smalltalk at: #ConfigurationOfRPackage) project version: 'default') load. HelpBrowser open ------------------------------------------------------------------- BTW: I still wonder why the classes are called RPackage and RPackageOrganizer instead of "Package" and "PackageOrganizer". Keep on talking small T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Feb. 15, 2011

Re: [Pharo-project] [COTDC] 11 - ColorMappingCanvas

by Henrik Johansen

On Feb 14, 2011, at 8:51 50PM, laurent laffont wrote: > On Mon, Feb 14, 2011 at 7:57 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 14 February 2011 18:45, laurent laffont <laurent.laffont(a)gmail.com> wrote: > > Today: ColorMappingCanvas > > > > As far as i understood, this class is abstract, and its subclasses > implement more specific behavior > - shadow > - semitransparency mapping > > > The idea of is kind of canvas is to modify/filter the final output in > rendering pipe.. > i.e., for each potential pixel operation like: > > source -> op -> output > > it introducing a color mapping stage: > > source -> op -> mapping -> output > > > So, then for instance you could make a subclass which could turn all > colors to be grayscale (disregarding that initial input was in > colors). > > in fact i think this guy took wrong direction. It is much more > effective to let the canvas to draw whatever it wants to some > backup/temporary surface, and once it done, simply blit + color-map > result to destination form using one, single strike. > > > ah ah, it seems last COTDC are: > - this class is bad written > - this is not used > - nobody understand > > still lot of work ;) > > Laurent ShadowCanvas is used in the Glamour theme when fastDragForMorphic is disabled. Cheers, Henry PS. You'll see a noticable increase in dragging performance (at least on non-Cog vms)if you change configureWindowBorderFor: to return a non-translucent value. This is because wantsToBeCachedByHand returns false when the morph isTranslucent. I don't really think the restriction makes much sense, a canvas should have no problem drawing a cached image with translucency, but changing it probably includes revisiting how paint rules are chosen, which will be a huge pain for whoever does it.

Feb. 15, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #69 on issue 3583 by tudor.gi...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 In the workspace variables are bound implicitly, and this should be taken into account during highlighting. So, after evaluating a:=1, a will be bound and it should appear as such without declaring it.

Feb. 15, 2011

Re: [Pharo-project] RPackage images

by Cyrille Delaunay

There is some comments in the classes RPackage and RPackageOrganizer. To load RPackage manually, there is a ConfigurationOfRPackage in www.squeaksource.com/PharoTaskForces 2011/2/15 Torsten Bergmann <astares(a)gmx.de> > Is there any documentation available on RPackage already? > Or a help book? > -- > Schon gehÃ¶rt? GMX hat einen genialen Phishing-Filter in die > Toolbar eingebaut! http://www.gmx.net/de/go/toolbar > >

Feb. 15, 2011