Re: [Pharo-dev] Moving from mc to tonel?

> I suspect it's related to the large number of commits in my repo. I made > some tweaks and succeeded to create the fast-import file. But I get: > All files in a single commit will be held temporarily in MemoryStore, so unless you have GBs of code in _single_ commit it shouldn't be a problem.

Re: [Pharo-dev] Moving from mc to tonel?

> On 5 Dec 2017, at 08:34, Alistair Grant wrote: > > On 5 December 2017 at 03:41, Martin Dias wrote: >> I suspect it's related to the large number of commits in my repo. I made >> some tweaks and succeeded to create the fast-import file. But I get:

Re: [Pharo-dev] Moving from mc to tonel?

On 5 December 2017 at 03:41, Martin Dias wrote: > I suspect it's related to the large number of commits in my repo. I made > some tweaks and succeeded to create the fast-import file. But I get: > > fatal: Unsupported command: . > fast-import: dumping crash report to

Re: [Pharo-dev] Pharo newsletter archive

+1 Doru > On Dec 5, 2017, at 7:54 AM, Stephane Ducasse wrote: > > Yes good idea! > Tx > > On Mon, Dec 4, 2017 at 7:52 PM, Torsten Bergmann wrote: >> Hi, >> >> the newsletter archive is now available on >> >> "newsletter.pharo.org" >> >> which is

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo TechTalk 21 Nov: Discord Demo

Thanks! Doru > On Nov 23, 2017, at 8:26 PM, Juraj Kubelka wrote: > > Hi, the new version is available here: > https://www.youtube.com/watch?v=y1EzOnfHUe0 > > Hopefully it helps :-) > Juraj > >> On Nov 22, 2017, at 15:45, Sean P. DeNigris

Re: [Pharo-dev] Pharo newsletter archive

Yes good idea! Tx On Mon, Dec 4, 2017 at 7:52 PM, Torsten Bergmann wrote: > Hi, > > the newsletter archive is now available on > > "newsletter.pharo.org" > > which is more easy to remember. > > Thanks Marcus for setting up the redirect! > > Bye > T. >

Re: [Pharo-dev] Moving from mc to tonel?

I suspect it's related to the large number of commits in my repo. I made some tweaks and succeeded to create the fast-import file. But I get: fatal: Unsupported command: . fast-import: dumping crash report to .git/fast_import_crash_10301 Do you recognize this error? I will check my changes

Re: [Pharo-dev] [Vm-dev] Garbage Collection (was Re: Discussing the roadmap)

Hi Eliot, On 4 December 2017 at 23:44, Eliot Miranda wrote: > > Alas a forwarding object has two fields that need to be set in separate words. > The class index in the header must be the forwarder class index, > and the first word of the object body must point to the

Re: [Pharo-dev] Bloc Feedback

On 5 December 2017 at 05:19, Stephane Ducasse wrote: > Hi Aliaksei > > Read again this sentence :) > > "BlPostAction" - a valuable that is guaranteed to be evaluated in the > beginning of every frame before anything else. > > MAy be BlPostAction should be renamed

Re: [Pharo-dev] Polymorphism between Strings and FileReference

To me stringOfFileReference is a bad smell. On Fri, Dec 1, 2017 at 12:04 PM, Cyril Ferlicot wrote: > On Fri, Dec 1, 2017 at 11:55 AM, Alistair Grant wrote: >> Hi Cyril, >> >> The normal way to handle this is #asFileReference, so you can just

Re: [Pharo-dev] [TechTalk] Topics Wanted for 2018!

I could show how to setup a pillar project. Stef On Fri, Dec 1, 2017 at 11:58 AM, Marcus Denker wrote: > Hi, > > As you know, we are trying to have one Pharo tech-talk per month. > > The idea is to use this for > -> mini “Lectures” > -> Demos of interesting Projects > ->

Re: [Pharo-dev] Bloc and Gestures

I really hope that we will be able to take advantage of the work done by merwan and jb on gestures but yes we need sdl20 working. Stef On Sat, Dec 2, 2017 at 1:02 PM, Aliaksei Syrel wrote: > Hi Sean, > > The main problem of gestures is that they can only theoretically work

Re: [Pharo-dev] Bloc Feedback

Hi Aliaksei Read again this sentence :) "BlPostAction" - a valuable that is guaranteed to be evaluated in the beginning of every frame before anything else. MAy be BlPostAction should be renamed BlEarlyAction On Sat, Dec 2, 2017 at 5:26 PM, Aliaksei Syrel wrote: > Hi,

