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

2017-04-14 Thread Stephane Ducasse
tx pavel! We need a look that we can identify pharo 60 as pharo 60 :) On Fri, Apr 14, 2017 at 2:42 PM, Pavel Krivanek wrote: > > > 2017-04-14 13:48 GMT+02:00 Denis Kudriashov : > >> >> 2017-04-14 13:27 GMT+02:00 Esteban Lorenzano : >> >>> But to me it is too late for such change. I am sure ther

Re: [Pharo-dev] Security in the image

2017-04-14 Thread Richard Sargent
LaeMing wrote > > Stephan Eggermont wrote >> On 12/04/17 09:34, LaeMing wrote: >>> What sort of security implications might that have and are there any >>> current >>> solutions to a multi-user single-image situation? >> >> Take a look at gemstone. >> https://www.youtube.com/user/JamesGFoster/vid

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

2017-04-14 Thread Pavel Krivanek
2017-04-14 13:48 GMT+02:00 Denis Kudriashov : > > 2017-04-14 13:27 GMT+02:00 Esteban Lorenzano : > >> 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 v

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

2017-04-14 Thread Pavel Krivanek
2017-04-14 14:20 GMT+02:00 Andrei Chis : > > > On Apr 14, 2017 14:13, "Pavel Krivanek" wrote: > > > > 2017-04-14 12:52 GMT+02:00 Andrei Chis : > >> 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

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

2017-04-14 Thread Andrei Chis
On Apr 14, 2017 14:13, "Pavel Krivanek" wrote: 2017-04-14 12:52 GMT+02:00 Andrei Chis : > 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

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

2017-04-14 Thread Andrei Chis
On Apr 14, 2017 14:11, "Denis Kudriashov" wrote: Maybe I am alone who do not like the dark theme. I'm also a fan of the white team. Can't really use the dark one. Cheers, Andrei But to me it is too late for such change. I am sure there are UI widgets/projects which looks horrible in dark. An

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

2017-04-14 Thread Denis Kudriashov
2017-04-14 13:46 GMT+02:00 Esteban Lorenzano : > But look&feel is different. You just open Pharo and have impression is it > looks good or not. Voting can work here. > > > yeah, but is impossible to satisfy everybody… specially in non-technical > stuff :) > It is important to satisfy majority. An

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

2017-04-14 Thread Denis Kudriashov
2017-04-14 13:27 GMT+02:00 Esteban Lorenzano : > 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 y

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

2017-04-14 Thread Esteban Lorenzano
> On 14 Apr 2017, at 13:44, Denis Kudriashov wrote: > > > 2017-04-14 13:27 GMT+02:00 Esteban Lorenzano >: >> 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. >

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

2017-04-14 Thread Denis Kudriashov
2017-04-14 13:27 GMT+02:00 Esteban Lorenzano : > 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

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

2017-04-14 Thread Alistair Grant
On Fri, Apr 14, 2017 at 01:29:05PM +0200, Esteban Lorenzano wrote: > > > On 14 Apr 2017, at 13:20, Alistair Grant wrote: > > > > 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? > > no, a

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

2017-04-14 Thread Esteban Lorenzano
> On 14 Apr 2017, at 13:27, Esteban Lorenzano wrote: > > >> On 14 Apr 2017, at 13:10, Denis Kudriashov > > 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

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

2017-04-14 Thread Esteban Lorenzano
> On 14 Apr 2017, at 13:20, Alistair Grant wrote: > > 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? no, and there is also no iceberg issue (iceberg is developed separately, at least for the

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

2017-04-14 Thread Pavel Krivanek
2017-04-14 13:20 GMT+02:00 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? > Iceberg issues are currently not maintained by FogBugz but own issue GitHub issue tracker. Anyway,

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

2017-04-14 Thread Esteban Lorenzano
> On 14 Apr 2017, at 13:10, Denis Kudriashov 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 th

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

2017-04-14 Thread 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

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

2017-04-14 Thread Pavel Krivanek
2017-04-14 12:52 GMT+02:00 Andrei Chis : > 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 sin

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

2017-04-14 Thread 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 decisio

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

2017-04-14 Thread Andrei Chis
On Apr 14, 2017 13:55, "Cyril Ferlicot D." 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 b

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

2017-04-14 Thread 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

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

2017-04-14 Thread 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 wrote: > Hi, > > in Pharo 7 all configurations will be removed and replaced with the > baselines. The bootstrapped image itsel

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

2017-04-14 Thread 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-

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

2017-04-14 Thread 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 : > PharmIDE works fine. But both images should has same bits > > 2017-04-12 16:44 GMT+02:00 Esteban Lorenzano : > >> Hello lis

[Pharo-dev] [pharo-project/pharo-core] c133d6: 60465

2017-04-14 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: c133d69caae272904bf9b8721d8bff3f471ae88d https://github.com/pharo-project/pharo-core/commit/c133d69caae272904bf9b8721d8bff3f471ae88d Author: Jenkins Build Server Date: 2017-04-14 (Fri, 14 Apr 2017

[Pharo-dev] [pharo-project/pharo-core]

2017-04-14 Thread GitHub
Branch: refs/tags/60465 Home: https://github.com/pharo-project/pharo-core

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

2017-04-14 Thread Alistair Grant
Hi Esteban, I've basically moved my personal environment to 64 bits, which means all of the following have been loaded and most have had some adhoc testing: Iceberg OSProcess MessageFlowBrowser TilingWindowManager Beacon NeoCSV (not tested) UDBC (SQLite3) Glorp Pillar Roassal2 Soup (not tested) Z

[Pharo-dev] changing default theme to DarkTheme

2017-04-14 Thread Esteban Lorenzano
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 Pharo3Them