- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Spotlight behaviour

by kilon alios

oh and Sven just installed flux and tried it, brilliant thanks for the recommendation. Still does not beats dark themes, but certainly helps :) Halogen setting makes it easier to my eyes. On Wed, Nov 20, 2013 at 5:15 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > Esteban thats look great to me, I would have gone as far as turing the > background of text editor to pitch black but even this theme is more than > fine for me. So yes it will be wise to post your code to smalltalkhub and > let us help you out with this. I am most certainly be interested to > contribute , dark themes are essential to my coding workflow. > > Sven its not so much about brightness, I find white as color, tiresome , > especially when I read text. The curios thing is that my eyes get strained > only with the white on screen and not on paper, I always have my brightness > at lowest level. But in the end, black is my color. A drak theme is better > because its not just a lower lightness thing its also the correct contast > at least for my eyes. > > About icons its a valid concern, but not a big deal for me right now. > Pharo needs a good theme support, my project will hopefully bring this to > the table but it will take me a lot of time to get there. > > > On Wed, Nov 20, 2013 at 4:25 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> btw... my goal is to achieve this: >> >> >> http://blog.jetbrains.com/blog/2013/06/11/inside-darcula-look-and-feel-an-i… >> >> (as Phil suggested some time ago, in a thread which was the reason I >> started to try a dark theme). >> >> Also... my intention is to contribute to clean a bit morphic by removing >> silly hardcode stuff and creating a separation betweek "skin" and >> "morph"... and more important, to easy the creation of new skins. >> >> but I still do not find a design that satisfy me... we'll see. >> >> Esteban >> >> On Nov 20, 2013, at 3:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >> > ok... I will package it and made it available in the course of the day >> then. >> > more hands means faster results :) >> > >> > Esteban >> > >> > On Nov 20, 2013, at 2:53 PM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> > >> >> >> >> On 20 Nov 2013, at 14:42, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >> >> >>> :) >> >>> >> >>> <Screen Shot 2013-11-20 at 2.40.12 PM.png> >> >>> >> >>> I'm slowly working in a darktheme... problem is the INCREDIBLE amount >> of hardcode colors and silly code. >> >>> So it will take some time until is ready (also because I work on it >> when I'm bored and not wanting to do what I should do... like today :P) >> >> >> >> Hey, Esteban, that looks already quite impressive. >> >> I am sure there are some people really anxious to try this and help. >> >> Is this theme already available somewhere ? >> >> >> >>> Esteban >> >>> >> >>> >> >>> On Nov 20, 2013, at 2:34 PM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> >>> >> >>>> yes I can confirm that this work also on windoom 7. Indeed Sven your >> Pharo looks a bit more sexy than mine. >> >>>> >> >>>> the code you posted works also like a charm for me , thank you. Now >> If I could get also a dark theme working with pharo that would be awesome. >> All this white hurts my eyes. But I guess I will have to compromise for the >> time being :) >> >>>> >> >>>> thank you >> >>>> >> >>>> >> >>>> On Wed, Nov 20, 2013 at 2:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> >>>> >> >>>> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <emaringolo(a)gmail.com> >> wrote: >> >>>> >> >>>>> Sven. >> >>>>> >> >>>>> What version are YOU using? Fonts and windows look so clean an >> sharp! :) >> >>>> >> >>>> ;-) >> >>>> >> >>>> Yes they are. >> >>>> >> >>>> Like I said, Pharo version #30582 >> >>>> >> >>>> defaultFont Source Sans Pro Normal points: 12 height: 21 >> >>>> listFont Source Sans Pro Normal points: 12 height: 21 >> >>>> menuFont Source Sans Pro Normal points: 12 height: 21 >> >>>> windowTitleFont Source Sans Pro Bold points: 12 height: 21 >> >>>> balloonFont Source Sans Pro Normal points: 9 height: 16 >> >>>> codeFont Source Code Pro Normal points: 11 height: 19 >> >>>> buttonFont Source Sans Pro Normal points: 12 height: 21 >> >>>> haloFont Source Sans Pro Normal points: 9 height: 16 >> >>>> >> >>>> Installed with a script from our local look and feel guru, Doru: >> >>>> >> >>>> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' >> 'SourceSansProBoldâ) >> >>>> do: [ :each | >> >>>> Smalltalk globals >> >>>> at: each asSymbol >> >>>> ifAbsent: [ >> >>>> Gofer new >> >>>> smalltalkhubUser: 'girba' project: 'FreeFonts'; >> >>>> package: each; >> >>>> load ]. >> >>>> (Smalltalk at: each asSymbol) new install ]. >> >>>> FreeTypeSystemSettings loadFt2Library: true. >> >>>> FreeTypeFontProvider current updateFromSystem. >> >>>> >> >>>> StandardFonts >> >>>> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' >> pointSize: 12); >> >>>> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >> >>>> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro Bold' >> pointSize: 12); >> >>>> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: >> 9); >> >>>> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 11). >> >>>> >> >>>> And then I finally make the window font bold, manually. >> >>>> >> >>>> The screenshot was done on Mac OS X 10.9 >> >>>> >> >>>> HTH, >> >>>> >> >>>> Sven >> >>>> >> >>>>> Esteban A. Maringolo >> >>>>> >> >>>>> >> >>>>> 2013/11/20 Sven Van Caekenberghe <sven(a)stfx.eu> >> >>>>> What version are you using ? >> >>>>> >> >>>>> In #30582 it does work: >> >>>>> <Screen Shot 2013-11-20 at 13.34.46.png> >> >>>>> >> >>>>> You can always try typing a space after Objectâ¦ >> >>>>> >> >>>>> Sven >> >>>>> >> >>>>> On 20 Nov 2013, at 13:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> wrote: >> >>>>> >> >>>>>> HI, >> >>>>>> >> >>>>>> do you know why search behaves like this? I was expecting Object >> to show up >> >>>>>> >> >>>>>> <Screenshot 2013-11-20 13.20.40.png> >> >>>>>> >> >>>>>> >> >>>>>> Cheers >> >>>>>> Uko >> >>>>> >> >>>>> >> >>>> >> >>>> >> >>>> >> >>> >> >> >> >> >> > >> >> >> >

