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

Re: [Pharo-project] Issue 832

by Henrik Sperre Johansen

Yes, rollbacking probably is the safest choice, As I implied in the mail, this was really meant as a experimental effort, to see if people on slower machines noticed the effects I was (pre)anticipating. I really don't see how an extra intersect: per Morph (containing submorphs) can make such a big difference... I'll definately post another update sometime in the future, I don't know when I'll have to look into it though. <rant> To me, the way it is right now seems unacceptable, there's really no reason to write a "smart" drawOn: routine for morphs that are likely to end up as a subMorph (saaaay, the TextMorph which I started investigating in the first place), as they have to redraw the entire area anyways. This leads to a bad cycle in morph development; "As long as at minimum the area we want to redraw is marked as, it's fine. There's no performance gain from reporting a more accurate area anyways". So you end up with "sloppy" damage rects for new morphs, which leads to more to fix if it IS changed, and slower performance for those whom redrawing the entire area rather than a subsection IS expensive. </rant> Cheers, Henry On 27.05.2009 19:44, StÃ©phane Ducasse wrote: > Thanks for reporting. > Henrik? > I could rollback the changes. > > Stef > > On May 27, 2009, at 6:25 PM, Gary Chambers wrote: > > >> Performance of UI seems poor after 832 integration. >> >> http://code.google.com/p/pharo/issues/detail?id=832 >> >> Regards, Gary >> >> _______________________________________________ >> 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 27, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Alexandre Bergel

I agree with what has been previously said. However, I think there is a fundamental difference between getting en error: 'Character code point ranges between 1 and 256 only' and 'subscript is out of bound'. Currently, CharacterTable has 256 slots. Maybe an initialization has to be done or something, but if you provide a value > 255, then you will get an error. Alexandre On 27 May 2009, at 17:26, Gabriel Cotelli wrote: > Yes, but if "value:" cannot lookup in the table uses some extended > character set... > > I think the negative check mut be done... about the > 255 I'm not > sure... > > On Wed, May 27, 2009 at 3:42 PM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: > > Please remove the upper limit, I think this was a > > pre-internationalization method which should have been updated but > was > > not because not used. > > But CharacterTable is an array of 256 characters long. > > Alexandre > > > > > > > 2009/5/27 Alexandre Bergel <alexandre(a)bergel.eu>: > >> Yes, with a negative argument. > >> Adding the check: > >> (0 > integer or: [255 < integer]) > >> ifTrue: [self error: 'parameter out of range 0..255']. > >> is probably enough. > >> Alexandre > >> > >> > >> On 27 May 2009, at 08:27, Gabriel Cotelli wrote: > >> > >> The ANSI Specification doesn't mention anything about that the > >> integer must > >> be in some range... the only thing that expects is that (Character > >> codePoint: x) codePoint = x .... > >> > >> anyway... I can add the verification... but that's not specified in > >> the > >> ANSI... anybody knowns some senders of this? I checked Pharo-Dev > >> and found > >> none.. maybe in the Web Image? > >> > >> Alexandre, how you obtain an error using value: ? given a negative > >> argument? > >> I tried with values greater than 255 and works in my image... > >> > >> Tonight I check that > >> > >> 2009/5/27 Alexandre Bergel <Alexandre.Bergel(a)inria.fr> > >> I went through all the changes proposed by this slice. I am not > >> sure how > >> should I review the code, but here is my try: > >> - the new version of Character class>>codePoint: anInteger seems to > >> have a > >> different behavior: > >> The old (current) code is > >> codePoint: integer > >> "Return a character whose encoding value is integer." > >> #Fundmntl. > >> (0 > integer or: [255 < integer]) > >> ifTrue: [self error: 'parameter out of range 0..255']. > >> ^ CharacterTable at: integer + 1 > >> The new one is: > >> codePoint: anInteger > >> "Just for ANSI Compliance" > >> ^self value: anInteger > >> value: anInteger > >> "Answer the Character whose value is anInteger." > >> anInteger > 255 ifTrue: [^self basicNew setValue: anInteger]. > >> ^ CharacterTable at: anInteger + 1. > >> At the end an error is raised, but this is not the same. > >> Was this review useful? > >> Cheers, > >> Alexandre > >> -- > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> Alexandre Bergel http://www.bergel.eu > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > >> > >> > >> > >> > >> _______________________________________________ > >> 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 > >> > >> -- > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> Alexandre Bergel http://www.bergel.eu > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > >> > >> > >> > >> > >> _______________________________________________ > >> 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 > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 27, 2009

Re: [Pharo-project] allObjectsDo: broken

by Lukas Renggli

