- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] changing default theme to DarkTheme

by HernÃ¡n Morales Durand

Then more respect for the word, because many people gave their life for it. 2017-04-21 7:52 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > in fact, Greece had a pretty hard dictatorship from '67 to '74 > > On 21 Apr 2017, at 12:40, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I think that 300 years of enslavement by the Ottoman Empire gave us (as a > nation) a pretty good idea , plus the Great Fire of Smyrna, plus Nazi > occupation etc. You assume too much. I was talking about Pharo by the way, > not politics. > > On Fri, Apr 21, 2017 at 1:32 PM HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > >> 2017-04-21 5:10 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >> >>> Resistance is futile >>> >>> You know what amazes me about this discussion ? >>> >>> The one thing that I find amazing is that we have like 58 messages >>> already , many of them complain about the dark theme and not one even >>> bothered posting a single screenshot demonstration all these "problems" , >>> just one . How hard it is to trigger a shortcut to capture an image so we >>> who love the dark theme can see why some people find it hard to use. >>> >>> And this is why I feel lucky that the deed is done and this is no >>> democracy.... very happy indeed :) >>> >>> >> You don't have ANY idea of how is to live without democracy. >> >> Cheers, >> >> HernÃ¡n >> >> >> >>> On Thu, Apr 20, 2017 at 8:48 PM Ben Coman <btc(a)openinworld.com> wrote: >>> >>>> I see in 60467 that the deed is done. Okay, so moving forward... be >>>> prepared ;) for a surge of feedback as a bunch of us >>>> dark-theme-newbies start using it in earnest. I understand those that >>>> been using it a while already are obviously happy with how its tuned, >>>> and probably not many things can be accommodated, but there is one >>>> thing... >>>> >>>> Maybe its that its 1AM, or its my astigmatism, but my first impression >>>> was a shock at the high contrast pure-white-on-black text - for the >>>> World Menu and System Browser - to the degree that my eyes felt >>>> crosseyed. Particularly the title-bar-text was jarring. Dimming it >>>> slightly made it *much* easier to focus. Could >>>> dark-theme-connoisseurs try this out... >>>> >>>> Pharo3DarkTheme>>textColor >>>> ^ Color veryLightGray lighter >>>> >>>> >>>> And wow! That very bright green in TestRunner hurts. >>>> >>>> >>>> Other than that, so far it looks cool. >>>> >>>> cheers -ben >>>> >>>> >>>> On Thu, Apr 20, 2017 at 3:19 AM, Stephane Ducasse >>>> <stepharo.self(a)gmail.com> wrote: >>>> > For the mooc we have normally an image: it is called Pharo 50. >>>> > >>>> > S. >>>> > >>>> > On Mon, Apr 17, 2017 at 3:34 PM, Mark Bestley <news%7B(a)bestley.co.uk> >>>> wrote: >>>> >> >>>> >> Dimitris Chloupis <kilon.alios(a)gmail.com> >>>> >> wrote: >>>> >> >>>> >> > --001a113a8620c74f7a054d5aba55 >>>> >> > Content-Type: text/plain; charset=UTF-8 >>>> >> > >>>> >> > Not before IMMEDIATELY realizing that all screenshots containing >>>> the >>>> >> > white >>>> >> > theme are outdated and will IMMEDIATELY prefer the dark ones that >>>> will >>>> >> > have >>>> >> > an updated view of the Pharo GUI compared to a screenshot that has >>>> the >>>> >> > white theme and it's outdated by two or more years. >>>> >> > >>>> >> >>>> >> No they will think it is for a different environment and waste time >>>> >> looking for a match. >>>> >> >>>> >> A beginner won't see that just that they cannot get the same answer >>>> as >>>> >> the mooc or documentation. >>>> >> >>>> >> They will look for a language where the documentation matches what >>>> they >>>> >> get as they don't know if the documentation or their code is wrong. >>>> (and >>>> >> probably cast aspersions on the quality of what they are using) >>>> >> >>>> >> > Updating the screenshots for PBE5 was a big pain and I am sure >>>> there are >>>> >> > ones that are left that are still outdated showing 1.4 , which is >>>> at >>>> >> > least >>>> >> > 6 years old. >>>> >> > >>>> >> >>>> >> -- >>>> >> Mark >>>> >> >>>> >> >>>> > >>>> >>>> >

April 21, 2017

