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

Re: [Pharo-project] "Smalltalk signalLowSpace" freeze the image

by Mariano Martinez Peck

Thanks Torsten. Indeed, the fix works perfect at least for this problem. Cheers Mariano On Tue, May 25, 2010 at 6:43 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Now on: > > http://code.google.com/p/pharo/issues/list?cursor=2473 > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 26, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Mariano Martinez Peck

and we should open a bug ticket....too much emails.. On Wed, May 26, 2010 at 9:39 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > maybe the condenseChanges with the new method trailer? > > > On Tue, May 25, 2010 at 10:31 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> I noticed a problem between >> 11357 and 11363 today >> apparently class definitions containing traits loses their traits. >> >> Stef >> >> On May 25, 2010, at 3:10 PM, Torsten Bergmann wrote: >> >> > 1. If you select a trait in the browser (for instance "NSTInflating") >> > and select "browse hierarchy (h)" from the context menu you will >> > notice a >> > >> > Trait(Object)>>doesNotUnderstand: >> #allSubclassesWithLevelDo:startingLevel: >> > >> > error. >> > >> > >> > 2. While it was no problem to build the pharo-dev from a >> > core 11367 image using ConfigurationOfPharo it now crashes with a DNU >> > while loading Nile when I use a newer pharo #11371 core image. >> > >> > Bye >> > T. >> > >> > >> > >> > -- >> > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! >> > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >> > >> > _______________________________________________ >> > 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 26, 2010

Re: [Pharo-project] Problem with Demo mode [WAS] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Serge Stinckwich

2010/5/26 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Wed, May 26, 2010 at 9:43 AM, Serge Stinckwich > <serge.stinckwich(a)gmail.com> wrote: >> >> It look likes the problem is related to the fact that Deja Vu fonts is >> only in 9 and 12pt under Mac OS X. > > > Serge: did you change to DejaVu fonts in Pharo1.1?Â because in this image, > StrikeFonts are by default. Yes i think so with the Settings tool. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

May 26, 2010

Re: [Pharo-project] Problem with Demo mode [WAS] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Mariano Martinez Peck

On Wed, May 26, 2010 at 9:43 AM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > It look likes the problem is related to the fact that Deja Vu fonts is > only in 9 and 12pt under Mac OS X. > Serge: did you change to DejaVu fonts in Pharo1.1? because in this image, StrikeFonts are by default. > > On Mon, May 24, 2010 at 11:02 PM, Alain Plantec <alain.plantec(a)free.fr> > wrote: > > Le 24/05/2010 16:53, Mariano Martinez Peck a Ã©crit : > >> > >> > >> On Mon, May 24, 2010 at 11:56 AM, Serge Stinckwich > >> <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>> wrote: > >> > >> When i switch to demo mode, method selector in System Browser are no > >> more bold in the bottom pane. > >> > >> > >> I didn't understand you. Could you please attach both screenshots: how > it > >> should be and how is it ? > >> > >> Alain do you know about this ? > > > > Hi, > > Strange, I've tested and all is ok here. > > could you try with > > -------- > > StandardFonts setDemoFonts > > -------- > > > > Alain > >> > >> Cheers > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 26, 2010

Re: [Pharo-project] plan for 1.1

by Marcus Denker

On May 26, 2010, at 10:20 AM, StÃ©phane Ducasse wrote: > Hi guys > > we were discussing how we can handle 1.1 and the flux of good changes. > Here is the proposal: > we take two or three weeks to let people try their code in 1.1 beta > we integrate fixes that are important or easy > then we wait one week > then we launch 1.1 rc and 1.2 unstable > > does this plan look ok for you? Ok for me. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 26, 2010

Re: [Pharo-project] ConfigurationOfVMMaker updated

by StÃ©phane Ducasse

