- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Emergency evaluator pops up on red tests

by Fabrizio Perin

Hi Stef, I just tried to evaluate in a workspace as you said and i've got the same result. Also by executing the test in Nautilus with cmd-t i've got the same. Cheers, fabrizio On Mar 30, 2012 3:30 PM, "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote: > did you try to run on single test manually > > Test debug:#l';l;k;lk;l2 > > Stef > > On Mar 30, 2012, at 1:28 PM, Fabrizio Perin wrote: > > > Hi, > > I loaded all my stuff in the latest moose based on 1.4. > > All the tests of my PetitPHPParser are red. When I click on one red > method the emergency evaluator pops up. > > > > To reproduce it: > > 1- grab the latest MooseJee from the ci: > > http://ci.moosetechnology.org/job/moose-latest-dev/ > > > > 2- load the petit php parser: > > Gofer new > > squeaksource: 'PetitPHPParser'; > > package: 'ConfigurationOfPetitPHPParser'; > > load. > > (Smalltalk at: #ConfigurationOfPetitPHPParser) perform: #loadDefault. > > > > 3- Run the tests of the php parser and click on any red method. > > > > How can I debug the problem? Any suggestions on how to proceed? > > > > Thanks, > > Fabrizio > > > > >

March 31, 2012

Re: [Pharo-project] type-inference: it works!

by Alexandre Bergel

Ah okays. Have you made some comparison with the result of Roel Typer? That would be an interesting point to compare with. cheers, Alexandre On 30 Mar 2012, at 09:33, Francisco Garau wrote: > No unit tests, sorry... > > Is not profiling, it's abstract intrepretation using types instead of objects. > > - Francisco > > > On 30 Mar 2012, at 15:15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Hi Francisco, >> >> I've tried your implementation. It seems to work in Pharo 1.4. Do you have unit test somewhere? >> How does your profiler work? From what you have said in your email, it seems you are profiling the execution. Is that true? >> >> Cheers, >> Alexandre >> >> >> On 29 Mar 2012, at 18:47, Francisco Garau wrote: >> >>> Load the attached ChangeSets: first Ti-Engine and then Ti-Support. >>> >>> You could then evaluate the below expressions -- watch the Transcript to see which methods are being analysed. >>> >>> TiSystem current reset. >>> string := '3 + 4'. >>> Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. >>> "=> return {<SmallInteger>} " >>> >>> TiSystem current reset. >>> string := 'Display boundingBox'. >>> Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. >>> "=> return {<Rectangle origin: <Point x: <SmallInteger> y: <SmallInteger>> corner: <Point x: <SmallInteger> y: <SmallInteger>>>}" >>> >>> TiSystem current explore. >>> >>> Analysing 'Display boundingBox' shows a couple of surprises: >>> The code never goes through the #new method (it creates objects using #basicNew and #@) >>> Object code goes through Object>>value but knowing that the implementation just answers self, it could be easily optimised. >>> >>> I will try to package it more nicely under Monticello -- there are still a few rough edges that need to be polished before getting it to the same state it was in 2001... >>> >>> Cheers, >>> Francisco >>> <Ti-Engine.2.cs><Ti-Support.2.cs> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 31, 2012

Re: [Pharo-project] [Pharo 1.4] Please test!

by Helene Bilbo

Guillermo Polito wrote > > For OB, there is an stable version published with the metacello > configuration. But it is not receiving a constant manteinance. > That's good news. Where can i find it? -- View this message in context: http://forum.world.st/Pharo-1-4-Please-test-tp4518277p4519342.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 31, 2012

Re: [Pharo-project] [Pharo 1.4] Please test!

by Marcus Denker

On Mar 30, 2012, at 4:09 PM, Scott Gibson wrote: > I am not sure of the plans for syntax highlighting in version 1.4 but when I go to Settings for Shout: Syntax Highlighting I am not given any controls to adjust the values. When I change try to make the changes programmatically (as in 1.3) I am given the error AnObsoleteSHStyleSetting. Is this functionality being removed or has it been replaced perhaps? this looks like a bug to me... setting it programmatically should work. -- Marcus Denker -- http://marcusdenker.de

March 31, 2012

Re: [Pharo-project] [Pharo 1.4] Please test!

by Marcus Denker