I played a bit with it. I came up with the following quick fix, but probably Eliot has a better solution. I find that code quite fragile anyway, if you instantiate an object in your enumeration block your lost (that was already the case before) ... allObjectsDo: aBlock "Evaluate the argument, aBlock, for each object in the system excluding SmallIntegers." | object | object := self someObject. [0 == object] whileFalse: [ (object class == MethodContext and: [ object closure == aBlock ]) ifFalse: [ aBlock value: object ]. object := object nextObject] On Wed, May 27, 2009 at 10:53 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > SystemNavigation default allObjectsDo: [ :e Â ] > > ...never terminates. At least since this is broken since #10268cl. > Version #10263 was still working. > > The suspect are new closures (I guess, creating new context instances > while iterating over all objects)... > > http://code.google.com/p/pharo/issues/detail?id=851 > > Adrian > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

May 27, 2009

Re: [Pharo-project] How To build exupery?

by Marco Schmidt

Is it possible to build exupery + alienffi (under linux and win32)? I wrapped my head trying to build a new vm to make some progress using libcurl ... Marco Schmidt 2009/5/27 Bryce Kampjes <bryce(a)kampjes.demon.co.uk> > On Wed, 2009-05-27 at 20:39 +0200, Giuseppe Luigi Punzi Ruiz wrote: > > I downloaded but I suppose a make install or something like this is > > needed, to put all files and plugins in the rigth place. > > What are you trying to do? The VM's include a pre-built squeak > executable, just execute that. > > There's also some source tarballs but they aren't recommended because > most people should either build from VMMaker (real source) or use a > pre-compiled VM. I supply the source packages because they were asked > for and there are a few legitimate uses for them. > > Bryce > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 27, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Gabriel Cotelli

Yes, but if "value:" cannot lookup in the table uses some extended character set... I think the negative check mut be done... about the > 255 I'm not sure... On Wed, May 27, 2009 at 3:42 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > > Please remove the upper limit, I think this was a > > pre-internationalization method which should have been updated but was > > not because not used. > > But CharacterTable is an array of 256 characters long. > > Alexandre > > > > > > > 2009/5/27 Alexandre Bergel <alexandre(a)bergel.eu>: > >> Yes, with a negative argument. > >> Adding the check: > >> (0 > integer or: [255 < integer]) > >> ifTrue: [self error: 'parameter out of range 0..255']. > >> is probably enough. > >> Alexandre > >> > >> > >> On 27 May 2009, at 08:27, Gabriel Cotelli wrote: > >> > >> The ANSI Specification doesn't mention anything about that the > >> integer must > >> be in some range... the only thing that expects is that (Character > >> codePoint: x) codePoint = x .... > >> > >> anyway... I can add the verification... but that's not specified in > >> the > >> ANSI... anybody knowns some senders of this? I checked Pharo-Dev > >> and found > >> none.. maybe in the Web Image? > >> > >> Alexandre, how you obtain an error using value: ? given a negative > >> argument? > >> I tried with values greater than 255 and works in my image... > >> > >> Tonight I check that > >> > >> 2009/5/27 Alexandre Bergel <Alexandre.Bergel(a)inria.fr> > >> I went through all the changes proposed by this slice. I am not > >> sure how > >> should I review the code, but here is my try: > >> - the new version of Character class>>codePoint: anInteger seems to > >> have a > >> different behavior: > >> The old (current) code is > >> codePoint: integer > >> "Return a character whose encoding value is integer." > >> #Fundmntl. > >> (0 > integer or: [255 < integer]) > >> ifTrue: [self error: 'parameter out of range 0..255']. > >> ^ CharacterTable at: integer + 1 > >> The new one is: > >> codePoint: anInteger > >> "Just for ANSI Compliance" > >> ^self value: anInteger > >> value: anInteger > >> "Answer the Character whose value is anInteger." > >> anInteger > 255 ifTrue: [^self basicNew setValue: anInteger]. > >> ^ CharacterTable at: anInteger + 1. > >> At the end an error is raised, but this is not the same. > >> Was this review useful? > >> Cheers, > >> Alexandre > >> -- > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> Alexandre Bergel http://www.bergel.eu > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > >> > >> > >> > >> > >> _______________________________________________ > >> 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 > >> > >> -- > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> Alexandre Bergel http://www.bergel.eu > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > >> > >> > >> > >> > >> _______________________________________________ > >> 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 > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 27, 2009

Re: [Pharo-project] New Pharo based on core 10318 with antialiased fonts

by StÃ©phane Ducasse

> Hi. > I recently download the new 10318 development image and it seems the > OBTextSelection>>isClassNode MNU is not fixed yet. > (See http://lists.gforge.inria.fr/pipermail/pharo-project/2009-May/008782.html) > I just want to remind it for you to fix it because it would be a > really pity to release a version with such a silly error. > Thanks and excellent work Yes I used the dev version in a lecture and we could get the menu working :) Stef

May 27, 2009

Re: [Pharo-project] Issue 832

by StÃ©phane Ducasse

On May 27, 2009, at 8:03 PM, Schwab,Wilhelm K wrote: > Stef, > > That would be nice for a temporary measure at least, because the > performance really has suffered. Assuming you roll back, would it > be enough to update my 10303 image? To rollback I will just issue a new update. sorry for the problem one my machine I did not notice it. Stef > > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] On Behalf Of StÃ©phane Ducasse > Sent: Wednesday, May 27, 2009 12:44 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Issue 832 > > Thanks for reporting. > Henrik? > I could rollback the changes. > > Stef > > On May 27, 2009, at 6:25 PM, Gary Chambers wrote: > >> Performance of UI seems poor after 832 integration. >> >> http://code.google.com/p/pharo/issues/detail?id=832 >> >> Regards, Gary >> >> _______________________________________________ >> 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 27, 2009

