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

Re: [Pharo-project] Open another image with Pharo 1.1.1 one-click on Mac OS

by Sven Van Caekenberghe

On 16 Feb 2011, at 19:34, Dennis Schetinin wrote: > I found an association > > <key>SqueakImageName</key> > <string>Pharo.image</string> > > in Info.plist file inside Pharo.app bundle and replaced it with > > <key>SqueakImagePath</key> > <string>/Applications/Pharo.app/Contents/Resources</string> > > (See http://www.smalltalkconsulting.com/html/squeakinfoplist.html for a list of available options) > > Now Pharo asks for image file but still using ~/Documents in the Open File dialog. I don't know if it is possible to open an image from inside the Pharo.app. The one-click image is more for (absolute) beginners and casual users. Once you really get started with Smalltalk, you should learn and become comfortable with the four key elements needed: image file changes file vm sources file Most users will have many images/changes files and multiple VMs, so you most often will have to make a choice, right-clicking on an image file and doing an Open with.. using the right VM is what I do. Sven

Feb. 16, 2011

Re: [Pharo-project] Open another image with Pharo 1.1.1 one-click on Mac OS

by Sven Van Caekenberghe

On 16 Feb 2011, at 16:39, Dennis Schetinin wrote: > Is it possible to setup a one-click Pharo.app to ask which image to open at startup? It saves images inside Pharo.app package which is great, but how to open them? > > TIA > > -- > Dennis Schetinin Dennis, Select the Pharo.app icon in the Finder, right-click to open the menu, select 'Show Package Contents', in there you will find the image and changes files and much more. Sven

Feb. 16, 2011

Re: [Pharo-project] [Moose-dev] Problem loading JNIPort

by Tudor Girba

Hi Cyrille, Did you manage to get JNIPort working on Pharo 1.2? Cheers, Doru On 14 Feb 2011, at 12:16, Tudor Girba wrote: > Hi Matthias, > > Thanks for reporting. I forwarded the message to the Pharo mailing list as well. > > Can anyone help? > > Cheers, > Doru > > > On 14 Feb 2011, at 12:10, Matthias Junker wrote: > >> Hi, >> >> i was trying to load JNIPort as described on squeaksource on my Macbook (OS X 10.6.6). I downloaded the latest Pharo 1.2 from Hudson (https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/) and opened it using SqueakVM 5.8b12. I was able to load Alien using the following command: >> >> Gofer it >> squeaksource:'MetacelloRepository' ; >> package: 'ConfigurationOfAlien'; >> load. >> >> ((Smalltalk globals classNamed: 'ConfigurationOfAlien') >> project version: 'Pharo 1.2') >> load: 'Core'; load: 'LibC >> >> Then i loaded the JNIPort Configuration: >> Gofer it >> squeaksource: 'JNIPort'; >> package: 'ConfigurationOfJNIPort'; >> load. >> >> But when i load the actual project with this: >> ConfigurationOfJNIPort project latestVersion load >> I get the following error in the class StandardLibInterface(AlienLibrary)>>load >> libraryName: '/System/Library/Frameworks/System.framework/System' >> errorCode: #'not found' >> >> When i check on the file system i find a symbolic link which points to /usr/lib/libSystem.B.dylib (which also exists there). >> >> Any hints to what i'm doing wrong? >> >> Cheers, >> Matt >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > -- www.tudorgirba.com "When people care, great things can happen."

Feb. 16, 2011

Re: [Pharo-project] Open another image with Pharo 1.1.1 one-click on Mac OS

by Dennis Schetinin

I found an association <key>SqueakImageName</key> <string>Pharo.image</string> in *Info.plist* file inside Pharo.app bundle and replaced it with <key>SqueakImagePath</key> <string>/Applications/Pharo.app/Contents/Resources</string> (See http://www.smalltalkconsulting.com/html/squeakinfoplist.html for a list of available options) Now Pharo asks for image file but still using ~/Documents in the Open File dialog. I don't know if it is possible to open an image from inside the Pharo.app. 2011/2/16 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> > On Linux, I simply edit the shell script to use the image of interest. I > don't know enough about macs to figure out whether "launch xyz.app" is using > the shell script or doing something completely different. Anybody? > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [ > pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Dennis Schetinin > [chaetal(a)gmail.com] > Sent: Wednesday, February 16, 2011 10:39 AM > To: Pharo-project > Subject: [Pharo-project] Open another image with Pharo 1.1.1 one-click on > Mac OS > > Is it possible to setup a one-click Pharo.app to ask which image to open at > startup? It saves images inside Pharo.app package which is great, but how > to open them? > > TIA > > -- > Dennis Schetinin > > -- Dennis Schetinin

Feb. 16, 2011

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

by Miguel CobÃ¡

Ok, I understand the goal. Count me in. El miÃ©, 16-02-2011 a las 13:52 +0100, StÃ©phane Ducasse escribiÃ³: > On Feb 16, 2011, at 12:59 PM, Schwab,Wilhelm K wrote: > > > Stef, > > > > The revised language is much improved. > > tx > > > I too am curious about what you have in mind on the conditions. > > We do not know. :) just fuzzy ideas. > We will decide with the community. Because the point is that this is not our stuff but a tool that should serve the community. > We were thinking > - individual memberships > - company memberships > - institution memberships > or/and a moral license so that you can buy pharo and a guy like igor/esteban can get pay to improve the infrastructure. > or a bounty (but a moral license is good since it does not bind the task). > > > > Are you looking for support from institutions or individuals? I assume both, but the thresholds would be different for UF than for me by myself. > > Yes both. This would be excellent. > > Recently I was asking myself three essential questions beside having a market: ok we have a client so what > - how do you control quality/process? > - how do you control that your runtime engine is ok/safe/longlasting (else better take java vms there are plenty) > - how do you reduce risk like truck factor in your community. > > Our main point is how can we minimize risk: I'm thinking to participate to a startup around a pharo software and here is a simple > simple scenario: imagine that eliot gets hired by XXAS to do javascript/ruby whatever and andreas (which does not reply to my mails > because I'm probably too insignificant) goes waco and that ian only shows up every three years instead of every year. > do you think that it is wise for companies to invest in an open-source smalltalk? > I would not. Now if we have a consortium, a build process, a quality process and one or two guys payed by the community > to improve continously the system more than we can. Then this is a message I can understand as an investor. > > Since we want to make sure that you all can do business we want to reduce risk and provide a good case for process, quality and the > rest. > > > Stef > > > > > > > Bill > > > > > > > > ________________________________________ > > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > > Sent: Wednesday, February 16, 2011 5:00 AM > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] Call for Pharo Support **important** > > > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Feb. 16, 2011

