- Pharo-dev - lists.pharo.org

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

by Philippe Marschall

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] font reading problems

by Esteban Lorenzano

Hi, On Apr 8, 2012, at 9:43 PM, Guillermo Polito wrote: > I like monospace fonts mostly for programming... > > Courier new? courier sucks :P > DejaVu sans mono? +1 > > On Sun, Apr 8, 2012 at 9:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> 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 >

April 8, 2012

Re: [Pharo-project] font reading problems

by Guillermo Polito

I like monospace fonts mostly for programming... Courier new? DejaVu sans mono? On Sun, Apr 8, 2012 at 9:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>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 >

April 8, 2012

[Pharo-project] font reading problems

by StÃ©phane Ducasse

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

April 8, 2012

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

by StÃ©phane Ducasse

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 8, 2012

Re: [Pharo-project] Invalid socket handle in Zinc Server after image startup

by Mark Smith

Great :). I hope you succeed in coaxing Sven to write a chapter. The more written down the better :). Mark. On 8 Apr 2012, at 17:48, StÃ©phane Ducasse wrote: > I'm trying to make sven write a chapter :) > So I added it to the server section :) > > Stef > >> Hi Sven, >> >> That makes a lot of sense :). >> >> Perhaps this could be added to the Getting Started section of the website? >> >> Thanks! >> >> Mark >> >> On 8 Apr 2012, at 17:11, Sven Van Caekenberghe wrote: >> >>> Mark, >>> >>> On 08 Apr 2012, at 16:11, Mark Smith wrote: >>> >>>> Hi all, >>>> >>>> Is anyone else having problems with Zinc servers not starting up correctly when the image is loaded? >>>> >>>> After the image starts up the server has an invalid socket handle. >>>> >>>> To reproduce, evaluate the following in a workspace, then save and quit the image. >>>> >>>> aServer := ZnServer on: 8080. >>>> aServer delegate: ((ZnMonticelloServerDelegate new) >>>> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >>>> aServer start >>>> >>>> Any ideas? >>>> >>>> Mark >>> >>> Only the default server (ZnServer default) is sent #register on #start so that it will be sent #start/#stop on System #startUp/#shutDown. >>> Have a look at ZnSingleThreadedServer>>#start and/or follow ZnServer>>#register. >>> >>> To make this work, either change your example to >>> >>> aServer := ZnServer defaultOn: 8080. >>> aServer delegate: ((ZnMonticelloServerDelegate new) >>> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >>> aServer start >>> >>> or to >>> >>> aServer := ZnServer on: 8080. >>> aServer delegate: ((ZnMonticelloServerDelegate new) >>> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >>> aServer register. >>> aServer start >>> >>> It is by design that not every server is registered (as not everyone needs this behavior). >>> The default server is an exception because it is used for first time and more casual usage and many people expect this behavior in Smalltalk. >>> >>> HTH, >>> >>> Sven >>> >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill >>> >> >> > >

April 8, 2012

Re: [Pharo-project] Invalid socket handle in Zinc Server after image startup

by StÃ©phane Ducasse

I'm trying to make sven write a chapter :) So I added it to the server section :) Stef > Hi Sven, > > That makes a lot of sense :). > > Perhaps this could be added to the Getting Started section of the website? > > Thanks! > > Mark > > On 8 Apr 2012, at 17:11, Sven Van Caekenberghe wrote: > >> Mark, >> >> On 08 Apr 2012, at 16:11, Mark Smith wrote: >> >>> Hi all, >>> >>> Is anyone else having problems with Zinc servers not starting up correctly when the image is loaded? >>> >>> After the image starts up the server has an invalid socket handle. >>> >>> To reproduce, evaluate the following in a workspace, then save and quit the image. >>> >>> aServer := ZnServer on: 8080. >>> aServer delegate: ((ZnMonticelloServerDelegate new) >>> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >>> aServer start >>> >>> Any ideas? >>> >>> Mark >> >> Only the default server (ZnServer default) is sent #register on #start so that it will be sent #start/#stop on System #startUp/#shutDown. >> Have a look at ZnSingleThreadedServer>>#start and/or follow ZnServer>>#register. >> >> To make this work, either change your example to >> >> aServer := ZnServer defaultOn: 8080. >> aServer delegate: ((ZnMonticelloServerDelegate new) >> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >> aServer start >> >> or to >> >> aServer := ZnServer on: 8080. >> aServer delegate: ((ZnMonticelloServerDelegate new) >> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >> aServer register. >> aServer start >> >> It is by design that not every server is registered (as not everyone needs this behavior). >> The default server is an exception because it is used for first time and more casual usage and many people expect this behavior in Smalltalk. >> >> HTH, >> >> Sven >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> > >

April 8, 2012

[Pharo-project] Milestone reached :-)

by Pavel Krivanek

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

April 8, 2012

Re: [Pharo-project] Invalid socket handle in Zinc Server after image startup

by Mark Smith

Hi Sven, That makes a lot of sense :). Perhaps this could be added to the Getting Started section of the website? Thanks! Mark On 8 Apr 2012, at 17:11, Sven Van Caekenberghe wrote: > Mark, > > On 08 Apr 2012, at 16:11, Mark Smith wrote: > >> Hi all, >> >> Is anyone else having problems with Zinc servers not starting up correctly when the image is loaded? >> >> After the image starts up the server has an invalid socket handle. >> >> To reproduce, evaluate the following in a workspace, then save and quit the image. >> >> aServer := ZnServer on: 8080. >> aServer delegate: ((ZnMonticelloServerDelegate new) >> directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). >> aServer start >> >> Any ideas? >> >> Mark > > Only the default server (ZnServer default) is sent #register on #start so that it will be sent #start/#stop on System #startUp/#shutDown. > Have a look at ZnSingleThreadedServer>>#start and/or follow ZnServer>>#register. > > To make this work, either change your example to > > aServer := ZnServer defaultOn: 8080. > aServer delegate: ((ZnMonticelloServerDelegate new) > directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). > aServer start > > or to > > aServer := ZnServer on: 8080. > aServer delegate: ((ZnMonticelloServerDelegate new) > directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). > aServer register. > aServer start > > It is by design that not every server is registered (as not everyone needs this behavior). > The default server is an exception because it is used for first time and more casual usage and many people expect this behavior in Smalltalk. > > HTH, > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill >

April 8, 2012

Re: [Pharo-project] Invalid socket handle in Zinc Server after image startup

by Sven Van Caekenberghe

Mark, On 08 Apr 2012, at 16:11, Mark Smith wrote: > Hi all, > > Is anyone else having problems with Zinc servers not starting up correctly when the image is loaded? > > After the image starts up the server has an invalid socket handle. > > To reproduce, evaluate the following in a workspace, then save and quit the image. > > aServer := ZnServer on: 8080. > aServer delegate: ((ZnMonticelloServerDelegate new) > directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). > aServer start > > Any ideas? > > Mark Only the default server (ZnServer default) is sent #register on #start so that it will be sent #start/#stop on System #startUp/#shutDown. Have a look at ZnSingleThreadedServer>>#start and/or follow ZnServer>>#register. To make this work, either change your example to aServer := ZnServer defaultOn: 8080. aServer delegate: ((ZnMonticelloServerDelegate new) directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). aServer start or to aServer := ZnServer on: 8080. aServer delegate: ((ZnMonticelloServerDelegate new) directory: (FileDirectory on: '/Users/sven/Tmp/monticello')). aServer register. aServer start It is by design that not every server is registered (as not everyone needs this behavior). The default server is an exception because it is used for first time and more casual usage and many people expect this behavior in Smalltalk. HTH, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

April 8, 2012