- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] How to debug code using DynamicVariable?

by Norbert Hartl

Am 24.06.2014 um 08:19 schrieb stepharo <stepharo(a)free.fr>: > >> The slice cannot be integrated automatically because there is a modal popping up >> >> Warning: Process should not be redefined. Proceed to store over it. >> >> Not sure what to do. Manual integration? > > We will check that :) > Marcus already integrated it. Thanks! norbert >> >> Norbert >> >> Am 23.06.2014 um 23:55 schrieb Norbert Hartl <norbert(a)hartl.name>: >> >>> https://pharo.fogbugz.com/default.asp?13378 >>> >>> Btw. I tested this as well in 3.0 and a backport would be highly appreciated. >>> >>> Norbert >>> >>> Am 23.06.2014 um 20:08 schrieb stepharo <stepharo(a)free.fr>: >>> >>>> Thanks Eliot. >>>> Sven, Norbert if you package that nicely (BTW having some tests would be great) we can include that in 4.0 >>>> >>>> Stef >>>> On 23/6/14 19:29, Eliot Miranda wrote: >>>>> and here are the changes I've just committed to Squeak trunk. >>>>> >>>>> >>>>> On Mon, Jun 23, 2014 at 10:05 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>>>> Hi Norbert, >>>>> >>>>> [ let me try again. never try and get code out too early in the morning ;-) ] >>>>> >>>>> it is the debugger that needs fixing, not your code !! :-). The debugger needs to respect process identity. Andreas and I (mostly Andreas) came up with the following changes at Qwaq. Your message is a good reminder that I need to add this to Squeak asap. >>>>> >>>>> The idea is for Process to have an additional inst var 'effectiveProcess' that holds the actual process running code. For the most part this is self, but in the debugger we substitute the process being debugged: >>>>> >>>>> Process methods for accessing >>>>> effectiveProcess >>>>> >>>>> "effectiveProcess is a mechanism to allow process-faithful debugging. The debugger executes code >>>>> >>>>> on behalf of processes, so unless some effort is made the identity of Processor activeProcess is not >>>>> >>>>> correctly maintained when debugging code. The debugger uses evaluate:onBehalfOf: to assign the >>>>> >>>>> debugged process as the effectiveProcess of the process executing the code, preserving process >>>>> >>>>> identity." >>>>> >>>>> ^effectiveProcess ifNil: [self] >>>>> >>>>> then the relevant methods in Process and processorScheduler defer to effectiveProcess, e.g. >>>>> >>>>> ProcessorScheduler methods for process state change >>>>> terminateActive >>>>> >>>>> "Terminate the process that is currently running." >>>>> >>>>> >>>>> activeProcess effectiveProcess terminate >>>>> >>>>> and the debugging methods use evaluate:onBehalfOf: to install the process being debugged: >>>>> >>>>> Process methods for private >>>>> evaluate: aBlock onBehalfOf: aProcess >>>>> >>>>> "Evaluate aBlock setting effectiveProcess to aProcess. Used >>>>> >>>>> in the execution simulation machinery to ensure that >>>>> >>>>> Processor activeProcess evaluates correctly when debugging." >>>>> >>>>> | oldEffectiveProcess | >>>>> >>>>> oldEffectiveProcess := effectiveProcess. >>>>> >>>>> effectiveProcess := aProcess. >>>>> >>>>> ^aBlock ensure: [effectiveProcess := oldEffectiveProcess] >>>>> >>>>> Process methods for changing suspended state >>>>> step >>>>> >>>>> >>>>> ^Processor activeProcess >>>>> >>>>> evaluate: [suspendedContext := suspendedContext step] >>>>> >>>>> onBehalfOf: self >>>>> >>>>> stepToCallee >>>>> >>>>> "Step until top context changes" >>>>> >>>>> >>>>> Processor activeProcess >>>>> >>>>> evaluate: >>>>> >>>>> [| ctxt | >>>>> >>>>> ctxt := suspendedContext. >>>>> >>>>> [ctxt == suspendedContext] whileTrue: [ >>>>> >>>>> suspendedContext := suspendedContext step]] >>>>> >>>>> onBehalfOf: self. >>>>> >>>>> ^suspendedContext >>>>> >>>>> etc. Changes from a Qwaq image attached. >>>>> >>>>> HTH >>>>> >>>>> >>>>> On Mon, Jun 23, 2014 at 4:50 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>>>> In my code I'm using a DynamicVariable to request a context object when needed. Until now I knew the name DynamicVariable only from seaside. There it is called WADynamicVariable and it is an exception. So I blindly assumed the pharo DynamicVariable works the same. >>>>> I thought this might be a good optimization not to travel the stack all the time but put in the process. >>>>> Now that I am using it I can see the difference. I find it real hard using it because I don't know how to debug/step in code. DynamicVariable is a process specific variable but as soon as a debugger opens it is very likely to be in another process. This makes stepping in method using the DynamicVariable impossible. The only way round is to set break points after the dynamic lookup and step from there. But this feels just wrong. >>>>> What would be the best way to have DynamicVariable and be able to debug anything? Or is there a variant that uses the stack instead of the "active" process? >>>>> >>>>> thanks, >>>>> >>>>> Norbert >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> best, >>>>> Eliot >>>>> >>>>> >>>>> >>>>> -- >>>>> best, >>>>> Eliot >>>> >>> >> >

