May 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Which fonts for Pharo 1.1 ?

by Richard Durr

I'd strongly argue to have true type fonts: * when you try to make something look good, you don't impair the ability to use fonts On Tue, May 11, 2010 at 10:55 AM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On May 11, 2010, at 10:37 16AM, StÃ©phane Ducasse wrote: > >> may be we should write that on the book henrik would like to write some paragraph on fonts for dummies like us. >> >> Stef > > I would need an account first then :) > > Cheers, > Henry > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 12, 2010

Re: [Pharo-project] VMs for Pharo 1.1

by Richard Durr

So does anybody know about the status of CogVM? ^^ On Tue, May 11, 2010 at 8:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > excellent! > > Stef > > On May 11, 2010, at 6:52 PM, John M McIntosh wrote: > >> >> On 2010-05-10, at 11:16 PM, laurent laffont wrote: >> >>> >>> Mac: John, I am not sure which VM we should use for Pharo 1.1. Can you give us a hint ? Â known problems ? does it include freetype ? >> >> >> Let me build and upload a 32bit bias macintosh V5.x VM for people to try later today, since I'd suggest that should be used. >> >> >> >> =========================================================================== >> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Â Twitter: Â squeaker68882 >> Corporate Smalltalk Consulting Ltd. Â http://www.smalltalkconsulting.com >> =========================================================================== >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 12, 2010

Re: [Pharo-project] I would like to kill some tests

by Alexandre Bergel

>> What is the important is the metaclass relationship, and not really the fact that Dictionary is a subclass of Set. >> I think this is better: >> self assert: Dictionary class superclass == Dictionary superclass class. >> self assert: OrderedCollection class superclass == OrderedCollection superclass class. > > ok > but do you think that the system would work if such test would not work? I understand that the point of the original test is to document how metaclasses and superclasses are linked. System like metaclasstalk have demonstrated that this link is not necessary to make a system work. Alexandre

May 12, 2010

[Pharo-project] Issue 2418 and fix in inbox

by Mariano Martinez Peck

http://code.google.com/p/pharo/issues/detail?id=2418 Fix is in inbox: Name: System-Tools-MarianoMartinezPeck.30 Author: MarianoMartinezPeck Time: 12 May 2010, 12:22:36 pm UUID: 4785af6c-1ebe-487d-af22-2640e763e9f5 Ancestors: System-Tools-StephaneDucasse.29 Fix to issue 2418 <http://code.google.com/p/pharo/issues/detail?id=2418>: Now MethodContext can be taken into account in SpaceTally as MethodContext allInstancesDo: is working again.

May 12, 2010

[Pharo-project] Issue 2124

by Luc Fabresse

SLICE-BadCharactersInPackagenames-fix2124-LucFabresse.1 fix 2124 : add a TestCase ensuring that existing package name do not contain \ / : * ? " < > | Another fix should prevent the creation of package names with bad characters Luc

May 12, 2010

[Pharo-project] [update 1.1] #11355

by Marcus Denker

11355 ----- Issue 2417: SystemNavigation allReferencesTo: is bogus Issue 2416: clean up MC packalges -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 12, 2010

[Pharo-project] [update 1.1] #11354

by StÃ©phane Ducasse

11354 ----- - Issue 2414: testMetaclassSupperclass - Issue 2415: wrong subclass in Association

May 12, 2010

Re: [Pharo-project] [Vm-dev] [ANN] DTrace for Squeak/Pharo

by Adrian Lienhard

Hi John, DTrace on my unix VM thinks it does not know ioShowDisplayOnWindow (I guess because I use X11 display). With a Mac VM I it works. To trace ioShowDisplayOnWindow you don't need a dedicated probe (and hence no specialized VM). The DTrace "pid" provider allows you to trace any function entry (and return): pid$target::ioShowDisplayOnWindow:entry { printf("%s'%s\n", probemod, probefunc); } Cheers, Adrian On May 11, 2010, at 19:03 , John M McIntosh wrote: > Ah, nice, yes very nice. > > One interesting one to have a probe for would be ioShowDisplayOnWindow so one can understand how much screen drawing goes on. > > On 2010-05-11, at 12:13 AM, Adrian Lienhard wrote: > >> >> Now there's also a DTrace provider for the Squeak VM: >> >> http://www.adrian-lienhard.ch/blog?dialog=smalltak-meets-dtrace >> >> DTrace is a powerful, kernel-based dynamic tracing framework. With the new provider one can analyze the execution of Pharo/Squeak applications. >> >> My post is an introduction that should get you quickly started. I've attached a pre-compiled VM for OS X. >> >> Hope you like it :) >> >> Cheers, >> Adrian >> ___________________ >> http://www.adrian-lienhard.ch/ >> > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > >

