Squeak-dev February 2018

squeak-dev@lists.squeakfoundation.org

51 participants
149 discussions

Time to Vote!
by Ron Teitelbaum 04 Feb '18

04 Feb '18

Hi All, Not sure if I've mentioned this but IT"S TIME TO VOTE! You may be asking why is Ron pushing so hard for people to vote? We are on track to have our lowest vote count ever. The number of voters is going down year to year but the drop this year is significant. I'm sure we can do better! Please let me know if you have trouble finding your ballot. I can resend it to you. Thanks! All the best, Ron Teitelbaum

11 17

Monticello Package Dependencies [Was: Re: ClockAndCalendarMorphs project on SqueakSource]
by Eliot Miranda 04 Feb '18

04 Feb '18

On Thu, Feb 1, 2018 at 10:35 AM, tim Rowledge <tim(a)rowledge.org> wrote: > > > > On 01-02-2018, at 9:58 AM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > > > > > > > On Thu, Feb 1, 2018 at 7:48 AM, Jakob Reschke <forums.jakob(a)resfarm.de> > wrote: > > I have been told that nobody uses the Monticello feature of > > dependencies among packages... > > > > At least for me that's because I didn't know they supported this :-(. I > think I shall try using it :-) > > I do (or at least, did, might have stopped at some point, get off my lawn) > use it for the WeatherStation package and NuScratchGPIO. The ui is a bit … > sparse. Functionally it seems to work quite nicely; it loads the required > packages before the main package. What else would it do? A bit more UI to > manage required packages would be nice; currently you can add one, or > remove them all. A bit sledge-hammer for my tastes. > We at least need to reveal it through the Monticello browser. I see no Dependences button or edit dependencies menu item anywhere. So for me the feature was completely invisible. I've been maintaining unnecessary load scripts for the VMMaker package when I could simply rely on dependencies. This isn't good guys :-( > tim > -- > tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim > Never trust a computer you can't lift. > _,,,^..^,,,_ best, Eliot

4 4

ClockAndCalendarMorphs project on SqueakSource
by Louis LaBrunda 04 Feb '18

04 Feb '18

Hi, I have created and uploaded my ClockAndCalendarMorphs project on SqueakSource. It depends upon another of my projects, KscAstroDataApp. KscAstroDataApp is used to calculate sunrise and sunset times displayed on the clock and calendar. Latitude and longitude are required for the sunrise and sunset calculations. If you don't supply them, no attempt will be made to do the calculations. In that case the KscAstroDataApp package should not be needed. Anyway it is probably best to download it too. I'm new to SqueakSource and I'm not sure I defined the dependency correctly. If not, I will fix it. Please let me know if you have any problems. The code below will get you started testing/playing with the clock morph. The latitude & longitude are for my location. The #initialize method of ClockImageMorph has a lot of comments about the options of the clock. Have fun. Lou | c | " c := ClockImageMorph clockFace: 'path2picture.jpg'." c := ClockImageMorph new. " c setTestMode." c desiredExtent: 1200@800. c setIncludeCalendar. c latitude: 40.66296 longitude: -74.535398. " c beTwentyFourHourClock." c setUseArabicNumerals. " c setUseRomanNumerals." c setAddCirclesAndTicks. " c setUseFancyHourHand. c setUseFancyMinuteHand. c setUseFancySecondHand." " c beFullScreen." c setShowDateTimeInfo. c numberColor: Color blue; circleColor: Color blue; tickColor: Color blue. c hourHandColor: Color blue; minuteHandColor: Color blue; secondHandColor: Color blue. c calendarTextColor: Color blue. c open. -- Louis LaBrunda Keystone Software Corp. SkypeMe callto://PhotonDemon

11 30

Re: [squeak-dev] [Newbies] Time to Vote!
by Ron Teitelbaum 03 Feb '18

03 Feb '18

Hi Offray, I'd be happy to add you to the voting list. Let me know and I'll add you for next year. I agree with you. Many years ago I used to be much more active (if you can believe that). My idea at the time was that we would actually have a period of time for campaigning. For a while, I started doing community interviews for news.squeak.org. I had tried also presenting questions, but I got some feedback that my questions were too focused on what I wanted and didn't represent the community at large. At that point, I tried to encourage the community to ask questions instead but that didn't work either because nobody asked questions. I'm was actually happy that everyone that is running this year gave some indication of what they are interested in doing and why they were running. See http://wiki.squeak.org/squeak/6590 - Posts related to the Election (chronological). I can tell you that for the group of people we have running there are no bad votes! Everyone is terrific! I could highlight some differences but that won't really help because the community members were correct, I AM BIASED. :) What I would recommend is getting on the voters' list. Talk to your friends and get to know the people that are active in the community. You might have to subscribe to Squeak-Dev or VM-Dev to get to know people better. Most of the candidates don't often post to the beginners' list. The beginners' list has always had a soft spot in my heart. I was here from the very beginning. That is why I include it in my election emails. Wow, just looking the beginners' list started in May 2006[1], it's been 12 years! Once you have a good idea of what the community needs, you could ask questions! Talk to the candidates. Your questions will probably be helpful for others that didn't take the time to ask but might want to know the answer too. Do let us know If you have other suggestions on ways we can improve or write me directly. I will do whatever I can to help! All the best, Ron Teitelbaum [1] http://lists.squeakfoundation.org/pipermail/beginners/2006-May/thread.html On Fri, Feb 2, 2018 at 6:32 PM, Offray Vladimir Luna Cárdenas < offray(a)riseup.net> wrote: > Hi, > > I have seen the voting call, but I don't know who I could vote for. I > think that we have excellent candidates list, but having low voting rates > is, for me a symptom of low communication rates, not about the voting > candidates, but about what is happening in general in the community. > > So, how can approach the more structural program about improving community > participation and communication so, we can have a more informed voting > campaign and proactivity from voters and the community in general. > > Cheers, > > Offray > > On 02/02/18 08:06, Ron Teitelbaum wrote: > > Hi All, > > Not sure if I've mentioned this but IT"S TIME TO VOTE! > > You may be asking why is Ron pushing so hard for people to vote? > > We are on track to have our lowest vote count ever. The number of voters > is going down year to year but the drop this year is significant. I'm sure > we can do better! > > Please let me know if you have trouble finding your ballot. I can resend > it to you. > > Thanks! > > All the best, > > Ron Teitelbaum > > > _______________________________________________ > Beginners mailing listBeginners@lists.squeakfoundation.orghttp://lists.squeakfoundation.org/mailman/listinfo/beginners > > > > _______________________________________________ > Beginners mailing list > Beginners(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/beginners > >