June 24, 2014

Re: [Pharo-dev] How to debug code using DynamicVariable?

by stepharo

On 24/6/14 08:19, stepharo wrote: > >> The slice cannot be integrated automatically because there is a modal >> popping up >> >> >> Warning: Process should not be redefined. Proceed to store >> over it. >> >> >> Not sure what to do. Manual integration? > > We will check that :) > >> >> Norbert >> >> Am 23.06.2014 um 23:55 schrieb Norbert Hartl <norbert(a)hartl.name >> <mailto:norbert@hartl.name>>: >> >>> https://pharo.fogbugz.com/default.asp?13378 >>> >>> Btw. I tested this as well in 3.0 and a backport would be highly >>> appreciated. >>> >>> Norbert >>> >>> Am 23.06.2014 um 20:08 schrieb stepharo <stepharo(a)free.fr >>> <mailto:stepharo@free.fr>>: >>> >>>> Thanks Eliot. >>>> Sven, Norbert if you package that nicely (BTW having some tests >>>> would be great) we can include that in 4.0 >>>> >>>> Stef >>>> On 23/6/14 19:29, Eliot Miranda wrote: >>>>> and here are the changes I've just committed to Squeak trunk. >>>>> >>>>> >>>>> On Mon, Jun 23, 2014 at 10:05 AM, Eliot Miranda >>>>> <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >>>>> >>>>> Hi Norbert, >>>>> >>>>> [ let me try again. never try and get code out too early >>>>> in the morning ;-) ] >>>>> >>>>> it is the debugger that needs fixing, not your code !! >>>>> :-). The debugger needs to respect process identity. Andreas >>>>> and I (mostly Andreas) came up with the following changes at >>>>> Qwaq. Your message is a good reminder that I need to add this >>>>> to Squeak asap. >>>>> >>>>> The idea is for Process to have an additional inst var >>>>> 'effectiveProcess' that holds the actual process running code. >>>>> For the most part this is self, but in the debugger we >>>>> substitute the process being debugged: >>>>> >>>>> /Process methods for accessing/ >>>>> *effectiveProcess* >>>>> "effectiveProcess is a mechanism to allow process-faithful >>>>> debugging. The debugger executes code >>>>> on behalf of processes, so unless some effort is made the >>>>> identity of Processor activeProcess is not >>>>> correctly maintained when debugging code. The debugger uses >>>>> evaluate:onBehalfOf: to assign the >>>>> debugged process as the effectiveProcess of the process >>>>> executing the code, preserving process >>>>> identity." >>>>> ^effectiveProcess ifNil: [self] >>>>> >>>>> then the relevant methods in Process and processorScheduler >>>>> defer to effectiveProcess, e.g. >>>>> >>>>> /ProcessorScheduler methods for process state change/ >>>>> *terminateActive* >>>>> "Terminate the process that is currently running." >>>>> >>>>> activeProcess effectiveProcess terminate >>>>> >>>>> and the debugging methods use evaluate:onBehalfOf: to install >>>>> the process being debugged: >>>>> >>>>> /Process methods for private/ >>>>> *evaluate: aBlock onBehalfOf: aProcess* >>>>> "Evaluate aBlock setting effectiveProcess to aProcess. Used >>>>> in the execution simulation machinery to ensure that >>>>> Processor activeProcess evaluates correctly when debugging." >>>>> | oldEffectiveProcess | >>>>> oldEffectiveProcess := effectiveProcess. >>>>> effectiveProcess := aProcess. >>>>> ^aBlock ensure: [effectiveProcess := oldEffectiveProcess] >>>>> >>>>> /Process methods for changing suspended state/ >>>>> *step* >>>>> >>>>> ^Processor activeProcess >>>>> evaluate: [suspendedContext := suspendedContext step] >>>>> onBehalfOf: self >>>>> >>>>> *stepToCallee* >>>>> "Step until top context changes" >>>>> >>>>> Processor activeProcess >>>>> evaluate: >>>>> [| ctxt | >>>>> ctxt := suspendedContext. >>>>> [ctxt == suspendedContext] whileTrue: [ >>>>> suspendedContext := suspendedContext step]] >>>>> onBehalfOf: self. >>>>> ^suspendedContext >>>>> >>>>> etc. Changes from a Qwaq image attached. >>>>> >>>>> HTH >>>>> >>>>> >>>>> On Mon, Jun 23, 2014 at 4:50 AM, Norbert Hartl >>>>> <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >>>>> >>>>> In my code I'm using a DynamicVariable to request a >>>>> context object when needed. Until now I knew the name >>>>> DynamicVariable only from seaside. There it is called >>>>> WADynamicVariable and it is an exception. So I blindly >>>>> assumed the pharo DynamicVariable works the same. >>>>> I thought this might be a good optimization not to travel >>>>> the stack all the time but put in the process. >>>>> Now that I am using it I can see the difference. I find it >>>>> real hard using it because I don't know how to debug/step >>>>> in code. DynamicVariable is a process specific variable >>>>> but as soon as a debugger opens it is very likely to be in >>>>> another process. This makes stepping in method using the >>>>> DynamicVariable impossible. The only way round is to set >>>>> break points after the dynamic lookup and step from there. >>>>> But this feels just wrong. >>>>> What would be the best way to have DynamicVariable and be >>>>> able to debug anything? Or is there a variant that uses >>>>> the stack instead of the "active" process? >>>>> >>>>> thanks, >>>>> >>>>> Norbert >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> best, >>>>> Eliot >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> best, >>>>> Eliot >>>> >>> >> >

