February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3743 in pharo: Fix Finder UI (add shortcuts and more commands)

by pharo＠googlecode.com

Comment #10 on issue 3743 by aplan...(a)gmail.com: Fix Finder UI (add shortcuts and more commands) http://code.google.com/p/pharo/issues/detail?id=3743 Hi Benjamin! I've found two problems: 1) Since keyStroke: is sent with the event as argument, now you have to get the character from the event :) ---- keyStroke: anEvent anEvent == $n ifTrue: [ ^ self browseSenders ]. ---- should be ---- keyStroke: anEvent anEvent keyCharacter == $n ifTrue: [ ^ self browseSenders ]. ---- 2) the menus are not built correctly (don't know why)

Feb. 25, 2011

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

by Marcus Denker

On Feb 25, 2011, at 6:14 PM, Guillermo Polito wrote: > I think the build will become unstable with every package update... So maybe we should update every ConfigurationOf used by pharo, and put symbolic versions into it > The 1.1 build is broken, too. So even for 1.1, we somhow load new packages, not the frozen ones. https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.1/ Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 25, 2011

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

by Guillermo Polito

I didn't try it yet, but using metacello browser, and letting it have a project description, will do the work for us ;). On Fri, Feb 25, 2011 at 1:09 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Marcus > > I would not add XML in dev. just dev tools no extra package. > So yes let us remove XML package. I already asked for that. > Now the problem encountered reveal something deeper. > > > STef > > On Feb 25, 2011, at 1:18 PM, Marcus Denker wrote: > > > I personally thing if we ever want to release 1.2, we need to start to be > more radical. > > > > The XML package breaks the build? So let's remove it completely. Let's > ship 1.2, but without > > all the packages that are problematic. > > > > Same for any other package that has a failing test. > > > > Marcus > > > > > > On Feb 25, 2011, at 1:12 PM, Torsten Bergmann wrote: > > > >> Still I do not understand: > >> > >> Evaluate this in an updated Pharo core 1.2: > >> > >> ------------------------------------------------------------------------ > >> Gofer new > >> squeaksource: 'MetacelloRepository'; > >> package: 'ConfigurationOfXMLSupport'; > >> load. > >> > >> (Smalltalk at: #ConfigurationOfXMLSupport) project latestVersion > >> ------------------------------------------------------------------------ > >> > >> returns 1.1.8 [ConfigurationOfXMLSupport] > >> > >> This is now broken by Otto. OK, he broke it, he has to repair it ;) > >> > >> But independent from that, the method in: > >> > >> ConfigurationOfPharo>>version12beta2: > >> > >> includes the following: > >> > >> project: 'XMLSupport' with: '1.1.6'. > >> > >> So I would have expected that for Pharo "1.2-beta2" the 1.1.6 (and not > the > >> 1.1.8) of XMLSupport gets loaded and Hudson should have been green. > >> > >> Why does Metacello load the 1.1.8 when a previous project version > (1.1.6) > >> is referenced? > >> > >> Dale, any comments? > >> > >> Bye > >> T. > >> > >> > >> > >> -- > >> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > >> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > >> > > > > -- > > Marcus Denker -- http://www.marcusdenker.de > > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > >

Feb. 25, 2011

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

by Guillermo Polito

I think the build will become unstable with every package update... So maybe we should update every ConfigurationOf used by pharo, and put symbolic versions into it Guille On Fri, Feb 25, 2011 at 1:50 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > On 25.02.2011, at 17:48, Marcus Denker wrote: > > > On Feb 25, 2011, at 5:42 PM, laurent laffont wrote: > > On Fri, Feb 25, 2011 at 5:11 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> >> On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote: >> >> > Markus wrote: >> >> The XML package breaks the build? So let's remove it completely. Let's >> ship >1.2, but without all the packages that are problematic. >> > >> > It's not that the package is problematic - the Configs are problematic >> >> Exact >> But still can't Pharo Dev focuses on tools and not frameworks that we >> should load by ourselves. >> Because else why not loading, cassandra, coucdb, opendbx, magma.... >> > > Because many more people are manipulating XML every day than connecting > to Cassandra ? > > > So now XML is fixed, not it fails due to a problem in the Mock package... > > We can not delay a release to fix all foreign packages. This makes no > sense. > > Absolutely not. Otto did a mistake so this caused problems. So isn't it > obvious to rollback the configuration back to the point it worked. > > Norbert > >

Feb. 25, 2011