Re: [Pharo-dev] changing default theme to DarkTheme

by Ben Coman

On Fri, Apr 21, 2017 at 4:10 PM, Dimitris Chloupis <kilon.alios(a)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-ne… cheers -ben

April 21, 2017

Re: [Pharo-dev] changing default theme to DarkTheme

by Esteban Lorenzano

in fact, Greece had a pretty hard dictatorship from '67 to '74 > On 21 Apr 2017, at 12:40, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I think that 300 years of enslavement by the Ottoman Empire gave us (as a nation) a pretty good idea , plus the Great Fire of Smyrna, plus Nazi occupation etc. You assume too much. I was talking about Pharo by the way, not politics. > > On Fri, Apr 21, 2017 at 1:32 PM HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: > 2017-04-21 5:10 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>>: > Resistance is futile > > You know what amazes me about this discussion ? > > The one thing that I find amazing is that we have like 58 messages already , many of them complain about the dark theme and not one even bothered posting a single screenshot demonstration all these "problems" , just one . How hard it is to trigger a shortcut to capture an image so we who love the dark theme can see why some people find it hard to use. > > And this is why I feel lucky that the deed is done and this is no democracy.... very happy indeed :) > > > You don't have ANY idea of how is to live without democracy. > > Cheers, > > HernÃ¡n > > > On Thu, Apr 20, 2017 at 8:48 PM Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: > I see in 60467 that the deed is done. Okay, so moving forward... be > prepared ;) for a surge of feedback as a bunch of us > dark-theme-newbies start using it in earnest. I understand those that > been using it a while already are obviously happy with how its tuned, > and probably not many things can be accommodated, but there is one > thing... > > Maybe its that its 1AM, or its my astigmatism, but my first impression > was a shock at the high contrast pure-white-on-black text - for the > World Menu and System Browser - to the degree that my eyes felt > crosseyed. Particularly the title-bar-text was jarring. Dimming it > slightly made it *much* easier to focus. Could > dark-theme-connoisseurs try this out... > > Pharo3DarkTheme>>textColor > ^ Color veryLightGray lighter > > > And wow! That very bright green in TestRunner hurts. > > > Other than that, so far it looks cool. > > cheers -ben > > > On Thu, Apr 20, 2017 at 3:19 AM, Stephane Ducasse > <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > > For the mooc we have normally an image: it is called Pharo 50. > > > > S. > > > > On Mon, Apr 17, 2017 at 3:34 PM, Mark Bestley <news%7B(a)bestley.co.uk <mailto:news%7B@bestley.co.uk>> wrote: > >> > >> Dimitris Chloupis <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> > >> wrote: > >> > >> > --001a113a8620c74f7a054d5aba55 > >> > Content-Type: text/plain; charset=UTF-8 > >> > > >> > Not before IMMEDIATELY realizing that all screenshots containing the > >> > white > >> > theme are outdated and will IMMEDIATELY prefer the dark ones that will > >> > have > >> > an updated view of the Pharo GUI compared to a screenshot that has the > >> > white theme and it's outdated by two or more years. > >> > > >> > >> No they will think it is for a different environment and waste time > >> looking for a match. > >> > >> A beginner won't see that just that they cannot get the same answer as > >> the mooc or documentation. > >> > >> They will look for a language where the documentation matches what they > >> get as they don't know if the documentation or their code is wrong. (and > >> probably cast aspersions on the quality of what they are using) > >> > >> > Updating the screenshots for PBE5 was a big pain and I am sure there are > >> > ones that are left that are still outdated showing 1.4 , which is at > >> > least > >> > 6 years old. > >> > > >> > >> -- > >> Mark > >> > >> > > >

April 21, 2017

Re: [Pharo-dev] changing default theme to DarkTheme

by HernÃ¡n Morales Durand