Nov. 20, 2013

Re: [Pharo-dev] Periscope for Pharo 3.0

by Juraj Kubelka

Thank you, Pavel! Jura El 20-11-2013, a las 11:32, Pavel Krivanek <pavel.krivanek(a)gmail.com> escribiÃ³: > Hi, > > I made Periscope update that works in Pharo 3.0. To try it simply open Configuration Browser and simply load stable version of the Periscope project. > > Cheers, > -- Pavel

Nov. 20, 2013

Re: [Pharo-dev] Spotlight behaviour

by kilon alios

Esteban thats look great to me, I would have gone as far as turing the background of text editor to pitch black but even this theme is more than fine for me. So yes it will be wise to post your code to smalltalkhub and let us help you out with this. I am most certainly be interested to contribute , dark themes are essential to my coding workflow. Sven its not so much about brightness, I find white as color, tiresome , especially when I read text. The curios thing is that my eyes get strained only with the white on screen and not on paper, I always have my brightness at lowest level. But in the end, black is my color. A drak theme is better because its not just a lower lightness thing its also the correct contast at least for my eyes. About icons its a valid concern, but not a big deal for me right now. Pharo needs a good theme support, my project will hopefully bring this to the table but it will take me a lot of time to get there. On Wed, Nov 20, 2013 at 4:25 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > btw... my goal is to achieve this: > > > http://blog.jetbrains.com/blog/2013/06/11/inside-darcula-look-and-feel-an-i… > > (as Phil suggested some time ago, in a thread which was the reason I > started to try a dark theme). > > Also... my intention is to contribute to clean a bit morphic by removing > silly hardcode stuff and creating a separation betweek "skin" and > "morph"... and more important, to easy the creation of new skins. > > but I still do not find a design that satisfy me... we'll see. > > Esteban > > On Nov 20, 2013, at 3:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > ok... I will package it and made it available in the course of the day > then. > > more hands means faster results :) > > > > Esteban > > > > On Nov 20, 2013, at 2:53 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> > >> On 20 Nov 2013, at 14:42, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> > >>> :) > >>> > >>> <Screen Shot 2013-11-20 at 2.40.12 PM.png> > >>> > >>> I'm slowly working in a darktheme... problem is the INCREDIBLE amount > of hardcode colors and silly code. > >>> So it will take some time until is ready (also because I work on it > when I'm bored and not wanting to do what I should do... like today :P) > >> > >> Hey, Esteban, that looks already quite impressive. > >> I am sure there are some people really anxious to try this and help. > >> Is this theme already available somewhere ? > >> > >>> Esteban > >>> > >>> > >>> On Nov 20, 2013, at 2:34 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > >>> > >>>> yes I can confirm that this work also on windoom 7. Indeed Sven your > Pharo looks a bit more sexy than mine. > >>>> > >>>> the code you posted works also like a charm for me , thank you. Now > If I could get also a dark theme working with pharo that would be awesome. > All this white hurts my eyes. But I guess I will have to compromise for the > time being :) > >>>> > >>>> thank you > >>>> > >>>> > >>>> On Wed, Nov 20, 2013 at 2:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >>>> > >>>> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > >>>> > >>>>> Sven. > >>>>> > >>>>> What version are YOU using? Fonts and windows look so clean an > sharp! :) > >>>> > >>>> ;-) > >>>> > >>>> Yes they are. > >>>> > >>>> Like I said, Pharo version #30582 > >>>> > >>>> defaultFont Source Sans Pro Normal points: 12 height: 21 > >>>> listFont Source Sans Pro Normal points: 12 height: 21 > >>>> menuFont Source Sans Pro Normal points: 12 height: 21 > >>>> windowTitleFont Source Sans Pro Bold points: 12 height: 21 > >>>> balloonFont Source Sans Pro Normal points: 9 height: 16 > >>>> codeFont Source Code Pro Normal points: 11 height: 19 > >>>> buttonFont Source Sans Pro Normal points: 12 height: 21 > >>>> haloFont Source Sans Pro Normal points: 9 height: 16 > >>>> > >>>> Installed with a script from our local look and feel guru, Doru: > >>>> > >>>> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' > 'SourceSansProBoldâ) > >>>> do: [ :each | > >>>> Smalltalk globals > >>>> at: each asSymbol > >>>> ifAbsent: [ > >>>> Gofer new > >>>> smalltalkhubUser: 'girba' project: 'FreeFonts'; > >>>> package: each; > >>>> load ]. > >>>> (Smalltalk at: each asSymbol) new install ]. > >>>> FreeTypeSystemSettings loadFt2Library: true. > >>>> FreeTypeFontProvider current updateFromSystem. > >>>> > >>>> StandardFonts > >>>> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' > pointSize: 12); > >>>> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); > >>>> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro Bold' > pointSize: 12); > >>>> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); > >>>> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 11). > >>>> > >>>> And then I finally make the window font bold, manually. > >>>> > >>>> The screenshot was done on Mac OS X 10.9 > >>>> > >>>> HTH, > >>>> > >>>> Sven > >>>> > >>>>> Esteban A. Maringolo > >>>>> > >>>>> > >>>>> 2013/11/20 Sven Van Caekenberghe <sven(a)stfx.eu> > >>>>> What version are you using ? > >>>>> > >>>>> In #30582 it does work: > >>>>> <Screen Shot 2013-11-20 at 13.34.46.png> > >>>>> > >>>>> You can always try typing a space after Objectâ¦ > >>>>> > >>>>> Sven > >>>>> > >>>>> On 20 Nov 2013, at 13:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >>>>> > >>>>>> HI, > >>>>>> > >>>>>> do you know why search behaves like this? I was expecting Object to > show up > >>>>>> > >>>>>> <Screenshot 2013-11-20 13.20.40.png> > >>>>>> > >>>>>> > >>>>>> Cheers > >>>>>> Uko > >>>>> > >>>>> > >>>> > >>>> > >>>> > >>> > >> > >> > > > > >

