- Pharo-dev - lists.pharo.org

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

by Simon Denier

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

May 27, 2009

[Pharo-project] a request for OB

by Alexandre Bergel

Hi David and other, When I load a Monticello package, I would really love to see it at the top of the list. Maybe a we could have 1 - Modified packages 2 - Loaded Packages 3 - Base system I happen to always use 'place at the top' on package that I load. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 27, 2009

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

by Ramiro Diaz Trepat

In the latest version before the one Damien published today. It was not working neither on the workspace nor on OmbiBrowser, although the underlining showed while typing. I can try the new image image when I get home tonight, and if you can't reproduce it, may be I can send you my image somehow. Cheers r. -----Original Message----- From: Romain Robbes [mailto:romain.robbes@lu.unisi.ch] Sent: 27 May 2009 12:32 To: Pharo-project(a)lists.gforge.inria.fr Development; Ramiro Diaz Trepat Subject: Re: [Pharo-project] New Pharo based on core 10318 with antialiased fonts 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 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.

May 27, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by StÃ©phane Ducasse

Indeed it may be useful to have the same verification. stef On May 27, 2009, at 1:51 PM, Alexandre Bergel wrote: > 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

[Pharo-project] SLICE-RelicensingPart1

by Alexandre Bergel

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

May 27, 2009

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

by Romain Robbes

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

May 27, 2009

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

by StÃ©phane Ducasse

Yes we should really have beta testers. Sorry for the bugs but knowing them is the only way to kill them. Stef On May 27, 2009, at 12:04 PM, Damien Cassou wrote: > On Wed, May 27, 2009 at 11:53 AM, Ramiro Diaz Trepat > <ramiro.diaz.trepat(a)jpmorgan.com> wrote: >> Is OCompletion integrated in this version? In the previous version >> it had stopped suggesting. > > It should work. If that's not the case please tell Romain Robbes > about it. > >> Do you know if Seaside 2.9 works with the new Pharo / closures ? > > It should work. Please report any problem on Pharo or Seaside > mailing lists. > > -- > 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 >

May 27, 2009

Re: [Pharo-project] windowsesque theme tweaks

by StÃ©phane Ducasse

cool :) Stef On May 27, 2009, at 11:43 AM, Gary Chambers wrote: > I'll integrate into Polymorph with some refactoring... > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Saturday, May 23, 2009 8:41 PM > Subject: Re: [Pharo-project] windowsesque theme tweaks > > >> gary I would like to include that in pharo (may be later we can >> package it better and more modular but for now, >> this is important not to lose it). >> So let me know. >> >> Stef >> >> On May 23, 2009, at 8:44 PM, Steve Wirts wrote: >> >>> Gary here's some tweaks I talked about (progressbar and tabbar >>> fixed). >>> After the attached is filedin, evaluate >>> >>> UIThemeXP setup >>> >>> then to see the tweaks try (progress bar) >>> >>> SystemProgressMorph example >>> >>> and (tab bar) >>> >>> UITheme exampleGroups >>> >>> also an odd thing that may hint at a bug, is >>> the progress bar moves faster while you move >>> the cursor. >>> >>> thanks. >>> sw >>> >>> <windowsesque.st>_______________________________________________ >>> 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] New Pharo based on core 10318 with antialiased fonts

by Damien Cassou

On Wed, May 27, 2009 at 11:53 AM, Ramiro Diaz Trepat <ramiro.diaz.trepat(a)jpmorgan.com> wrote: > Is OCompletion integrated in this version? Â In the previous version it had stopped suggesting. It should work. If that's not the case please tell Romain Robbes about it. > Do you know if Seaside 2.9 works with the new Pharo / closures ? It should work. Please report any problem on Pharo or Seaside mailing lists. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 27, 2009

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

by Ramiro Diaz Trepat

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.

May 27, 2009