Then don't talk about democracy, because you weren't born at Ottoman Empire nor Nazi occupation, and many of us actually were born and lived under military dictatorship. So next time think twice before putting a smile besides "no democracy". 2017-04-21 7:40 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > I think that 300 years of enslavement by the Ottoman Empire gave us (as a > nation) a pretty good idea , plus the Great Fire of Smyrna, plus Nazi > occupation etc. You assume too much. I was talking about Pharo by the way, > not politics. > > On Fri, Apr 21, 2017 at 1:32 PM HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > >> 2017-04-21 5:10 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >> >>> Resistance is futile >>> >>> You know what amazes me about this discussion ? >>> >>> The one thing that I find amazing is that we have like 58 messages >>> already , many of them complain about the dark theme and not one even >>> bothered posting a single screenshot demonstration all these "problems" , >>> just one . How hard it is to trigger a shortcut to capture an image so we >>> who love the dark theme can see why some people find it hard to use. >>> >>> And this is why I feel lucky that the deed is done and this is no >>> democracy.... very happy indeed :) >>> >>> >> You don't have ANY idea of how is to live without democracy. >> >> Cheers, >> >> HernÃ¡n >> >> >> >>> On Thu, Apr 20, 2017 at 8:48 PM Ben Coman <btc(a)openinworld.com> wrote: >>> >>>> I see in 60467 that the deed is done. Okay, so moving forward... be >>>> prepared ;) for a surge of feedback as a bunch of us >>>> dark-theme-newbies start using it in earnest. I understand those that >>>> been using it a while already are obviously happy with how its tuned, >>>> and probably not many things can be accommodated, but there is one >>>> thing... >>>> >>>> Maybe its that its 1AM, or its my astigmatism, but my first impression >>>> was a shock at the high contrast pure-white-on-black text - for the >>>> World Menu and System Browser - to the degree that my eyes felt >>>> crosseyed. Particularly the title-bar-text was jarring. Dimming it >>>> slightly made it *much* easier to focus. Could >>>> dark-theme-connoisseurs try this out... >>>> >>>> Pharo3DarkTheme>>textColor >>>> ^ Color veryLightGray lighter >>>> >>>> >>>> And wow! That very bright green in TestRunner hurts. >>>> >>>> >>>> Other than that, so far it looks cool. >>>> >>>> cheers -ben >>>> >>>> >>>> On Thu, Apr 20, 2017 at 3:19 AM, Stephane Ducasse >>>> <stepharo.self(a)gmail.com> wrote: >>>> > For the mooc we have normally an image: it is called Pharo 50. >>>> > >>>> > S. >>>> > >>>> > On Mon, Apr 17, 2017 at 3:34 PM, Mark Bestley <news%7B(a)bestley.co.uk> >>>> wrote: >>>> >> >>>> >> Dimitris Chloupis <kilon.alios(a)gmail.com> >>>> >> wrote: >>>> >> >>>> >> > --001a113a8620c74f7a054d5aba55 >>>> >> > Content-Type: text/plain; charset=UTF-8 >>>> >> > >>>> >> > Not before IMMEDIATELY realizing that all screenshots containing >>>> the >>>> >> > white >>>> >> > theme are outdated and will IMMEDIATELY prefer the dark ones that >>>> will >>>> >> > have >>>> >> > an updated view of the Pharo GUI compared to a screenshot that has >>>> the >>>> >> > white theme and it's outdated by two or more years. >>>> >> > >>>> >> >>>> >> No they will think it is for a different environment and waste time >>>> >> looking for a match. >>>> >> >>>> >> A beginner won't see that just that they cannot get the same answer >>>> as >>>> >> the mooc or documentation. >>>> >> >>>> >> They will look for a language where the documentation matches what >>>> they >>>> >> get as they don't know if the documentation or their code is wrong. >>>> (and >>>> >> probably cast aspersions on the quality of what they are using) >>>> >> >>>> >> > Updating the screenshots for PBE5 was a big pain and I am sure >>>> there are >>>> >> > ones that are left that are still outdated showing 1.4 , which is >>>> at >>>> >> > least >>>> >> > 6 years old. >>>> >> > >>>> >> >>>> >> -- >>>> >> Mark >>>> >> >>>> >> >>>> > >>>> >>>>

April 21, 2017

Re: [Pharo-dev] changing default theme to DarkTheme

by Dimitris Chloupis