Nov. 20, 2013

Re: [Pharo-dev] Spotlight behaviour

by Esteban A. Maringolo

The problem with dark themes is that they require icons prepared for dark backgrounds. And not only in terms of alpha channels, but also in terms of contrast. I like the dark theming of Adobe products, or the "gray" theming of video editing software. But I once read that it was made dark to give prominence to the subject of the editor, in this case pictures and videos. Sublime Text and even Vim can afford this, because they're code pane centric editors. In our case, what should have the prominence? The code pane? the selectors in the browser? Anyhow, I like the fact Pharo looks better and better. I'd only want that no operation other than painting/event dispatching take place in the main (UI?) thread. :) Regards, Esteban A. Maringolo 2013/11/20 Esteban Lorenzano <estebanlm(a)gmail.com>: > btw... my goal is to achieve this: > > http://blog.jetbrains.com/blog/2013/06/11/inside-darcula-look-and-feel-an-i… > > (as Phil suggested some time ago, in a thread which was the reason I started to try a dark theme). > > Also... my intention is to contribute to clean a bit morphic by removing silly hardcode stuff and creating a separation betweek "skin" and "morph"... and more important, to easy the creation of new skins. > > but I still do not find a design that satisfy me... we'll see. > > Esteban > > On Nov 20, 2013, at 3:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> ok... I will package it and made it available in the course of the day then. >> more hands means faster results :) >> >> Esteban >> >> On Nov 20, 2013, at 2:53 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> On 20 Nov 2013, at 14:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> :) >>>> >>>> <Screen Shot 2013-11-20 at 2.40.12 PM.png> >>>> >>>> I'm slowly working in a darktheme... problem is the INCREDIBLE amount of hardcode colors and silly code. >>>> So it will take some time until is ready (also because I work on it when I'm bored and not wanting to do what I should do... like today :P) >>> >>> Hey, Esteban, that looks already quite impressive. >>> I am sure there are some people really anxious to try this and help. >>> Is this theme already available somewhere ? >>> >>>> Esteban >>>> >>>> >>>> On Nov 20, 2013, at 2:34 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >>>> >>>>> yes I can confirm that this work also on windoom 7. Indeed Sven your Pharo looks a bit more sexy than mine. >>>>> >>>>> the code you posted works also like a charm for me , thank you. Now If I could get also a dark theme working with pharo that would be awesome. All this white hurts my eyes. But I guess I will have to compromise for the time being :) >>>>> >>>>> thank you >>>>> >>>>> >>>>> On Wed, Nov 20, 2013 at 2:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> >>>>> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>>> >>>>>> Sven. >>>>>> >>>>>> What version are YOU using? Fonts and windows look so clean an sharp! :) >>>>> >>>>> ;-) >>>>> >>>>> Yes they are. >>>>> >>>>> Like I said, Pharo version #30582 >>>>> >>>>> defaultFont Source Sans Pro Normal points: 12 height: 21 >>>>> listFont Source Sans Pro Normal points: 12 height: 21 >>>>> menuFont Source Sans Pro Normal points: 12 height: 21 >>>>> windowTitleFont Source Sans Pro Bold points: 12 height: 21 >>>>> balloonFont Source Sans Pro Normal points: 9 height: 16 >>>>> codeFont Source Code Pro Normal points: 11 height: 19 >>>>> buttonFont Source Sans Pro Normal points: 12 height: 21 >>>>> haloFont Source Sans Pro Normal points: 9 height: 16 >>>>> >>>>> Installed with a script from our local look and feel guru, Doru: >>>>> >>>>> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBoldâ) >>>>> do: [ :each | >>>>> Smalltalk globals >>>>> at: each asSymbol >>>>> ifAbsent: [ >>>>> Gofer new >>>>> smalltalkhubUser: 'girba' project: 'FreeFonts'; >>>>> package: each; >>>>> load ]. >>>>> (Smalltalk at: each asSymbol) new install ]. >>>>> FreeTypeSystemSettings loadFt2Library: true. >>>>> FreeTypeFontProvider current updateFromSystem. >>>>> >>>>> StandardFonts >>>>> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 12); >>>>> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>>>> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro Bold' pointSize: 12); >>>>> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>>>> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 11). >>>>> >>>>> And then I finally make the window font bold, manually. >>>>> >>>>> The screenshot was done on Mac OS X 10.9 >>>>> >>>>> HTH, >>>>> >>>>> Sven >>>>> >>>>>> Esteban A. Maringolo >>>>>> >>>>>> >>>>>> 2013/11/20 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>>> What version are you using ? >>>>>> >>>>>> In #30582 it does work: >>>>>> <Screen Shot 2013-11-20 at 13.34.46.png> >>>>>> >>>>>> You can always try typing a space after Objectâ¦ >>>>>> >>>>>> Sven >>>>>> >>>>>> On 20 Nov 2013, at 13:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>>>> >>>>>>> HI, >>>>>>> >>>>>>> do you know why search behaves like this? I was expecting Object to show up >>>>>>> >>>>>>> <Screenshot 2013-11-20 13.20.40.png> >>>>>>> >>>>>>> >>>>>>> Cheers >>>>>>> Uko >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >> > >

