Re: [Pharo-dev] Discussing the roadmap

On Thu, Jul 6, 2017 at 11:27 PM, Tim Mackinnon wrote: > I didn’t mean to touch a nerve - and this was why I wrote “minor” points - > but you did ask for feedback… you did not :) Just that if we just count on fully book engineers working on super important features we will not

Re: [Pharo-dev] Discussing the roadmap

On Friday 07 July 2017 03:26 AM, Eliot Miranda wrote: Let's say that currently the mark-compact collector collects at about 1Gb per second (that's about what I'm seeing on my MacMini for a 600Mb heap, collected and compacted in about 530ms on a 2.3GHz Core i7, = 1.1Gb/s). For the moment let's

Re: [Pharo-dev] Discussing the roadmap

> On 6 Jul 2017, at 23:56, Eliot Miranda wrote: > > Hi Sven, > > On Thu, Jul 6, 2017 at 10:10 AM, Sven Van Caekenberghe wrote: > > > On 6 Jul 2017, at 18:41, Eliot Miranda wrote: > > > > Hi Stef, > > > >> On Jul 6, 2017, at

Re: [Pharo-dev] Discussing the roadmap

Hi Sven, On Thu, Jul 6, 2017 at 10:10 AM, Sven Van Caekenberghe wrote: > > > On 6 Jul 2017, at 18:41, Eliot Miranda wrote: > > > > Hi Stef, > > > >> On Jul 6, 2017, at 1:55 AM, Stephane Ducasse > wrote: > >> > >> We would like to

Re: [Pharo-dev] Discussing the roadmap

Hi Stef, On Thu, Jul 6, 2017 at 1:20 PM, Stephane Ducasse wrote: > I updated the roadmap. > > Btw eliot I think that you should sync with clement and esteban. > trust me, we do. > I'm not the guy taking decision here. We should agree on the key > elements of the

Re: [Pharo-dev] Discussing the roadmap

On Thu, Jul 6, 2017 at 12:44 PM, Denis Kudriashov wrote: > > 2017-07-06 19:10 GMT+02:00 Sven Van Caekenberghe : > >> Actually, being able to efficiently keep a couple of GB worth of objects >> in memory, even better 10s of GB seems like an important short term

Re: [Pharo-dev] Ideas wanted: "Patterns to sustain feedback loops"

Hi Steph, first let me apologize. That was supposed to be a private message to Marcus as he requested. On Thu, Jul 6, 2017 at 1:30 PM, Stephane Ducasse wrote: > Eliot > > this is why we created the consortium and are working hard to make > sure that the community

Re: [Pharo-dev] Discussing the roadmap

I didn’t mean to touch a nerve - and this was why I wrote “minor” points - but you did ask for feedback… Point noted on giving user feedback - I’d actually like to fix things, but currently its just too hard to submit fixes other than pull requests for documentation that is sitting in git hub

Re: [Pharo-dev] Ideas wanted: "Patterns to sustain feedback loops"

Eliot this is why we created the consortium and are working hard to make sure that the community can pay its engineers. Now marcus is probably looking for feedback patterns in the dev process, idea generation process. Stef On Thu, Jul 6, 2017 at 6:53 PM, Eliot Miranda

Re: [Pharo-dev] Discussing the roadmap

I updated the roadmap. Btw eliot I think that you should sync with clement and esteban. I'm not the guy taking decision here. We should agree on the key elements of the roadmap as well as requirements expressed by people that put money on the table. Once all the agenda/requirements/analyse is

Re: [Pharo-dev] Discussing the roadmap

2017-07-06 19:10 GMT+02:00 Sven Van Caekenberghe : > Actually, being able to efficiently keep a couple of GB worth of objects > in memory, even better 10s of GB seems like an important short term goal. I > for one don't really care for games or music. I do care about server >

Re: [Pharo-dev] Discussing the roadmap

