- Pharo-dev - lists.pharo.org

[Pharo-project] 1.4 ready?

by Pavel Krivanek

Hi, as I see on http://code.google.com/p/pharo/issues/list?can=2&q=label%3AMilestone-1.4, there are only three open issues for 1.4. Two of them are ready to integrate and one needs only CI configuration. Are we ready to release? Cheers, -- Pavel

April 9, 2012

[Pharo-project] about cmd+b, cmd-n

by StÃ©phane Ducasse

Hi A while ago I added the fact that cmd+b on a selector behave as cmd+m cmd+m on a class behave as cmd+b cmd+N on a selector as cmd+n cmd+n on a class as cmd+N but we lost this cool change probably with the new text editor. Could somebody have a look because it was a cool and simple usability improvement. http://code.google.com/p/pharo/issues/detail?id=5588 Stef

April 9, 2012

Re: [Pharo-project] Milestone reached :-)

by Pavel Krivanek

Hi Martin, It's interesting idea - to have separate Fuel packages for serialization and materialization (and probably some common base). Currently it is not the most important task to do (we need to clean the residues of the Compiler in the image etc.) but I like it :-) -- Pavel On Mon, Apr 9, 2012 at 6:21 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > Nice! > I guess fuel needs for materialization only 50% of its methods and 2/3 of > its classes.Â In a future I can work on that if you think it's worthwhile. > > MartÃn > > On Sun, Apr 8, 2012 at 1:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: >> >> Simply gorgeous! >> >> On Apr 8, 2012, at 6:23 PM, Pavel Krivanek wrote: >> >> > Hi, >> > >> > I created an experimental CI build that loads Fuel into the Pharo >> > Kernel, unloads Compiler and uses an special launcher that expects a >> > binary package name as command line argument. >> > >> > >> > https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Fuel/ >> > >> > You can test it with something like (see attachment): >> > >> > CogVM PharoKernel-Fuel-1.4.image testingPackage.fuel >> > >> > Following code exports a fuel binary package from the image: >> > >> > FileStream forceNewFileNamed: 'testingPackage.fuel' do: [:aStream | >> > Â Â Â aStream binary. >> > Â Â Â FLPackageStore new storeOn: aStream packageNamed: >> > 'TestingPackage'.]. >> > >> > As you can see from the output of the testing class, there is no >> > Compiler class in the image. >> > >> > Cheers, >> > -- Pavel >> > <testingClassOutput.txt><TestingPackage.st><testingPackage.fuel> >> >> >

April 9, 2012

Re: [Pharo-project] SMark

by Martin Dias

Hi Stefan, thank you very much. I think it'll be useful for Fuel. Keep you posted! Best regards MartÃn On Thu, Apr 5, 2012 at 5:28 PM, Stefan Marr <smalltalk(a)stefan-marr.de>wrote: > Hi Martin: > > On 04 Apr 2012, at 09:57, Stefan Marr wrote: > > > Hi Martin: > > > > On 03 Apr 2012, at 21:50, Martin Dias wrote: > > > >> I like SMark, so I am evaluating how straightforward would be to move > Fuel benchmark suite. A couple of questions: > >> > >> 1) I had some undeclared references, no problem? > >> HeadlessSave class>>run: (RVMOperations is Undeclared) > >> ScriptStarter class>>transportersForFileOutMenu (Transporter is > Undeclared) > > > > I fixed these warnings and fixed a couple of minor issues, like missing > initialization and use of deprecated stuff on Pharo 1.4. > > The configuration loads now without issues into Pharo 1.3, Pharo 1.4, and > Squeak 4.3. > > There are two failing tests, but these are expected failures ;) > > Let me know if you have any other problems. > > Thanks > Stefan > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

April 9, 2012

Re: [Pharo-project] Milestone reached :-)

by Martin Dias

