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

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes
by Marcus Denker Feb. 25, 2011

Feb. 25, 2011

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.

3 3

[Pharo-project] [OT] Why PHP is better than Ruby
by Igor Stasenko Feb. 25, 2011

Feb. 25, 2011

My friend gave me a fun post.. http://najafali.com/php-is-better-than-ruby.html rofl... -- Best regards, Igor Stasenko AKA sig.

3 2

[Pharo-project] about Issue 3728: Changed MenuMorph references to go through UIManager default menuClass
by StÃ©phane Ducasse Feb. 25, 2011

Feb. 25, 2011

Hi fernando here are my own changes. Please have a look and let me know what you think. Stef Stef

1 0

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes
by Marcus Denker Feb. 25, 2011

Feb. 25, 2011

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.

1 0

Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes
by Marcus Denker Feb. 25, 2011

Feb. 25, 2011

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.

6 9

[Pharo-project] Issue 3757 in pharo: 1.2 build is broken due to XML package
by pharo＠googlecode.com Feb. 25, 2011

Feb. 25, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage Importance-High New 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 1.2 build is broken due to XML package

1 5

[Pharo-project] [update 1.3] #13066
by Alain Plantec Feb. 25, 2011

Feb. 25, 2011

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

1 0

[Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes
by Torsten Bergmann Feb. 25, 2011

Feb. 25, 2011

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 Laurent wrote: >For XML I can fix this tonight if Otto don't want / can do it. Yes, the problematic 1.1.8 version of XMLSupport has to be fixed. But it is not yet used by Pharo ... so this is not the reason: What strikes me is that ConfigurationOfPharo STILL references the working 1.1.6 version BUT the corrupt 1.1.8 version is loaded instead. THIS is the reason why Hudson is read! If you look at ConfigurationOfPharo then it hasnt changed since 18 February 2011 (ConfigurationOfPharo-GuillermoPolito.134) and if you load "ConfigurationOfXMLSupport-DaleHenrichs.46" from 9 February 2011 and check what Otto Behrens changed then you will notice that he did'nt touch the 1.1.6 version of ConfigurationOfXMLSupport. He just added a baseline/version 1.1.8 and 1.1.9. So the "old" version 1.1.6 which is used by ConfigurationOfPharo was not touched either. To me this looks like a Metacello resolving remote project versions problem? (that's why I CC:ed Dale) >But I agree that it seems few people care about 1.2. Sad, I like it far >better than 1.1.1. Yes, but I think we opened 1.3 too early. I think thats why community does not concentrate on Pharo dev 1.2 too much and continues to work on 1.3 core instead. Thats good for moving Pharo forward - but not for outside visibility. How should others deliver software on top of Pharo if Pharo isnt delivered itself? >I personally thing if we ever want to release 1.2, we need to start to be >more radical. Yes - but not by throwing out broken packages. What if Hudson is broken by a problem in clas Object. Would you throw out Kernel? Instead I would propose for the harvesters/integrators to stop integrating stuff for 1.3 until Pharo 1.2 is out of the door... Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

4 4

Feb. 25, 2011

Hi gary I was reading http://code.google.com/p/pharo/issues/detail?id=3728 which converts MenuMorph new -> UIManager default menuClass And I was wondering: - UIManager regulate coarse grained interaction - UITheme takes into account settings Now UIManager does not provide handy MenuMorph creation method besides choose.... and friends. And now I'm looking at TEasilyThemed and it refers to MenuMorph so I'm wondering if in headless we could not still have popup menu raised. Stef

2 3

[Pharo-project] Could we clean/remove some of the old themes?
by stephane ducasse Feb. 25, 2011

Feb. 25, 2011

I would suggest to remove/package in a separate package StandardSqueak to remove the Pro theme (because the fonts are broken) to rename softSqueak into Colorful Stef

2 1