> Only 2 minor items stick out as missing: > > 1) Continuing to improve keyboard shortcut support (its a lot better, but > not quite completed - I really miss some shortcuts, particularly the ability > to meta-tab between windows - ALT-Tab only works in some windows, and widen > selection in the

Re: [Pharo-dev] Discussing the roadmap

Tx eliot Clement edited the text so I thought that this is correct and normally yes I know these details. Just that I wrote all the comments for all the points and after 1 hour it gets boring :) On Thu, Jul 6, 2017 at 6:41 PM, Eliot Miranda wrote: > Hi Stef, > >> On Jul

Re: [Pharo-dev] Discussing the roadmap

> On 6 Jul 2017, at 18:41, Eliot Miranda wrote: > > Hi Stef, > >> On Jul 6, 2017, at 1:55 AM, Stephane Ducasse wrote: >> >> We would like to share this list with you and get your feedback and inputs. >> It will be presented and discussed

Re: [Pharo-dev] Ideas wanted: "Patterns to sustain feedback loops"

Hi Marcus, as you know I, and others, think the most important thing is analyzing the community economically and trying to increase the flow of resources into the community and keeping people and their skills in the community. If we do not get on a growth path we are small enough that we

Re: [Pharo-dev] Discussing the roadmap

Hi Stef, > On Jul 6, 2017, at 1:55 AM, Stephane Ducasse wrote: > > We would like to share this list with you and get your feedback and inputs. > It will be presented and discussed again at ESUG. > > Stef on the behalf of the engineering team of the Pharo consortium. >

Re: [Pharo-dev] [ANN] Iceberg 0.5.1 with Pull Request review tool

