March 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Unicode merge

by StÃ©phane Ducasse

cool I will test that. I hope that we will not have traffic jam with the closure compiler. Stef On Mar 23, 2009, at 6:27 PM, Michael Rueger wrote: > Michael Rueger wrote: > >> I will let you know when I figured out a way how to load >> everything :-) > > OK, for early adopters :-) > > in the PharoInbox there are two slices that need to be loaded in order > into a current 10259 image: > > SLICE-UnicodeRwrite1-michael_rueger.1 > SLICE-UnicodeRewrite2.2.mcm (which is actually a config map). > > at least on my Windows system these load and withstand some quick > testing. > > Please test and let me know if it works on your platform and if not > (not > too unlikely ;-) ), which platform you are on and the debug log if > possible. > > On Linux you need to make sure to run the VM with the UTF-8 options > enabled. > > Thank you all for testing! > > Michael > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 23, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by StÃ©phane Ducasse

I saw thanks. I hope to get some times continuing to explore the possible fixes. Stef On Mar 23, 2009, at 4:49 PM, Henrik Johansen wrote: > Done and done. > I'd rather not make a .cs for the > ClosureCompilerTest >>testInjectIntoDecompilations failure though, > as I neither feel comfortable messing around with Scanner, nor > particularily feel like it would be a good idea to change the test to > assume _ instead of := ... > > Cheers, > Henry > > StÃ©phane Ducasse wrote: >> excellent!!!! >> can you post cs to the Bugtracker so that >> we can reload all the fixes in a couple of click? >> >> http://code.google.com/p/pharo/issues/detail?id=685 >> >> I'm busy writing something else right now >> >> Stef >> On Mar 23, 2009, at 1:53 PM, Henrik Johansen wrote: >> >> >>> Here's a fix for the BlockContext test. >>> Basically, the error message had changed format, so the test that >>> the >>> correct error message was reported failed. >>> I changed the test to check for the (new) error format (which adds >>> argument(s) at the end of the sentence), and changed the error >>> message >>> to not call printstring, since this resulted in the string >>> containing >>> '1' instead of 1. >>> For some reason (which I'm not aware of) the printstring of numbers >>> seem >>> to include quotes. >>> >>> On a totally unrelated note, (didn't include it in the cs since it's >>> not >>> remotely related) >>> Debugger contents:notifying contains a call to Smalltalk>> isMorphic >>> which should probably be removed, comes up everytime you try to >>> save a >>> method edit in the debugger. >>> >>> Cheers, >>> Henry >>> >>> StÃ©phane Ducasse wrote: >>> >>>> I released an archive with two images >>>> 10259 with tests run >>>> 10259-withClosure + john + lukas + my fixes so far >>>> >>>> so that we can go faster to fix the problems >>>> >>>> https://gforge.inria.fr/frs/?group_id=1299 and files >>>> >>>> Stef >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> >>>> >>> 'From Pharo0.1 of 16 May 2008 [Latest update: #10259] on 23 March >>> 2009 at 1:47:53 pm'! >>> >>> !BlockClosure methodsFor: 'error handing' stamp: 'Henrik Sperre >>> Johansen 3/23/2009 13:45'! >>> numArgsError: numArgsForInvocation >>> >>> | printNArgs | >>> printNArgs := [:n| n printString, ' argument', (n = 1 ifTrue: [''] >>> ifFalse:['s'])]. >>> self error: >>> 'This block accepts ', (printNArgs value: numArgs), >>> ', but was called with ', (printNArgs value: >>> numArgsForInvocation), '.'! ! >>> >>> >>> !BlockContextTest methodsFor: 'tests - evaluating' stamp: 'Henrik >>> Sperre Johansen 3/23/2009 13:45'! >>> testValueWithArguments >>> self >>> should: [aBlockContext >>> valueWithArguments: #(1 )] >>> raise: Error. >>> self >>> shouldnt: [aBlockContext >>> valueWithArguments: #()] >>> raise: Error. >>> [aBlockContext >>> valueWithArguments: #(1 )] >>> ifError: [:err :rcvr | self assert: err = 'Error: This block >>> accepts 0 arguments, but was called with 1 argument.']. >>> [[:i | 3 + 4] >>> valueWithArguments: #(1 2)] >>> ifError: [:err :rcvr | self assert: err = 'Error: This block >>> accepts 1 argument, but was called with 2 arguments.']! ! >>> >>> _______________________________________________ >>> 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 >> >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 23, 2009