I think that 300 years of enslavement by the Ottoman Empire gave us (as a nation) a pretty good idea , plus the Great Fire of Smyrna, plus Nazi occupation etc. You assume too much. I was talking about Pharo by the way, not politics. On Fri, Apr 21, 2017 at 1:32 PM HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > 2017-04-21 5:10 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > >> Resistance is futile >> >> You know what amazes me about this discussion ? >> >> The one thing that I find amazing is that we have like 58 messages >> already , many of them complain about the dark theme and not one even >> bothered posting a single screenshot demonstration all these "problems" , >> just one . How hard it is to trigger a shortcut to capture an image so we >> who love the dark theme can see why some people find it hard to use. >> >> And this is why I feel lucky that the deed is done and this is no >> democracy.... very happy indeed :) >> >> > You don't have ANY idea of how is to live without democracy. > > Cheers, > > HernÃ¡n > > > >> On Thu, Apr 20, 2017 at 8:48 PM Ben Coman <btc(a)openinworld.com> wrote: >> >>> I see in 60467 that the deed is done. Okay, so moving forward... be >>> prepared ;) for a surge of feedback as a bunch of us >>> dark-theme-newbies start using it in earnest. I understand those that >>> been using it a while already are obviously happy with how its tuned, >>> and probably not many things can be accommodated, but there is one >>> thing... >>> >>> Maybe its that its 1AM, or its my astigmatism, but my first impression >>> was a shock at the high contrast pure-white-on-black text - for the >>> World Menu and System Browser - to the degree that my eyes felt >>> crosseyed. Particularly the title-bar-text was jarring. Dimming it >>> slightly made it *much* easier to focus. Could >>> dark-theme-connoisseurs try this out... >>> >>> Pharo3DarkTheme>>textColor >>> ^ Color veryLightGray lighter >>> >>> >>> And wow! That very bright green in TestRunner hurts. >>> >>> >>> Other than that, so far it looks cool. >>> >>> cheers -ben >>> >>> >>> On Thu, Apr 20, 2017 at 3:19 AM, Stephane Ducasse >>> <stepharo.self(a)gmail.com> wrote: >>> > For the mooc we have normally an image: it is called Pharo 50. >>> > >>> > S. >>> > >>> > On Mon, Apr 17, 2017 at 3:34 PM, Mark Bestley <news%7B(a)bestley.co.uk> >>> wrote: >>> >> >>> >> Dimitris Chloupis <kilon.alios(a)gmail.com> >>> >> wrote: >>> >> >>> >> > --001a113a8620c74f7a054d5aba55 >>> >> > Content-Type: text/plain; charset=UTF-8 >>> >> > >>> >> > Not before IMMEDIATELY realizing that all screenshots containing the >>> >> > white >>> >> > theme are outdated and will IMMEDIATELY prefer the dark ones that >>> will >>> >> > have >>> >> > an updated view of the Pharo GUI compared to a screenshot that has >>> the >>> >> > white theme and it's outdated by two or more years. >>> >> > >>> >> >>> >> No they will think it is for a different environment and waste time >>> >> looking for a match. >>> >> >>> >> A beginner won't see that just that they cannot get the same answer as >>> >> the mooc or documentation. >>> >> >>> >> They will look for a language where the documentation matches what >>> they >>> >> get as they don't know if the documentation or their code is wrong. >>> (and >>> >> probably cast aspersions on the quality of what they are using) >>> >> >>> >> > Updating the screenshots for PBE5 was a big pain and I am sure >>> there are >>> >> > ones that are left that are still outdated showing 1.4 , which is at >>> >> > least >>> >> > 6 years old. >>> >> > >>> >> >>> >> -- >>> >> Mark >>> >> >>> >> >>> > >>> >>>

April 21, 2017

Re: [Pharo-dev] changing default theme to DarkTheme

by HernÃ¡n Morales Durand