Nov. 20, 2013

Re: [Pharo-dev] Tuning Opal Optimizations

by Igor Stasenko

On 19 November 2013 16:20, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 19 Nov 2013, at 16:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > Hi, > > > > It seems that #timesRepeat: is compiled/optimized away by Opal, which is > probably good. BTW, what is the list of selectors that get this treatment ? > > > RBMessageNode has #isInlined that returns trueâ¦ not all cases where the > selector is send it is optimised, so a list would be one of > âpossiblyoptimizedâ selectorsâ¦ > maybe #isInlined could check first against that list to quickly return > false for all the other selectors. > > > In the PEGParser example of Xtreams #timesRepeat: is implemented for a > non Integer class, which obviously leads to errors. > > > oh, yes, that is a problem. We started for ifTrue: to do an on-the-fly > re-compiling and executing the ifTrue:, but itâs a bit of work to get it > right for all casesâ¦ so we did not finish > that. But it would be possible... > > > Is there a way to tune this ? > > Can it be set at a level higher than in each method ? > > > > Yes, you can do it per class-hierarchyâ¦ you can implement on the class > side a method to parametrize the compiler: > > compiler > ^super compiler options: #(- optionInlineTimesRepeat) > > .. and i feel really glad that Marcus armed my idea of option specification e.g. #(+ optionToEnable1 - optionToDisable anotherOptionToDisable + optionToEnable2 ) :) > Marcus > > > > -- Best regards, Igor Stasenko.