[Pharo-project] Issue 3720 in pharo: searching all source code: Comment Reference>>#asNode DNU

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2 New issue 3720 by marcus.d...(a)gmail.com: searching all source code: Comment Reference>>#asNode DNU http://code.google.com/p/pharo/issues/detail?id=3720 In 1.2 buid #141 do a search in all source for "caseOf:" --> DNU in CommentReference

Feb. 16, 2011

Re: [Pharo-project] Issue 3718 in pharo: Color class>>wheel: should be (back) on class side

by pharo＠googlecode.com

Comment #1 on issue 3718 by jbth...(a)gmail.com: Color class>>wheel: should be (back) on class side http://code.google.com/p/pharo/issues/detail?id=3718 UPDATE: Actually, it looks like there were *3* versions of wheel:, across both class and instance side: Color>>wheel: thisMany Color class>>wheel: thisMany Color class>>wheel: thisMany saturation: s brightness: v In 1.2rc2, only the first one is present, which returns a wheel starting from that color. The class versions return a wheel starting from hue 0. I consider the class-side versions conceptually distinct (ie. the Canonical Color Wheel) and valuable in themselves, but since they all go through the instance-side method, I can also see the argument for keeping only that method (in the interest of minimalism?). Squeak 4.1 still has all 3 methods. The Pharo code that is doing (Color new wheel:), looks like a "canonical" usage. In any case, if collapsing to 1 method, all the senders need to be cleaned up to consistently message the instance, and the test comment at the bottom fixed. For documentation, I note here the canonical Color class>>wheel: was effectively (Color h:0.0 s:0.9 v:0.7) wheel:

Feb. 16, 2011

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

by Igor Stasenko

On 16 February 2011 18:15, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Tue, Feb 15, 2011 at 11:50 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> Eliot a final question. >> So how will you handle OPAL compiler change in Cog? >> Do you require that marcus and jorge have to deal with decompiler of >> caseOf: in addition to all the rest? >> Is it a strong requirement? Because then this is clear that Opal will be >> delayed. But may be it is not that important after all. >> Just curious. > > OPAL is a Smalltalk compiler. Â I can therefore assume that it will compile > Smalltalk. Â caseOf: is valid Smalltalk and so will be compiled by OPAL. > Â Whether Marcus chooses to optimise caseOf: or not is up to him. And this was the question from the beginning of this thread :) Except that not all realized that Stef were talking about new compiler (Opal), not existing one. I am perfectly fine with current state of Compiler.. and it is really not worth adding/removing something from it, because in Pharo plans to integrate new compiler infrastructure. So, it is obvious that any work on old compiler is a waste of time and energy. >> >> Stef >> (if you think that I focus on details then I'm certainly an idiot). >> >> > > -- Best regards, Igor Stasenko AKA sig.

Feb. 16, 2011

Re: [Pharo-project] [COTDC] 13 - NullEncoder

by Igor Stasenko

On 16 February 2011 18:21, laurent laffont <laurent.laffont(a)gmail.com> wrote: > On Wed, Feb 16, 2011 at 6:02 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 16 February 2011 17:46, laurent laffont <laurent.laffont(a)gmail.com> >> wrote: >> > Today: Â NullEncoder >> > >> >> I am a Canvas superclass with completely misleading name and purpose. > > > yep. And not referenced. Should be merged with Canvas ? You kidding? If not, then give me an answer, what canvas should do for these messages: canvas contents canvas writeDictionary: dict canvas cr canvas process: someObject ? :) And what is the canvas'es target ivar? what it suppose to represent? > Laurent. > >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > -- Best regards, Igor Stasenko AKA sig.

Feb. 16, 2011

Re: [Pharo-project] [Metacello] Metacello tests failing in 1.2

by Dale Henrichs

On 02/15/2011 05:46 PM, Guillermo Polito wrote: > Hi Dale! > > There are 13 failing tests on the 1.2 dev build since a week ago ( > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/141/testReport/ > ). Do we have the right version? Do you have any clue so I don't dive > in the code blindly? :) > > Cheers, > Guille I didn't know that there were test failures until today ... I guess I'll see what I can figure out ... Dale

Feb. 16, 2011