2017-04-21 5:10 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > Resistance is futile > > You know what amazes me about this discussion ? > > The one thing that I find amazing is that we have like 58 messages already > , many of them complain about the dark theme and not one even bothered > posting a single screenshot demonstration all these "problems" , just one . > How hard it is to trigger a shortcut to capture an image so we who love the > dark theme can see why some people find it hard to use. > > And this is why I feel lucky that the deed is done and this is no > democracy.... very happy indeed :) > > You don't have ANY idea of how is to live without democracy. Cheers, HernÃ¡n > On Thu, Apr 20, 2017 at 8:48 PM Ben Coman <btc(a)openinworld.com> wrote: > >> I see in 60467 that the deed is done. Okay, so moving forward... be >> prepared ;) for a surge of feedback as a bunch of us >> dark-theme-newbies start using it in earnest. I understand those that >> been using it a while already are obviously happy with how its tuned, >> and probably not many things can be accommodated, but there is one >> thing... >> >> Maybe its that its 1AM, or its my astigmatism, but my first impression >> was a shock at the high contrast pure-white-on-black text - for the >> World Menu and System Browser - to the degree that my eyes felt >> crosseyed. Particularly the title-bar-text was jarring. Dimming it >> slightly made it *much* easier to focus. Could >> dark-theme-connoisseurs try this out... >> >> Pharo3DarkTheme>>textColor >> ^ Color veryLightGray lighter >> >> >> And wow! That very bright green in TestRunner hurts. >> >> >> Other than that, so far it looks cool. >> >> cheers -ben >> >> >> On Thu, Apr 20, 2017 at 3:19 AM, Stephane Ducasse >> <stepharo.self(a)gmail.com> wrote: >> > For the mooc we have normally an image: it is called Pharo 50. >> > >> > S. >> > >> > On Mon, Apr 17, 2017 at 3:34 PM, Mark Bestley <news%7B(a)bestley.co.uk> >> wrote: >> >> >> >> Dimitris Chloupis <kilon.alios(a)gmail.com> >> >> wrote: >> >> >> >> > --001a113a8620c74f7a054d5aba55 >> >> > Content-Type: text/plain; charset=UTF-8 >> >> > >> >> > Not before IMMEDIATELY realizing that all screenshots containing the >> >> > white >> >> > theme are outdated and will IMMEDIATELY prefer the dark ones that >> will >> >> > have >> >> > an updated view of the Pharo GUI compared to a screenshot that has >> the >> >> > white theme and it's outdated by two or more years. >> >> > >> >> >> >> No they will think it is for a different environment and waste time >> >> looking for a match. >> >> >> >> A beginner won't see that just that they cannot get the same answer as >> >> the mooc or documentation. >> >> >> >> They will look for a language where the documentation matches what they >> >> get as they don't know if the documentation or their code is wrong. >> (and >> >> probably cast aspersions on the quality of what they are using) >> >> >> >> > Updating the screenshots for PBE5 was a big pain and I am sure there >> are >> >> > ones that are left that are still outdated showing 1.4 , which is at >> >> > least >> >> > 6 years old. >> >> > >> >> >> >> -- >> >> Mark >> >> >> >> >> > >> >>

April 21, 2017

Re: [Pharo-dev] changing default theme to DarkTheme

by Dimitris Chloupis

and I agree your method is easier on the eyes , though I would want it a bit brighter because I have many bright windows (unfortunately ) outside pharo window and they will steal my focus The lesson of this story.... Try Nireas or make your own custom theme. No theme will make you as happy as making your own theme and frankly its so easy. On Fri, Apr 21, 2017 at 11:10 AM Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Resistance is futile > > You know what amazes me about this discussion ? > > The one thing that I find amazing is that we have like 58 messages already > , many of them complain about the dark theme and not one even bothered > posting a single screenshot demonstration all these "problems" , just one . > How hard it is to trigger a shortcut to capture an image so we who love the > dark theme can see why some people find it hard to use. > > And this is why I feel lucky that the deed is done and this is no > democracy.... very happy indeed :) > > On Thu, Apr 20, 2017 at 8:48 PM Ben Coman <btc(a)openinworld.com> wrote: > >> I see in 60467 that the deed is done. Okay, so moving forward... be >> prepared ;) for a surge of feedback as a bunch of us >> dark-theme-newbies start using it in earnest. I understand those that >> been using it a while already are obviously happy with how its tuned, >> and probably not many things can be accommodated, but there is one >> thing... >> >> Maybe its that its 1AM, or its my astigmatism, but my first impression >> was a shock at the high contrast pure-white-on-black text - for the >> World Menu and System Browser - to the degree that my eyes felt >> crosseyed. Particularly the title-bar-text was jarring. Dimming it >> slightly made it *much* easier to focus. Could >> dark-theme-connoisseurs try this out... >> >> Pharo3DarkTheme>>textColor >> ^ Color veryLightGray lighter >> >> >> And wow! That very bright green in TestRunner hurts. >> >> >> Other than that, so far it looks cool. >> >> cheers -ben >> >> >> On Thu, Apr 20, 2017 at 3:19 AM, Stephane Ducasse >> <stepharo.self(a)gmail.com> wrote: >> > For the mooc we have normally an image: it is called Pharo 50. >> > >> > S. >> > >> > On Mon, Apr 17, 2017 at 3:34 PM, Mark Bestley <news%7B(a)bestley.co.uk> >> wrote: >> >> >> >> Dimitris Chloupis <kilon.alios(a)gmail.com> >> >> wrote: >> >> >> >> > --001a113a8620c74f7a054d5aba55 >> >> > Content-Type: text/plain; charset=UTF-8 >> >> > >> >> > Not before IMMEDIATELY realizing that all screenshots containing the >> >> > white >> >> > theme are outdated and will IMMEDIATELY prefer the dark ones that >> will >> >> > have >> >> > an updated view of the Pharo GUI compared to a screenshot that has >> the >> >> > white theme and it's outdated by two or more years. >> >> > >> >> >> >> No they will think it is for a different environment and waste time >> >> looking for a match. >> >> >> >> A beginner won't see that just that they cannot get the same answer as >> >> the mooc or documentation. >> >> >> >> They will look for a language where the documentation matches what they >> >> get as they don't know if the documentation or their code is wrong. >> (and >> >> probably cast aspersions on the quality of what they are using) >> >> >> >> > Updating the screenshots for PBE5 was a big pain and I am sure there >> are >> >> > ones that are left that are still outdated showing 1.4 , which is at >> >> > least >> >> > 6 years old. >> >> > >> >> >> >> -- >> >> Mark >> >> >> >> >> > >> >>

