- Pharo-dev - lists.pharo.org

Re: [Pharo-project] SLICE-RelicensingPart1

by Alexandre Bergel

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 27, 2009

[Pharo-project] [ANN] 10319

by StÃ©phane Ducasse

Issue 838: Make mouse buttons mapping platform dependent relicensing (tx gabriel) Stef

May 27, 2009

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

by Simon Denier

On 27 mai 09, at 15:42, Romain Robbes wrote: > > On May 27, 2009, at 3:37 PM, Simon Denier wrote: > >> >> On 27 mai 09, at 14:49, Romain Robbes wrote: >> >>> Oh ok. Indeed I noticed it works in the workspace, but not in OB. >>> How can we fix this? Just by including ECompletionOmniBrowser in the >>> distribution? >> >> Yes, installing ECompletionOmniBrowser before OCompletion should do >> the trick. >> Also It didnt work in the workspace in the previous Pharo, but now it >> seems ok. >> Finally another bug has disappeared: duplication/shift of beginning >> characters when completing directly (from 'aVar', I would get >> 'aaVariable' when pressing tab if the first choice is ok - that was >> annoying) >> > > When did that one last disappear? It was supposed to be gone for a > long time ... I have the bug in 10309. Maybe related to Sensor fixes. > > > Romain > >> >>> >>> >>> Romain >>> >>> On May 27, 2009, at 2:24 PM, Simon Denier wrote: >>> >>>> Hi Romain >>>> >>>> I didnt take time to notice you, but ECompletionOmniBrowser is >>>> missing >>>> in the Pharo distrib, hence it does not work at all in OB unless >>>> you >>>> install it. >>>> >>>> >>>> On 27 mai 09, at 13:31, Romain Robbes wrote: >>>> >>>>> Hi Ramiro, >>>>> >>>>> In which version was OCompletion not working for you? >>>>> >>>>> Romain >>>>> >>>>> On May 27, 2009, at 11:53 AM, Ramiro Diaz Trepat wrote: >>>>> >>>>>> Hi Damien, >>>>>> A couple of trivial questions >>>>>> Is OCompletion integrated in this version? In the previous >>>>>> version >>>>>> it had stopped suggesting. >>>>>> Do you know if Seaside 2.9 works with the new Pharo / closures ? >>>>>> Cheers, and thanks for all this great dev images. >>>>>> >>>>>> r. >>>>>> >>>>>> >>>>>> -----Original Message----- >>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr >>>>>> ] On Behalf Of Damien Cassou >>>>>> Sent: 27 May 2009 10:50 >>>>>> To: Pharo Development >>>>>> Subject: [Pharo-project] New Pharo based on core 10318 with >>>>>> antialiased fonts >>>>>> >>>>>> New Pharo: http://pharo-project.org/download >>>>>> >>>>>> -- >>>>>> 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 >>>>>> This email is confidential and subject to important disclaimers >>>>>> and >>>>>> conditions including on offers for the purchase or sale of >>>>>> securities, accuracy and completeness of information, viruses, >>>>>> confidentiality, legal privilege, and legal entity disclaimers, >>>>>> available at http://www.jpmorgan.com/pages/disclosures/email. >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>>> project >>>>> >>>>> -- >>>>> Romain Robbes >>>>> http://www.inf.unisi.ch/phd/robbes >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>>> >>>> >>>> -- >>>> Simon >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> Romain Robbes >>> http://www.inf.unisi.ch/phd/robbes >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Romain Robbes > http://www.inf.unisi.ch/phd/robbes > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Simon

May 27, 2009

[Pharo-project] Issue 839: Debugging of closures can cause further error

by StÃ©phane Ducasse

> > http://code.google.com/p/pharo/issues/detail?id=839&colspec=ID%20Type%20Sta… > > >

May 27, 2009

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

by Romain Robbes