1 0

MQTT for Squeak?
by tim Rowledge 02 Feb '18

02 Feb '18

I’m having all sorts of fun making some weather station and environmental sensors with assorted Pi and ESP8266 boards and I need a nice way to make the sensor nodes report back to base. Since the ESP8266 modules don’t run squeak (shame!) I’m using Arduino-c++ (blech) on them, and since the weather sensor code already existed in python (double-blech) I’m using that on the weather-pi board. I’ve been recommended to look at MQTT as a way to bind them all together and from what little sense I can make of the assorted stuff that googling had lead me to (good grief, so much acronym laden gibberish) it looks like it might do the job. Googling for a squeak mqtt package has revealed nothing thus far so I’m now appealing to the list for any news. tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Useful Latin Phrases:- O! Plus! Perge! Aio! Hui! Hem! = Oh! More! Go on! Yes! Ooh! Ummm!

8 28

The Inbox: Kernel-tonyg.1148.mcz
by commits＠source.squeak.org 02 Feb '18

02 Feb '18

A new version of Kernel was added to project The Inbox: http://source.squeak.org/inbox/Kernel-tonyg.1148.mcz ==================== Summary ==================== Name: Kernel-tonyg.1148 Author: tonyg Time: 31 January 2018, 11:37:21.27021 pm UUID: 2a675301-406b-4222-9599-84358a7cc506 Ancestors: Kernel-eem.1147 Brings the Promise implementation closer to Javascript/A+ promises in two ways: * Resolving a Promise with another Promise causes them to be chained together * Resolving or Rejecting a Promise that is not pending is a no-op, like the Firefox/Chrome/etc in-browser promise implementations. The tests have been changed in KernelTests-tonyg.331 accordingly. =============== Diff against Kernel-eem.1147 =============== Item was changed: Object subclass: #Promise + instanceVariableNames: 'value resolvers mutex state error rejecters' - instanceVariableNames: 'onError value resolvers mutex state error rejectors rejecters' classVariableNames: '' poolDictionaries: '' category: 'Kernel-Processes'! + !Promise commentStamp: 'tonyg 1/31/2018 23:34' prior: 0! - !Promise commentStamp: 'fbs 5/17/2013 18:23' prior: 0! I represent the result of an asynchronous message. Once the message is processed, I will be resolved to a value. I am typically instantiated by invocations of #futureSend:at:args: (and not by #futureDo:atArgs:). See class-comment of FutureNode. I also implement the Promises/A+ Javascript specification. This allows you to chain my instances to perform arbitrarily complex asynchronous tasks with error handling baked in. + A Promise may be in one of three possible states: #pending, #fulfilled or #rejected. A Promise may move from #pending -> #fulfilled (by way of the resolveWith: message), or from #pending -> #rejected (by way of rejectWith:). No other state changes may occur. + + Once #fulfilled or #rejected, a Promise's value must not change. In keeping with the major Javascript Promise implementations' interpretations of this, calls to resolveWith: or rejectWith: when a Promise is in #fulfilled or #rejected state are simply ignored - an error is not signalled. (See test cases PromiseTest testFirstResolutionWins, testCannotRejectFulfilledPromise and testCannotResolveaRejectedPromise.)! - A Promise may be in one of three possible states: #pending, #fulfilled or #rejected. A Promise may move from #pending -> #fulfilled, or from #pending -> #rejected. No other state changes may occur. Once #fulfilled or #rejected, a Promise's value must change.! Item was changed: ----- Method: Promise>>rejectWith: (in category 'resolving') ----- rejectWith: anObject "Reject this promise." mutex critical: [ + (state == #pending) ifTrue: [ + error := anObject. + state := #rejected. + rejecters do: [:r | self evaluateRejecter: r]]]! - (state == #fulfilled) ifTrue: [self error: 'Promise was already resolved']. - (state == #rejected) ifTrue: [self error: 'Promise was already rejected']. - error := anObject. - state := #rejected. - rejecters do: [:r | self evaluateRejecter: r]].! Item was changed: ----- Method: Promise>>resolveWith: (in category 'resolving') ----- resolveWith: arg + "Resolve this promise. If arg is itself a Promise, make this promise depend upon it, + as detailed in the Promises/A+ spec: + https://promisesaplus.com/#the-promise-resolution-procedure" + + (arg isKindOf: Promise) + ifTrue: [ + arg whenResolved: [:v | self resolveWith: v]. + arg whenRejected: [:e | self rejectWith: e]] + ifFalse: [ + mutex critical: [ + (state == #pending) ifTrue: [ + value := arg. + state := #fulfilled. + resolvers do: [:r | self evaluateResolver: r]]]]! - "Resolve this promise" - mutex critical: [ - (state == #fulfilled) ifTrue: [self error: 'Promise was already resolved']. - (state == #rejected) ifTrue: [self error: 'Promise was already resolved']. - value := arg. - state := #fulfilled. - resolvers do: [:r | - self evaluateResolver: r]].! Item was changed: ----- Method: Promise>>then: (in category 'monad') ----- then: resolvedBlock + ^ self then: resolvedBlock ifRejected: [:e | "Pass rejection reason along" e].! - ^ self then: resolvedBlock ifRejected: [:ignored | "Do nothing"].!