April 21, 2017

Re: [Pharo-dev] changing default theme to DarkTheme

by Dimitris Chloupis

Resistance is futile You know what amazes me about this discussion ? The one thing that I find amazing is that we have like 58 messages already , many of them complain about the dark theme and not one even bothered posting a single screenshot demonstration all these "problems" , just one . How hard it is to trigger a shortcut to capture an image so we who love the dark theme can see why some people find it hard to use. And this is why I feel lucky that the deed is done and this is no democracy.... very happy indeed :) On Thu, Apr 20, 2017 at 8:48 PM Ben Coman <btc(a)openinworld.com> wrote: > I see in 60467 that the deed is done. Okay, so moving forward... be > prepared ;) for a surge of feedback as a bunch of us > dark-theme-newbies start using it in earnest. I understand those that > been using it a while already are obviously happy with how its tuned, > and probably not many things can be accommodated, but there is one > thing... > > Maybe its that its 1AM, or its my astigmatism, but my first impression > was a shock at the high contrast pure-white-on-black text - for the > World Menu and System Browser - to the degree that my eyes felt > crosseyed. Particularly the title-bar-text was jarring. Dimming it > slightly made it *much* easier to focus. Could > dark-theme-connoisseurs try this out... > > Pharo3DarkTheme>>textColor > ^ Color veryLightGray lighter > > > And wow! That very bright green in TestRunner hurts. > > > Other than that, so far it looks cool. > > cheers -ben > > > On Thu, Apr 20, 2017 at 3:19 AM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: > > For the mooc we have normally an image: it is called Pharo 50. > > > > S. > > > > On Mon, Apr 17, 2017 at 3:34 PM, Mark Bestley <news%7B(a)bestley.co.uk> > wrote: > >> > >> Dimitris Chloupis <kilon.alios(a)gmail.com> > >> wrote: > >> > >> > --001a113a8620c74f7a054d5aba55 > >> > Content-Type: text/plain; charset=UTF-8 > >> > > >> > Not before IMMEDIATELY realizing that all screenshots containing the > >> > white > >> > theme are outdated and will IMMEDIATELY prefer the dark ones that will > >> > have > >> > an updated view of the Pharo GUI compared to a screenshot that has the > >> > white theme and it's outdated by two or more years. > >> > > >> > >> No they will think it is for a different environment and waste time > >> looking for a match. > >> > >> A beginner won't see that just that they cannot get the same answer as > >> the mooc or documentation. > >> > >> They will look for a language where the documentation matches what they > >> get as they don't know if the documentation or their code is wrong. (and > >> probably cast aspersions on the quality of what they are using) > >> > >> > Updating the screenshots for PBE5 was a big pain and I am sure there > are > >> > ones that are left that are still outdated showing 1.4 , which is at > >> > least > >> > 6 years old. > >> > > >> > >> -- > >> Mark > >> > >> > > > >

April 21, 2017

Re: [Pharo-dev] #renameTo: and #moveTo:

by Alistair Grant

