On 01 May 2014, at 14:23, phil@highoctane.be wrote:Yesssssssss!!!!!!
Esteban,�� you really made�� my day on this one.
you are welcome :)The good thing is also that with your changes we can spot where to look for changing all we want now.
yes, the idea was to make a dark theme possible by removing hardcoded colorisation and dumb things (I like current one, but the most important is that now *it is* possible to play with themes for real).��now, we need to think how we can actually integrate the changes to the image (I suppose not in the way it is done now, as I said��� it is mostly a hack).��EstebanThanks again.
Phil
Le 1 mai 2014 14:08, "Sven Van Caekenberghe" <sven@stfx.eu> a ��crit :
>
> Wow!
>
> This will make a couple of people very happy, and it is quite impressive.
>
> Seriously, you found time to finish this while labouring during days on the Pharo 3 release, are you sure you are not extra-terrestial ?
>
> Works like a charm :
>
>
> 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 <estebanlm@gmail.com> 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��
>>
>