Nov. 20, 2013

Re: [Pharo-dev] Spotlight behaviour

by Pavel Krivanek

You can get interesting results when you play a little bit with Color class. It's Smalltalk ;-) -- Pavel 2013/11/20 Esteban Lorenzano <estebanlm(a)gmail.com> > ok... I will package it and made it available in the course of the day > then. > more hands means faster results :) > > Esteban > > On Nov 20, 2013, at 2:53 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > On 20 Nov 2013, at 14:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > >> :) > >> > >> <Screen Shot 2013-11-20 at 2.40.12 PM.png> > >> > >> I'm slowly working in a darktheme... problem is the INCREDIBLE amount > of hardcode colors and silly code. > >> So it will take some time until is ready (also because I work on it > when I'm bored and not wanting to do what I should do... like today :P) > > > > Hey, Esteban, that looks already quite impressive. > > I am sure there are some people really anxious to try this and help. > > Is this theme already available somewhere ? > > > >> Esteban > >> > >> > >> On Nov 20, 2013, at 2:34 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > >> > >>> yes I can confirm that this work also on windoom 7. Indeed Sven your > Pharo looks a bit more sexy than mine. > >>> > >>> the code you posted works also like a charm for me , thank you. Now If > I could get also a dark theme working with pharo that would be awesome. All > this white hurts my eyes. But I guess I will have to compromise for the > time being :) > >>> > >>> thank you > >>> > >>> > >>> On Wed, Nov 20, 2013 at 2:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >>> > >>> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > >>> > >>>> Sven. > >>>> > >>>> What version are YOU using? Fonts and windows look so clean an sharp! > :) > >>> > >>> ;-) > >>> > >>> Yes they are. > >>> > >>> Like I said, Pharo version #30582 > >>> > >>> defaultFont Source Sans Pro Normal points: 12 height: 21 > >>> listFont Source Sans Pro Normal points: 12 height: 21 > >>> menuFont Source Sans Pro Normal points: 12 height: 21 > >>> windowTitleFont Source Sans Pro Bold points: 12 height: 21 > >>> balloonFont Source Sans Pro Normal points: 9 height: 16 > >>> codeFont Source Code Pro Normal points: 11 height: 19 > >>> buttonFont Source Sans Pro Normal points: 12 height: 21 > >>> haloFont Source Sans Pro Normal points: 9 height: 16 > >>> > >>> Installed with a script from our local look and feel guru, Doru: > >>> > >>> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' > 'SourceSansProBoldâ) > >>> do: [ :each | > >>> Smalltalk globals > >>> at: each asSymbol > >>> ifAbsent: [ > >>> Gofer new > >>> smalltalkhubUser: 'girba' project: 'FreeFonts'; > >>> package: each; > >>> load ]. > >>> (Smalltalk at: each asSymbol) new install ]. > >>> FreeTypeSystemSettings loadFt2Library: true. > >>> FreeTypeFontProvider current updateFromSystem. > >>> > >>> StandardFonts > >>> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' > pointSize: 12); > >>> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); > >>> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro Bold' > pointSize: 12); > >>> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); > >>> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 11). > >>> > >>> And then I finally make the window font bold, manually. > >>> > >>> The screenshot was done on Mac OS X 10.9 > >>> > >>> HTH, > >>> > >>> Sven > >>> > >>>> Esteban A. Maringolo > >>>> > >>>> > >>>> 2013/11/20 Sven Van Caekenberghe <sven(a)stfx.eu> > >>>> What version are you using ? > >>>> > >>>> In #30582 it does work: > >>>> <Screen Shot 2013-11-20 at 13.34.46.png> > >>>> > >>>> You can always try typing a space after Objectâ¦ > >>>> > >>>> Sven > >>>> > >>>> On 20 Nov 2013, at 13:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >>>> > >>>>> HI, > >>>>> > >>>>> do you know why search behaves like this? I was expecting Object to > show up > >>>>> > >>>>> <Screenshot 2013-11-20 13.20.40.png> > >>>>> > >>>>> > >>>>> Cheers > >>>>> Uko > >>>> > >>>> > >>> > >>> > >>> > >> > > > > > > >

