On 20 Nov 2013, at 15:45, Esteban A. Maringolo <[email protected]> wrote:
> 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? I have no idea, but huge white pane kills my eyes :) > > 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 <[email protected]>: >> btw... my goal is to achieve this: >> >> http://blog.jetbrains.com/blog/2013/06/11/inside-darcula-look-and-feel-an-interview-with-konstantin-bulenkov/ >> >> (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 <[email protected]> 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 <[email protected]> wrote: >>> >>>> >>>> On 20 Nov 2013, at 14:42, Esteban Lorenzano <[email protected]> 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 <[email protected]> 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 <[email protected]> >>>>>> wrote: >>>>>> >>>>>> On 20 Nov 2013, at 13:46, Esteban A. Maringolo <[email protected]> >>>>>> 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 <[email protected]> >>>>>>> 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 <[email protected]> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> >