Nice! I guess fuel needs for materialization only 50% of its methods and 2/3 of its classes. In a future I can work on that if you think it's worthwhile. MartÃn On Sun, Apr 8, 2012 at 1:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Simply gorgeous! > > On Apr 8, 2012, at 6:23 PM, Pavel Krivanek wrote: > > > Hi, > > > > I created an experimental CI build that loads Fuel into the Pharo > > Kernel, unloads Compiler and uses an special launcher that expects a > > binary package name as command line argument. > > > > > https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Fuel/ > > > > You can test it with something like (see attachment): > > > > CogVM PharoKernel-Fuel-1.4.image testingPackage.fuel > > > > Following code exports a fuel binary package from the image: > > > > FileStream forceNewFileNamed: 'testingPackage.fuel' do: [:aStream | > > aStream binary. > > FLPackageStore new storeOn: aStream packageNamed: > 'TestingPackage'.]. > > > > As you can see from the output of the testing class, there is no > > Compiler class in the image. > > > > Cheers, > > -- Pavel > > <testingClassOutput.txt><TestingPackage.st><testingPackage.fuel> > > >

April 9, 2012

Re: [Pharo-project] font reading problems

by Ben Coman

StÃ©phane Ducasse wrote: > Hi guys > > I do not like the default font because there is not enough space around : > so this is difficult to see it for example in > > := > ------------------------------------------------------------------------ > > > > > so what can be done? > Can we modify this font? > > Stef As well, it is hard to see the period at the end of statement - particularly following a closing square bracket.

April 9, 2012

Re: [Pharo-project] Recover from an MNU in start up list?

by Craig Latta

> One way is in gdb put a breakpoint in the MNU processing > (createActualMessage). Or do it from the VM simulator. If you can't get it work, I'll take a stab at it. good luck, -C -- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468

April 9, 2012

[Pharo-project] Using stdout in Windows --> 'File stdout is closed'

by Martin Dias

Hi In my windows 7, I get an error when trying to write to "FileStream stdout" in both Pharo 1.4 and 1.3 (revisions #14423 and #13320). To reproduce, - download: https://ci.lille.inria.fr/pharo/job/Pharo%201.4/373/artifact/Pharo-1.4.zip - evaluate: FileStream stdout nextPutAll: 'a'. Is this a known issue? I couldn't find it in issue tracker. Thanks in advance. MartÃn

April 8, 2012

Re: [Pharo-project] Recover from an MNU in start up list?

by Max Leske

For 1.3 see http://code.google.com/p/pharo/issues/detail?can=2&start=0&num=100&q=&colsp… For 1.4 I don't know. Max PS: Still working on a working fixâ¦ sorry for the delay but I'm trying to be thorough On 08.04.2012, at 23:26, Philippe Marschall wrote: > Hi > > I extracted a superclass and now I get a MNU during image startup because I have an instance of the now abstract base class in the start up list. > > The image comes up for a fraction of a second and the crashes (PharoDebug.log). Any idea of how I can recover from this? > > Cheers > Philippe > >

April 8, 2012

Re: [Pharo-project] Recover from an MNU in start up list?

by Eliot Miranda

On Sun, Apr 8, 2012 at 2:26 PM, Philippe Marschall <kustos(a)gmx.net> wrote: > Hi > > I extracted a superclass and now I get a MNU during image startup because > I have an instance of the now abstract base class in the start up list. > > The image comes up for a fraction of a second and the crashes > (PharoDebug.log). Any idea of how I can recover from this? > One way is in gdb put a breakpoint in the MNU processing (createActualMessage). Then when you hit the MNU edit the message object to something harmless such as Message selector: #class arguments: #(), and proceed. This isn't easy. You have to learn how to find symbols in the VM (you'll need to find eg. #class) and how to store pointers in an object. So only consider doing this if the image is worth a few hours learning arcane VM innards, and possibly building a debug VM that'll be less fragile in gdb. > Cheers > Philippe > > > -- best, Eliot

April 8, 2012