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

Re: [Pharo-project] RPackage images

by StÃ©phane Ducasse

Thanks cyrille I think that we should finish 1.2 and release it and after I will focus on RPackage integration. On Feb 15, 2011, at 10:38 AM, Cyrille Delaunay wrote: > We have now an hudson job that build images with RPackage integrated and that run all the tests in the image: > > https://pharo-ic.lille.inria.fr/hudson/view/Pharo-TaskForces/job/Pharo%20RP… > > Feel free to use it and report any problem. > See also: > > http://code.google.com/p/pharo/issues/detail?id=3609&q=RPackage&colspec=ID%…

Feb. 15, 2011

[Pharo-project] Issue 3705 in pharo: UI Enhancements

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com Labels: Fixed Milestone-1.3 New issue 3705 by stephane...(a)gmail.com: UI Enhancements http://code.google.com/p/pharo/issues/detail?id=3705 Fixup window pane colours wrt faded background windows. (factored over to UITheme). Fix for hotspot of eydropper cursor when picking colour from screen in ColorSelectorDialogWindow,

Feb. 15, 2011

Re: [Pharo-project] UI fixes for the day...

by StÃ©phane Ducasse

thanks Gary It will be integrated in 1.3. Stef On Feb 15, 2011, at 2:15 PM, Gary Chambers wrote: > Attached cs files for: > > Fixup window pane colours wrt faded background windows. (factored over to UITheme). > > Fix for hotspot of eydropper cursor when picking colour from screen in ColorSelectorDialogWindow, > > Regards, Gary > <ColorSelectorHotspotFix.1.cs><PaneColorFixes.1.cs>

Feb. 15, 2011

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

by StÃ©phane Ducasse

>>> 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. ? Apparently igor is just saying the contrary. You probably say no for the second point. I can understand that when we want to generate switch in C this is better to have that at the AST level. Now I do not see why this would be needed to inline it. >> VMMaker is used in many images, not just Pharo. And #caseOf: >> is used in packages other than VMMaker. Do you have a list? >> 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. Yes this is what I will do. I will keep that name and put a big warning. > ;-P > > You don't need to remove #caseOf: implementation. I can stay. Well yes we can always turn around. Now in my house I regularly empty my garbage can. > 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. Good to know that. We should rewrite all the users of caseOf: in Pharo and add a lint rule checking them and one day we will remove it. Because we cannot drag all these stuffs forever. Stef

Feb. 15, 2011

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

by Adrian Lienhard

BTW, the call is also online at http://pharo-project.org/community/consortium Adrian On Feb 15, 2011, at 14:02 , StÃ©phane Ducasse wrote: > 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 > > > <Pharo-LetterOfSupport-EN.doc>

Feb. 15, 2011

[Pharo-project] OB questiÃ³n

by Diogenes Moreira

Is there a short cut to remove all searchs...?? Best.

Feb. 15, 2011

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

by pharo＠googlecode.com

Comment #73 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 A little sum up :) From a 1.2 Dev image 12335: - FixWorkspaceAgain.1 - FixSHWorkspace.1 - FixWorkspace1.2.1 - PrepareFixWorkspaceMenu.2 - FixWorkspaceMenu.1 - FixSHWorkspaceToFixMenu.1 From a 1.3 Core image 13055: - FixWorkspaceAgain.1 - FixWorkspace1.3.1 - PrepareFixWorkspaceMenu.2 - FixWorkspaceMenu.1

Feb. 15, 2011

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

by pharo＠googlecode.com

Comment #72 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 Some cs about refactorisation, and reactivating the style/unstyle item in the menu: For 1.2 and 1.3: - PrepareFixWorkspaceMenu.2 - FixWorkspaceMenu.1 For 1.2 Dev (to fix SHWorkspace): - FixSHWorkspaceToFixMenu.1 Attachments: PrepareFixWorkspaceMenu.2.cs 1.0 KB FixWorkspaceMenu.1.cs 10.0 KB FixSHWorkspaceToFixMenu.1.cs 349 bytes

Feb. 15, 2011

[Pharo-project] UI fixes for the day...

by Gary Chambers

Attached cs files for: Fixup window pane colours wrt faded background windows. (factored over to UITheme). Fix for hotspot of eydropper cursor when picking colour from screen in ColorSelectorDialogWindow, Regards, Gary

Feb. 15, 2011

[Pharo-project] RPackage images

by Torsten Bergmann

>> BTW: I still wonder why the classes are called RPackage and >>RPackageOrganizer instead of "Package" and "PackageOrganizer". > >Because of name clashes. Ah ... I see. It clashes with classes in category "PackageInfo-Base". I just looked if there is a class Package, but there is none. But PackageOrganizer is already taken. Since there is SystemOrganizer, ClassOrganizer I think it would later have a clean PackageOrganizer Maybe in 1.3. the existing PackageOrganizer from "PackageInfo-Base" should be renamed already to prepare RPackage integration... Bye T. -- Schon gehÃ¶rt? GMX hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://www.gmx.net/de/go/toolbar

Feb. 15, 2011