May 12, 2010

Re: [Pharo-project] I would like to kill some tests

by Igor Stasenko

On 11 May 2010 23:39, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On May 11, 2010, at 9:34 PM, Alexandre Bergel wrote: > >>> testMetaclassSuperclass >>> Â Â Â "self run: #testMetaclassSuperclass" >>> >>> Â Â Â self assert: Dictionary class superclass == Set class. >>> Â Â Â self assert: OrderedCollection class superclass == SequenceableCollection class. >> >> What is the important is the metaclass relationship, and not really the fact that Dictionary is a subclass of Set. >> I think this is better: >> Â Â Â self assert: Dictionary class superclass == Dictionary superclass class. >> Â Â Â self assert: OrderedCollection class superclass == OrderedCollection superclass class. > > ok > but do you think that the system would work if such test would not work? > I dont quite understand, what this test testing. Yes, in ST-80, a class inheritance chain and metaclass inheritance chain must go in parallel. But there's nothing in VM (to my knowledge), which prevents you from sidestepping from this convention. This means, that a system may work even if such test will fail. I made my own experiments with it , by creating a prototype-based framework , and along with existing prototypes implementation, it serves as a proof, that its not critical for a system to organize your behaviors strictly only in such way(s). > >>> I would rewrite the test as: >> >> testSuperclass >> Â Â Â "self debug: #testSuperclass" >> >> Â Â Â | s b | >> >> Â Â Â s := OrderedCollection new. >> Â Â Â b := [:cls | cls ifNotNil: [s add: cls. b value: cls superclass] ]. >> Â Â Â b value: OrderedCollection. >> >> Â Â Â self assert: OrderedCollection allSuperclasses = s allButFirst. >> Â Â Â self assert: OrderedCollection withAllSuperclasses = s. >> >> You even test #withAllSuperclasses in that case. > > this one is more interesting > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

May 12, 2010

Re: [Pharo-project] [Metacello] Fwd: Metacello questions

by Dale Henrichs

----- "Andreas.Raab" <andreas.raab(a)gmail.com> wrote: | 5) Bootstrapping Metacello? | | I found that most of the ConfigurationsOfXXX include some code to | 'bootstrap' Metacello in some form. There appear to be variants on | the | code; is there a "canonical bootstrap method" that should be used? | There is a canonical bootstrap method that is documented here: http://code.google.com/p/metacello/wiki/EnsureMetacello But the best technique is to copy the class MetacelloConfigTemplate where all of the required methods are already implemented... For more information see my answer to Question #6 below. | 6) A standard Configuration template? | | The Metacello tutorial is very useful as far as the configuration | goes | but it falls short of getting into the details of what it means to | provide a 'working' configuration. Testing the configuration isn't | covered (is there a way to get back to a 'clean' state?); | bootstrapping | isn't covered; the meaning of #isMetacelloConfig, | #metacelloVesion:loads:, #lastMetacelloVersionLoad and several other | -seemingly random- methods that can be found on most -but not all- of | the configurations. There is no indication on what these do, if | they're | required, recommended, or optional. Is there some 'standard' | Configuration template that people can use to avoid guessing about | which | parts of the boilerplate to copy from some other configuration? There is a FAQ on creating a new Metacello configuration: http://code.google.com/p/metacello/wiki/FAQ#How_do_I_create_a_Metacello_Con… but unfortunately the instructions are buried within a series of workspaces in ProfStef ... a Pharo-only package:( I've just extracted the instructions and added the following link to the FAQ answer: http://code.google.com/p/metacello/wiki/CreateMetacelloConfiguration Hope this helps, Dale

May 11, 2010