Re: [Pharo-dev] [Pharo-users] Pharo 6 snap install

On Sun, Apr 16, 2017 at 11:55:27PM +0200, Luke Gorrie wrote: > I have the VM building under nix from the master branch now. The build is > based > loosely on the linux.64x64 mvm script so it's building a 64-bit x86-64 VM. The > pharo-vm commit I am testing is 1c38b03f (from wednesday.) > > I

Re: [Pharo-dev] [Pharo-users] Pharo 6 snap install

Luke, I don't see this in the latest binary and I have not adjusted the rtprio figures at all. I can try running some simple tests if you send them to me. $ curl get.pharo.org/64/60+vmLatest | bash file Pharo.image Pharo.image: Smalltalk image Spur 64b +C+NF+Tag (68021) $ prlimit

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

Ephestos is my project that is a single configuration that unites all my other projects under one roof. Ephestos loads 1) Nireas 2) ChronosManager 3) SmaCC (not mine) 4) Atlas 5) CPP 6) Octopus 7) BPY 8) Orpheas . Each one of them a separate git repo with its own baseline. Some of them depend on

Re: [Pharo-dev] [Pharo-users] Pharo 6 snap install

I have the VM building under nix from the master branch now. The build is based loosely on the linux.64x64 mvm script so it's building a 64-bit x86-64 VM. The pharo-vm commit I am testing is 1c38b03f (from wednesday.) I have tried opening both Pharo-60465.image and Pharo-50771.image and both give

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

On 16/04/17 23:27, Cyril Ferlicot D. wrote: On 16/04/2017 23:13, Stephan Eggermont wrote: We do not break things a week before the release. We break them a week after the release. Otherwise, why bother. Stephan As I asked in my previous mail, what is broken? There are 214 instances of the

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

On 16/04/2017 23:13, Stephan Eggermont wrote: > We do not break things a week before the release. We break them a week > after the release. Otherwise, why bother. > > Stephan > As I asked in my previous mail, what is broken? In Pharo 4 there is broken things. In Pharo 6 I don't see what is

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

On 16/04/17 16:14, Dimitris Chloupis wrote: Just for the record the easiest way to load packages in the image the Package Browser relies solely on configurations . Is there a plan to migrate because as much I am vocal supporter of Pharo moving to git it will be a big lose if Package Browser is

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

On 16/04/17 20:53, Cyril Ferlicot D. wrote: Also, I use the dark theme since almost two years and I don't remember having problems. Do you have examples? Within two minutes I found a non-themed visualization in Moose. The switching works a lot better than last time I looked at dark theme.

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

On 16/04/17 20:53, Cyril Ferlicot D. wrote: And last, when a new version of a programming language is out, we do not expect all applications to be up to date with the language at the time of the release. We do not break things a week before the release. We break them a week after the release.

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

Yes it's actually more than that. It's called Nireas and I think it's the only theme that comes with its own GUI that allows to customize its colors , so it's very flexible. It's available at Package Browser On Sun, 16 Apr 2017 at 21:53, Stephane Ducasse wrote: > did

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

On 16/04/2017 20:31, Stephan Eggermont wrote: > Sorry, but that does not make sense to me. I've only heard complaints > about dependent projects not honoring theme color settings, and I've > never been able to switch themes actually work without leaving artifacts > behind. I agree it makes sense

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

did you publish the blue theme as an autonomous package? On Sun, Apr 16, 2017 at 2:18 PM, Dimitris Chloupis wrote: > Me too, even my blue theme is nothing more than a customization of dark > theme. Plus dark theme is based on darcula dark theme which is by far the > most

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

On 16/04/2017 08:54, Tudor Girba wrote: > However, Configurations are useful in offering people a way to understand how > the code is organized. For example, in Moose we have the inspector extension > that shows the dependencies and it is very valuable. > > The only thing we need is to

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

Hi Norbert, 2017-04-16 13:28 GMT-03:00 Norbert Hartl : > I wonder why voting is considered something good. To me voting is rather a > last resort strategy. > Voting is taking power without the need for having an opinion nor any > reason. To me the sense of voting is to make

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

I wonder why voting is considered something good. To me voting is rather a last resort strategy. Voting is taking power without the need for having an opinion nor any reason. To me the sense of voting is to make most people feel empowered/comfortable. And the outcome is often poor or even

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

On Sat, Apr 15, 2017 at 8:01 PM, Cyril Ferlicot D. wrote: > Can people just explain to my why we have so many big threads each time > a default settings is changed? > Law of triviality. https://en.wikipedia.org/wiki/Law_of_triviality Because its natural to have

Re: [Pharo-dev] [Pharo-users] Pharo 6 snap install