Re: [Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

by pharo＠googlecode.com

Comment #5 on issue 3757 by Torsten....(a)astares.de: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 When I load it manually it works for me (didnt clear package cache).

Feb. 25, 2011

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

by Norbert Hartl

On 25.02.2011, at 17:48, Marcus Denker wrote: > > On Feb 25, 2011, at 5:42 PM, laurent laffont wrote: > >> On Fri, Feb 25, 2011 at 5:11 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote: >> >> > Markus wrote: >> >> The XML package breaks the build? So let's remove it completely. Let's ship >1.2, but without all the packages that are problematic. >> > >> > It's not that the package is problematic - the Configs are problematic >> >> Exact >> But still can't Pharo Dev focuses on tools and not frameworks that we should load by ourselves. >> Because else why not loading, cassandra, coucdb, opendbx, magma.... >> >> Because many more people are manipulating XML every day than connecting to Cassandra ? >> > > So now XML is fixed, not it fails due to a problem in the Mock package... > > We can not delay a release to fix all foreign packages. This makes no sense. > Absolutely not. Otto did a mistake so this caused problems. So isn't it obvious to rollback the configuration back to the point it worked. Norbert

Feb. 25, 2011

[Pharo-project] Issue 3760 in pharo: Build 1.2 Fails due to Mock package

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage Importance-High New issue 3760 by marcus.d...(a)gmail.com: Build 1.2 Fails due to Mock package http://code.google.com/p/pharo/issues/detail?id=3760 Solution: Remove the package that is the problem. THERE_BE_DRAGONS_HERE MessageNotUnderstood: receiver of "evaluateMessageSend:" is nil 25 February 2011 5:41:49 pm VM: unix - i686 - linux - Squeak4.1 of 17 April 2010 [latest update: #9957] Image: Pharo1.2rc2 [Latest update: #12338] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /builds/workspace/Pharo 1.2/Pharo-1.2-AfterRunningTests Trusted Dir /builds/workspace/Pharo 1.2/Pharo-1.2-AfterRunningTests/secure Untrusted Dir /builds/workspace/Pharo 1.2/Pharo-1.2-AfterRunningTests/My Squeak UndefinedObject(Object)>>doesNotUnderstand: #evaluateMessageSend: Receiver: nil Arguments and temporary variables: <<error during printing> Receiver's instance variables: nil MockObject>>evaluateMessage: Receiver: <<error during printing>> Arguments and temporary variables: aMessage: someMessage Receiver's instance variables: <<error during printing>> MockObject(MocketryProxy)>>doesNotUnderstand: #someMessage Receiver: <<error during printing>> Arguments and temporary variables: aMessage: someMessage Receiver's instance variables: <<error during printing>> [mock1 someMessage] in [[mock1 someMessage] fork. Processor yield] in MessageContextSpecAcceptanceTests>>testShouldBeAsynchronousIfMessageInOtherProcess Receiver: MessageContextSpecAcceptanceTests>>#testShouldBeAsynchronousIfMessageInOtherProcess Arguments and temporary variables: Receiver's instance variables: testSelector: #testShouldBeAsynchronousIfMessageInOtherProcess mock1: nil mock2: nil [self value. Processor terminateActive] in BlockClosure>>newProcess Receiver: [mock1 someMessage] Arguments and temporary variables: Receiver's instance variables: outerContext: [[mock1 someMessage] fork. Processor yield] in MessageContextSpe...etc... startpc: 55 numArgs: 0 --- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #evaluateMessageSend: MockObject>>evaluateMessage: MockObject(MocketryProxy)>>doesNotUnderstand: #someMessage [mock1 someMessage] in [[mock1 someMessage] fork. Processor yield] in MessageContextSpecAcceptanceTests>>testShouldBeAsynchronousIfMessageInOtherProcess [self value. Processor terminateActive] in BlockClosure>>newProcess

Feb. 25, 2011

[Pharo-project] [update 1.3] #13066

by Alain Plantec

Issue 3759: Stragger -> stagger Issue 3742: MorphTreeMorph keyStroke: send Event object instead of Character Alain

Feb. 25, 2011

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes

by Marcus Denker

On Feb 25, 2011, at 5:42 PM, laurent laffont wrote: > On Fri, Feb 25, 2011 at 5:11 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote: > > > Markus wrote: > >> The XML package breaks the build? So let's remove it completely. Let's ship >1.2, but without all the packages that are problematic. > > > > It's not that the package is problematic - the Configs are problematic > > Exact > But still can't Pharo Dev focuses on tools and not frameworks that we should load by ourselves. > Because else why not loading, cassandra, coucdb, opendbx, magma.... > > Because many more people are manipulating XML every day than connecting to Cassandra ? > So now XML is fixed, not it fails due to a problem in the Mock package... We can not delay a release to fix all foreign packages. This makes no sense. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 25, 2011

Re: [Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3757 by marcus.d...(a)gmail.com: 1.2 build is broken due to XML package http://code.google.com/p/pharo/issues/detail?id=3757 Now this is fixed, and the build fails due to another reason. (We will *never* release 1.2, this is my prediction)

Feb. 25, 2011