On 01 May 2014, at 14:07, Sven Van Caekenberghe <[email protected]> wrote:
> Wow! > > This will make a couple of people very happy, and it is quite impressive. thanks! yes I made it for Phil and Yuriy :) > > Seriously, you found time to finish this while labouring during days on the > Pharo 3 release, are you sure you are not extra-terrestial ? well.. there were some dead moments while waiting for things to be ready (but I wasn’t able to work on more complicated things, I needed to keep my concentration on the release)… and then I have insomnia :P Esteban > > Works like a charm : > > <Screen Shot 2014-05-01 at 14.03.07.png> > > Thanks. > > Sven > > PS: Yes, we should do the effort to make it possible to do this for real > (clean). > > On 01 May 2014, at 13:24, Esteban Lorenzano <[email protected]> wrote: > >> Dark Theme for Pharo 3 >> ================== >> >> So, I finally took some time and hacked a Dark Theme for Pharo 3: >> >> <Screen Shot 2014-05-01 at 13.11.57.png> >> >> How you install it? You need to execute this script: >> >> “1. You need this because otherwise Gofer merge becomes dumb :P" >> MCRepositoryGroup default >> addRepository: (MCSmalltalkhubRepository >> owner: 'estebanlm' >> project: 'Pharo3DarkTheme'). >> “2. Now we can actually MERGE the project" >> Gofer it >> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; >> package: 'Pharo3DarkTheme'; >> merge. >> “3. And then install it" >> Pharo3DarkTheme installFullTheme. >> >> WARNING 1: You need to do a merge (notice the script) >> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. >> WARNING 3: This changes something in the Pharo3Theme too... so you can go >> back after installing, but not completely :) >> >> Considerations >> -------------- >> >> It can look like an easy task, to make a theme over a non native GUI like >> Pharo, but let me tell you: It is not. There are a lot of glitches and >> errors of design you have to overcome to get a working version of a theme. >> This is a pitty because we claim that our system is clean (or should be >> clean) and easy to understand. >> >> But all the Morphic implementation is a hack over a hack, with preconcepts >> and hardcodes everywhere, up to a point that to make the smallest change is >> an incredibly annoying task. >> >> Then... I added ""yet another hack"" to this infinite list. I made it >> because we need something like this, even if not a good solution. And I also >> made it to start a debate into our community. I truly believe that Morphic >> was a great idea, but I also believe that current implementation is doomed. >> I would like to discuss a new implementation, with a good design (for >> example I believe it should be a clear separation between a morph and it's >> skin, making easy the actual-hard task of changing a colorset). >> I also believe there will be a clear separation between what is a Morph (a >> graphical unit) and a Widget (who at the time should use morphs, but that's >> another story). >> Etc., etc., etc. >> >> So, will we start the longtime postponed effort of effectively replace >> current Morphic? >> >> In the mean time, enjoy the theme. Is so cool that I'm considering making it >> my default theme :P >> >> Esteban >> >