On Thu, Apr 20, 2017 at 09:21:01PM +0200, Nicolas Cellier wrote: > 2017-04-20 9:53 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > > > What? Google this: man stat The first field of stat structure is > > a device ID, so deciding if two files are on same file system or > > not is doable by checking this field for the source file and > > destination file (if it exists) or directory - modulo the fact > > that you'd have to care of symbolic links with lstat. > > I meant from within the image. Also, while this is fine for > Linux, and probably for MacOS, what about Windows? > > Ah, so it's more a Squeak/Pharo VM problem than a unix problem ;) You > are right, there is a call to stat() in unix file plugin > > https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/platforms/unix/p… > > but the device info is not passed back to the image... Too bad! But it should be a straightforward extension. I think I'll ask on vm-dev if anyone objects to me adding this extension. Thanks for pointing this out! Cheers, Alistair > As for windows, it's not a problem, there is a rename function that > would move files across devices (but not directories!) See rename() on > msdn https://msdn.microsoft.com/en-us/library/zw5t957f.aspx

April 21, 2017

Re: [Pharo-dev] [Vm-dev] Order of evaluation bug with in lined to:do: in both Opal and Squeak compilers.

by Nicolai Hess

John Brant discovered this bug recenlty: (see bottom of his post) http://forum.world.st/collection-flatCollect-something-VS-collection-collec… 2017-04-21 1:56 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > > > On Thu, Apr 20, 2017 at 4:41 PM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > >> Hi All, >> >> just stumbled across a bytecode compiler bug that's in both the >> Squeak compiler and the Opal compiler. I'm told by ClÃ©ment that Opal >> mimics the bug to avoid crashing legacy code. So there may be places that >> depend on this bug. It would be good to eliminate the dependencies and the >> bug. >> >> For illustration look at the to:do: loop in the ifNil: arm in >> Context>>privRefresh: >> >> Context>>privRefresh >> "Reinitialize the receiver so that it is in the state it was at its >> creation." >> closureOrNil >> ifNotNil: >> [pc := closureOrNil startpc. >> self stackp: closureOrNil numArgs + closureOrNil numCopiedValues. >> 1 to: closureOrNil numCopiedValues do: >> [:i | self tempAt: closureOrNil numArgs + i put: (closureOrNil at: i)]] >> ifNil: >> [pc := method initialPC. >> self stackp: method numTemps. >> method numArgs+1 to: method numTemps do: >> [:i | self tempAt: i put: nil]] >> >> >> This should evaluate method numArgs + 1 then method numTemps. If it were >> written as a non-in-lined (method numArgs+1 to: method numTemps) do: [:i| >> self tempAt: i put: nil] then the [self tempAt: i put: nil] block would be >> created next. But the bytecode for the inlined version is >> >> self stackp: method numTemps. >> 63 <70> self >> 64 <84 40 03> pushRcvr: 3 >> 67 <D6> send: numTemps >> 68 <E1> send: stackp: >> 69 <87> pop >> >> iLimit := method numTemps >> 70 <84 40 03> pushRcvr: 3 >> 73 <D6> send: numTemps >> 74 <69> popIntoTemp: 1 >> >> i := method numArgs + 1 >> 75 <84 40 03> pushRcvr: 3 >> 78 <D2> send: numArgs >> 79 <76> pushConstant: 1 >> 80 <B0> send: + >> 81 <81 40> storeIntoTemp: 0 (squeak) <69> popIntoTemp: 1 (pharo) >> 83 <10> pushTemp: 0 >> 84 <11> pushTemp: 1 >> 85 <B4> send: <= >> 86 <AC 0B> jumpFalse: 99 >> >> There is a second bug in the Squeak bytecode; storeIntoTemp: is used to >> load i whereas it should be popIntoTemp:. It was this second bug that >> alerted me to the order-of-evaluation bug. >> > > The second bug (Squeak's use of storeIntoTemp:) is actually only a poor > implementation of the value/effect distinction through the inlined > ifNil:ifNotNil:. Because ifNil:ifNotNil: has a value (albeit one that is > discarded) the Squeak compiler generates a storeIntoTemp: to p[reserve the > value of the to:do: lop, which is the initial index. So the bug is not > within the generation of the to:do: (the only bug there being the > order-of-evaluation one). The bug is actually outside; the loop should be > being generated for effect but is being evaluated for value. > > On the order of evaluation bug, does anyone have any memory of which > methods depended on this bug? > > _,,,^..^,,,_ >> best, Eliot >> > > > > -- > _,,,^..^,,,_ > best, Eliot > >

April 21, 2017