Nov. 20, 2013

Periscope for Pharo 3.0

by Pavel Krivanek

Hi, I made Periscope update that works in Pharo 3.0. To try it simply open Configuration Browser and simply load stable version of the Periscope project. Cheers, -- Pavel

Nov. 20, 2013

Re: [Pharo-dev] Spotlight behaviour

by Esteban Lorenzano

btw... my goal is to achieve this: http://blog.jetbrains.com/blog/2013/06/11/inside-darcula-look-and-feel-an-i… (as Phil suggested some time ago, in a thread which was the reason I started to try a dark theme). Also... my intention is to contribute to clean a bit morphic by removing silly hardcode stuff and creating a separation betweek "skin" and "morph"... and more important, to easy the creation of new skins. but I still do not find a design that satisfy me... we'll see. Esteban On Nov 20, 2013, at 3:18 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > ok... I will package it and made it available in the course of the day then. > more hands means faster results :) > > Esteban > > On Nov 20, 2013, at 2:53 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 20 Nov 2013, at 14:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> :) >>> >>> <Screen Shot 2013-11-20 at 2.40.12 PM.png> >>> >>> I'm slowly working in a darktheme... problem is the INCREDIBLE amount of hardcode colors and silly code. >>> So it will take some time until is ready (also because I work on it when I'm bored and not wanting to do what I should do... like today :P) >> >> Hey, Esteban, that looks already quite impressive. >> I am sure there are some people really anxious to try this and help. >> Is this theme already available somewhere ? >> >>> Esteban >>> >>> >>> On Nov 20, 2013, at 2:34 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >>> >>>> yes I can confirm that this work also on windoom 7. Indeed Sven your Pharo looks a bit more sexy than mine. >>>> >>>> the code you posted works also like a charm for me , thank you. Now If I could get also a dark theme working with pharo that would be awesome. All this white hurts my eyes. But I guess I will have to compromise for the time being :) >>>> >>>> thank you >>>> >>>> >>>> On Wed, Nov 20, 2013 at 2:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>> >>>>> Sven. >>>>> >>>>> What version are YOU using? Fonts and windows look so clean an sharp! :) >>>> >>>> ;-) >>>> >>>> Yes they are. >>>> >>>> Like I said, Pharo version #30582 >>>> >>>> defaultFont Source Sans Pro Normal points: 12 height: 21 >>>> listFont Source Sans Pro Normal points: 12 height: 21 >>>> menuFont Source Sans Pro Normal points: 12 height: 21 >>>> windowTitleFont Source Sans Pro Bold points: 12 height: 21 >>>> balloonFont Source Sans Pro Normal points: 9 height: 16 >>>> codeFont Source Code Pro Normal points: 11 height: 19 >>>> buttonFont Source Sans Pro Normal points: 12 height: 21 >>>> haloFont Source Sans Pro Normal points: 9 height: 16 >>>> >>>> Installed with a script from our local look and feel guru, Doru: >>>> >>>> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBoldâ) >>>> do: [ :each | >>>> Smalltalk globals >>>> at: each asSymbol >>>> ifAbsent: [ >>>> Gofer new >>>> smalltalkhubUser: 'girba' project: 'FreeFonts'; >>>> package: each; >>>> load ]. >>>> (Smalltalk at: each asSymbol) new install ]. >>>> FreeTypeSystemSettings loadFt2Library: true. >>>> FreeTypeFontProvider current updateFromSystem. >>>> >>>> StandardFonts >>>> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 12); >>>> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>>> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro Bold' pointSize: 12); >>>> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>>> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 11). >>>> >>>> And then I finally make the window font bold, manually. >>>> >>>> The screenshot was done on Mac OS X 10.9 >>>> >>>> HTH, >>>> >>>> Sven >>>> >>>>> Esteban A. Maringolo >>>>> >>>>> >>>>> 2013/11/20 Sven Van Caekenberghe <sven(a)stfx.eu> >>>>> What version are you using ? >>>>> >>>>> In #30582 it does work: >>>>> <Screen Shot 2013-11-20 at 13.34.46.png> >>>>> >>>>> You can always try typing a space after Objectâ¦ >>>>> >>>>> Sven >>>>> >>>>> On 20 Nov 2013, at 13:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>>> >>>>>> HI, >>>>>> >>>>>> do you know why search behaves like this? I was expecting Object to show up >>>>>> >>>>>> <Screenshot 2013-11-20 13.20.40.png> >>>>>> >>>>>> >>>>>> Cheers >>>>>> Uko >>>>> >>>>> >>>> >>>> >>>> >>> >> >> >