On Sun, Apr 16, 2017 at 10:50 PM, Alistair Grant wrote: > Hi Ben, > > On Sun, Apr 16, 2017 at 10:42:42PM +0800, Ben Coman wrote: >> On Sat, Apr 15, 2017 at 4:34 PM, Luke Gorrie wrote: >> > On 15 April 2017 at 10:08, Alistair Grant >>

Re: [Pharo-dev] [Pharo-users] Pharo 6 snap install

Hi Ben, On Sun, Apr 16, 2017 at 10:42:42PM +0800, Ben Coman wrote: > On Sat, Apr 15, 2017 at 4:34 PM, Luke Gorrie wrote: > > On 15 April 2017 at 10:08, Alistair Grant > > wrote: > > > > Grabbing the source directly from Git is attractive if (a) I know > >

Re: [Pharo-dev] [Pharo-users] Pharo 6 snap install

On Sat, Apr 15, 2017 at 4:34 PM, Luke Gorrie wrote: > On 15 April 2017 at 10:08, Alistair Grant wrote: > > Grabbing the source directly from Git is attractive if (a) I know that I am > choosing a good version and (b) I am able to build it in a good way. > >

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

Just for the record the easiest way to load packages in the image the Package Browser relies solely on configurations . Is there a plan to migrate because as much I am vocal supporter of Pharo moving to git it will be a big lose if Package Browser is not ported . On Sun, 16 Apr 2017 at 09:55,

Re: [Pharo-dev] Epicea should ask before recovering

2017-04-16 12:09 GMT+02:00 Peter Uhnak : > Of course if I am the only person that uses images in such a way then I > can just work around it myself. (because having endless lists of config > options is also nightmare) Me too

Re: [Pharo-dev] [Pharo-users] Pharo 6 snap install

Whoops, now copied to pharo-dev to continue discussion there. On Sun, Apr 16, 2017 at 9:13 PM, Ben Coman wrote: > On Sat, Apr 15, 2017 at 12:43 PM, Luke Gorrie wrote: >> >> On 14 April 2017 at 22:20, Stephane Ducasse wrote: >>> >>>

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

Me too, even my blue theme is nothing more than a customization of dark theme. Plus dark theme is based on darcula dark theme which is by far the most popular dark theme out there. On Sun, 16 Apr 2017 at 14:27, Stephane Ducasse wrote: > clement esteban is using the dark

Re: [Pharo-dev] Help currency review

tx ben indeed this is nice to update this text s. On Sat, Apr 8, 2017 at 4:25 AM, Ben Coman wrote: > At this late stage of Pharo 6 development, it might be good to do a pass > at... > World > Help > Help Browser content > > Epicea >Browsers - mentions two separate browser

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

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 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

[Pharo-dev] Pharo VM build for nix, was: Re: [Pharo-users] Pharo 6 snap install

I made a pull request from the work-in-progress branch where I am tweaking things to build the latest VM under nix: https://github.com/pharo-project/pharo-vm/pull/129 The tricky bit that I haven't confronted properly yet is the overlap between nix and mvm/zeroconf i.e. each one wants to be in

[Pharo-dev] Iceberg and git repository management

Hi, is Iceberg (or its git subsytem) capable of more than just Pharo code management? More specifically, would it be possible with Iceberg to commit e.g. a change to a README.md or .travis.yml file in the repository? Thanks, Peter

[Pharo-dev] Epicea should ask before recovering

Hi, can we modify epicea before asking for recovery? Because right now when I close image to intentionally throw away changes (because I managed to break the image or whatever), Epicea will freeze the image on startup for 10-15 seconds for even a mere 6-method change. (I also had it freeze for

[Pharo-dev] Parser for mongodb queries in javascript notations

Hello! I'm creating MongoDBBrowser that have all CRUD operations and I need a parser that translates javascript queries in MongoDB to the queries, for making selects, inserts etc. using Mongo class. For example, I have query db.SomeCollection.find( {$or: [ { name: { $regex: /test/i } }, {

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

Hi Esteban, On Fri, Apr 14, 2017 at 08:06:05AM +, Alistair Grant wrote: > > 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 If I try this with any of the VMs I built,

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

However, Configurations are useful in offering people a way to understand how the code is organized. For example, in Moose we have the inspector extension that shows the dependencies and it is very valuable. The only thing we need is to Metacello to be able to load new versions of the

Re: [Pharo-dev] [Pharo-users] why is adding instance variables so slow?

Hi, Please let’s move this discussion on pharo-dev. And keep going :) Cheers, Doru > On Apr 14, 2017, at 12:09 PM, Denis Kudriashov wrote: > > > 2017-04-14 11:09 GMT+02:00 teso...@gmail.com : > Hi, I think the problem was not clearly explained.

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

Life can be very UNFAIR but I don't see how it is related to the previously expressed opinions about what people fell. Le 15/04/2017 à 17:07, Stephane Ducasse a écrit : > behavior. I'm just thinking that it is UNFAIR -- Dr. Geo http://drgeo.eu