June 24, 2014

Re: [Pharo-dev] Stepping through with GLORP Proxies

by stepharo

On 24/6/14 08:18, stepharo wrote: > Esteban > > I would like to know how different are the Glorp proxies from the ones > of Mariano. > Because we are thinking about to get by default a nice proxy system. > Proxies in the sense of object representing one that is not in the > system (and not proxies > as metaobject or representing an object that is around as in the JS > literature). Ideally I would like > to unify both. > > Stef > > On 23/6/14 20:45, Esteban A. Maringolo wrote: >> Eliot, >> >> I never installed your proposed changes in a Pharo 3 image because >> there is a significant change in ContextPart. Your proposed changeset >> changes classVars of ContextPart. >> >> Your proposal: >> classVariableNames: 'MaxLengthForASingleDebugLogReport >> MaxStackDepthForASingleDebugLogReport PrimitiveFailToken QuickStep >> ValueIndex' >> >> Current vars: >> classVariableNames: 'PrimitiveFailToken QuickStep >> SpecialPrimitiveSimulators TryNamedPrimitiveTemplateMethod' >> >> Would you mind adapting your mirror methods changes to work also in >> Pharo 3 (and maybe in Pharo 4 too?). >> >> Esteban A. Maringolo >> >> >> 2014-02-26 14:40 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >>> Hi Esteban, >>> >>> find attached. Let me know of any problems. >>> >>> >>> On Wed, Feb 26, 2014 at 8:32 AM, Esteban A. Maringolo >>> <emaringolo(a)gmail.com> >>> wrote: >>>> Hi Eliot, >>>> >>>> >>>> 2013-11-30 18:30 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >>>>> On Fri, Nov 29, 2013 at 2:22 PM, Esteban A. Maringolo >>>>> <emaringolo(a)gmail.com> >>>>> wrote: >>>>>> 2013/11/29 Eliot Miranda <eliot.miranda(a)gmail.com>: >>>>>>> I'll either prepare a change set or submit. It'll get done. >>>>>> I can continue stepping into until the change is ready. >>>>>> Please make it compatible with Pharo 2 (whatever that means in >>>>>> term of >>>>>> code) :) >>>>> >>>>> OK, the code is now in Squeak trunk. What image should I use to >>>>> integrate >>>>> into Pharo 2? A url please... >>>> I'm coming back late to this. Because the change wasn't integrated in >>>> Pharo 2. >>>> >>>> Do you have the changeset applied to Squeak Trunk? I'd like to reapply >>>> it in my Pharo 2 image (at my own risk). >>>> Can you send it to may email address? >>>> >>>> Thank you! >>>> >>>> Esteban A. Maringolo >>>> >>> >>> >>> -- >>> best, >>> Eliot >> >

