- Pharo-dev - lists.pharo.org

rename instance variable does not work on class side instance var

by pharo4Stef＠free.fr

Hi guys I noticed that rename instance variable does not work on class side instance var. Stef

April 18, 2014

Re: [Pharo-dev] Japanese character in Pharo

by jannik laval

Thank you Sven, I can use it in Phratch now :) Cheers, Jannik 2014-04-10 17:55 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Hi Jannik, > > Of course, it can be done ;-) > > First make sure you set a Unicode font, then working with Japanese > characters should be no problem: > > > > Of course, encoding is something else, but UTF-8 will certainly work. For > the above, I just copy/pasted some text from Wikipedia (I am on Mac OS X). > > HTH, > > Sven > > On 10 Apr 2014, at 17:26, jannik laval <jannik.laval(a)gmail.com> wrote: > > Hi guys, > > A user of Phratch said to me that the japanese characters are not > recognized in Phratch. > I tried to locate the problem and it seems that Pharo itself does not > recognize them. > > In a Phratch image, just run this line, that display the contents of a > file with japaneze character: > (FileSystem workingDirectory / 'locale' / 'ja.po') contents > > Or, use the attached file, which is the same. > > Is it a known problem ? or should I configure something in settings to > take into account these characters ? > > Thank you. > > -- > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://www.phratch.com > http://car.mines-douai.fr/ > > <ja.po> > > > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://car.mines-douai.fr/

April 18, 2014

About fonts

by stepharo

Hi pharoers I found the problems with the fonts and now I understand one of the possible way Roassal got broken. Imagine the following FT is on -> roassal works perfectly (using vectorial fonts) the standard fonts (default, code and others) are using vector graphics font. I deselect FT -> defaults and other are now in strike fonts like vera I reselect FT -> the defaults are still in strike fonts and this will then lead to errors in roassal. So I think that we should have a real object handling the restore and others. I will try to have a look in the end of the week. stef

April 18, 2014

Re: [Pharo-dev] Monkey working?

by Esteban Lorenzano

all the INRIA infrastructure is stopped (they are doing I do not understand what, like enlarging the hard disk capability or so). so, no monkey and no ci at all until is fixed :( Esteban On 18 Apr 2014, at 14:44, Ben Coman <btc(a)openinworld.com> wrote: > > The following three cases have status "Resolved (Fix Review Needed)" for a couple of days and haven't been picked up by the monkey. Is there something wrong with Monkey or those cases? > * https://pharo.fogbugz.com/f/cases/11934/Last-Modified-Classed-group-in-Naut… > * https://pharo.fogbugz.com/f/cases/13195/testAllSetsAreHealthy-fails-on-ci-s… > * https://pharo.fogbugz.com/f/cases/13204/Hard-to-see-Morph-halo-label > > cheers -ben >

April 18, 2014

Monkey working?

by Ben Coman

The following three cases have status "Resolved (Fix Review Needed)" for a couple of days and haven't been picked up by the monkey. Is there something wrong with Monkey or those cases? * https://pharo.fogbugz.com/f/cases/11934/Last-Modified-Classed-group-in-Naut… * https://pharo.fogbugz.com/f/cases/13195/testAllSetsAreHealthy-fails-on-ci-s… * https://pharo.fogbugz.com/f/cases/13204/Hard-to-see-Morph-halo-label cheers -ben

April 18, 2014

Re: [Pharo-dev] UndefinedObject>>allSuperclassesDo: aBlockContext self shouldBeImplemented

by Marcus Denker

Yes, looks like it. UndefinedObject should just ignore the call as it stands in for a class that has no superclass. self shouldBeImplemented should be removed, I would say. On 17 Apr 2014, at 22:15, phil(a)highoctane.be wrote: > Weird... > > is this a bug? > > Phil >

April 18, 2014

Re: [Pharo-dev] Condense changes

by Sven Van Caekenberghe

On 18 Apr 2014, at 13:28, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 18.04.2014 um 13:19 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> >> On 18 Apr 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> Smalltalk condenseChanges >> >> That is old, please read https://pharo.fogbugz.com/f/cases/12729/Smalltalk-condenseChanges-raises-Zn… >> > Ok, thanks, the search didnât bring up that issue. But if the PharoChangesCondenser is integrated in the image why is it not used when Smalltalk condenseChanges is invoked? Another case of âlet us load that stuff but donât make it publicâ? Because it does not (yet) work on Windows. The new code is way better (faster, easier to understand).

April 18, 2014

Re: [Pharo-dev] Condense changes

by Norbert Hartl

Am 18.04.2014 um 13:19 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 18 Apr 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Smalltalk condenseChanges > > That is old, please read https://pharo.fogbugz.com/f/cases/12729/Smalltalk-condenseChanges-raises-Zn… > Ok, thanks, the search didnât bring up that issue. But if the PharoChangesCondenser is integrated in the image why is it not used when Smalltalk condenseChanges is invoked? Another case of âlet us load that stuff but donât make it publicâ? Norbert

April 18, 2014

Re: [Pharo-dev] Condense changes

by Sven Van Caekenberghe

On 18 Apr 2014, at 12:23, Norbert Hartl <norbert(a)hartl.name> wrote: > Smalltalk condenseChanges That is old, please read https://pharo.fogbugz.com/f/cases/12729/Smalltalk-condenseChanges-raises-Zn…

April 18, 2014

Re: [Pharo-dev] Condense changes

by Norbert Hartl

Am 18.04.2014 um 12:20 schrieb Norbert Hartl <norbert(a)hartl.name>: > > Am 18.04.2014 um 11:45 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > >> >> On 17 Apr 2014, at 21:13, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: >> >>> hi all, >>> >>> In a fresh image #30826, I tried: >>> >>> Smalltalk image condenseChanges -> ZnInvalidUTF8 error >>> >>> https://pharo.fogbugz.com/default.asp?12729& >>> describes that but it is closed. >>> >>> I tried the new version: >>> >>> PharoChangesCondenser condense. -> parse error >>> >> Works fine for me. No error. > Well, I did Smalltalk condenseChanges Norbert > I investigated that yesterday while playing with shrinking of an image and Iâve found the culprit. > > https://pharo.fogbugz.com/default.asp?13207 > > Norbert > >> >> >>> Do we open a new bug? >>> >>> Is there another way that I missed? >>> >>> Do you agree that we should remove condenseChanges from SmalltalkImage? >>> >> In Pharo4â¦ >> >> Marcus

April 18, 2014