cool. Stef On May 26, 2010, at 10:25 AM, Torsten Bergmann wrote: > I've updated the newest development version 1.4 of ConfigurationOfVMMaker > so it loads well in latest Squeak 4.1., Squeak trunk, Pharo 1.0 and Pharo 1.1. and uses the latest packages available. Tested on all four platforms. > > Note that version 1.4 is still blessed with #development in the Metacello spec. > > What is new > =========== > - world menu registration works also in Pharo 1.1. > - switch to the new SqS/FreetypePlugin for the Squeak part > (see Squeak bug 7521) > - include latest packages available for VM building > > > For Squeak evaluate: > ---------------------------------------------------------------------- > Installer squeaksource > project: 'MetacelloRepository'; > install: 'ConfigurationOfVMMaker'. > > ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4') load > ---------------------------------------------------------------------- > > > For Pharo evaluate: > ---------------------------------------------------------------------- > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfVMMaker'; > load. > > ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4') load > ---------------------------------------------------------------------- > > Always remember that Metacello allows you to load newest packages > (if they appear) by loading the baseline. Here you can use: > > ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4-baseline') load > > > > What is open > ============ > > VMMaker still has > - #fixTemps > - deprecated #findLastOccuranceOfString: vs. findLastOccurenceOfString: > - ... > > that could be cleaned up if all VM Builders switch to the latest Squeak and > Pharo releases. We should really move forward here! Does anyone still use > old Squeak 3.6/3.8 to build the VM? What do you think? > > Thx > T. > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 26, 2010

Re: [Pharo-project] =nil to isNil rewrite part 1 in inbox

by Mariano Martinez Peck

Gabriel, is there an issue in the bug tracker for that? If not, please do it! Thanks Mariano 2010/5/26 Gabriel Cotelli <g.cotelli(a)gmail.com> > SLICE-RewriteEqualsNilToIsNil-GabrielOmarCotelli.2 > > Rewrite = nil to isNil in Pharo Core code. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 26, 2010

[Pharo-project] ConfigurationOfVMMaker updated

by Torsten Bergmann

I've updated the newest development version 1.4 of ConfigurationOfVMMaker so it loads well in latest Squeak 4.1., Squeak trunk, Pharo 1.0 and Pharo 1.1. and uses the latest packages available. Tested on all four platforms. Note that version 1.4 is still blessed with #development in the Metacello spec. What is new =========== - world menu registration works also in Pharo 1.1. - switch to the new SqS/FreetypePlugin for the Squeak part (see Squeak bug 7521) - include latest packages available for VM building For Squeak evaluate: ---------------------------------------------------------------------- Installer squeaksource project: 'MetacelloRepository'; install: 'ConfigurationOfVMMaker'. ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4') load ---------------------------------------------------------------------- For Pharo evaluate: ---------------------------------------------------------------------- Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfVMMaker'; load. ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4') load ---------------------------------------------------------------------- Always remember that Metacello allows you to load newest packages (if they appear) by loading the baseline. Here you can use: ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4-baseline') load What is open ============ VMMaker still has - #fixTemps - deprecated #findLastOccuranceOfString: vs. findLastOccurenceOfString: - ... that could be cleaned up if all VM Builders switch to the latest Squeak and Pharo releases. We should really move forward here! Does anyone still use old Squeak 3.6/3.8 to build the VM? What do you think? Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

May 26, 2010

Re: [Pharo-project] old method #withInheritanceTraitCompositionIncludes: , equivalence?

by StÃ©phane Ducasse

create a bug entry so that we do not forget to have a look at it, may be adrien remove it during his cleaning. Stef > > I donÂ´t know if is important. Perhaps no. I use it for know if a instance > have in some class parent the use of a trait. > > Always I could use the same code from old method. > > Regards. > -- > View this message in context: http://forum.world.st/old-method-withInheritanceTraitCompositionIncludes-eq… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 26, 2010

Re: [Pharo-project] #and:and:and: deprecated on 1.1, why?

by StÃ©phane Ducasse

reasons - and:and:and: is only used in squeak totally not portable. (we could live with that) - and: is optimized by the compiler - and:and: are not optimized is it ok? Stef On May 26, 2010, at 10:10 AM, nullPointer wrote: > > But I donÂ´t understand why the methods #and:and:and: AND #and:and:and:and: > must be deprecateds... what is the equivalence now for that messages? is > possible create a #&& and #|| messages? > > Regards > -- > View this message in context: http://forum.world.st/and-and-and-deprecated-on-1-1-why-tp2230786p2231198.h… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 26, 2010