Re: [Pharo-dev] [pharo-project/pharo-core] d2bfc7: 60040

Great. Congratulations! Doru > On May 27, 2016, at 12:43 PM, Esteban Lorenzano wrote: > > so yes, we finally did it :) > > Esteban > >> On 27 May 2016, at 12:27, GitHub wrote: >> >> 60040 >> 14605 Integrate Epicea >>

[Pharo-dev] got some bugs in Pharo 50

Just to report (I did not have the time to check in 60a) but I got red square of death with komitter. I also got NECTypedModel>>initializeSelectorsFor: aClass |excludedClasses| selectors reset. excludedClasses := (expanded ifTrue: [#()] ifFalse: [Object withAllSuperclasses]).

Re: [Pharo-dev] Debugger is not stable

Hi. 2016-06-04 18:01 GMT+02:00 stepharo : > I got it now > GTInspector does not open on latest stack frame but the one before and > if I scroll I get it > Yes. And step into not autoscroll stack view. I like GTDebugger. It is step forward for our tools. Now only real

Re: [Pharo-dev] Debugger is not stable

Hi, We certainly want to have a bullet proof debugger. However, by looking at the selector you mention, the problem you got with the crashing debugger is almost surely reproducible with the old debugger. It is unlikely related to the GT Debugger (which is essentially a UI). The issue you

Re: [Pharo-dev] Spotter suggestions

Hi, I promised to get back to this one. I know it’s late, but I somehow did not manage until now. I apologize. There is a bit of discrepancy between what happens during the development of GT and what is being communicated. One of the feelings that seem to come through is that the feedback is

[Pharo-dev] the impact of moldability

Hi, There were a couple of emails in the recent period that questioned the usefulness of moldability (the ability of developers to customize their tools deeply and inexpensively). More specifically, the question was about the moldability of the GTDebugger. I put together a couple of thoughts

Re: [Pharo-dev] Debugger is not stable

Hi, I tried several times to reproduce this and could not. If you could get an image with the problem it would be the best case scenario. Cheers, Doru > On Jun 4, 2016, at 5:39 PM, stepharo wrote: > > Hi andrei > > >> >> Do you use a particular Wallet object? > it was

Re: [Pharo-dev] Debugger is not stable

Hi andrei Do you use a particular Wallet object? it was in one of the tests. I put a halt into the coinFor: into2: What image are you using? Pharo5.0 Latest update: #50759 Can you fuel out and send the stack if you get this error again? I will try to reproduce it and send it to you.

Re: [Pharo-dev] 200000 factorial => VM crash

+ 1 Thank you very much Eliot

Re: [Pharo-dev] VR tracking

Hi bob Le 2/6/16 à 18:10, Bob Clark a écrit : I was just thinking about integration of Pharo into modern technologies and I've seen some of your scope & scale of graphics work. It's been years since I did graphics but thinking about the future because I's love Pharo to get into the gaming

Re: [Pharo-dev] Bloc/TxText Status

This morning I discussed with Doru, and Bloc goes well… It silently went through some active development phase. good to know :( I should not have invested into bloc in fact. Stef

Re: [Pharo-dev] Pillar configuration bug ?

Le 03/06/2016 14:51, Esteban Lorenzano a écrit : > Without the parser you can’t do anything so I would expect the parser to be a > core part. > But anyway, even agreeing with your PoV, if I load #(html exporter), then I > have unreferenced pillar classes in the resulting image (PRDocumentItem

Re: [Pharo-dev] Debugger is not stable

Hi Stef, On Sat, Jun 4, 2016 at 9:08 AM, stepharo wrote: > Hi andrei > > ThibaultDucasse/Wallet > > And remove the roundTo: 0.1 in the coinFor:into2: method. > > The while loop will iterate forever and pressing on into nearly kill you > > else you get killed by DNU from the

Re: [Pharo-dev] Pillar configuration bug ?

> On 04 Jun 2016, at 09:35, stepharo wrote: > >>> >>> On 01 Jun 2016, at 20:44, Damien Cassou wrote: >>> >>> On June 1, 2016 6:31:29 PM GMT+02:00, Esteban Lorenzano >>> wrote: I’m installing pillar like this:

Re: [Pharo-dev] Debugger is not stable

Hi, > On Jun 4, 2016, at 9:08 AM, stepharo wrote: > > Hi andrei > ThibaultDucasse/Wallet > > And remove the roundTo: 0.1 in the coinFor:into2: method. > The while loop will iterate forever and pressing on into nearly kill you > > else you get killed by DNU from the

Re: [Pharo-dev] install GitFileTree from catalog --> missing class

This is why we need to have metadata of loaded packages inside the image. Because right now the maintainer of the package is forced to remove information from his configuration :( Been there with RB. Setf Le 3/6/16 à 13:38, Esteban Lorenzano a écrit : yes, but then GitFileTree from

Re: [Pharo-dev] Pillar configuration bug ?

On 01 Jun 2016, at 20:44, Damien Cassou wrote: On June 1, 2016 6:31:29 PM GMT+02:00, Esteban Lorenzano wrote: I’m installing pillar like this: pillar: spec spec project: 'Pillar' with: [ spec

Re: [Pharo-dev] endless loop again

Le 3/6/16 à 19:16, Esteban A. Maringolo a écrit : Regarding the first part of your email, about UI lockups, it is almost unavoidable, because in Pharo almost everything happens in the main thread, as you pointed out. Yes. This is all my point. When only UI events should happen there, and

Re: [Pharo-dev] Debugger is not stable

Hi andrei ThibaultDucasse/Wallet And remove the roundTo: 0.1 in the coinFor:into2: method. The while loop will iterate forever and pressing on into nearly kill you else you get killed by DNU from the debugger. Stef PS: Yes I know I'm the stupider guy in the world because I criticise the