June 24, 2014

Re: [Pharo-dev] is it save to always recompute a TextMorphs extent if the font changed

by stepharo

On 24/6/14 08:14, stepharo wrote: > Hi nicolai > > this is a couple of weeks were I'm thinking about the way widgets use > fonts. > It is orthogonal to your mail but related. Most of the system is > refering to fonts via a global variable. > And to me this is wrong. > I would like to experiment with a solution similar to Settings: > - 1 Font should be hold by an instance variables of the widgets. > The code of the widgets should only refer to this state > > - 2 Now there is the question of the propagation when we change > and there I would do the same as settings: > pragma + builder > > What do the community think? > > Stef > > > > > On 23/6/14 22:00, Nicolai Hess wrote: >> About issue 13376 Wrong TextMorph extent for ButtonMorphs >> <https://pharo.fogbugz.com/default.asp?13376> : >> >> If you use different fonts as default font and button font, buttons >> labels may get truncated. >> >> One solution would be to always recompute the TextMorphs extent when its >> font changes, but I don't know if this is always desirable. >> >> Otherwise, if we recompute the extent on the creation time of the button, >> I am not sure if all buttonlabels have styled text. >

June 24, 2014

[pharo-project/pharo-core]

by GitHub

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

June 24, 2014

[pharo-project/pharo-core] 04f830: 40038

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 04f830fd8e01b0bd1a187d5986d96cc87aae2358 https://github.com/pharo-project/pharo-core/commit/04f830fd8e01b0bd1a187d59… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-24 (Tue, 24 Jun 2014) Changed paths: M Kernel.package/Process.class/definition.st A Kernel.package/Process.class/instance/accessing/effectiveProcess.st M Kernel.package/Process.class/instance/changing suspended state/activateReturn_value_.st M Kernel.package/Process.class/instance/changing suspended state/complete_.st M Kernel.package/Process.class/instance/changing suspended state/popTo_.st M Kernel.package/Process.class/instance/changing suspended state/popTo_value_.st M Kernel.package/Process.class/instance/changing suspended state/return_value_.st M Kernel.package/Process.class/instance/changing suspended state/step.st M Kernel.package/Process.class/instance/changing suspended state/stepToCallee.st M Kernel.package/Process.class/instance/changing suspended state/stepToSendOrReturn.st M Kernel.package/Process.class/instance/changing suspended state/step_.st A Kernel.package/Process.class/instance/private/evaluate_onBehalfOf_.st M Kernel.package/ProcessorScheduler.class/instance/accessing/activePriority.st M Kernel.package/ProcessorScheduler.class/instance/accessing/activeProcess.st M Kernel.package/ProcessorScheduler.class/instance/process state change/terminateActive.st A KernelTests.package/ProcessSpecificTest.class/instance/testing/testDynamicVariableAccessFromDifferentProcess.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script38.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40038.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40038 13378 DynamicVariable cannot be stepped in debugger https://pharo.fogbugz.com/f/cases/13378 http://files.pharo.org/image/40/40038.zip

June 24, 2014

Re: [Pharo-dev] Handling keyboard eventsâ¦

