Re: [Pharo-dev] [Moose-dev] MacroRecorder available in Pharo

WOW a pharo video where someone actually speaks, thats rare :D Impressive tool, and certainly useful if you have to do a lot of changes in a lot of code. The name is a bit misleading because its not really a general purpose macro recorder and focused only on transformations. I vaguely remember

Re: [Pharo-dev] VoyageMongo and cache compaction

> On 04 Dec 2015, at 00:16, Ben Coman wrote: > > I haven't used VoyageMongo, but just a general comment that maybe the > testcase is best produced at your end, since you understand the > symptoms and can cut down a slice of your application as a template. > Publishing that

Re: [Pharo-dev] Java Future

Question: how long to drop the slice into the inbox? On Fri, Dec 4, 2015 at 8:51 AM, EuanM wrote: > Hi Steph, > > As a newcomer, here is my experience with my first bug-fix: > > I wrote the fix in about 5 minutes. > > It then took several weeks to get the big-fix accepted

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

I feel you :) Without having thought this through completely: if you look at the implementation of DynamicVariable>>value:during: you’ll see that the way it works is that the variable is bound to the active process. In the debugger you have access to the process that is being debugged and thus

Re: [Pharo-dev] [pharo-project/pharo-core] d12673: 50483

ConfigurationOfIDE job fails because of this error: Could not resolve: Glamour-Morphic-Brick-Tests [Glamour-Morphic-Brick-Tests-TheIntegrator.14] in /builds/workspace/Pharo-5.0-Update-Step-1-Tracker/package-cache http://smalltalkhub.com/mc/Moose/Glamour/main/ Can someone with write permissions

Re: [Pharo-dev] Java Future

We are quite fast in integrating the last weeks (even months). *Reviewed* fixes get integrated within hours, and I try to review as much as I can if others do not. To me this sounds like a fix to some other project on SmalltalkHub. T The thing here is that this is like gitHub: if a random Java

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

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

[Pharo-dev] [pharo-project/pharo-core] d12673: 50483

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

[Pharo-dev] [issue tracker] action of package maintainers needed

Hi, We have again 6 issues that are “fixed upstream” https://pharo.fogbugz.com/f/filters/138/fixed-upstream The maintainers of these packages should not forget to push a current version into Pharo. The easier you do that, the earlier the

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