6 5

The Inbox: System-bf.997.mcz
by commits＠source.squeak.org 02 Feb '18

02 Feb '18

Bert Freudenberg uploaded a new version of System to project The Inbox: http://source.squeak.org/inbox/System-bf.997.mcz ==================== Summary ==================== Name: System-bf.997 Author: bf Time: 25 January 2018, 4:56:35.380251 pm UUID: 604954ca-0389-43c0-a5c7-4ddc8e613cc9 Ancestors: System-dtl.996 Simplify project dispatch selector detection. No hard-coded list. Almost as good. =============== Diff against System-dtl.996 =============== Item was removed: - ----- Method: Project class>>baseSelectors (in category 'dispatching') ----- - baseSelectors - "The list of known base selectors that may be dispatched to project specific - implementations. For example, #OpenLabel:in: will be dispatched to #mvcOpenLabel:in: - for its MVC specific implementation. Add new base selectors here if additional methods - are added as targets of the dispatchTo:addPrefixAndSend:withArguments: mechanism." - - ^ { - #StartUpLeftFlush . - #StartUpWithCaption:icon:at:allowKeyboard: . - #OpenLabel:in: . - #Open: . - #Open . - #OpenOn:context:label:contents:fullView: . - #ResumeProcess: . - #OpenContext:label:contents: - } - ! Item was removed: - ----- Method: Project class>>dispatchSelectors (in category 'dispatching') ----- - dispatchSelectors - "All known targets of the dispatch mechanism" - - "Project dispatchSelectors" - - | selectors dispatchPrefixes | - selectors := OrderedCollection new. - dispatchPrefixes := Set withAll: (Project allSubclasses collect: [ :e | e basicNew selectorPrefixForDispatch ]). - self baseSelectors do: [ :base | - dispatchPrefixes do: [ :prefix | - selectors add: (prefix, base) asSymbol ] ]. - ^ selectors - - ! Item was changed: ----- Method: Project class>>isDispatchSelector: (in category 'dispatching') ----- isDispatchSelector: aSelector "In support of package modularity, some method selectors are generated based on project type and dispatched to the appropriate implementation for that project. For methods with these selectors, let dispatchTo:addPrefixAndSend:withArguments: be found as a sender." + | dispatchPrefixes prefix otherSelector | + dispatchPrefixes := Project allSubclasses collect: + [:cls | cls basicNew selectorPrefixForDispatch]. + "If it doesn't start with a recognized prefix, it's not dispatchable" + prefix := dispatchPrefixes detect: [:each | aSelector beginsWith: each] + ifNone: [^false]. + "If a similar symbol exists for all other prefixes, it's likely dispatchable" + ^(dispatchPrefixes copyWithout: prefix) + allSatisfy: [:otherPrefix | + otherSelector := otherPrefix, (aSelector allButFirst: prefix size). + Symbol hasInterned: otherSelector ifTrue: [:s]] - - ^ self dispatchSelectors includes: aSelector. !