Nov. 20, 2013

Re: [Pharo-dev] Spotlight behaviour

by Esteban Lorenzano

ok... I will package it and made it available in the course of the day then. more hands means faster results :) Esteban On Nov 20, 2013, at 2:53 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 20 Nov 2013, at 14:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> :) >> >> <Screen Shot 2013-11-20 at 2.40.12 PM.png> >> >> I'm slowly working in a darktheme... problem is the INCREDIBLE amount of hardcode colors and silly code. >> So it will take some time until is ready (also because I work on it when I'm bored and not wanting to do what I should do... like today :P) > > Hey, Esteban, that looks already quite impressive. > I am sure there are some people really anxious to try this and help. > Is this theme already available somewhere ? > >> Esteban >> >> >> On Nov 20, 2013, at 2:34 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >> >>> yes I can confirm that this work also on windoom 7. Indeed Sven your Pharo looks a bit more sexy than mine. >>> >>> the code you posted works also like a charm for me , thank you. Now If I could get also a dark theme working with pharo that would be awesome. All this white hurts my eyes. But I guess I will have to compromise for the time being :) >>> >>> thank you >>> >>> >>> On Wed, Nov 20, 2013 at 2:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> >>>> Sven. >>>> >>>> What version are YOU using? Fonts and windows look so clean an sharp! :) >>> >>> ;-) >>> >>> Yes they are. >>> >>> Like I said, Pharo version #30582 >>> >>> defaultFont Source Sans Pro Normal points: 12 height: 21 >>> listFont Source Sans Pro Normal points: 12 height: 21 >>> menuFont Source Sans Pro Normal points: 12 height: 21 >>> windowTitleFont Source Sans Pro Bold points: 12 height: 21 >>> balloonFont Source Sans Pro Normal points: 9 height: 16 >>> codeFont Source Code Pro Normal points: 11 height: 19 >>> buttonFont Source Sans Pro Normal points: 12 height: 21 >>> haloFont Source Sans Pro Normal points: 9 height: 16 >>> >>> Installed with a script from our local look and feel guru, Doru: >>> >>> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBoldâ) >>> do: [ :each | >>> Smalltalk globals >>> at: each asSymbol >>> ifAbsent: [ >>> Gofer new >>> smalltalkhubUser: 'girba' project: 'FreeFonts'; >>> package: each; >>> load ]. >>> (Smalltalk at: each asSymbol) new install ]. >>> FreeTypeSystemSettings loadFt2Library: true. >>> FreeTypeFontProvider current updateFromSystem. >>> >>> StandardFonts >>> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 12); >>> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro Bold' pointSize: 12); >>> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 9); >>> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 11). >>> >>> And then I finally make the window font bold, manually. >>> >>> The screenshot was done on Mac OS X 10.9 >>> >>> HTH, >>> >>> Sven >>> >>>> Esteban A. Maringolo >>>> >>>> >>>> 2013/11/20 Sven Van Caekenberghe <sven(a)stfx.eu> >>>> What version are you using ? >>>> >>>> In #30582 it does work: >>>> <Screen Shot 2013-11-20 at 13.34.46.png> >>>> >>>> You can always try typing a space after Objectâ¦ >>>> >>>> Sven >>>> >>>> On 20 Nov 2013, at 13:23, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>> >>>>> HI, >>>>> >>>>> do you know why search behaves like this? I was expecting Object to show up >>>>> >>>>> <Screenshot 2013-11-20 13.20.40.png> >>>>> >>>>> >>>>> Cheers >>>>> Uko >>>> >>>> >>> >>> >>> >> > >

Nov. 20, 2013

Re: [Pharo-dev] Spotlight behaviour

by Sven Van Caekenberghe

On 20 Nov 2013, at 14:34, kilon alios <kilon.alios(a)gmail.com> wrote: > All this white hurts my eyes. One thing you could try is to use a tool like f.lux (http://justgetflux.com) It adjusts the color temperature of your display according to the time of day, so that is bluer/harder when it is daylight and orange/softer when it is night (manipulating gamma). It is pretty cool. Sven

Nov. 20, 2013