Re: [Pharo-project] How To build exupery?

by Bryce Kampjes

On Wed, 2009-05-27 at 20:39 +0200, Giuseppe Luigi Punzi Ruiz wrote: > I downloaded but I suppose a make install or something like this is > needed, to put all files and plugins in the rigth place. What are you trying to do? The VM's include a pre-built squeak executable, just execute that. There's also some source tarballs but they aren't recommended because most people should either build from VMMaker (real source) or use a pre-compiled VM. I supply the source packages because they were asked for and there are a few legitimate uses for them. Bryce

May 27, 2009

[Pharo-project] allObjectsDo: broken

by Adrian Lienhard

SystemNavigation default allObjectsDo: [ :e ] ...never terminates. At least since this is broken since #10268cl. Version #10263 was still working. The suspect are new closures (I guess, creating new context instances while iterating over all objects)... http://code.google.com/p/pharo/issues/detail?id=851 Adrian

May 27, 2009

Re: [Pharo-project] New Pharo based on core 10318 with antialiased fonts

by Mariano Martinez Peck

On Wed, May 27, 2009 at 7:32 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Upload where? The OB tools are not part of Pharo-core, Sorry. You are totally right. > so we cannot > patch it there. Hence this really needs to go to the OB repository > from which Damien creates Pharo images. I don't know much about OB and > who maintains it, so could somebody tell us what the right way to get > patches integrated is? > > Cheers, > Adrian > > > On May 27, 2009, at 22:17 , Mariano Martinez Peck wrote: > > > What we could do is to upload both quick workaround (the one Nico > > did for > > the debugger) and the one of creating the method isClassNode which > > returns > > false. Obviously this is temporal till the real fix arrives. The > > ticket > > won't be closed. > > > > Then we add a comment in the ticket that says "to reproduce this, > > remove > > isClassNode method and do a right click on the code ....". > > > > I think this will help Pharo users. > > > > Cheers, > > > > On Wed, May 27, 2009 at 6:36 PM, Adrian Lienhard <adi(a)netstyle.ch> > > wrote: > > > >> Thanks. > >> No let's hope some OB maintainer picks it up... > >> > >> Adrian > >> > >> On May 27, 2009, at 21:17 , Nicolas Chillo wrote: > >> > >>> Ready. > >>> http://code.google.com/p/pharo/issues/detail?id=849 > >>> > >>> Nicolas > >>> > >>> On Wed, May 27, 2009 at 4:10 PM, Adrian Lienhard <adi(a)netstyle.ch> > >>> wrote: > >>> > >>>> Hi Nicolas, > >>>> > >>>> Could you open an issue in the tracker? This would significantly > >>>> decrease the risk that the bug gets forgotten. > >>>> > >>>> Thanks, > >>>> Adrian > >>>> > >>>> On May 27, 2009, at 20:05 , Nicolas Chillo wrote: > >>>> > >>>>> Hi. > >>>>> I recently download the new 10318 development image and it seems > >>>>> the > >>>>> OBTextSelection>>isClassNode MNU is not fixed yet. > >>>>> (See > >>>>> > >>>> > >> > http://lists.gforge.inria.fr/pipermail/pharo-project/2009-May/008782.html) > >>>>> I just want to remind it for you to fix it because it would be a > >>>>> really pity > >>>>> to release a version with such a silly error. > >>>>> Thanks and excellent work. > >>>>> Nicolas > >>>>> > >>>>> On Wed, May 27, 2009 at 12:59 PM, Damien Cassou < > >> damien.cassou(a)gmail.com > >>>>>> wrote: > >>>>> > >>>>>> On Wed, May 27, 2009 at 3:37 PM, Simon Denier < > Simon.Denier(a)inria.fr > >>>>>>> > >>>>>> wrote: > >>>>>>> Yes, installing ECompletionOmniBrowser before OCompletion > >>>>>>> should do > >>>>>>> the trick. > >>>>>> > >>>>>> Could you please check Romain and tell me so that I can update > >>>>>> the > >>>>>> script? > >>>>>> > >>>>>> -- > >>>>>> Damien Cassou > >>>>>> http://damiencassou.seasidehosting.st > >>>>>> > >>>>>> "Lambdas are relegated to relative obscurity until Java makes > >>>>>> them > >>>>>> popular by not having them." James Iry > >>>>>> > >>>>>> _______________________________________________ > >>>>>> 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 > >>>> > >>>> > >>>> _______________________________________________ > >>>> 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 > >> > >> > >> _______________________________________________ > >> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 27, 2009