Re: [Pharo-project] Unicode merge

by Michael Rueger

Michael Rueger wrote: > I will let you know when I figured out a way how to load everything :-) OK, for early adopters :-) in the PharoInbox there are two slices that need to be loaded in order into a current 10259 image: SLICE-UnicodeRwrite1-michael_rueger.1 SLICE-UnicodeRewrite2.2.mcm (which is actually a config map). at least on my Windows system these load and withstand some quick testing. Please test and let me know if it works on your platform and if not (not too unlikely ;-) ), which platform you are on and the debug log if possible. On Linux you need to make sure to run the VM with the UTF-8 options enabled. Thank you all for testing! Michael

March 23, 2009

[Pharo-project] tooltips for inspector 'mystery' buttons

by Dale Henrichs

With 10259, there are tool tips for the 'mystery' buttons in the inspectors... If you have added a custom inspector method, you need to add #tooltip: to your pragama like the following for Object>>basicInspectorNodes: <inspector: #'1' priority: 600 toolTip: 'Basic elements'> Dale

March 23, 2009

Re: [Pharo-project] [ANN] Closures for beta testers

by Henrik Johansen

Done and done. I'd rather not make a .cs for the ClosureCompilerTest >>testInjectIntoDecompilations failure though, as I neither feel comfortable messing around with Scanner, nor particularily feel like it would be a good idea to change the test to assume _ instead of := ... Cheers, Henry StÃ©phane Ducasse wrote: > excellent!!!! > can you post cs to the Bugtracker so that > we can reload all the fixes in a couple of click? > > http://code.google.com/p/pharo/issues/detail?id=685 > > I'm busy writing something else right now > > Stef > On Mar 23, 2009, at 1:53 PM, Henrik Johansen wrote: > > >> Here's a fix for the BlockContext test. >> Basically, the error message had changed format, so the test that the >> correct error message was reported failed. >> I changed the test to check for the (new) error format (which adds >> argument(s) at the end of the sentence), and changed the error message >> to not call printstring, since this resulted in the string containing >> '1' instead of 1. >> For some reason (which I'm not aware of) the printstring of numbers >> seem >> to include quotes. >> >> On a totally unrelated note, (didn't include it in the cs since it's >> not >> remotely related) >> Debugger contents:notifying contains a call to Smalltalk>> isMorphic >> which should probably be removed, comes up everytime you try to save a >> method edit in the debugger. >> >> Cheers, >> Henry >> >> StÃ©phane Ducasse wrote: >> >>> I released an archive with two images >>> 10259 with tests run >>> 10259-withClosure + john + lukas + my fixes so far >>> >>> so that we can go faster to fix the problems >>> >>> https://gforge.inria.fr/frs/?group_id=1299 and files >>> >>> Stef >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> >>> >> 'From Pharo0.1 of 16 May 2008 [Latest update: #10259] on 23 March >> 2009 at 1:47:53 pm'! >> >> !BlockClosure methodsFor: 'error handing' stamp: 'Henrik Sperre >> Johansen 3/23/2009 13:45'! >> numArgsError: numArgsForInvocation >> >> | printNArgs | >> printNArgs := [:n| n printString, ' argument', (n = 1 ifTrue: [''] >> ifFalse:['s'])]. >> self error: >> 'This block accepts ', (printNArgs value: numArgs), >> ', but was called with ', (printNArgs value: >> numArgsForInvocation), '.'! ! >> >> >> !BlockContextTest methodsFor: 'tests - evaluating' stamp: 'Henrik >> Sperre Johansen 3/23/2009 13:45'! >> testValueWithArguments >> self >> should: [aBlockContext >> valueWithArguments: #(1 )] >> raise: Error. >> self >> shouldnt: [aBlockContext >> valueWithArguments: #()] >> raise: Error. >> [aBlockContext >> valueWithArguments: #(1 )] >> ifError: [:err :rcvr | self assert: err = 'Error: This block >> accepts 0 arguments, but was called with 1 argument.']. >> [[:i | 3 + 4] >> valueWithArguments: #(1 2)] >> ifError: [:err :rcvr | self assert: err = 'Error: This block >> accepts 1 argument, but was called with 2 arguments.']! ! >> >> _______________________________________________ >> 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 > > >

March 23, 2009

[Pharo-project] Unicode merge

by Michael Rueger

Hi all, in the process of merging the unicode work into the current system I will upload a bunch of packages to the inbox. The packages will not load as they are, will need some config maps etc to load it all. I will let you know when I figured out a way how to load everything :-) Michael

March 23, 2009

Re: [Pharo-project] Software update

by Mariano Martinez Peck

On Mon, Mar 23, 2009 at 6:57 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Mon, Mar 23, 2009 at 9:19 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > The update stream only includes update for the image pharo-core > > for the pharo-dev you should use the universe browser. > > Universe is currently not used anymore to build pharo-dev. I'm > building them using Monticello. The best solution is to save your code > externally using Monticello and use the most recent pharo-dev when it > comes out. That will ensure your code can be loaded in all images. > That's a best practice used by different people. > Ok, thanks for explain me this. I will do it this way then. > > You can also use the update stream to update the core and MC to update > the packages you want but I do not recommend this solution. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 23, 2009

Re: [Pharo-project] New Pharo-dev AND web based on 10259

by StÃ©phane Ducasse

thanks amigo Stef On Mar 23, 2009, at 4:08 PM, Damien Cassou wrote: > Here are pharo-dev and pharo-web based on latest 10259 before Closure: > http://code.google.com/p/pharo/wiki/Downloads?tm=2 > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 23, 2009

Re: [Pharo-project] stephane.ducasse@inria.fr

by StÃ©phane Ducasse

excellent!!!! can you post cs to the Bugtracker so that we can reload all the fixes in a couple of click? http://code.google.com/p/pharo/issues/detail?id=685 I'm busy writing something else right now Stef On Mar 23, 2009, at 1:53 PM, Henrik Johansen wrote: > Here's a fix for the BlockContext test. > Basically, the error message had changed format, so the test that the > correct error message was reported failed. > I changed the test to check for the (new) error format (which adds > argument(s) at the end of the sentence), and changed the error message > to not call printstring, since this resulted in the string containing > '1' instead of 1. > For some reason (which I'm not aware of) the printstring of numbers > seem > to include quotes. > > On a totally unrelated note, (didn't include it in the cs since it's > not > remotely related) > Debugger contents:notifying contains a call to Smalltalk>> isMorphic > which should probably be removed, comes up everytime you try to save a > method edit in the debugger. > > Cheers, > Henry > > StÃ©phane Ducasse wrote: >> I released an archive with two images >> 10259 with tests run >> 10259-withClosure + john + lukas + my fixes so far >> >> so that we can go faster to fix the problems >> >> https://gforge.inria.fr/frs/?group_id=1299 and files >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> > 'From Pharo0.1 of 16 May 2008 [Latest update: #10259] on 23 March > 2009 at 1:47:53 pm'! > > !BlockClosure methodsFor: 'error handing' stamp: 'Henrik Sperre > Johansen 3/23/2009 13:45'! > numArgsError: numArgsForInvocation > > | printNArgs | > printNArgs := [:n| n printString, ' argument', (n = 1 ifTrue: [''] > ifFalse:['s'])]. > self error: > 'This block accepts ', (printNArgs value: numArgs), > ', but was called with ', (printNArgs value: > numArgsForInvocation), '.'! ! > > > !BlockContextTest methodsFor: 'tests - evaluating' stamp: 'Henrik > Sperre Johansen 3/23/2009 13:45'! > testValueWithArguments > self > should: [aBlockContext > valueWithArguments: #(1 )] > raise: Error. > self > shouldnt: [aBlockContext > valueWithArguments: #()] > raise: Error. > [aBlockContext > valueWithArguments: #(1 )] > ifError: [:err :rcvr | self assert: err = 'Error: This block > accepts 0 arguments, but was called with 1 argument.']. > [[:i | 3 + 4] > valueWithArguments: #(1 2)] > ifError: [:err :rcvr | self assert: err = 'Error: This block > accepts 1 argument, but was called with 2 arguments.']! ! > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 23, 2009

[Pharo-project] New Pharo-dev AND web based on 10259

by Damien Cassou

Here are pharo-dev and pharo-web based on latest 10259 before Closure: http://code.google.com/p/pharo/wiki/Downloads?tm=2 -- Damien Cassou http://damiencassou.seasidehosting.st

March 23, 2009