by phil＠highoctane.be

On Tue, Jun 24, 2014 at 10:07 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi everyone, > > sorry, if Iâm annoying with this question, but is there a way to handle > keyboard events (on mac) in a normal way? Because keyUp and keyDown do not > have any information about the key itself. I know that itâs a long story > also related with vm but maybe someone made some hacks to solve this > problem? > > Cheers > Uko > The logic is in sqSqueakOSXApplication+events.m Now, I do not have the latest version but it is true that keyUp and keyDown are not handled very nicely there. KeyDown doesn't seem to have any code (but one could set something there as the code is available). KeyUp has something. I do not know why things are done this way. There may be side effects in the VM if one changes the way things are... Good luck. (void) recordCharEvent:(NSString *) unicodeString fromView: (NSView<sqSqueakOSXView> *) mainView { sqKeyboardEvent evt; unichar unicode; unsigned char macRomanCharacter; NSInteger i; NSRange picker; NSUInteger totaLength; evt.type = EventTypeKeyboard; evt.timeStamp = (int) ioMSecs(); picker.location = 0; picker.length = 1; totaLength = [unicodeString length]; for (i=0;i < totaLength;i++) { unicode = [unicodeString characterAtIndex: i]; if ([mainView lastSeenKeyBoardStrokeDetails]) { evt.modifiers = [self translateCocoaModifiersToSqueakModifiers: [[mainView lastSeenKeyBoardStrokeDetails] modifierFlags]]; evt.charCode = [[mainView lastSeenKeyBoardStrokeDetails] keyCode]; } else { evt.modifiers = 0; evt.charCode = 0; } if ((evt.modifiers & CommandKeyBit) && (evt.modifiers & ShiftKeyBit)) { /* command and shift */ if ((unicode >= 97) && (unicode <= 122)) { /* convert ascii code of command-shift-letter to upper case */ unicode = unicode - 32; } } NSString *lookupString = [[NSString alloc] initWithCharacters: &unicode length: 1]; [lookupString getBytes: &macRomanCharacter maxLength: 1 usedLength: NULL encoding: NSMacOSRomanStringEncoding options: 0 range: picker remainingRange: NULL]; [lookupString release]; evt.pressCode = EventKeyDown; unsigned short keyCodeRemembered = evt.charCode; evt.utf32Code = 0; evt.reserved1 = 0; evt.windowIndex = (int)[[mainView windowLogic] windowIndex]; [self pushEventToQueue: (sqInputEvent *)&evt]; evt.charCode = macRomanCharacter; evt.pressCode = EventKeyChar; evt.modifiers = evt.modifiers; evt.utf32Code = unicode; [self pushEventToQueue: (sqInputEvent *) &evt]; if (i > 1 || ![mainView lastSeenKeyBoardStrokeDetails]) { evt.pressCode = EventKeyUp; evt.charCode = keyCodeRemembered; evt.utf32Code = 0; [self pushEventToQueue: (sqInputEvent *) &evt]; } } interpreterProxy->signalSemaphoreWithIndex(gDelegateApp.squeakApplication.inputSemaphoreIndex); } --Phil

June 24, 2014

Handling keyboard eventsâ¦

by Yuriy Tymchuk

Hi everyone, sorry, if Iâm annoying with this question, but is there a way to handle keyboard events (on mac) in a normal way? Because keyUp and keyDown do not have any information about the key itself. I know that itâs a long story also related with vm but maybe someone made some hacks to solve this problem? Cheers Uko

June 24, 2014

[pharo-project/pharo-core]

by GitHub

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

June 24, 2014

[pharo-project/pharo-core] d8bb46: 30850

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: d8bb46043b0475cf1c01c3af5578c681f16aa668 https://github.com/pharo-project/pharo-core/commit/d8bb46043b0475cf1c01c3af… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-24 (Tue, 24 Jun 2014) Changed paths: M ProfStef-Core.package/PharoSyntaxTutorial.class/instance/interactive/prepareDebuggerExample.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script112.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30850.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30850 13349 PackPort to 3: 11987 Launching ProfStef should not require initials https://pharo.fogbugz.com/f/cases/13349 http://files.pharo.org/image/30/30850.zip

June 24, 2014