its ironic you say this Stephan and the irony is that you claim that Dark Theme is inappropriate because Pharo uses so many hard coded colours when it was Esteban's effort to have a dark theme that decreased the amount of hard coded methods and modified them to support themes. The very reason you use that Dark Theme should not be used as default is the very reason to use it because it will forces us to detect those methods and convert them to support our Theme classes. This will not only improve the Dark Themes but ANY future theme.
What I can say with certainty is that the way to move forward is most definitely not to move back. I also do not like the fact that GTSpotter has its own theme support , I found it a terrible idea when it first appeared, after a long time using GTSpotter , still find it a terrible idea that is completely disconnected from the main theme. On Fri, Apr 21, 2017 at 3:49 PM Stephan Eggermont <step...@stack.nl> wrote: > On 21/04/17 13:26, Dimitris Chloupis wrote: > > > > > > On Fri, Apr 21, 2017 at 1:53 PM Ben Coman > > <b...@openinworld.com > > <mailto:b...@openinworld.com>> wrote: > > > > On Fri, Apr 21, 2017 at 4:10 PM, Dimitris Chloupis > > <kilon.al...@gmail.com > > <mailto:kilon.al...@gmail.com>> wrote: > > > You know what amazes me about this discussion ? > > > > > > not one even bothered posting > > > a single screenshot demonstration all these "problems" , just one . > > > > To rebut you, you haven't been paying attention :) :P > > > https://pharo.fogbugz.com/f/cases/19941/Dark-Theme-overlapped-title-bars-need-to-be-distinctive > > > > cheers -ben > > > > > > I mean in this thread , will make it easier, because for example fogbuz > > asks for a login. > > You still haven't been paying attention. We have hard-coded colors all > over the place. And I am not interested in new bug reports now. I want > the theme switch reverted and done after the release. This is just bad > process and it should be stopped. > > Stephan > > > >