On May 27, 2009, at 3:37 PM, Simon Denier wrote: > > On 27 mai 09, at 14:49, Romain Robbes wrote: > >> Oh ok. Indeed I noticed it works in the workspace, but not in OB. >> How can we fix this? Just by including ECompletionOmniBrowser in the >> distribution? > > Yes, installing ECompletionOmniBrowser before OCompletion should do > the trick. > Also It didnt work in the workspace in the previous Pharo, but now it > seems ok. > Finally another bug has disappeared: duplication/shift of beginning > characters when completing directly (from 'aVar', I would get > 'aaVariable' when pressing tab if the first choice is ok - that was > annoying) > When did that one last disappear? It was supposed to be gone for a long time ... Romain > >> >> >> Romain >> >> On May 27, 2009, at 2:24 PM, Simon Denier wrote: >> >>> Hi Romain >>> >>> I didnt take time to notice you, but ECompletionOmniBrowser is >>> missing >>> in the Pharo distrib, hence it does not work at all in OB unless you >>> install it. >>> >>> >>> On 27 mai 09, at 13:31, Romain Robbes wrote: >>> >>>> Hi Ramiro, >>>> >>>> In which version was OCompletion not working for you? >>>> >>>> Romain >>>> >>>> On May 27, 2009, at 11:53 AM, Ramiro Diaz Trepat wrote: >>>> >>>>> Hi Damien, >>>>> A couple of trivial questions >>>>> Is OCompletion integrated in this version? In the previous >>>>> version >>>>> it had stopped suggesting. >>>>> Do you know if Seaside 2.9 works with the new Pharo / closures ? >>>>> Cheers, and thanks for all this great dev images. >>>>> >>>>> r. >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr >>>>> ] On Behalf Of Damien Cassou >>>>> Sent: 27 May 2009 10:50 >>>>> To: Pharo Development >>>>> Subject: [Pharo-project] New Pharo based on core 10318 with >>>>> antialiased fonts >>>>> >>>>> New Pharo: http://pharo-project.org/download >>>>> >>>>> -- >>>>> 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 >>>>> This email is confidential and subject to important disclaimers >>>>> and >>>>> conditions including on offers for the purchase or sale of >>>>> securities, accuracy and completeness of information, viruses, >>>>> confidentiality, legal privilege, and legal entity disclaimers, >>>>> available at http://www.jpmorgan.com/pages/disclosures/email. >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>> >>>> -- >>>> Romain Robbes >>>> http://www.inf.unisi.ch/phd/robbes >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> -- >>> Simon >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> Romain Robbes >> http://www.inf.unisi.ch/phd/robbes >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Romain Robbes http://www.inf.unisi.ch/phd/robbes

May 27, 2009

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

by Simon Denier

On 27 mai 09, at 14:49, Romain Robbes wrote: > Oh ok. Indeed I noticed it works in the workspace, but not in OB. > How can we fix this? Just by including ECompletionOmniBrowser in the > distribution? Yes, installing ECompletionOmniBrowser before OCompletion should do the trick. Also It didnt work in the workspace in the previous Pharo, but now it seems ok. Finally another bug has disappeared: duplication/shift of beginning characters when completing directly (from 'aVar', I would get 'aaVariable' when pressing tab if the first choice is ok - that was annoying) > > > Romain > > On May 27, 2009, at 2:24 PM, Simon Denier wrote: > >> Hi Romain >> >> I didnt take time to notice you, but ECompletionOmniBrowser is >> missing >> in the Pharo distrib, hence it does not work at all in OB unless you >> install it. >> >> >> On 27 mai 09, at 13:31, Romain Robbes wrote: >> >>> Hi Ramiro, >>> >>> In which version was OCompletion not working for you? >>> >>> Romain >>> >>> On May 27, 2009, at 11:53 AM, Ramiro Diaz Trepat wrote: >>> >>>> Hi Damien, >>>> A couple of trivial questions >>>> Is OCompletion integrated in this version? In the previous version >>>> it had stopped suggesting. >>>> Do you know if Seaside 2.9 works with the new Pharo / closures ? >>>> Cheers, and thanks for all this great dev images. >>>> >>>> r. >>>> >>>> >>>> -----Original Message----- >>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr >>>> ] On Behalf Of Damien Cassou >>>> Sent: 27 May 2009 10:50 >>>> To: Pharo Development >>>> Subject: [Pharo-project] New Pharo based on core 10318 with >>>> antialiased fonts >>>> >>>> New Pharo: http://pharo-project.org/download >>>> >>>> -- >>>> 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 >>>> This email is confidential and subject to important disclaimers and >>>> conditions including on offers for the purchase or sale of >>>> securities, accuracy and completeness of information, viruses, >>>> confidentiality, legal privilege, and legal entity disclaimers, >>>> available at http://www.jpmorgan.com/pages/disclosures/email. >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> Romain Robbes >>> http://www.inf.unisi.ch/phd/robbes >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Romain Robbes > http://www.inf.unisi.ch/phd/robbes > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Simon

May 27, 2009

[Pharo-project] Pharo and XML

by Torsten Bergmann

What's the status of XML support for pharo? Anyone tested if old (squeak) parsers work and what about xpath? @Alexandre: Whats the reason to put class "XMLParserTest" (a unit test) into the parser package instead of the XML testing package? (see XML-Parser-AlexandreBergel.15.mcz on 'http://www.squeaksource.com/XMLSupport') Thx T. -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

May 27, 2009

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

by Romain Robbes

Oh ok. Indeed I noticed it works in the workspace, but not in OB. How can we fix this? Just by including ECompletionOmniBrowser in the distribution? Romain On May 27, 2009, at 2:24 PM, Simon Denier wrote: > Hi Romain > > I didnt take time to notice you, but ECompletionOmniBrowser is missing > in the Pharo distrib, hence it does not work at all in OB unless you > install it. > > > On 27 mai 09, at 13:31, Romain Robbes wrote: > >> Hi Ramiro, >> >> In which version was OCompletion not working for you? >> >> Romain >> >> On May 27, 2009, at 11:53 AM, Ramiro Diaz Trepat wrote: >> >>> Hi Damien, >>> A couple of trivial questions >>> Is OCompletion integrated in this version? In the previous version >>> it had stopped suggesting. >>> Do you know if Seaside 2.9 works with the new Pharo / closures ? >>> Cheers, and thanks for all this great dev images. >>> >>> r. >>> >>> >>> -----Original Message----- >>> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr >>> ] On Behalf Of Damien Cassou >>> Sent: 27 May 2009 10:50 >>> To: Pharo Development >>> Subject: [Pharo-project] New Pharo based on core 10318 with >>> antialiased fonts >>> >>> New Pharo: http://pharo-project.org/download >>> >>> -- >>> 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 >>> This email is confidential and subject to important disclaimers and >>> conditions including on offers for the purchase or sale of >>> securities, accuracy and completeness of information, viruses, >>> confidentiality, legal privilege, and legal entity disclaimers, >>> available at http://www.jpmorgan.com/pages/disclosures/email. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> Romain Robbes >> http://www.inf.unisi.ch/phd/robbes >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Romain Robbes http://www.inf.unisi.ch/phd/robbes

May 27, 2009

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

by Torsten Bergmann

For Seaside 29, I've tested in newest 10318 (dev build from Damien). It's easy to install, just evaluate ScriptLoader loadSeaside29. ScriptLoader loadComanche The second one is necessary since the first one only loads the standard comanche without closure support. (this is how the standard seaside load test that is used here is implemented, maybe it assumes Squeak) So the second one loads the additional closure changes for comanche (newer comanche packages) to make it work with pharo. After that add a new adapter in the seaside control panel and point your browser to http://localhost:8080 So it is at least running ... Running the "Seaside-Tests-*" Tests gives 2 Errors in WAContinuationTest (#testNestedWhileTrue and #testWhileTrue) and 1 failure in WACodecTest (#testGenericCodecMacRoman) on a Win32 machine. Note the nice icons for WAComponent and friends in the OB Package Browser after loading ;) Bye Torsten -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

May 27, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Gabriel Cotelli

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 >

May 27, 2009