[Pharo-dev] changing default theme to DarkTheme

Stephane Ducasse stepharo.self at gmail.com
Sun Apr 16 07:26:28 EDT 2017


clement esteban is using the dark theme since several years!!!!
phil too.
No new code!

On Sun, Apr 16, 2017 at 12:35 AM, Clément Bera <bera.clement at gmail.com>
wrote:

> Isn't a couple days before release a bit late to change the default theme
> ? Aren't we in feature freeze mode ?
>
> If for marketing it makes sense to switch to the dark theme, then let's
> switch to dark theme. But why not switching for Pharo 7 instead ?
> Instability is bad for marketing anyway, isn't it ?
>
> I don't mind for myself, I will always switch back with user settings to
> the light theme it's more about the general perception of Pharo stability.
>
> On Sat, Apr 15, 2017 at 11:31 AM, phil at highoctane.be <phil at highoctane.be>
> wrote:
>
>> Bah, I made GTSpotter dark theme work with SublimishTheme and got the
>> "yeah, for Pharo7".
>>
>> It is pissing me off but what can I say, just follow what is released.
>>
>> Compare Pharo 1 and Pharo 6. Worlds apart. I hope this continues.
>>
>> Phil
>>
>> On Sat, Apr 15, 2017 at 4:48 PM, Hernán Morales Durand <
>> hernan.morales at gmail.com> wrote:
>>
>>> I vote for a voting system for these kind of changes. I cannot say it
>>> more clearly, and I don't know why is asking for a voting system negative?
>>>
>>> We all have problems. In the meantime you will make all the changes you
>>> like to do, and I will continue working on my own way, until I find there
>>> is more voice for the "small minority".
>>>
>>> 2017-04-15 9:30 GMT-03:00 Stephane Ducasse <stepharo.self at gmail.com>:
>>>
>>>> Hi Hernan
>>>>
>>>> Why are you always so negative? Do you think that this is easy?
>>>>
>>>> Inria paid Denis to build a remote tool suite for ***research
>>>> purpose*** and we discovered that a new remote invocation framework was
>>>> needed and that they were far too many discussions between the model and
>>>> the view.
>>>> Denis proposed to build a new browser (and it was not in our plans) and
>>>> we decided that we cannot do it otherwise.
>>>> We could keep this tool for us but we share it with the community.
>>>>
>>>> Do you want another example?
>>>> I asked christopher to build versionner and he discovered that he
>>>> cannot script well enough the model. And versionner was made
>>>> for everybody. Now with git we will have to revise it.
>>>>
>>>> Do you want another example?
>>>> Iceberg we payed nicolas passerini to analyse the situation and to
>>>> build a system that other people
>>>> can use it.
>>>>
>>>> Do you want another example?
>>>> Esteban got in his face the FFI problem: you see Spur arrives and FFI
>>>> nabive boost does not so what do we do?
>>>> He worked like a mad (and it was not planned because we thought that
>>>> igor would adpta NB to spur then to 64 bits).
>>>> And the FFI is for everbody.
>>>>
>>>> Do you want another example?
>>>> We spent one year with pavel, guillermo and christophe to make sure
>>>> that we can make sure that the three yars
>>>> effort of the phd of guillermo on bootstrap are not lost.
>>>>
>>>> Do you want more?
>>>> All my books are open-source? Do you know how much time I take to write
>>>> a book?
>>>>
>>>> I spent 8 months designing a mooc and do you know how much I earned
>>>> doing it: 3000 Euros ( so I will make the computation to know how much per
>>>> hour I lost) and the mooc is free.
>>>>
>>>> May be all these examples have no value for you. But for me they have.
>>>>
>>>> So you see you can piss on us if it makes you feeling better, and you
>>>> can rant in your corner.
>>>> But this is not the vision I have about a community because we are
>>>> sharing all the things that we are doing.
>>>>
>>>> Stef
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Apr 15, 2017 at 9:05 AM, Hernán Morales Durand <
>>>> hernan.morales at gmail.com> wrote:
>>>>
>>>>>
>>>>> 2017-04-14 8:44 GMT-03:00 Denis Kudriashov <dionisiydk at gmail.com>:
>>>>>
>>>>>>
>>>>>> 2017-04-14 13:27 GMT+02:00 Esteban Lorenzano <estebanlm at gmail.com>:
>>>>>>
>>>>>>> Also I am really wondering that this decision was not publicly
>>>>>>> discussed. We should vote for such kind of changes.
>>>>>>>
>>>>>>>
>>>>>>> no, this is not how it works.
>>>>>>>
>>>>>>
>>>>>> yes, it is how it could work :)
>>>>>>
>>>>>> Current approach is not bad for technical choices because it is
>>>>>> difficult to make everybody evolved in particular technical topic.
>>>>>> But look&feel is different. You just open Pharo and have impression
>>>>>> is it looks good or not. Voting can work here.
>>>>>>
>>>>>
>>>>> I would forget about it. I stopped waiting for votes long time ago in
>>>>> this community. Also I decided to stop contributing to external projects
>>>>> (including reporting bugs) because who knows which tool (browser, morphic,
>>>>> etc) the board would like to add/remove tomorrow. I will not invest my time
>>>>> fixing tools who knows what's the plan on them.
>>>>>
>>>>> The best you can do is to work in the dark and adapt your stuff with
>>>>> each new Pharo version.
>>>>> Of course anyone with enough time/money could fork a new more
>>>>> democratic Pharo ;)
>>>>>
>>>>> Hernán
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20170416/11ec8dce/attachment-0002.html>


More information about the Pharo-dev mailing list