April 2017 - Pharo-dev - lists.pharo.org

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

by Esteban Lorenzano

> On 14 Apr 2017, at 13:10, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Maybe I am alone who do not like the dark theme. you can put a preference to switch it back. > But to me it is too late for such change. I am sure there are UI widgets/projects which looks horrible in dark. And people probably test them in pharo 6 before this change. So they will be very surprised. no, dark theme is around since 3 years and is very depurated. In fact, many people already use it as they preferred theme. > 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. We do not vote: most of the decisions are made by consensus and there is also the board who takes some decisions without asking because we pursuit an objective: for example we did not ask anybody if they wanted a new browser, we (the board) decided that Nautilus was not good enough and then we pushed for Calypso. > Anyway settings are recovered at image startup. So I can live with it. yep, thatâs the ideaâ¦ nothing is irreversible :) Esteban > > 2017-04-14 9:09 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > Hello guys, > > I wanted to let you know that we talked at the board and we want to make the DarkTheme a default for Pharo 6.0. > This is just because we want to have a visual immediate reference of changing things (yeah, marketing ;) ) > > Those which still do not like it can still execute > > Pharo3Theme beCurrent. > > (in their startup actions, if you want) > > And everything will be as before. > > Esteban >

April 14, 2017

Re: [Pharo-dev] Please, test our 64bits builds

by Alistair Grant

On Wed, Apr 12, 2017 at 05:44:05PM +0200, Pavel Krivanek wrote: > - Iceberg commits do not work (known issue) Is there a fogbugz issue for this? Thanks, Alistair

April 14, 2017

Re: [Pharo-dev] Remove all Configurations in the Pharo 6 release?

by Pavel Krivanek

2017-04-14 12:52 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > Isn't it a bit too late for such a change? Might break projects that > expect configurations to be present. > I do not think so. We do not have configurations for the system itself (well, we have them in an external repository but they are not update since switch to baselines). They are used only for the actively maintained semi-external projects like GT, QA, Epicea, Zinc etc. However even in that case they are sometimes out-of-sync with the upstream. Most users of such configurations are using the upstream configurations. If some one is using wrongly the versions in Pharo, he uses reference to the Pharo repository where the configurations will still be present. Cheers, -- Pavel > > Cheers, > Andrei > > On Fri, Apr 14, 2017 at 1:07 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > >> Hi, >> >> in Pharo 7 all configurations will be removed and replaced with the >> baselines. The bootstrapped image itself does not load the configurations >> at all. Most of them is now outdated and old versions of configurations in >> the standard Pharo image can cause problems for users of newer versions >> semi-internal packages (like Moose-Algos). >> >> So we, me and Cyril think that we should remove all current >> Configurations from the image just before the Pharo 6 release. Do you see >> any disadvantages of this step? >> >> Cheers, >> -- Pavel >> > >

April 14, 2017

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

by Denis Kudriashov

Maybe I am alone who do not like the dark theme. But to me it is too late for such change. I am sure there are UI widgets/projects which looks horrible in dark. And people probably test them in pharo 6 before this change. So they will be very surprised. Also I am really wondering that this decision was not publicly discussed. We should vote for such kind of changes. Anyway settings are recovered at image startup. So I can live with it. 2017-04-14 9:09 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hello guys, > > I wanted to let you know that we talked at the board and we want to make > the DarkTheme a default for Pharo 6.0. > This is just because we want to have a visual immediate reference of > changing things (yeah, marketing ;) ) > > Those which still do not like it can still execute > > Pharo3Theme beCurrent. > > (in their startup actions, if you want) > > And everything will be as before. > > Esteban >

April 14, 2017

Re: [Pharo-dev] Remove all Configurations in the Pharo 6 release?

by Andrei Chis

On Apr 14, 2017 13:55, "Cyril Ferlicot D." <cyril.ferlicot(a)gmail.com> wrote: On 14/04/2017 12:52, Andrei Chis wrote: > Isn't it a bit too late for such a change? Might break projects that > expect configurations to be present. > Is there such projects? I know some that use the GT related ones. For me it seems really bad to get a project depending on his configuration. I definetly agree. Just doing it so early to the release will most likely lead to side effects. Cheers, Andrei > Cheers, > Andrei > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

April 14, 2017

Re: [Pharo-dev] Remove all Configurations in the Pharo 6 release?

by Cyril Ferlicot D.

On 14/04/2017 12:52, Andrei Chis wrote: > Isn't it a bit too late for such a change? Might break projects that > expect configurations to be present. > Is there such projects? For me it seems really bad to get a project depending on his configuration. > Cheers, > Andrei > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

April 14, 2017

Re: [Pharo-dev] Remove all Configurations in the Pharo 6 release?

by Andrei Chis

Isn't it a bit too late for such a change? Might break projects that expect configurations to be present. Cheers, Andrei On Fri, Apr 14, 2017 at 1:07 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > in Pharo 7 all configurations will be removed and replaced with the > baselines. The bootstrapped image itself does not load the configurations > at all. Most of them is now outdated and old versions of configurations in > the standard Pharo image can cause problems for users of newer versions > semi-internal packages (like Moose-Algos). > > So we, me and Cyril think that we should remove all current Configurations > from the image just before the Pharo 6 release. Do you see any > disadvantages of this step? > > Cheers, > -- Pavel >

April 14, 2017

Remove all Configurations in the Pharo 6 release?

by Pavel Krivanek

Hi, in Pharo 7 all configurations will be removed and replaced with the baselines. The bootstrapped image itself does not load the configurations at all. Most of them is now outdated and old versions of configurations in the standard Pharo image can cause problems for users of newer versions semi-internal packages (like Moose-Algos). So we, me and Cyril think that we should remove all current Configurations from the image just before the Pharo 6 release. Do you see any disadvantages of this step? Cheers, -- Pavel

April 14, 2017

Re: [Pharo-dev] Please, test our 64bits builds

by Denis Kudriashov

And I fixed compatibility between images. So now you can develop remotely 32bits server image on 64bits client and otherwise. 2017-04-12 18:07 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > PharmIDE works fine. But both images should has same bits > > 2017-04-12 16:44 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> Hello list, >> >> We are approaching to release and one big thing of this one is the 64bits >> supports for Pharo (limited, since there is still not support for Windows, >> but it will arrive, eventually ;) ) >> I asked you to test a couple of months ago but now we are in better shape >> to do it. >> >> - VM and image are getting more and more stable and crashes shouldnât >> happen (but thatâs why I want you to test: to discover possible >> bugs/crashes) >> - I made 64bits a zeroconf citizen: http://get.pharo.org/64 >> >> Now, you can test it by just doing: >> >> curl get.pharo.org/64/60+vmLatest | bash >> >> (In linux or mac, remember it will not work for Windows) >> >> thanks! >> Esteban >> >> >> >

April 14, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60465 Home: https://github.com/pharo-project/pharo-core

April 14, 2017