January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Fwd: DejaVu font from Cuis]

by Mariano Martinez Peck

2010/1/3 Alain Plantec <alain.plantec(a)free.fr> > > > Hi all, > > I've packaged the bitmap deja vu nice fonts from Cuis. > The Graphics-DejaVuFonts package is at http://www.squeaksource.com/DejaVu. > Font are installed when you load the package (available sizes are 5, 6, 7, > 8, 9, 10, 11, 12 14, 17 and 22). > It can be unloaded without any problem (font are kept in the image). > What I suggest would to keep them as default font set in the core and maybe > remove the accuny one. > (I can make a package for accuny also so that is would be reloadable if > needed). > what do you think ? > > Cool Alan!! I am really newbie with fonts. Would you mind explaining me the difference between the new Strike Fonts we have in the latest core images and this new fonts? They are just different fonts, no more than that? We will replace the Strike Fonts with these ? Cheers Mariano > Alain > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 3, 2010

[Pharo-project] [Fwd: DejaVu font from Cuis]

by Alain Plantec

Jan. 3, 2010

[Pharo-project] [update 1.1] #11133

by StÃ©phane Ducasse

11133 ----- - Issue 1735: Fixes for SMTPClient (mantis goran s code) - http://bugs.squeak.org/view.php?id=6843 by goran long time ago - Add an accessor for the localHostName in SMPTClient since Unix systems often return localhost.localdomain or 0.0.0.0 from NetNameResolver localHostName which is not accepted by many MTAs. If client code knows the name from elsewhere (by means of configuration etc.) it can provide it explicitly. by andreas raab

Jan. 3, 2010

Re: [Pharo-project] [Seaside] Mac VM 5.2b1 ships

by StÃ©phane Ducasse

Hi I asked abotu alien because at Amsterdam eliot used bird names to refer to FFI implementation. So I was thinking that building on top of Alien was a move into the future. May be you should talk with eliot. Stef > > 64-bit FFI will work on Unix and Windows with these fixes. I have not > tried Mac, but I expect that some work would be needed. The changes > are not trivial, and will affect the plugin, the VM itself, and the > Pharo/Squeak images. > > The next big fix on our VM-team "to-do list" is to get sound working > on 64-bit platforms, and FFI will come after that. > > I do not know the status of alien now, but my understanding is that > it is limited to intel processors and 32-bit platforms. My guess is > that it would be good to fix the old FFI first because those changes > would likely have an impact on alien also. But I do not know much > about alien, so I am not the best person to say. > > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 3, 2010

Re: [Pharo-project] FontChooser open -> DNU

by StÃ©phane Ducasse

On Jan 3, 2010, at 9:03 PM, Alain Plantec wrote: > StÃ©phane Ducasse a Ã©crit : >> Hi >> >> Adrian I will integrate your suggestion. >> Now I looked at all the Users of FontChooser and I tried to get one >> >> AbstractSettingDeclaration>>getFont >> ^ FontChooser >> openWithWindowTitle: 'Font for ' , self name >> for: self >> setSelector: #realValue: >> getSelector: #realValue >> >> does not work >> > yes it works. > It is used by the setting browser. Ok I was just executing the expression stupidly >> Then I looked at all the Users of FontChooserMorph >> >> openWithWindowTitle: titleString for: anObject setSelector: setSelector getSelector: getSelector >> "FontChooser openWithWindowTitle: 'Choose the Menu Font' for: Preferences setSelector: #setMenuFontTo: getSelector: #standardMenuFont" >> >> is doing a reference to Preferences? >> > It is the comment which was showing an example. > I will change this example. Yes this was my point because soon bye bye Preferences :) > Alain > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 3, 2010

Re: [Pharo-project] [Seaside] Mac VM 5.2b1 ships

by David T. Lewis

On Sun, Jan 03, 2010 at 08:58:41PM +0100, St?phane Ducasse wrote: > > On Jan 3, 2010, at 8:51 PM, David T. Lewis wrote: > > > On Sun, Jan 03, 2010 at 01:52:07PM +0100, Mariano Martinez Peck wrote: > >> Hi John! I have just download the vm and played for a while. I have a good > >> news and a bad one. > >> > >> The good news is that the bug of the double copy past seems to be gone away. > >> Maybe because what you said about "lack mac menu integration". I should > >> check because if then, when you do that, I have the double paste bug again, > >> at least we know where it comes from :) > >> > >> The bad news is that FFI is not working, but it is ok as you said the only > >> plugin you compile was FreeType and it seems to be working for me :) > > > > FFI will not work on any 64-bit VM. Details here: > > > > http://bugs.squeak.org/view.php?id=7237 > > http://lists.squeakfoundation.org/pipermail/vm-dev/2008-May/001945.html > > Dave > > Do you mean without your fixes? > BTW Do you know the status of alien on other platform than mac? 64-bit FFI will work on Unix and Windows with these fixes. I have not tried Mac, but I expect that some work would be needed. The changes are not trivial, and will affect the plugin, the VM itself, and the Pharo/Squeak images. The next big fix on our VM-team "to-do list" is to get sound working on 64-bit platforms, and FFI will come after that. I do not know the status of alien now, but my understanding is that it is limited to intel processors and 32-bit platforms. My guess is that it would be good to fix the old FFI first because those changes would likely have an impact on alien also. But I do not know much about alien, so I am not the best person to say. Dave