On Mar 30, 2012, at 4:19 PM, Nick Ager wrote: > Trying the soon to be released 3.0.7: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside30'; > load. > > (ConfigurationOfSeaside30 project version: '3.0.7') load: 'OneClick'. > > I see the following issues during loading: > > RBAddMethodChange>>printOn: (RBPlatform is Undeclared) > RBCommentChange>>primitiveExecute (RBPlatform is Undeclared) > RBCommentChange>>printOn: (RBPlatform is Undeclared) RB is not part of 1.4 > OBDefinition>>doItReceiver (FakeClassPool is Undeclared) FakeClassPool was removed because it is not needed. It was already Deprecated in 1.3 http://code.google.com/p/pharo/issues/detail?id=3704 (March 1, 2011) > WAScreenshot>>toggleUIProcess (Project is Undeclared) > WAScreenshot>>toggleUIProcess (Project is Undeclared) > WAScreenshot>>toggleUIProcess (Project is Undeclared) > WAScreenshot>>toggleUIText (Project is Undeclared) Project was removed (it was already nearly empty in 1.3, the only removed earlier was that it was a bit tricky moving the state to UIManager) We could add this to Deprecated14 or Compatibility, even (as an empty class?) > Evaluated -> Seaside-Core >> seaside304DoIts ? > Form>>writerForMimeType: (PCXReadWriter is Undeclared) PCXReadWriter was removed (nobody uses that anymore, it's a very very old graphics format: ). This was already moved to Deprecated13 (but we did not deprecate all the methods) http://code.google.com/p/pharo/issues/detail?id=4072 Do we really need this? Marcus -- Marcus Denker -- http://marcusdenker.de

March 31, 2012

Re: [Pharo-project] direct object manipulation

by Alexandre Bergel

>> I didn't, but wait. What does this intall? Why not to simply package the libraries with the VM? > > because it is a third-party library. > To me, your proposal sounds similar to "why not simply package > Operating System libraries with the VM". > Because in this case you need cairo. But in case of OpenGL, you will > need opengl libs.. so "package everything" goes nowhere. > >> I tried once to use port/fink and I broke the internal of OSX, after having downloaded 500 Mb. >> > i know that using external libs sometimes is painful. But this is like > that. And we're not alone with these problems. > I think there's many other software which have to deal with it. > > Another solution is to implement everything by own :) Well... The Cairo libraries are shipped with VisualWorks. When I install VW, I've just say that I want Cairo, and everything works well. I have played a bit with Cairo on VW and I am quite happy so far. I would not have played with it if I had to install the lib externally with port/fink. I personally would not mind to have the virtual machine twice as big if cairo is shipped with it. I think it depends on what do you want to do in the mid-long term: throwing away the squeak bitmap rendering and using Cairo for real? What should be the external library, the squeak bitmap rendering or Cairo? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 31, 2012

Re: [Pharo-project] [Pharo 1.4] Please test!

by Nick Ager

Trying the soon to be released 3.0.7: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. (ConfigurationOfSeaside30 project version: '3.0.7') load: 'OneClick'. I see the following issues during loading: RBAddMethodChange>>printOn: (RBPlatform is Undeclared) RBCommentChange>>primitiveExecute (RBPlatform is Undeclared) RBCommentChange>>printOn: (RBPlatform is Undeclared) OBDefinition>>doItReceiver (FakeClassPool is Undeclared) WAScreenshot>>toggleUIProcess (Project is Undeclared) WAScreenshot>>toggleUIProcess (Project is Undeclared) WAScreenshot>>toggleUIProcess (Project is Undeclared) WAScreenshot>>toggleUIText (Project is Undeclared) Evaluated -> Seaside-Core >> seaside304DoIts Form>>writerForMimeType: (PCXReadWriter is Undeclared) http://code.google.com/p/seaside/issues/detail?id=719 Cheers Nick On 30 March 2012 15:08, Scott Gibson <wsgibson(a)windstream.net> wrote: > I am not sure of the plans for syntax highlighting in version 1.4 but when > I go to Settings for Shout: Syntax Highlighting I am not given any controls > to adjust the values. When I change try to make the changes > programmatically (as in 1.3) I am given the error AnObsoleteSHStyleSetting. > Is this functionality being removed or has it been replaced perhaps? > > Thanks! > Scott Gibson > > On Mar 30, 2012, at 3:26 AM, Marcus Denker wrote: > > > > > > > You can download the lastest 1.4 here for testing: > > > > > https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSucces… > > > > And a first version of the one-click here: > > > > > https://ci.lille.inria.fr/pharo/job/Pharo%20One%20Click%20image/lastSuccess… > > > > > > > > > > -- > > Marcus Denker -- http://marcusdenker.de > > > > > > >

March 31, 2012

Re: [Pharo-project] type-inference: it works!

by Alexandre Bergel