Here’s a snippet to play with: p := Processor activeProcess. x := 2. v := TestDynamicVariable value: x during: [ ((p instVarNamed: 'env') ifNotNil: [ :env| env copyWithout: nil ]) inspect ]. ((p instVarNamed: 'env') ifNotNil: [ :env| env

[Pharo-dev] changes view broken

Oh oh, I broke the changes view. For example, open Repository of Rubric, select a latest package, press changes -> no result merge -> shows the diff caused by my fix for 17148 Seeing changes and

Re: [Pharo-dev] Java Future

There were two issues - one was lack of handover of packages in the Catalog. The other required a reboot of Smalltalkhub On 4 December 2015 at 09:54, Marcus Denker wrote: > We are quite fast in integrating the last weeks (even months). > > *Reviewed* fixes get integrated

[Pharo-dev] MacroRecorder available in Pharo

Hello guys, I would like to present you MacroRecorder, a tool to build custom source code transformations in Pharo. The tool is available in the Catalog for some weeks now. The current version runs in Pharo 5 and there is an old version running in Pharo 4. To show how this tool works, I

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

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

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

On Fri, Dec 4, 2015 at 12:05 PM, Max Leske wrote: > > On 04 Dec 2015, at 14:29, Mariano Martinez Peck > wrote: > > Max...Seaside uses WADynamicVariable (NOT DynamicVariable) which > are completely different. WADynamicVariable uses exception mechanism >

Re: [Pharo-dev] Java Future

We do need more ease of integration with other software. I agree Normally we should have spur by next wednesday * 64 bit * OS Process made easier. Mariano did you started to work on that? * FFI not requiring a PhD Yes. * Being able to use Pharo with normal text based tools (like

Re: [Pharo-dev] Unicode Support

Hi Euan I think it’s great that you’re trying this. I hope you know what you’re getting yourself into :) I’m no Unicode expert but I want to add two points to your list (although you’ve probably already thought of them): - Normalisation and conversion

Re: [Pharo-dev] GTDebugger not draggable with latest VM

Seems that starting with Pharo 50483 one cannot drag the inspector/playground/debugger. No idea what happened. On Fri, Dec 4, 2015 at 3:19 PM, Blondeau Vincent < vincent.blond...@worldline.com> wrote: > Hi, > > > > I have a problem on the latest Moose6.0 image. > > I was not able to open a

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

> On 04 Dec 2015, at 14:29, Mariano Martinez Peck wrote: > > Max...Seaside uses WADynamicVariable (NOT DynamicVariable) which are > completely different. WADynamicVariable uses exception mechanism while > DynamicVariable uses the ProcessSpecificVariable. > But thanks

Re: [Pharo-dev] [pharo-project/pharo-core] d12673: 50483

Thank you. -- Pavel 2015-12-04 13:37 GMT+01:00 Andrei Chis : > I copied the package to the Glamour repo. > But I have no idea why the integrator decided to create that package. > > Cheers, > Andrei > > On Fri, Dec 4, 2015 at 12:20 PM, Pavel Krivanek

Re: [Pharo-dev] GTDebugger not draggable with latest VM

Seems to happen due to the fix in issue 17178 On Fri, Dec 4, 2015 at 4:21 PM, Andrei Chis wrote: > Seems that starting with Pharo 50483 one cannot drag the > inspector/playground/debugger. > > No idea what happened. > > On

[Pharo-dev] Call for Papers: Constrained and Reactive Objects Workshop at Modularity 2016

CROW 2016 - Constrained and Reactive Objects Workshop The Constrained and Reactive Objects Workshop (CROW) invites papers that present research results related to using constraints and reactive programming in combination or integrated with imperative and object-oriented systems. This research

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

Max...Seaside uses WADynamicVariable (NOT DynamicVariable) which are completely different. WADynamicVariable uses exception mechanism while DynamicVariable uses the ProcessSpecificVariable. But thanks anyway! On Fri, Dec 4, 2015 at 7:32 AM, Max Leske wrote: > Here’s a

Re: [Pharo-dev] [Pharo-users] MacroRecorder available in Pharo

Excellent! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Dec 4, 2015, at 5:34 AM, Gustavo Santos wrote: > > Hello guys, > > I would like to present you

[Pharo-dev] GTDebugger not draggable with latest VM

Hi, I have a problem on the latest Moose6.0 image. I was not able to open a Roassal view, I had a NativeBoost Generic failure... So I updated the VM to last stable, and, now, the GTdebugger and the Moose panel are not draggable anymore... Can somebody is able to reproduce the problem? Thanks

Re: [Pharo-dev] [pharo-project/pharo-core] d12673: 50483

I copied the package to the Glamour repo. But I have no idea why the integrator decided to create that package. Cheers, Andrei On Fri, Dec 4, 2015 at 12:20 PM, Pavel Krivanek wrote: > ConfigurationOfIDE job fails because of this error: > Could not resolve:

Re: [Pharo-dev] How to listen Monticello load start/end (and origin of changes)

Hi Martin, Interesting solution but it feels a bit like a hack. For the GTools we made a solution that triggers a custom announcer before and after a Monticello load. We'll make a slice later today. Cheers, Andrei On Thu, Dec 3, 2015 at 3:46 PM, Martin Dias wrote: > Hi,

[Pharo-dev] SessionManager (aka new startup / shutdown list manager) needs testers

Hi, Guillermo, Pablo and I started to work on a new implementation for the image startup / shutdown list. The old implementation misses domain objects, polluted the SmalltalkImage class and introduced crazy dependencies to other packages. So, what is Session Manager? a replacement of the

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

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

[Pharo-dev] [pharo-project/pharo-core] 03087c: 50484

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 03087c82c794c6db8cb3a15435a9e920e8b99cc9 https://github.com/pharo-project/pharo-core/commit/03087c82c794c6db8cb3a15435a9e920e8b99cc9 Author: Jenkins Build Server Date:

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

OK, I solved the Halt problem. I did it by adding: WADebugErrorHandler class >> exceptionSelector ^ super exceptionSelector, Halt And this override: WAErrorHandler >> handleException: anException (Error handles: anException) ifTrue: [ ^ self handleError: anException ]. (Warning handles:

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

On Fri, Dec 4, 2015 at 1:29 PM, Mariano Martinez Peck wrote: > OK. But be aware it is very very little tested and probably still a hack, > and it still need overrides. Hopefully you will help me to polish it until > we get a "SeasidePharoDebugging" package with no

Re: [Pharo-dev] How to listen Monticello load start/end (and origin of changes)

Hi, A fix is now available that uses custom announcements to signal the start/end of a monticello version load (MCVersionLoaderStartAnnouncement, MCVersionLoaderStopAnnouncement) A review is required: https://pharo.fogbugz.com/f/cases/17186 Cheers, Andrei On Fri, Dec 4, 2015 at 1:52 PM, Andrei

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

> Am 04.12.2015 um 16:05 schrieb Max Leske : > > >> On 04 Dec 2015, at 14:29, Mariano Martinez Peck > > wrote: >> >> Max...Seaside uses WADynamicVariable (NOT DynamicVariable) which are >> completely different.

Re: [Pharo-dev] #sum:, #detectSum:, #sumNumbers:

> On 04 Dec 2015, at 01:49, Ben Coman wrote: > > On Fri, Dec 4, 2015 at 4:23 AM, Nicolai Hess > wrote: >> >> >> 2015-12-03 14:48 GMT+01:00 Ben Coman : >>> >>> On Wed, Dec 2, 2015 at 10:45 PM,

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

> On 04 Dec 2015, at 17:11, Mariano Martinez Peck wrote: > > I found a way Much cleaner and easier. Awesome! > I will clean it, test it a bit more and try to package it for public usage :) Give me a snippet! I want to play with it! :D > > On Fri, Dec 4, 2015 at

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

OK. But be aware it is very very little tested and probably still a hack, and it still need overrides. Hopefully you will help me to polish it until we get a "SeasidePharoDebugging" package with no override :) All what I mention here is tested in Pharo 4.0 with Seaside 3.1.4.1. These are the

[Pharo-dev] [pharo-project/pharo-core] 7a8e6d: 50485

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 7a8e6d1b8907aa8fa9d5b71564122941517413f6 https://github.com/pharo-project/pharo-core/commit/7a8e6d1b8907aa8fa9d5b71564122941517413f6 Author: Jenkins Build Server Date:

Re: [Pharo-dev] GTDebugger not draggable with latest VM

Case 17178 added an extra check to the handling of mouse movement to use the result from asking the event handler by default (if the morph has an event handler) in the same way as other “handles” methods behaves. The default behaviour for Morph event handling is that if an event handler is

Re: [Pharo-dev] Differences Compiler vs. OpalCompiler (or parser)

2015-12-04 20:29 GMT+01:00 Andrei Chis : > > > On Sat, Nov 21, 2015 at 3:25 PM, Nicolai Hess > wrote: > >> >> >> 2015-11-20 22:57 GMT+01:00 Eliot Miranda : >> >>> Hi Nicolai, >>> >>> On Fri, Nov 20, 2015 at 1:37 PM,

Re: [Pharo-dev] GTDebugger not draggable with latest VM

2015-12-04 17:42 GMT+01:00 Henrik Nergaard : > Case 17178 added an extra check to the handling of mouse movement to use > the result from asking the event handler by default (if the morph has an > event handler) in the same way as other “handles” methods behaves. The >

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

OK, I started publishing here: http://smalltalkhub.com/mc/marianopeck/MarianoPublic/main package called SeasidePharoDebugging I did not even have the time to try it..just committed. I must leave now. byw On Fri, Dec 4, 2015 at 2:43 PM, Mariano Martinez Peck wrote: >

Re: [Pharo-dev] SessionManager (aka new startup / shutdown list manager) needs testers

2015-12-04 13:39 GMT+01:00 Christophe Demarey : > Hi, > > Guillermo, Pablo and I started to work on a new implementation for the > image startup / shutdown list. > The old implementation misses domain objects, polluted the SmalltalkImage > class and introduced crazy

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

OK, I tested it and it works. I added only one test but I plan to add more. On Fri, Dec 4, 2015 at 4:59 PM, Mariano Martinez Peck wrote: > OK, I started publishing here: > http://smalltalkhub.com/mc/marianopeck/MarianoPublic/main package > called SeasidePharoDebugging

Re: [Pharo-dev] Unicode Support

> On 04 Dec 2015, at 17:00, Max Leske wrote: > > Hi Euan > > I think it’s great that you’re trying this. I hope you know what you’re > getting yourself into :) > > > I’m no Unicode expert but I want to add two points to your list (although > you’ve probably already

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

I added more tests to WACurrentRequestDebuggingTest. If you see, all tests work except #callbackAndHalt. At a later point we will likely need to do this for the rest of the WADynamicVariable subclasses (they are 3 in total). Cheers, On Fri, Dec 4, 2015 at 7:17 PM, Mariano Martinez Peck

Re: [Pharo-dev] Differences Compiler vs. OpalCompiler (or parser)

On Sat, Nov 21, 2015 at 3:25 PM, Nicolai Hess wrote: > > > 2015-11-20 22:57 GMT+01:00 Eliot Miranda : > >> Hi Nicolai, >> >> On Fri, Nov 20, 2015 at 1:37 PM, Nicolai Hess >> wrote: >> >>> GTDummyExamples class >>> d: