[Pharo-dev] [Pharo 7.0-dev] Build #140: 20446 Properly categorize finalizeValues and finalize messages in "finali…

There is a new Pharo build available! The status of the build #140 was: SUCCESS. The Pull Request #303 was integrated: "20446 Properly categorize finalizeValues and finalize messages in "finali…" Pull request url: https://github.com/pharo-project/pharo/pull/303 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #139: 20458 Two uncommented classes in Reflectivity package

There is a new Pharo build available! The status of the build #139 was: SUCCESS. The Pull Request #304 was integrated: "20458 Two uncommented classes in Reflectivity package" Pull request url: https://github.com/pharo-project/pharo/pull/304 Issue Url:

Re: [Pharo-dev] Iceberg Default Subdirectory Setting?

Stephan Eggermont-3 wrote > Is that shared with multiple images? There is already a setting to share repos (actually to set a default repo root folder). This setting would just be for where the packages live relative to the git root folder of that particular repo (e.g. ./src, ./repository, etc).

Re: [Pharo-dev] Iceberg Default Subdirectory Setting?

On 20/09/17 23:50, Sean P. DeNigris wrote: I always put my packages in gitroot/repository per instructions I read when I was starting with FT (Dale's IIRC). It's a (minor) drag to type that every time I add a local git repo. How would y'all feel about a setting? Is that shared with multiple

[Pharo-dev] Iceberg Default Subdirectory Setting?

I always put my packages in gitroot/repository per instructions I read when I was starting with FT (Dale's IIRC). It's a (minor) drag to type that every time I add a local git repo. How would y'all feel about a setting? - Cheers, Sean -- Sent from:

Re: [Pharo-dev] [Pharo 7.0-dev] Build #135: 20434-use-Ring2-during-the-bootstrap

Yes it was the talk of the conference and it would have been a tough talk without the cartoons :) On Wed, Sep 20, 2017 at 12:08 PM, Sven Van Caekenberghe wrote: > >> On 20 Sep 2017, at 11:40, Marcus Denker wrote: >> >> More infos about Ring2: >> >>

Re: [Pharo-dev] Pharo-Launcher Windows 10 requires admin privilg

Tx a lot for the feedback! On Wed, Sep 20, 2017 at 8:49 AM, Alex Laurie wrote: > Latest version of Pharo launcher requires Admin privileges to launch > properly. If it doesn't have Admin permission it throws a "stdout does not > exist." error. > > Not sure if this is the

Re: [Pharo-dev] Bloc status

Sean you should consider that TxText was important because it enabled the new textEditor. Bloc is stabilising for real. I can tell you that it was not an easy decision to rewrite Bloc after Brescia. And it should get out. SimpleMorphic and Morphic 3 where not related to our effort. I really

Re: [Pharo-dev] Iceberg

On 19/09/17 17:52, Marcus Denker wrote: I personally find it very confusing that http://files.pharo.org/vm/ does not have the current VMs… Now I am confused. The date seems to suggest they are current? At least on Linux Stephan

Re: [Pharo-dev] [Pharo 7.0-dev] Build #138: 20443-SDL-Event-not-initialized

And now opening external window is working out of the box. Cool. 2017-09-20 18:28 GMT+02:00 : > There is a new Pharo build available! > > The status of the build #138 was: SUCCESS. > > The Pull Request #300 was integrated: "20443-SDL-Event-not-initialized" > Pull

[Pharo-dev] [Pharo 7.0-dev] Build #138: 20443-SDL-Event-not-initialized

There is a new Pharo build available! The status of the build #138 was: SUCCESS. The Pull Request #300 was integrated: "20443-SDL-Event-not-initialized" Pull request url: https://github.com/pharo-project/pharo/pull/300 Issue Url: https://pharo.fogbugz.com/f/cases/20443 Build Url:

Re: [Pharo-dev] Pharo-Launcher Windows 10 requires admin privilg

Thx for your feedback. How did you install it? Actually for a long time I believe PharoLauncher should be installed under a User folder (the same as Unix systems) and not under "Program Files" which may be the root cause of such problems. If PharoLauncher has been installed under "Program

[Pharo-dev] [Pharo 7.0-dev] Build #137: 20435-The-CI-process-should-fail-if-the-conversion-fails

There is a new Pharo build available! The status of the build #137 was: SUCCESS. The Pull Request #292 was integrated: "20435-The-CI-process-should-fail-if-the-conversion-fails" Pull request url: https://github.com/pharo-project/pharo/pull/292 Issue Url:

Re: [Pharo-dev] Bloc status

Tudor Girba-2 wrote > As we are a commercial entity, for us this is a business issue, not a > hobby. This means that we have all incentives to finish things so that we > can build what we actually want to build :). This is good to hear. I share Marcus' concern. After (almost? about?) 10 years in