4 8

The Trunk: System-tpr.999.mcz
by commits＠source.squeak.org 02 Feb '18

02 Feb '18

tim Rowledge uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-tpr.999.mcz ==================== Summary ==================== Name: System-tpr.999 Author: tpr Time: 1 February 2018, 4:13:05.258994 pm UUID: 70bdd4f7-96fe-4233-bff2-48012f607163 Ancestors: System-dtl.998 Finally, remove the Project>>dispatchTo:addPrefixAndSend:withArguments: method. See prior commits ToolBuilder-Kernel-tpr.121 ToolBuilder-MVC-tpr.53 ToolBuilder-Morphic-tpr.207 ST80-tpr.234 Tools-tpr.795 Network-tpr.217 MorphicExtras-tpr.217 Morphic-tpr.1392 CommandLine-tpr.10 =============== Diff against System-dtl.998 =============== Item was changed: ----- Method: Preferences class>>restoreDefaultFonts (in category 'prefs - fonts') ----- restoreDefaultFonts "Since this is called from menus, we can take the opportunity to prompt for missing font styles." " Preferences restoreDefaultFonts " UserInterfaceTheme allThemes detect: [:ea | UserInterfaceTheme current name ~= ea name and: [UserInterfaceTheme current name includesSubstring: ea name]] ifFound: [:ea | + (Project uiManager - (Project current uiManager confirm: ('Do you want to apply\"{1}"?' translated withCRs format: {ea name}) title: 'Apply UI Theme' translated) ifTrue: [ea apply]] ifNone: [self inform: 'Sorry, could not revert font choices.\Please apply a UI theme with smaller fonts.' translated withCRs].! Item was removed: - ----- Method: Project class>>isDispatchSelector: (in category 'dispatching') ----- - isDispatchSelector: aSelector - "In support of package modularity, some method selectors are generated based - on project type and dispatched to the appropriate implementation for that project. - For methods with these selectors, let dispatchTo:addPrefixAndSend:withArguments: - be found as a sender." - | dispatchPrefixes prefix otherSelector | - dispatchPrefixes := Project allSubclasses collect: - [:cls | cls basicNew selectorPrefixForDispatch]. - "If it doesn't start with a recognized prefix, it's not dispatchable" - prefix := dispatchPrefixes detect: [:each | aSelector beginsWith: each] - ifNone: [^false]. - "If a similar symbol exists for all other prefixes, it's likely dispatchable" - ^(dispatchPrefixes copyWithout: prefix) - allSatisfy: [:otherPrefix | - otherSelector := otherPrefix, (aSelector allButFirst: prefix size). - Symbol hasInterned: otherSelector ifTrue: [:s]] - ! Item was removed: - ----- Method: Project>>dispatchTo:addPrefixAndSend:withArguments: (in category 'dispatching') ----- - dispatchTo: requestor addPrefixAndSend: baseSelector withArguments: arguments - "Sender wants to perform a method with dependencies on the type of project. - Dispatch to an appropriate method for the current project. - - This method is a workaround for lack of proper ToolBuilder support in the sender, - and should be eliminated when possible (dtl Feb 2010)" - - <hasLiteralTest: #isDispatchSelector:> - | selector | - selector := (self selectorPrefixForDispatch, baseSelector) asSymbol. - ^ requestor perform: selector withArguments: arguments! Item was changed: ----- Method: Project>>okToChange (in category 'release') ----- okToChange "Answer whether the window in which the project is housed can be dismissed -- which is destructive. We never clobber a project without confirmation" | answer | (self confirm: ('Do you really want to delete the project\{1}\and all its content?' withCRs translated format:{self name})) ifFalse: [^ false]. self subProjects ifNotEmpty: [:sp | + answer := Project uiManager - answer := Project current uiManager chooseFrom: #( "1" 'Lift all sub-projects' "2" 'Discard all sub-projects (NO UNDO!!)' "3 or 0" 'Cancel') lines: #(2) title: ('The project {1}\contains {2} sub-project(s).' withCRs translated format:{self name. sp size}). (answer = 0 or: [answer = 3]) ifTrue: [^ false]. answer = 1 ifTrue: [self liftSubProjects. ^ true]. answer = 2 ifTrue: [^ sp allSatisfy: [:ea | ea okToChange]]]. ^ true!

1 0

The Trunk: CommandLine-tpr.10.mcz
by commits＠source.squeak.org 02 Feb '18

02 Feb '18

tim Rowledge uploaded a new version of CommandLine to project The Trunk: http://source.squeak.org/trunk/CommandLine-tpr.10.mcz ==================== Summary ==================== Name: CommandLine-tpr.10 Author: tpr Time: 1 February 2018, 4:06:45.057704 pm UUID: 303563e6-0663-4b85-a5a6-52ef7b134e68 Ancestors: CommandLine-tpr.9 Preliminary support for changes involved in removing the Project>>dispatchTo:addPrefixAndSend:withArguments: method. =============== Diff against CommandLine-tpr.9 =============== Item was added: + ----- Method: DummyUIManager>>openDebugger:on:context:label:contents:fullView: (in category 'ui requests') ----- + openDebugger: aDebugger on: process context: context label: title contents: contentsStringOrNil fullView: bool + "open a debugger - the two versions for mvc & morphic are very close and can surely be merged so that this can be removed" + ^nil! Item was added: + ----- Method: DummyUIManager>>openFancyMailComposition: (in category 'ui requests') ----- + openFancyMailComposition: fancyMail + "FancyMailComposition should probably be removed in favour of MailComposition, but at least ought to be made a ToolBuilder thing" + ^nil! Item was added: + ----- Method: DummyUIManager>>openPluggableFileList:label:in: (in category 'ui requests') ----- + openPluggableFileList: aPluggableFileList label: aString in: aWorld + "PluggableFileList is being deprecated and this can go away soon" + ^nil! Item was added: + ----- Method: DummyUIManager>>openPluggableFileListLabel:in: (in category 'ui requests') ----- + openPluggableFileListLabel: aString in: aWorld + "PluggableFileList is being deprecated and this can go away soon" + ^nil! Item was added: + ----- Method: DummyUIManager>>resumeDebugger:process: (in category 'ui requests') ----- + resumeDebugger: aDebugger process: aTopView + "resume a debugger - the two versions for mvc & morphic are very close and can surely be merged so that this can be removed" + ^nil! Item was added: + ----- Method: DummyUIManager>>startUpMenu:withCaption:icon:at:allowKeyboard: (in category 'ui requests') ----- + startUpMenu: aMenu withCaption: captionOrNil icon: aForm at: location allowKeyboard: aBoolean + "A menu needs to startup and depends on the current type of ui manager for what sort of startup to do. Very ugly, and really needs replacing with a much better menu system" + + ^nil + !

1 0

The Trunk: Morphic-tpr.1392.mcz
by commits＠source.squeak.org 02 Feb '18

02 Feb '18

tim Rowledge uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-tpr.1392.mcz ==================== Summary ==================== Name: Morphic-tpr.1392 Author: tpr Time: 1 February 2018, 3:57:56.837746 pm UUID: aba8b7c8-c8f4-4293-bcda-18c504122d6b Ancestors: Morphic-mt.1391 Preliminary support for changes involved in removing the Project>>dispatchTo:addPrefixAndSend:withArguments: method. =============== Diff against Morphic-mt.1391 =============== Item was removed: - ----- Method: Debugger class>>morphicContext: (in category '*Morphic-instance creation') ----- - morphicContext: aContext - "Answer an instance of me for debugging the active process starting with the given context." - - ^ self new - process: Processor activeProcess - controller: nil - context: aContext! Item was removed: - ----- Method: Debugger class>>morphicOpenContext:label:contents: (in category '*Morphic-opening') ----- - morphicOpenContext: aContext label: aString contents: contentsStringOrNil - "Open a notifier in response to an error, halt, or notify. A notifier view just shows a short view of the sender stack and provides a menu that lets the user open a full debugger." - "Simulation guard" - <primitive: 19> - ErrorRecursionGuard critical: - [ ErrorRecursion not & Preferences logDebuggerStackToFile ifTrue: - [ Smalltalk - logSqueakError: aString - inContext: aContext ]. - ErrorRecursion ifTrue: - [ ErrorRecursion := false. - self primitiveError: aString ]. - ErrorRecursion := true. - self - informExistingDebugger: aContext - label: aString. - (Debugger morphicContext: aContext) - openNotifierContents: contentsStringOrNil - label: aString. - ErrorRecursion := false]. - Processor activeProcess suspend ! Item was removed: - ----- Method: Debugger class>>morphicOpenInterrupt:onProcess: (in category '*Morphic-opening') ----- - morphicOpenInterrupt: aString onProcess: interruptedProcess - "Open a notifier in response to an interrupt. An interrupt occurs when the user types the interrupt key (cmd-. on Macs, ctrl-c or alt-. on other systems) or when the low-space watcher detects that memory is low." - | debugger | - <primitive: 19> "Simulation guard" - debugger := self new. - debugger - process: interruptedProcess - controller: nil - context: interruptedProcess suspendedContext. - debugger externalInterrupt: true. - - Preferences logDebuggerStackToFile ifTrue: - [(aString includesSubstring: 'Space') & (aString includesSubstring: 'low') - ifTrue: [Smalltalk logError: aString inContext: debugger interruptedContext to: 'LowSpaceDebug.log'] - "logging disabled for 4.3 release, see - http://lists.squeak.org/pipermail/squeak-dev/2011-December/162503.html" - "ifFalse: [Smalltalk logSqueakError: aString inContext: debugger interruptedContext]"]. - - Preferences eToyFriendly ifTrue: [Project current world stopRunningAll]. - ^debugger - openNotifierContents: nil label: aString; - yourself - ! Item was added: + ----- Method: Debugger class>>openContext:label:contents: (in category '*Morphic-opening') ----- + openContext: aContext label: aString contents: contentsStringOrNil + "Open a notifier in response to an error, halt, or notify. A notifier view just shows a short view of the sender stack and provides a menu that lets the user open a full debugger." + "Simulation guard" + <primitive: 19> + ErrorRecursionGuard critical: + [ ErrorRecursion not & Preferences logDebuggerStackToFile ifTrue: + [ Smalltalk + logSqueakError: aString + inContext: aContext ]. + ErrorRecursion ifTrue: + [ ErrorRecursion := false. + self primitiveError: aString ]. + ErrorRecursion := true. + self + informExistingDebugger: aContext + label: aString. + (Debugger context: aContext) + openNotifierContents: contentsStringOrNil + label: aString. + ErrorRecursion := false]. + Processor activeProcess suspend ! Item was added: + ----- Method: Debugger class>>openInterrupt:onProcess: (in category '*Morphic-opening') ----- + openInterrupt: aString onProcess: interruptedProcess + "Open a notifier in response to an interrupt. An interrupt occurs when the user types the interrupt key (cmd-. on Macs, ctrl-c or alt-. on other systems) or when the low-space watcher detects that memory is low." + | debugger | + <primitive: 19> "Simulation guard" + debugger := self new. + debugger + process: interruptedProcess + controller: (ScheduledControllers + ifNotNil: [:sc | + "this means we are in an MVC project" + sc inActiveControllerProcess == interruptedProcess + ifTrue: [ScheduledControllers activeController]]) + context: interruptedProcess suspendedContext. + debugger externalInterrupt: true. + + Preferences logDebuggerStackToFile ifTrue: + [(aString includesSubstring: 'Space') & (aString includesSubstring: 'low') + ifTrue: [Smalltalk logError: aString inContext: debugger interruptedContext to: 'LowSpaceDebug.log'] + "logging disabled for 4.3 release, see + http://lists.squeak.org/pipermail/squeak-dev/2011-December/162503.html" + "ifFalse: [Smalltalk logSqueakError: aString inContext: debugger interruptedContext]"]. + + Preferences eToyFriendly ifTrue: [Project current world stopRunningAll]. + ^debugger + openNotifierContents: nil label: aString; + yourself + !

1 0

Jump to page: