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

Re: [Pharo-project] combo box?

by Gabriel Brunstein

cool!Gracias! (thanks!) On Fri, Aug 14, 2009 at 3:01 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > See this: > > UITheme exampleBasicControls. > UITheme exampleColorControls. > UITheme exampleDialogs. > UITheme exampleGroups. > UITheme exampleOtherControls. > UITheme exampleWindowWithToolbars. > > 2009/8/14 Gabriel Brunstein <gaboto(a)gmail.com> > >> anybody know how to do a combo box in pharo? any example to look? >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

Aug. 14, 2009

Re: [Pharo-project] combo box?

by Mariano Martinez Peck

See this: UITheme exampleBasicControls. UITheme exampleColorControls. UITheme exampleDialogs. UITheme exampleGroups. UITheme exampleOtherControls. UITheme exampleWindowWithToolbars. 2009/8/14 Gabriel Brunstein <gaboto(a)gmail.com> > anybody know how to do a combo box in pharo? any example to look? > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 14, 2009

Re: [Pharo-project] Fonts

by Mariano Martinez Peck

Alex: I don't know if I understand you, but FreeType has to scan for new installed or removed fonts. In the beginning this was done when the image was open. But as this takes several seconds and this were not something very common, it was removed from startup. However, as you can read here: http://code.google.com/p/pharo/wiki/CodeSnippets You can evaluate this to refresh the fonts: FreeTypeFontProvider current updateFromSystem Best, Mariano On Fri, Aug 14, 2009 at 3:45 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Dear List, > > In a core 10401, I copied the Font folder next to the image. When I > open the font chooser, one 'Accuny' is listed. Apparently, the font > folder is not scanned. Is there a way to enforce this? > > Few release earlier, the following expression worked as expected: > (LogicalFont familyName: 'Accuny' pointSize: 10) > widthOfString: > 'abc' => 20 > > In a 10401, an exception is raised: DNU ByteString>>between:and: > The error stems from: > -=-=-=-=-=-=-=-=-=-=-=-= > FreeTypeFontProvider>>fontInfoFor: aLogicalFont familyName: familyName > | family member | > ... > family := self families at: familyName ifAbsent:[]. > ... > -=-=-=-=-=-=-=-=-=-=-=-= > > familyName is expected to be a string apparently, but it is used as an > integer. > Is this a bug, or the protocol recently changed? > > 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 >

Aug. 14, 2009

[Pharo-project] combo box?

by Gabriel Brunstein

anybody know how to do a combo box in pharo? any example to look?

Aug. 14, 2009

Re: [Pharo-project] Incompatibilities was: #< if at first you dont succeed..

by Igor Stasenko

and besides, one could always redefine #new in subclasses to avoid calling #initialize 2009/8/14 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > A newbie - welcome! Â We're always happy to spread the addiction. Â To find out for yourself, do this: > > Â 1) open a workspace, type Object new. > Â 2) select the new text, right click and choose debug-it > Â 3) step into #new, and note that it take you to > Â Â Â Â ^self basicNew initialize > > At the risk of oversimplifying, that creates a no-frills instance and then invokes #initialize. Â Not all Smalltalks do this; it is either a bug or a feature depending on one's perspective, though I confess I have bigger things to worry about at present. > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Daniel P Zepeda > Sent: Friday, August 14, 2009 11:52 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] Incompatibilities was: #< if at first you dont succeed.. > > > On Aug 14, 2009, at 10:38 AM, Ken.Dickey wrote: > >> Squeak and Pharo already have some invompatabilities (e.g. not >> requiring #initialize after #new). > > I'm sort of a newbie, can you elaborate on not requiring #initialize after #new somewhat, or point me to where it is documented, I searched around a little bit, but quickly got lost. > > Thanks! > > DZ > > _______________________________________________ > 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 > -- Best regards, Igor Stasenko AKA sig.

Aug. 14, 2009

Re: [Pharo-project] Incompatibilities was: #< if at first you dont succeed..

by Schwab,Wilhelm K