Will this update be picked up with the scripted steps you described for 0.5 (particularly if you want to run in a v6 image?).And do we just run them again to get it? (I assume that if you have already loaded 0.5 you just do the metacello bit - but in a new image, would those steps get you

Re: [Pharo-dev] Discussing the roadmap

That's an exciting list - that keeps up the momentum of what you guys started (and in fact called out at ESUG 2017 in Lugano - so interesting this is a 10 year milestone). I’m pleased to see the Retina item listed as well as building on refactoring and command line support (I’ll bet others

Re: [Pharo-dev] [ANN] Iceberg 0.5.1 with Pull Request review tool

it should be fixed now, I think :) > On 6 Jul 2017, at 17:07, Pavel Krivanek wrote: > > There seems to be an issue in the baseline with circular dependencies. Load > it, skip all warnings and then try to reload all packages in the Iceberg > repository (from the

Re: [Pharo-dev] [ANN] Iceberg 0.5.1 with Pull Request review tool

There seems to be an issue in the baseline with circular dependencies. Load it, skip all warnings and then try to reload all packages in the Iceberg repository (from the Iceberg window). -- Pavel 2017-07-06 16:53 GMT+02:00 Norbert Hartl : > Am I the only one or are there

Re: [Pharo-dev] Epicea feedback

Thanks I still didn't invest time to fix them but I registered both in fogbugz as: https://pharo.fogbugz.com/f/cases/20223/Epicea-check-usability-bug-to-apply-changes https://pharo.fogbugz.com/f/cases/20225/Epicea-would-be-nice-is-to-have-some-menus-on-the-sessions-items cheers, Martin On Sat,

Re: [Pharo-dev] Epicea and #name in #behaviorAffectedName

Hi Torsten, just copied your report into here: https://pharo.fogbugz.com/f/cases/20222/Epicea-deprecation-warning-dialog-popped-up-and-repeated-itself-unstoppable I'll see it ASAP. Thanks and sorry for my delay. Martín El 19/5/2017 17:45, "Torsten Bergmann" escribió: > Hi, >

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

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

[Pharo-dev] [pharo-project/pharo-core] 9b87bb: 60507

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 9b87bb71fd929f5f2af417887b3598f79784ae60 https://github.com/pharo-project/pharo-core/commit/9b87bb71fd929f5f2af417887b3598f79784ae60 Author: Jenkins Build Server Date:

Re: [Pharo-dev] OSPlatform currentVersion

Ok, it works in the 7.0 vm. I opened the ticket again in order that we do not forget the fix for 6.1 https://pharo.fogbugz.com/f/cases/20156/OSPlatform-current-returns-a-MacOSPlatform-instead-of-a-MacOSXPlatform-on-macOS-Sierra

Re: [Pharo-dev] OSPlatform currentVersion

Ok, then it is a regression because I downloaded vm and image freshly before trying thanks, Norbert > Am 06.07.2017 um 14:15 schrieb Alistair Grant : > > Hi Norbet, > > Take a look at: > >

Re: [Pharo-dev] OSPlatform currentVersion

Hi Norbet, Take a look at: http://forum.world.st/Working-OSProcess-configuration-for-Pharo-6-release-please-tp4952002p4952005.html HTH, Alistair On 6 July 2017 at 14:06, Norbert Hartl wrote: > Does anyone know when the output for > > OSPlatform currentVersion > > changed?

[Pharo-dev] OSPlatform currentVersion

Does anyone know when the output for OSPlatform currentVersion changed? In Pharo 4 I get '1095' and in pharo6 I get '10.12.5'. The determination if it is a OSX system or older is done by currentVersion asNumber >= 1000 which changes behaviour because the currentVersion string has been

Re: [Pharo-dev] Discussing the roadmap

TxText removal is already done too. -- Pavel 2017-07-06 10:55 GMT+02:00 Stephane Ducasse : > We would like to share this list with you and get your feedback and inputs. > It will be presented and discussed again at ESUG. > > Stef on the behalf of the engineering team of

Re: [Pharo-dev] Simply Happy

Pharo is finally in a mature state. I would not recommend Pharo few years back because of severe lack of documentation and libraries and several other issues.I would definetly recommend it now to people who want to try something fresh and well designed. Documentation is in much better state, new

Re: [Pharo-dev] Simply Happy

+42 > On 6 Jul 2017, at 10:58, Tudor Girba wrote: > > +100 > > Doru > > >> On Jul 6, 2017, at 10:57 AM, Stephane Ducasse >> wrote: >> >> Hi pharoing people >> >> Just a little word to tell you that I'm super happy about the future of >>

Re: [Pharo-dev] Simply Happy

Definitely. Glad to be aboard the flying bus. Phil On Thu, Jul 6, 2017 at 10:57 AM, Stephane Ducasse wrote: > Hi pharoing people > > Just a little word to tell you that I'm super happy about the future of > Pharo. > The consortium is growing and will probably be able

Re: [Pharo-dev] Simply Happy

Yeah, it is truly great! I think we've crossed a border. In the past a lot of our legacy was compensating the awesomeness. In the meantime I have the feeling that the awesomeness sticks out much more clear. Thank you all for making this community! Norbet > Am 06.07.2017 um 10:57 schrieb

Re: [Pharo-dev] Simply Happy

Thank you ! I'm trying to push Pharo in Cameroon now. On Thu, Jul 6, 2017 at 9:57 AM, Stephane Ducasse wrote: > Hi pharoing people > > Just a little word to tell you that I'm super happy about the future of > Pharo. > The consortium is growing and will probably be able

Re: [Pharo-dev] Simply Happy

+100 Doru > On Jul 6, 2017, at 10:57 AM, Stephane Ducasse wrote: > > Hi pharoing people > > Just a little word to tell you that I'm super happy about the future of Pharo. > The consortium is growing and will probably be able to pay esteban and > clement. > The

[Pharo-dev] Simply Happy

Hi pharoing people Just a little word to tell you that I'm super happy about the future of Pharo. The consortium is growing and will probably be able to pay esteban and clement. The roadmap for Pharo 70 is really exciting. The bootstrap, git and the new project in the pipe will boost us. So I

[Pharo-dev] Discussing the roadmap

We would like to share this list with you and get your feedback and inputs. It will be presented and discussed again at ESUG. Stef on the behalf of the engineering team of the Pharo consortium. # Pharo 7 (and 8) potential roadmap This document contains a list of actions that should be done