[Pharo-dev] [Pharo 7.0-dev] Build #358: 20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages

There is a new Pharo build available! The status of the build #358 was: SUCCESS. The Pull Request #569 was integrated: "20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages" Pull request url: https://github.com/pharo-project/pharo/pull/569 Issue Url:

[Pharo-dev] Pharo newsletter archive

Hi, the newsletter archive is now available on "newsletter.pharo.org" which is more easy to remember. Thanks Marcus for setting up the redirect! Bye T.

Re: [Pharo-dev] [Vm-dev] Garbage Collection (was Re: Discussing the roadmap)

Hi Ben, > On Dec 4, 2017, at 6:38 AM, Ben Coman wrote: > >> On 4 December 2017 at 15:47, Clément Bera wrote: >> >> Here are some ideas/things to say on the tip of my head: >> - Changing an object to a forwarding object is non atomic (we need to

[Pharo-dev] feenk log

Hi, Here is an update of the work on Bloc and GT: Bloc: - Bezier curves (cubic and quadratic). https://twitter.com/feenkcom/status/93476564021504 https://twitter.com/feenkcom/status/934856909001252865 - Dragging is now possible through a BlDragHandler that can be attached to any element.

Re: [Pharo-dev] Alternative bytecode sets demo request

Hi Ben, > On Dec 4, 2017, at 4:17 AM, Ben Coman wrote: > >> On 4 December 2017 at 10:48, Eliot Miranda wrote: >> Hi Ben, >> >>> On Sun, Dec 3, 2017 at 6:08 PM, Ben Coman wrote: >>> >>> I'm shooting in the dark here since

[Pharo-dev] [Pharo 7.0-dev] Build #357: 20781-update-to-iceberg-064

There is a new Pharo build available! The status of the build #357 was: SUCCESS. The Pull Request #560 was integrated: "20781-update-to-iceberg-064" Pull request url: https://github.com/pharo-project/pharo/pull/560 Issue Url: https://pharo.fogbugz.com/f/cases/20781 Build Url:

Re: [Pharo-dev] Alternative bytecode sets demo request

On 4 December 2017 at 10:48, Eliot Miranda wrote: > Hi Ben, > > On Sun, Dec 3, 2017 at 6:08 PM, Ben Coman wrote: >> >> I'm shooting in the dark here since its a bit hard to grasp... >> a. The implications of support alternative bytecode sets >>

[Pharo-dev] [Pharo 7.0-dev] Build #356: 20793-During-Bootstrap-if-a-baseline-installation-fails-it-should-cancel-the-process

There is a new Pharo build available! The status of the build #356 was: FAILURE. The Pull Request #567 was integrated: "20793-During-Bootstrap-if-a-baseline-installation-fails-it-should-cancel-the-process" Pull request url: https://github.com/pharo-project/pharo/pull/567 Issue Url:

Re: [Pharo-dev] Design pattern for wrapper/proxy objects?

Hi Luke, Not only for the details of a particular proxy implementation like Ghost, but also because of all the discussions around it, I think this journal paper [1] we wrote may be of help to you. Cheers, [1] https://hal.inria.fr/hal-01081236 On Mon, Dec 4, 2017 at 5:51 AM, Luke Gorrie

Re: [Pharo-dev] Pharo Launcher endless loop opening debuggers in Pharo 6.1

Hi, I cannot reproduce this bug. Do you have the log or the stack trace? > Le 2 déc. 2017 à 14:51, Bernhard Pieber a écrit : > > I ran into an annoying problem using the latest Pharo 6.1 (stable) from Pharo > Launcher. I am on macOS Sierra Version 10.12.6. > > Steps to

Re: [Pharo-dev] [Vm-dev] Garbage Collection (was Re: Discussing the roadmap)

--- Begin Message --- Perhaps the solution resides in settings you can tweak from within Smalltalk?  Something like MemoryPolicy you have in VisualWorks for memory & garbage collection management. I don't think fixing the behavior of memory management & garbage collection (marking, sweeping,

Re: [Pharo-dev] Design pattern for wrapper/proxy objects?

Thanks Ben & Henrik for the ideas! I will scratch my head a bit and then try to do something sensible. :-)

Re: [Pharo-dev] Design pattern for wrapper/proxy objects?

For proxies/wrappers, you might want to look into how the Ghost framework interrupts sends. (I don't know the exact details, but I'd guess step 1 is subclassing ProtoObject, rather than Object) For your specific case, isn't there already a *Struct class in the image you can subclass, create a