[Pharo-dev] [Pharo 7.0-dev] Build #136: 20415-Restore-the-extra-morphic-worlds-properly-on-startup

There is a new Pharo build available! The status of the build #136 was: SUCCESS. The Pull Request #298 was integrated: "20415-Restore-the-extra-morphic-worlds-properly-on-startup" Pull request url: https://github.com/pharo-project/pharo/pull/298 Issue Url:

Re: [Pharo-dev] [Pharo 7.0-dev] Build #135: 20434-use-Ring2-during-the-bootstrap

> On 20 Sep 2017, at 11:40, Marcus Denker wrote: > > More infos about Ring2: > > https://www.slideshare.net/esug/metamodeling-of-custom-pharo-images The cartoons on the slides are hilarious ! >> On 20 Sep 2017, at 11:32, ci-pharo-ci-jenki...@inria.fr wrote: >>

Re: [Pharo-dev] [Pharo 7.0-dev] Build #135: 20434-use-Ring2-during-the-bootstrap

More infos about Ring2: https://www.slideshare.net/esug/metamodeling-of-custom-pharo-images > On 20 Sep 2017, at 11:32, ci-pharo-ci-jenki...@inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #135 was: SUCCESS. > > The Pull Request #294 was

[Pharo-dev] [Pharo 7.0-dev] Build #135: 20434-use-Ring2-during-the-bootstrap

There is a new Pharo build available! The status of the build #135 was: SUCCESS. The Pull Request #294 was integrated: "20434-use-Ring2-during-the-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/294 Issue Url: https://pharo.fogbugz.com/f/cases/20434 Build Url:

Re: [Pharo-dev] Bloc status

Hi, > On Sep 20, 2017, at 10:23 AM, Marcus Denker wrote: > >> >> On 20 Sep 2017, at 10:12, Tudor Girba wrote: >> >> Hi, >> >>> On Sep 20, 2017, at 9:22 AM, Norbert Hartl wrote: >>> >>> >>> Am 19.09.2017 um 22:50

Re: [Pharo-dev] Bloc status

> On 20 Sep 2017, at 10:12, Tudor Girba wrote: > > Hi, > >> On Sep 20, 2017, at 9:22 AM, Norbert Hartl wrote: >> >> >> >>> Am 19.09.2017 um 22:50 schrieb Tudor Girba : >>> >>> Hi, >>> >>> Thanks for the question :). >>> >>>

[Pharo-dev] [Pharo 7.0-dev] Build #134: 20431-Move-initialization-of-Color-InstructionStream-and-SmallInteger

There is a new Pharo build available! The status of the build #134 was: SUCCESS. The Pull Request #290 was integrated: "20431-Move-initialization-of-Color-InstructionStream-and-SmallInteger" Pull request url: https://github.com/pharo-project/pharo/pull/290 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #133: 20437 recategorized methods

There is a new Pharo build available! The status of the build #133 was: SUCCESS. The Pull Request #295 was integrated: "20437 recategorized methods" Pull request url: https://github.com/pharo-project/pharo/pull/295 Issue Url: https://pharo.fogbugz.com/f/cases/20437 Build Url:

Re: [Pharo-dev] Bloc status

Hi, > On Sep 20, 2017, at 9:22 AM, Norbert Hartl wrote: > > > >> Am 19.09.2017 um 22:50 schrieb Tudor Girba : >> >> Hi, >> >> Thanks for the question :). >> >> Indeed, the summary of Stef is quite good. >> >> Here are some additions: >> - Indeed,

Re: [Pharo-dev] Bloc status

> Am 19.09.2017 um 22:50 schrieb Tudor Girba : > > Hi, > > Thanks for the question :). > > Indeed, the summary of Stef is quite good. > > Here are some additions: > - Indeed, Bloc gets stable. Recently, we learned that we can optimize the > layouts even more and Alex

[Pharo-dev] Pharo-Launcher Windows 10 requires admin privilg

Latest version of Pharo launcher requires Admin privileges to launch properly. If it doesn't have Admin permission it throws a "stdout does not exist." error. Not sure if this is the right mailing list for the launcher, if not let me know. Cheers, Alex