Hi Francisco, I've tried your implementation. It seems to work in Pharo 1.4. Do you have unit test somewhere? How does your profiler work? From what you have said in your email, it seems you are profiling the execution. Is that true? Cheers, Alexandre On 29 Mar 2012, at 18:47, Francisco Garau wrote: > Load the attached ChangeSets: first Ti-Engine and then Ti-Support. > > You could then evaluate the below expressions -- watch the Transcript to see which methods are being analysed. > > TiSystem current reset. > string := '3 + 4'. > Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. > "=> return {<SmallInteger>} " > > TiSystem current reset. > string := 'Display boundingBox'. > Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. > "=> return {<Rectangle origin: <Point x: <SmallInteger> y: <SmallInteger>> corner: <Point x: <SmallInteger> y: <SmallInteger>>>}" > > TiSystem current explore. > > Analysing 'Display boundingBox' shows a couple of surprises: > The code never goes through the #new method (it creates objects using #basicNew and #@) > Object code goes through Object>>value but knowing that the implementation just answers self, it could be easily optimised. > > I will try to package it more nicely under Monticello -- there are still a few rough edges that need to be polished before getting it to the same state it was in 2001... > > Cheers, > Francisco > <Ti-Engine.2.cs><Ti-Support.2.cs> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 31, 2012

Re: [Pharo-project] [Pharo 1.4] Please test!

by Scott Gibson

I am not sure of the plans for syntax highlighting in version 1.4 but when I go to Settings for Shout: Syntax Highlighting I am not given any controls to adjust the values. When I change try to make the changes programmatically (as in 1.3) I am given the error AnObsoleteSHStyleSetting. Is this functionality being removed or has it been replaced perhaps? Thanks! Scott Gibson On Mar 30, 2012, at 3:26 AM, Marcus Denker wrote: > > > You can download the lastest 1.4 here for testing: > > https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSucces… > > And a first version of the one-click here: > > https://ci.lille.inria.fr/pharo/job/Pharo%20One%20Click%20image/lastSuccess… > > > > > -- > Marcus Denker -- http://marcusdenker.de > >

March 31, 2012

Re: [Pharo-project] [Pharo 1.4] Please test!

by Tudor Girba

The Moose build is green on the latest Pharo 1.4. Cheers, Doru On Fri, Mar 30, 2012 at 11:10 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > For OB, there is an stable version published with the metacello > configuration.Â But it is not receiving a constant manteinance. > > For Nautilus, you will also find an stable metacello configuration, and > currently there is work on it to enhance it and make it work in the current > pharo images. > > > On Fri, Mar 30, 2012 at 10:53 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: >> >> No, no problem. Just that my 1.3 OneClick defaulted to OB. >> OB is way better for working with code when compared to the default thing. >> What should I look for? Nautilus? OB? All this looks like a tad confusing. >> >> >> 2012/3/30 Guillermo Polito <guillermopolito(a)gmail.com> >>> >>> >>> >>> On Fri, Mar 30, 2012 at 10:15 AM, phil(a)highoctane.be <phil(a)highoctane.be> >>> wrote: >>>> >>>> The browser is looking weird. >>>> Which one is it? No OB package view anymore? >>> >>> >>> It is the default System Browser, no OB.Â You can donwload OB by yourself >>> using the ConfigurationOfOmniBrowser from MetacelloRepository. >>> >>> Ask if you need help :). >>> >>> Guille >>> >>>> >>>> >>>> >>>> 2012/3/30 Marcus Denker <marcus.denker(a)inria.fr> >>>>> >>>>> >>>>> >>>>> You can download the lastest 1.4 here for testing: >>>>> >>>>> >>>>> Â https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSucces… >>>>> >>>>> And a first version of the one-click here: >>>>> >>>>> >>>>> Â https://ci.lille.inria.fr/pharo/job/Pharo%20One%20Click%20image/lastSuccess… >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Marcus Denker -- http://marcusdenker.de >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Philippe Back >>>> "Helping you hit the top 3 outcomes you really want to achieve" >>>> >>>> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >>>> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >>>> http://philippeback.be >>>> >>>> High Octane SPRL >>>> rue cour Boisacq 101 >>>> 1301 Bierges >>>> >>> >> >> >> >> -- >> Philippe Back >> "Helping you hit the top 3 outcomes you really want to achieve" >> >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be >> | Web: http://philippeback.eu | Blog: >> http://philippeback.be >> >> High Octane SPRL >> rue cour Boisacq 101 >> 1301 Bierges >> > -- www.tudorgirba.com "Every thing has its own flow"

March 31, 2012