A newbie - welcome! We're always happy to spread the addiction. To find out for yourself, do this: 1) open a workspace, type Object new. 2) select the new text, right click and choose debug-it 3) step into #new, and note that it take you to ^self basicNew initialize At the risk of oversimplifying, that creates a no-frills instance and then invokes #initialize. Not all Smalltalks do this; it is either a bug or a feature depending on one's perspective, though I confess I have bigger things to worry about at present. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Daniel P Zepeda Sent: Friday, August 14, 2009 11:52 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Incompatibilities was: #< if at first you dont succeed.. On Aug 14, 2009, at 10:38 AM, Ken.Dickey wrote: > Squeak and Pharo already have some invompatabilities (e.g. not > requiring #initialize after #new). I'm sort of a newbie, can you elaborate on not requiring #initialize after #new somewhat, or point me to where it is documented, I searched around a little bit, but quickly got lost. Thanks! DZ _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 14, 2009

Re: [Pharo-project] Incompatibilities was: #< if at first you dont succeed..

by Michael Roberts

A default implementation of new on the class sends initialize to the instance by default. All you need to do is implement the initialize method if you want to. Cheers mike On Friday, August 14, 2009, Daniel P Zepeda <daniel(a)zepeda.ws> wrote: > > On Aug 14, 2009, at 10:38 AM, Ken.Dickey wrote: > >> Squeak and Pharo already have some invompatabilities (e.g. not >> requiring >> #initialize after #new). > > I'm sort of a newbie, can you elaborate on not requiring #initialize > after #new somewhat, or point me to where it is documented, I searched > around a little bit, but quickly got lost. > > Thanks! > > DZ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 14, 2009

[Pharo-project] Incompatibilities was: #< if at first you dont succeed..

by Daniel P Zepeda

On Aug 14, 2009, at 10:38 AM, Ken.Dickey wrote: > Squeak and Pharo already have some invompatabilities (e.g. not > requiring > #initialize after #new). I'm sort of a newbie, can you elaborate on not requiring #initialize after #new somewhat, or point me to where it is documented, I searched around a little bit, but quickly got lost. Thanks! DZ

Aug. 14, 2009

[Pharo-project] Fonts

by Alexandre Bergel

Dear List, In a core 10401, I copied the Font folder next to the image. When I open the font chooser, one 'Accuny' is listed. Apparently, the font folder is not scanned. Is there a way to enforce this? Few release earlier, the following expression worked as expected: (LogicalFont familyName: 'Accuny' pointSize: 10) widthOfString: 'abc' => 20 In a 10401, an exception is raised: DNU ByteString>>between:and: The error stems from: -=-=-=-=-=-=-=-=-=-=-=-= FreeTypeFontProvider>>fontInfoFor: aLogicalFont familyName: familyName | family member | ... family := self families at: familyName ifAbsent:[]. ... -=-=-=-=-=-=-=-=-=-=-=-= familyName is expected to be a string apparently, but it is used as an integer. Is this a bug, or the protocol recently changed? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 14, 2009

Re: [Pharo-project] Complex number support discussion

by Schwab,Wilhelm K

Ken, All of us will welcome something that can do sophisticed mathematics, provided it does not break the base system when installed, and has no/limited runtime penalty when not needed. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Ken.Dickey Sent: Friday, August 14, 2009 10:38 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Complex number support discussion Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > A 2-10x performance hit is all the more reason why such a creation > should be dormant unless specifically invoked - translation, no > coercion into the controversial type. Â While there are uses for systems that are "smart" > enough to give exact answers, most computation happens in a world of > tolerances, with numbers that are not cherry picked for aesthetics. > > As somebody else (Sig perhaps) said, the behavior of the base system > magnitude classes should not change when a different package is loaded. > Â #asComplex is the gateway through which one can tell the system that > complex numbers are expected and desired. Â The more you write, the > more it becomes clear that there also would need to be a > #asComplexSymbolic or something to invoke behavior one might expect > from Maple and other symbolic systems. > > I strongly recommend starting with a numerical approach to a "closed > system" of complex numbers. Â GSL provides much of what should be > available, and can be mapped into Pharo by FFI/Alien. Â The result > would get used. Â If you then want to compete with Maple and > Mathematica, that really should be done separately. Â For examle, there > are times when I use logs to estimate the number of digits required to > hold a number, and if the argument is negative, I goofed and expect an error. Bill, My apologies for mixing a personal "philosophy discussion" into the Complex header. Â The Complex implementation does not suffer from the performance hit mentioned and as I stated earlier, I have no current desire to make Pharo into Mathematica. Â I would welcome a package which did this, however. -KenD _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 14, 2009