On 14 May 2014, at 17:33, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 14 May 2014, at 15:22, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Maybe it is not such bad idea to have it as default theme for Pharo 4, at least at the start. It's the best way to force people to report bugs in theming ;-)
thatâs the idea (and in part they are already). Problem is that there is an annoying bug around that prevent us to take them into account :) but yes, for Pharo4 they will be there.
oops⦠I misread (the problems of multitasking): I thought you were talking about the fonts (they will be there). So far, not the theme or the fonts are meant to be defaults, just to be available. Esteban
Esteban
-- Pavel
2014-05-14 15:01 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>: thanks for the nice comments. yes, Iâm working on making it something better that a hack (I will probably finish it next week). Then, we think on including it in a future update on Pharo 3. now⦠it will be available, but I do not think it will be the default theme. But it will be there for choosing it. Also, I think theme it-self still need some care, let me know your findings and I will fix it as soon as possible :)
for programatically, I have added a fonts.st fonts to the autoconfiguration of pharo
StartupLoader default executeAtomicItems: { StartupAction name: 'Fonts 3.0' code: [ | pointSize fontName codeFontName |
FreeTypeSystemSettings loadFt2Library: true. FreeTypeFontProvider current updateFromSystem.
pointSize := 10. fontName := 'Source Sans Pro'. codeFontName := 'Source Code Pro'. StandardFonts setAllStandardFontsTo: (LogicalFont familyName: fontName pointSize: pointSize); haloFont: (LogicalFont familyName: fontName pointSize: pointSize - 1); balloonFont: (LogicalFont familyName: fontName pointSize: pointSize - 1); windowTitleFont: (LogicalFont familyName: fontName pointSize: pointSize + 1); listFont: (LogicalFont familyName: fontName pointSize: pointSize); menuFont: (LogicalFont familyName: fontName pointSize: pointSize); codeFont: (LogicalFont familyName: codeFontName pointSize: pointSize) ] runOnce: true. }.
this is usually in:
OSX: ~/Library/Preferences/pharo/3.0 Linux: ~/.config/pharo/3.0 (Iâm not sure, but somewhere there) Windows: no idea :)
cheers, Esteban
On 14 May 2014, at 14:48, Goubier Thierry <thierry.goubier@cea.fr> wrote:
Le 14/05/2014 14:36, Esteban A. Maringolo a écrit :
2014-05-14 5:39 GMT-03:00 Sven Van Caekenberghe <sven@stfx.eu>:
Hi,
I have been using the new Pharo 3 Dark Theme since it was announced on May 1st. In my specific case, I am using the FreeType fonts Open Sans Regular 11 and Source Code Pro Regular 11 on a MacBookAir, both on the 13 inch 1440x900 built in screen and on a 23 inch 1920x1024 external monitor.
Every day there is a moment that I think: this looks so nice, this is so pleasant to use. Really Esteban, I don't know how you did it, but the color palette is really well chosen, plain beautiful. Let's make this either a permanent part of Pharo or an easy to load extension, real soon.
I want to say thanks too.
I'm using it since day one, it's easier for my eyes.
And even got somebody attention, who asked me what I was using...
I vote to make it permanent.
Regards!
ps: I'm using the default "DejaVu" fonts, how do you set the TTF font programatically?
I do it in the settings... and export them; However, when I rebuilt an image, I need to execute:
FreeTypeFontProvider current updateFromSystem
For the settings to apply.
Thierry
Esteban A. Maringolo
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95