Jan. 3, 2010

Re: [Pharo-project] FontChooser open -> DNU

by Alain Plantec

StÃ©phane Ducasse a Ã©crit : > Hi > > Adrian I will integrate your suggestion. > Now I looked at all the Users of FontChooser and I tried to get one > > AbstractSettingDeclaration>>getFont > ^ FontChooser > openWithWindowTitle: 'Font for ' , self name > for: self > setSelector: #realValue: > getSelector: #realValue > > does not work > yes it works. It is used by the setting browser. > Then I looked at all the Users of FontChooserMorph > > openWithWindowTitle: titleString for: anObject setSelector: setSelector getSelector: getSelector > "FontChooser openWithWindowTitle: 'Choose the Menu Font' for: Preferences setSelector: #setMenuFontTo: getSelector: #standardMenuFont" > > is doing a reference to Preferences? > It is the comment which was showing an example. I will change this example. Alain

Jan. 3, 2010

Re: [Pharo-project] [Seaside] Mac VM 5.2b1 ships

by StÃ©phane Ducasse

On Jan 3, 2010, at 8:51 PM, David T. Lewis wrote: > On Sun, Jan 03, 2010 at 01:52:07PM +0100, Mariano Martinez Peck wrote: >> Hi John! I have just download the vm and played for a while. I have a good >> news and a bad one. >> >> The good news is that the bug of the double copy past seems to be gone away. >> Maybe because what you said about "lack mac menu integration". I should >> check because if then, when you do that, I have the double paste bug again, >> at least we know where it comes from :) >> >> The bad news is that FFI is not working, but it is ok as you said the only >> plugin you compile was FreeType and it seems to be working for me :) > > FFI will not work on any 64-bit VM. Details here: > > http://bugs.squeak.org/view.php?id=7237 > http://lists.squeakfoundation.org/pipermail/vm-dev/2008-May/001945.html Dave Do you mean without your fixes? BTW Do you know the status of alien on other platform than mac? Stef > > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 3, 2010

Re: [Pharo-project] [Seaside] Mac VM 5.2b1 ships

by David T. Lewis

On Sun, Jan 03, 2010 at 01:52:07PM +0100, Mariano Martinez Peck wrote: > Hi John! I have just download the vm and played for a while. I have a good > news and a bad one. > > The good news is that the bug of the double copy past seems to be gone away. > Maybe because what you said about "lack mac menu integration". I should > check because if then, when you do that, I have the double paste bug again, > at least we know where it comes from :) > > The bad news is that FFI is not working, but it is ok as you said the only > plugin you compile was FreeType and it seems to be working for me :) FFI will not work on any 64-bit VM. Details here: http://bugs.squeak.org/view.php?id=7237 http://lists.squeakfoundation.org/pipermail/vm-dev/2008-May/001945.html Dave

Jan. 3, 2010

Re: [Pharo-project] FontChooser open -> DNU

by StÃ©phane Ducasse

Hi Adrian I will integrate your suggestion. Now I looked at all the Users of FontChooser and I tried to get one AbstractSettingDeclaration>>getFont ^ FontChooser openWithWindowTitle: 'Font for ' , self name for: self setSelector: #realValue: getSelector: #realValue does not work Then I looked at all the Users of FontChooserMorph openWithWindowTitle: titleString for: anObject setSelector: setSelector getSelector: getSelector "FontChooser openWithWindowTitle: 'Choose the Menu Font' for: Preferences setSelector: #setMenuFontTo: getSelector: #standardMenuFont" is doing a reference to Preferences? Alain will probably fix that. Stef > It seems you cannot open a FontChooser like this because it expects a > setSelector, getSelector, and a receiver. > > See for instance the call in the method #chooseCodeFont. > > If called by FontChooser class>>open, some code fails that expects > these selectors and receiver being initialized. So maybe we should > just delete #open?! > > Cheers, > Adrian > > > On Jan 1, 2010, at 18:14 , StÃ©phane Ducasse wrote: > >> Hi guys >> >> Apparently FontChooser open raise an error >> >> http://code.google.com/p/pharo/issues/list?thanks=1728 >> >> Stef >> >> >> >> >> _______________________________________________ >> 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

Jan. 3, 2010