Squeak-dev November 2019

squeak-dev@lists.squeakfoundation.org

23 participants
232 discussions

The Trunk: Kernel-mt.1283.mcz
by commits＠source.squeak.org 08 Dec '19

08 Dec '19

Marcel Taeumel uploaded a new version of Kernel to project The Trunk: http://source.squeak.org/trunk/Kernel-mt.1283.mcz ==================== Summary ==================== Name: Kernel-mt.1283 Author: mt Time: 27 November 2019, 10:25:51.203363 am UUID: 04694a24-76a1-a941-b664-645ffc7f27e6 Ancestors: Kernel-nice.1282 Removes Kernel -> Regex dependency. =============== Diff against Kernel-nice.1282 =============== Item was changed: ----- Method: BlockClosure>>valueSupplyingAnswers: (in category 'evaluating') ----- valueSupplyingAnswers: aListOfPairs "evaluate the block using a list of questions / answers that might be called upon to automatically respond to Object>>confirm: or FillInTheBlank requests" ^self on: ProvideAnswerNotification do: [ :notification | | caption | caption := notification messageText withSeparatorsCompacted. "to remove new lines" aListOfPairs detect: [ :each | caption = each first or: [ (caption includesSubstring: each first caseSensitive: false) or: [ (each first match: caption) or: [ (caption respondsTo: #matchesRegex:) + and: [ [caption matchesRegex: each first] on: Error do: [false] ] ] ] ] ] - and: [ [caption matchesRegex: each first] on: RegexSyntaxError do: [false] ] ] ] ] ] ifFound: [ :answer | notification resume: answer second ] ifNone: [ (ProvideAnswerNotification signal: notification messageText) ifNil: [ notification resume ] ifNotNil: [ :outerAnswer | notification resume: outerAnswer ] ] ]!

3 3

Adjusting the volume of a sound as it's playing
by Jim Rosenberg 08 Dec '19

08 Dec '19

Apologies in advance if this has been fixed in more recent versions of Squeak; I'm developing at the moment under Squeak 4.3. I have a project in which I'm adding sound to a longstanding body of artistic work implemented in Squeak. I'm going to need several sounds playing at once; typically there will be one or more instances of RepeatingSound and probably just one (or zero) MixedSound. When the MixedSound comes on I want to turn down the volume on the other sounds. How to do this. It has been driving me crazy. I was getting absolutely nothing to work to actually change the volume. There seems to be the right method in AbstractSound -- adjustVolumeTo:overMSecs: -- but in Squeak 4.3 this seems to not be properly overridden in MixedSound or RepeatingSound. I was getting absolutely nothing to work until I stumbled onto changing leftVols and rightVols by brute force at an explorer. This DOES WORK. leftVols and rightVols are instance variables in MixedSound, so it seems to me they should be changed by MixedSound's own implementation of adjustVolumeTo:overMSecs:. RepeatingSound should have its own implementation which just passes on to its sound. Maybe there's a better way to do this, but given that AbstractSound does have the right method, it seems like overriding here is the right thing to do. Comments? -Thanks, Jim

3 6

The Trunk: Morphic-mt.1592.mcz
by commits＠source.squeak.org 08 Dec '19

08 Dec '19

Marcel Taeumel uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-mt.1592.mcz ==================== Summary ==================== Name: Morphic-mt.1592 Author: mt Time: 22 November 2019, 5:38:54.489669 pm UUID: 7611ae0c-a1d0-ea42-84c5-0d2474fe2643 Ancestors: Morphic-mt.1591 Move rotation-specific stuff from Etoys to Morphic. It is used in Morphic anyway. #heading, #heading: #rotationDegrees, #rotationDegrees: #referencePosition, #referencePosition: #forwardDirection, #forwardDirection: =============== Diff against Morphic-mt.1591 =============== Item was added: + ----- Method: CircleMorph>>heading (in category 'rotate scale and flex') ----- + heading + "Overwritten to store the angle in #forwardDirection." + + ^ self rotationDegrees! Item was changed: + ----- Method: CircleMorph>>heading: (in category 'rotate scale and flex') ----- - ----- Method: CircleMorph>>heading: (in category 'geometry eToy') ----- heading: newHeading + "Overwritten to store the angle in #forwardDirection." + - "Set the receiver's heading (in eToy terms). - Note that circles never use flex shells." self rotationDegrees: newHeading.! Item was changed: + ----- Method: MatrixTransformMorph>>heading (in category 'rotate scale and flex') ----- - ----- Method: MatrixTransformMorph>>heading (in category 'geometry eToy') ----- heading "Return the receiver's heading (in eToy terms)" ^ self forwardDirection + self innerAngle! Item was added: + ----- Method: MatrixTransformMorph>>heading: (in category 'rotate scale and flex') ----- + heading: newHeading + "Set the receiver's heading (in eToy terms)" + self rotateBy: ((newHeading - self forwardDirection) - self innerAngle).! Item was changed: + ----- Method: MatrixTransformMorph>>setDirectionFrom: (in category 'rotate scale and flex') ----- - ----- Method: MatrixTransformMorph>>setDirectionFrom: (in category 'geometry eToy') ----- setDirectionFrom: aPoint | delta degrees | delta := (self transformFromWorld globalPointToLocal: aPoint) - super rotationCenter. degrees := delta degrees + 90.0. self forwardDirection: (degrees \\ 360) rounded. ! Item was changed: + ----- Method: Morph>>forwardDirection (in category 'rotate scale and flex') ----- - ----- Method: Morph>>forwardDirection (in category 'accessing') ----- forwardDirection + "Return the receiver's offset to distinguish #heading from #rotationDegrees." + + ^ self valueOfProperty: #forwardDirection ifAbsent: [0.0]! - "Return the receiver's forward direction (in eToy terms)" - ^self valueOfProperty: #forwardDirection ifAbsent:[0.0]! Item was added: + ----- Method: Morph>>forwardDirection: (in category 'rotate scale and flex') ----- + forwardDirection: newDirection + + self setProperty: #forwardDirection toValue: newDirection.! Item was added: + ----- Method: Morph>>heading (in category 'rotate scale and flex') ----- + heading + "Answer the current heading, which is #rotationDegrees relative to the #forwardDirection." + + ^ self rotationDegrees + self forwardDirection! Item was added: + ----- Method: Morph>>heading: (in category 'rotate scale and flex') ----- + heading: newHeading + + self rotationDegrees: (newHeading - self forwardDirection).! Item was changed: ----- Method: Morph>>rotationDegrees (in category 'rotate scale and flex') ----- rotationDegrees - "Default implementation." + self isFlexed ifFalse: [^ 0.0]. + self owner in: [:flexShell | ^ flexShell rotationDegrees].! - ^ 0.0 - ! Item was added: + ----- Method: Morph>>rotationDegrees: (in category 'rotate scale and flex') ----- + rotationDegrees: degrees + + self isFlexed ifFalse: [self addFlexShell]. + self owner in: [:flexShell | flexShell rotationDegrees: degrees].! Item was added: + ----- Method: Morph>>setDirectionFrom: (in category 'rotate scale and flex') ----- + setDirectionFrom: aPoint + | delta degrees | + delta := (self transformFromWorld globalPointToLocal: aPoint) - self referencePosition. + degrees := delta degrees + 90.0. + self forwardDirection: (degrees \\ 360) rounded. + ! Item was added: + ----- Method: PolygonMorph>>heading (in category 'rotate scale and flex') ----- + heading + "Overwritten to store the angle in #forwardDirection." + + ^ self rotationDegrees! Item was added: + ----- Method: PolygonMorph>>heading: (in category 'rotate scale and flex') ----- + heading: newHeading + "Overwritten to store the angle in #forwardDirection." + + self rotationDegrees: newHeading.! Item was changed: + ----- Method: PolygonMorph>>rotationDegrees: (in category 'rotate scale and flex') ----- - ----- Method: PolygonMorph>>rotationDegrees: (in category 'halo control') ----- rotationDegrees: degrees | flex center | (center := self valueOfProperty: #referencePosition) ifNil: [self setProperty: #referencePosition toValue: (center := self bounds center)]. flex := (MorphicTransform offset: center negated) withAngle: (degrees - self forwardDirection) degreesToRadians. self setVertices: (vertices collect: [:v | (flex transform: v) - flex offset]). self forwardDirection: degrees. ! Item was added: + ----- Method: SketchMorph>>heading: (in category 'rotate scale and flex') ----- + heading: newHeading + "If not rotating normally, change forward direction rather than heading" + rotationStyle == #normal ifTrue:[^super heading: newHeading]. + self isFlexed + ifTrue:[self forwardDirection: newHeading - owner rotationDegrees] + ifFalse:[self forwardDirection: newHeading]. + self layoutChanged! Item was removed: - ----- Method: TransformationMorph>>degreesOfFlex (in category 'geometry eToy') ----- - degreesOfFlex - "Return any rotation due to flexing" - ^ self rotationDegrees! Item was changed: + ----- Method: TransformationMorph>>forwardDirection (in category 'rotate scale and flex') ----- - ----- Method: TransformationMorph>>forwardDirection (in category 'accessing') ----- forwardDirection "Return the rendee's forward direction. If I have no rendee then return 0.0 degrees " | rendee | ( rendee := self renderedMorph) == self ifTrue: [ ^ 0.0 ] . ^ rendee forwardDirection! Item was changed: + ----- Method: TransformationMorph>>forwardDirection: (in category 'rotate scale and flex') ----- - ----- Method: TransformationMorph>>forwardDirection: (in category 'geometry eToy') ----- forwardDirection: degrees "If we have a rendee set its forward direction. Else do nothing." | rendee | ( rendee := self renderedMorph) == self ifTrue: [ ^ self ] . ^rendee forwardDirection: degrees! Item was changed: + ----- Method: TransformationMorph>>heading (in category 'rotate scale and flex') ----- - ----- Method: TransformationMorph>>heading (in category 'geometry eToy') ----- heading "End recusion when necessary." | rendee | (rendee := self renderedMorph) == self ifTrue: [ ^0.0 ] . ^ rendee heading! Item was changed: + ----- Method: TransformationMorph>>heading: (in category 'rotate scale and flex') ----- - ----- Method: TransformationMorph>>heading: (in category 'geometry eToy') ----- heading: newHeading "If we have a rendee set its heading. Else do nothing." | rendee | ( rendee := self renderedMorph) == self ifTrue: [ ^ self ] . ^rendee heading: newHeading! Item was changed: ----- Method: TransformationMorph>>rotationDegrees (in category 'rotate scale and flex') ----- rotationDegrees + "Overwritten because we can directly inform about the rotation." + ^ self angle radiansToDegrees negated! Item was changed: + ----- Method: TransformationMorph>>rotationDegrees: (in category 'rotate scale and flex') ----- - ----- Method: TransformationMorph>>rotationDegrees: (in category 'accessing') ----- rotationDegrees: degrees + "Overwritten because we know how to rotate our submorphs." + self adjustAfter:[self angle: degrees degreesToRadians negated]! Item was changed: + ----- Method: TransformationMorph>>setDirectionFrom: (in category 'rotate scale and flex') ----- - ----- Method: TransformationMorph>>setDirectionFrom: (in category 'geometry eToy') ----- setDirectionFrom: aPoint | delta degrees inner | inner := self renderedMorph. inner == self ifTrue:[^self]. delta := (inner transformFromWorld globalPointToLocal: aPoint) - inner referencePosition. degrees := delta degrees + 90.0. self forwardDirection: (degrees \\ 360) rounded. !

3 2

The Inbox: System-ct.1120.mcz
by commits＠source.squeak.org 06 Dec '19

06 Dec '19

A new version of System was added to project The Inbox: http://source.squeak.org/inbox/System-ct.1120.mcz ==================== Summary ==================== Name: System-ct.1120 Author: ct Time: 26 October 2019, 10:22:46.213469 pm UUID: 7ed0a01b-5518-e24f-9ead-65e1789c94d4 Ancestors: System-ct.1117 Revise System-ct.1117 (concerning CommonRequestStrings): Fix wrong dependency and improve code formatting =============== Diff against System-ct.1117 =============== Item was changed: ----- Method: Utilities class>>initializeCommonRequestStrings (in category 'common requests') ----- initializeCommonRequestStrings "Initialize the common request strings, a directly-editable list of expressions that can be evaluated from the 'do...' menu." CommonRequestStrings := StringHolder new contents: ( + String streamContents: [:stream | self commonRequestBlocks + do: [:block | block decompile statements + do: [:statement | stream + nextPutAll: (statement shortPrintString + copyWithRegex: '\s+' + matchesReplacedWith: String space); + nextPut: $.] + separatedBy: [stream cr]] + separatedBy: [stream cr; nextPut: $-; cr]]) - String streamContents: [:stream | - self commonRequestBlocks - do: [:block | - block decompile statements - do: [:statement | - statement veryShortPrintOn: stream. - stream nextPut: $.] - separatedBy: [stream cr]] - separatedBy: [stream cr; nextPut: $-; cr]]) "Utilities initializeCommonRequestStrings"!

4 5

SqueakSource mail/smtp setup
by tim Rowledge 03 Dec '19

03 Dec '19

I've been having 'fun' again with my personal squeaksource adventures. This time it is getting commit mails to actually send; in case I probably need to modify things to use SecureSMTPClient (assuming anyone thinks it still works?) and in another test case I need to change the default port. Adding a port number to the squeaksource settings page won't be too much of a pain (I hope, assuming I remember any of it after a couple of months) but I'd much rather hear that someone has already solved this and save the time. Anyone? tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Strange OpCodes: LCD: Launch Cartridge Disk

2 5

The Trunk: Morphic-eem.1596.mcz
by commits＠source.squeak.org 30 Nov '19

30 Nov '19

Eliot Miranda uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-eem.1596.mcz ==================== Summary ==================== Name: Morphic-eem.1596 Author: eem Time: 29 November 2019, 4:50:37.46714 pm UUID: e4ca2f3d-c9db-4468-bb91-cf698317b2f1 Ancestors: Morphic-mt.1595 Have seNders in the text editor also look up references to literals. =============== Diff against Morphic-mt.1595 =============== Item was changed: ----- Method: TextEditor>>selectedSelector (in category 'menu messages') ----- selectedSelector "Try to make a selector out of the current text selection" + | tokens | + tokens := Scanner new typedScanTokens: self selection string. + ^tokens isEmpty ifFalse: [tokens first]! - ^self selection string findSelector! Item was changed: ----- Method: TextEditor>>sendersOfIt (in category 'menu messages') ----- sendersOfIt "Open a senders browser on the selected selector" - | aSelector | self lineSelectAndEmptyCheck: [^ self]. + self selectedSelector ifNotNil: + [:aSelector| ^self systemNavigation browseAllCallsOn: aSelector]. + self selectedLiteral ifNotNil: + [:aLiteral| ^self systemNavigation browseAllCallsOn: aLiteral]. + morph flash! - (aSelector := self selectedSelector) == nil ifTrue: [^ morph flash]. - self systemNavigation browseAllCallsOn: aSelector!

2 2

ECOOP'20 Berlin - Call for Papers
by Fabio Niephaus 29 Nov '19

29 Nov '19

============================================================ The 34th Edition of ECOOP Call for Papers 13th-17th July 2020 Berlin, Germany https://2020.ecoop.org/ ============================================================ ECOOP is a conference about programming. Originally its primary focus was on object orientation, but now it looks at a much broader range of programming topics. Areas of interest include, at least, the design, implementation, optimization, analysis, and theory of programs, programming languages, and programming environments. It solicits both innovative and creative solutions to real problems as well as evaluations of existing solutions—evaluations that provide new insights. It also encourages the submission of reproduction studies. ECOOP 2020 solicits high-quality submissions describing original, unpublished results. The program committee will evaluate the technical contribution of each submission as well as its general relevance and accessibility to the ECOOP audience according the following criteria: - Originality. Papers must present new ideas and place them appropriately within the context established by previous research in the field. - Significance. The results in the paper must have the potential to add significantly to the state of the art or practice. - Evidence. The paper must present evidence supporting its claims. Examples of evidence include implemented systems, experimental results, statistical analyses, case studies, formalizations, and proofs. - Clarity. The paper must present its contributions and results clearly. On submission, authors will be asked to identify their paper with one of the following categories: - Research Paper. This is the most traditional category and solicits high quality research papers that demonstrate advances in the field. (As an alternative to being published in the conference proceedings, authors may wish to submit research papers to be considered for publication in ACM TOPLAS or Science of Computer Programming.) - Tool Insights Paper. These submissions focus on the practical details of the design and implementation of PL tools—details that are often omitted from regular research papers, despite being fascinating and worthy of communication. A strong Tool Insights Paper should communicate engineering experience and insights that are likely to be useful to other members of the PL community, who may face similar problems in future. Examples of issues that Tool Insights Papers might focus on include, but are not limited to: performance, reliability, portability, inter-tool integration, infrastructure re-use, evaluation issues, theory/practice gaps, precision/efficiency, and soundness/efficiency trade-offs. - Reproduction Study. A Reproduction Study is an empirical evaluation. It reconstructs an already published experiment but in a different context (for example, using a different virtual machine or platform, or in a different class of applications) in order to validate or refute important results of earlier work. A good Reproduction Study includes thorough empirical evaluation as well as a detailed comparison with the previous results, providing reasons for possible disagreements. (A thoroughly-conducted Reproduction Study that perfectly replicates an existing experiment and reaches the same conclusions will be regarded as significant, so long as said experiment is significant enough to be worthy of reproduction.) - Experience Report. Such reports focus on noteworthy applications of known PL techniques, tools, and ideas in interesting domains and by other communities. Examples include, but are not limited to, applications of PL techniques in industry, open source, education, and other academic disciplines. We welcome reports on successful applications of PL ideas and reports that shed light on limitations and problems that may provide inspiration for future research. - Pearl. This category solicits articles that explain a known idea in a new and elegant way, to the benefit of the PL community. A Pearl may well be shorter than a regular research paper, but there is no hard requirement on this. - Brave New Idea. The Brave New Idea category solicits forward-looking articles on ideas in the field of PL that may take some time to substantiate, but for which early communication to the community is likely to be of benefit. For this category we welcome papers that are particularly conceptually novel or unconventional and that as a result may be harder to back up by traditional evaluation methods. A Brave New Idea paper may well be shorter than a regular research paper, but there is no requirement for it to be so. Paper Submission ================ Only papers that have not been published and are not under review for publication elsewhere may be submitted. Double submissions will be rejected without review. If major parts of an ECOOP submission have appeared elsewhere in any form, authors are required to notify the ECOOP program chair and explain the overlap and relationship. Authors are also required to inform the program chair about closely related work submitted to another conference while the ECOOP submission is under review. Papers must be no longer than 25 pages, excluding references. See below for information about appendices. Authors will not be penalized for papers that are shorter than the page limit. Submissions will be carried out electronically via the conference website [1]. ECOOP Proceedings are published by Dagstuhl LIPIcs. Papers must be written in English and follow the Dagstuhl LIPIcs LaTeX-style template [2]. Authors retain ownership of their content. Note: Submitted papers do not need to include the ACM classification or keywords. Also, please DO NOT put your name in either the \author or \Copyright macro, in order to maintain anonymity for double-blind reviewing (see below). Anonymity ========= ECOOP will use light double-blind reviewing: authors’ identities are withheld until a reviewer submits his or her review (as usual, reviews are anonymous). To facilitate this, submitted papers must adhere to two rules: - Author names and institutions must be omitted. - References to authors’ own other work should be in the third person (for example, not “We build on our previous work…” but rather “We build on the work of…”). When in doubt, contact the Program Chair. Additional Material =================== Clearly marked additional appendices containing analyses, statistics, supporting proofs, etc. of possible value to reviewers but not published in the final publication, may be included beyond the page limit. The submission system provides an option to submit supplementary material; for example, a technical report including proofs, or web pages and repositories that cannot easily be anonymized. This supplementary material will be made available to reviewers after the initial reviews have been completed, when author names are revealed. Reviewers are under no obligation to examine such appendices and supplementary material. Therefore, the paper must be a stand-alone document - the appendices and supplementary material are a way of providing useful information that cannot fit in the page limit; they are not a means to extend the page limit. Authors of papers that have been submitted but not accepted by previous conferences may optionally submit a Note to Reviewers. The Note to Reviewers should provide the following information: - the identity of the previous venue(s) (for example, ESOP 2020, ‹Programming› 2020, POPL 2020, OOPSLA 2019) - a list the major issues identified by the reviews at those venues - a description of the changes made to the paper in response to those reviews These notes will be made available to reviewers after their initial reviews have been completed and author names have been revealed. Response Period =============== Authors will be given a three-day period to read and respond to the reviews of their papers before the program committee meeting. Responses have no formal length limit, but concision is likely to be effective. Artifact Evaluation =================== To reward the creation of artifacts and support replication of experiments, authors of accepted research papers may submit artifacts (such as tools, data, models, or videos) to be evaluated by an Artifact Evaluation Committee. Artifacts that pass muster will be recognized officially. Important Dates =============== - Paper submission: 10 January 2020 (Fri) - Author response: 16–18 March 2020 (Mon-Wed) - Author notification: 8 April 2020 (Wed) Journal First ============= We have Journal First arrangements with ACM Transactions on Programming Languages and Systems and Elsevier Science of Computer Programming. Common to both routes --------------------- Only new research papers are eligible for the Journal First routes to ECOOP 2020. That is, it is not acceptable to submit an extension of a previous conference paper, even if the associated journal solicits extended papers via its standard submission route. Authors of all accepted Journal First papers will be invited to submit a short abstract for their paper to appear in the ECOOP 2020 conference proceedings. Journal First papers will be included along with research papers submitted directly to the conference when a Distinguished Paper is selected. Science of Computer Programming route ------------------------------------- See this dedicated web page [3] for full details of how to submit to the ECOOP 2020 Science of Computer Programming (SCP) special issue. Submission deadline: December 2, 2019 (Mon) ACM Transactions on Programming Languages and Systems route ----------------------------------------------------------- See this announcement [4] for details of the TOPLAS scheme whereby papers submitted to TOPLAS can be presented at selected conferences. Authors interested in this route should submit their paper to TOPLAS via its usual submission system and mark it as an ECOOP 2020 submission. The ECOOP Program Chair will then be informed of this submission and will have some input into the review process. Submission deadline: October 10, 2019 (Thu) More Information ================ For additional information, please contact the ECOOP Program Chair, Robert Hirschfeld [5]. [1] https://2020.ecoop.org/track/ecoop-2020-papers [2] https://www.dagstuhl.de/en/publications/lipics/instructions-for-authors/ [3] https://www.journals.elsevier.com/science-of-computer-programming/call-for-… [4] https://toplas.acm.org/announcements.cfm#submit-a-paper-for-pldi-2016 [5] robert.hirschfeld(a)hpi.uni-potsdam.de

1 0

The Trunk: Tools-mt.922.mcz
by commits＠source.squeak.org 29 Nov '19

29 Nov '19

Marcel Taeumel uploaded a new version of Tools to project The Trunk: http://source.squeak.org/trunk/Tools-mt.922.mcz ==================== Summary ==================== Name: Tools-mt.922 Author: mt Time: 29 November 2019, 11:45:06.040061 am UUID: 2a67c032-4bcf-334d-898e-862aeafd93af Ancestors: Tools-mt.921 Due to recurrent requests, add an #ifNil-check for the class argument in the label-formatting methods of all code holders. Still, also document the situation in a flag comment. At least, this makes this method more robust for the upcoming release. :-) =============== Diff against Tools-mt.921 =============== Item was changed: ----- Method: CodeHolder>>formattedLabel:forSelector:inClass: (in category 'message list') ----- formattedLabel: aString forSelector: aSymbol inClass: aClass + "Show deprecated messages differently so that users recognize them quickly to avoid them. This is a performance critical method in the user interface." - "Show deprecated messages differently so that users recognize them quickly to avoid them." | formattedLabel | + self flag: #investigate. "mt: aClass must never be nil!! Faulty tools should override this call themselves or fix the caller site." + aClass ifNil: [^ aString]. + (aSymbol = #Definition or: [aSymbol = #Comment]) ifTrue: [aClass isDeprecated ifFalse: [^ aString]] ifFalse: [(aClass isDeprecated or: [(aClass compiledMethodAt: aSymbol ifAbsent: [^ aString]) isDeprecated]) ifFalse: [^ aString]]. formattedLabel := aString asText. (self userInterfaceTheme deprecatedMessageAttributes ifNil: [{TextColor gray. TextEmphasis struckOut}]) do: [:textAttribute | formattedLabel addAttribute: textAttribute]. ^ formattedLabel.!

1 0

The Trunk: 60Deprecated-mt.66.mcz
by commits＠source.squeak.org 29 Nov '19

29 Nov '19

Marcel Taeumel uploaded a new version of 60Deprecated to project The Trunk: http://source.squeak.org/trunk/60Deprecated-mt.66.mcz ==================== Summary ==================== Name: 60Deprecated-mt.66 Author: mt Time: 29 November 2019, 11:43:24.082061 am UUID: c4f0cc4d-13c8-5a4c-9b28-a572260ca3a0 Ancestors: 60Deprecated-mt.65 Complements Tools-mt.920/921. =============== Diff against 60Deprecated-mt.65 =============== Item was added: + ----- Method: Inspector>>selectedSlotName (in category '*60Deprecated-selecting') ----- + selectedSlotName + + self deprecated: 'Use #selectedFieldName instead.'. + ^ self selectedFieldName!

1 0

The Trunk: Tools-mt.921.mcz
by commits＠source.squeak.org 29 Nov '19

29 Nov '19

Marcel Taeumel uploaded a new version of Tools to project The Trunk: http://source.squeak.org/trunk/Tools-mt.921.mcz ==================== Summary ==================== Name: Tools-mt.921 Author: mt Time: 29 November 2019, 11:42:49.542061 am UUID: 73dad5fb-bcd1-f742-ab5b-e29d165d6d63 Ancestors: Tools-mt.920 Debugger: Implements the idea of inbox Tools-eem.915, which preserves inspectors' states when toggling the selected context. Because it is model-only, should work also in MVC debuggers. There might be a quick with #update:with: in PluggableTextView, though. =============== Diff against Tools-mt.920 =============== Item was changed: CodeHolder subclass: #Debugger + instanceVariableNames: 'interruptedProcess contextStack contextStackIndex contextStackList receiverInspector receiverInspectorState contextVariablesInspector contextVariablesInspectorState externalInterrupt proceedValue selectingPC savedCursor isolationHead failedProject labelString message untilExpression' - instanceVariableNames: 'interruptedProcess contextStack contextStackIndex contextStackList receiverInspector contextVariablesInspector externalInterrupt proceedValue selectingPC savedCursor isolationHead failedProject labelString message untilExpression' classVariableNames: 'ContextStackKeystrokes ErrorReportServer FullStackSize InterruptUIProcessIfBlockedOnErrorInBackgroundProcess NotifierStackSize SavedExtent StackSizeLimit WantsAnnotationPane' poolDictionaries: '' category: 'Tools-Debugger'! !Debugger commentStamp: '<historical>' prior: 0! I represent the machine state at the time of an interrupted process. I also represent a query path into the state of the process. The debugger is typically viewed through a window that views the stack of suspended contexts, the code for, and execution point in, the currently selected message, and inspectors on both the receiver of the currently selected message, and the variables in the current context. Special note on recursive errors: Some errors affect Squeak's ability to present a debugger. This is normally an unrecoverable situation. However, if such an error occurs in an isolation layer, Squeak will attempt to exit from the isolation layer and then present a debugger. Here is the chain of events in such a recovery. * A recursive error is detected. * The current project is queried for an isolationHead * Changes in the isolationHead are revoked * The parent project of isolated project is returned to * The debugger is opened there and execution resumes. If the user closes that debugger, execution continues in the outer project and layer. If, after repairing some damage, the user proceeds from the debugger, then the isolationHead is re-invoked, the failed project is re-entered, and execution resumes in that world. ! Item was changed: ----- Method: Debugger>>contextStackIndex:oldContextWas: (in category 'private') ----- contextStackIndex: anInteger oldContextWas: oldContext "Change the context stack index to anInteger, perhaps in response to user selection." + | isNewMethod selectedContextSlotName | + self saveReceiverInspectorState. + self saveContextVariablesInspectorState. - | isNewMethod selectedContextSlotName index | contextStackIndex := anInteger. anInteger = 0 ifTrue: [currentCompiledMethod := contents := nil. self changed: #contextStackIndex. self decorateButtons. self contentsChanged. contextVariablesInspector object: nil. receiverInspector object: self receiver. ^self]. + selectedContextSlotName := contextVariablesInspector selectedFieldName. - selectedContextSlotName := contextVariablesInspector selectedSlotName. isNewMethod := oldContext == nil or: [oldContext method ~~ (currentCompiledMethod := self selectedContext method)]. isNewMethod ifTrue: [contents := self selectedMessage. self contentsChanged. self pcRange]. self changed: #contextStackIndex. self decorateButtons. contextVariablesInspector object: self selectedContext. + self restoreContextVariablesInspectorState. - ((index := contextVariablesInspector fieldList indexOf: selectedContextSlotName) ~= 0 - and: [index ~= contextVariablesInspector selectionIndex]) ifTrue: - [contextVariablesInspector toggleIndex: index]. receiverInspector object: self receiver. + self restoreReceiverInspectorState. isNewMethod ifFalse: [self changed: #contentsSelection]! Item was added: + ----- Method: Debugger>>keyForContextVariablesInspectorState (in category 'user interface') ----- + keyForContextVariablesInspectorState + + ^ self contextVariablesInspector object ifNotNil: [:ctxt | ctxt method]! Item was added: + ----- Method: Debugger>>keyForReceiverInspectorState (in category 'user interface') ----- + keyForReceiverInspectorState + + ^ self receiverInspector object! Item was added: + ----- Method: Debugger>>restoreContextVariablesInspectorState (in category 'user interface') ----- + restoreContextVariablesInspectorState + "For the user's convenience. Save field selection and user-typed content in the context-variables inspector. See #saveContextVariablesInspectorState." + + contextVariablesInspectorState ifNotNil: [:stateForAll | + self keyForContextVariablesInspectorState ifNotNil: [:keyForState | + stateForAll + at: keyForState + ifPresent: [:state | + self contextVariablesInspector selectFieldNamed: state first. + state second ifNotNil: [:contentsTyped | + self contextVariablesInspector + setContentsTyped: contentsTyped]]]].! Item was added: + ----- Method: Debugger>>restoreReceiverInspectorState (in category 'user interface') ----- + restoreReceiverInspectorState + "For the user's convenience. Restore field selection and user-typed content in the receiver inspector. See #saveReceiverInspectorState." + + receiverInspectorState ifNotNil: [:stateForAll | + self keyForReceiverInspectorState ifNotNil: [:keyForState | + stateForAll + at: keyForState + ifPresent: [:state | + self receiverInspector selectFieldNamed: state first. + state second ifNotNil: [:contentsTyped | + self receiverInspector + setContentsTyped: contentsTyped]]]].! Item was added: + ----- Method: Debugger>>saveContextVariablesInspectorState (in category 'user interface') ----- + saveContextVariablesInspectorState + "For the user's convenience. Save field selection and user-typed content in the context-variables inspector. See #restoreContextVariablesInspectorState." + + | stateToSave keyForState | + (keyForState := self keyForContextVariablesInspectorState) + ifNil: [^ self]. + contextVariablesInspectorState + ifNil: [contextVariablesInspectorState := IdentityDictionary new]. + stateToSave := { + self contextVariablesInspector selectedFieldName. + self contextVariablesInspector contentsTyped }. + contextVariablesInspectorState + at: keyForState + put: stateToSave.! Item was added: + ----- Method: Debugger>>saveReceiverInspectorState (in category 'user interface') ----- + saveReceiverInspectorState + "For the user's convenience. Save field selection and user-typed content in the receiver inspector. See #restoreReceiverInspectorState." + + | stateToSave keyForState | + (keyForState := self keyForReceiverInspectorState) + ifNil: [^ self]. + receiverInspectorState + ifNil: [receiverInspectorState := IdentityDictionary new]. + stateToSave := { + self receiverInspector selectedFieldName. + self receiverInspector contentsTyped }. + receiverInspectorState + at: keyForState + put: stateToSave.!

1 0

← Newer
1
2
3
4
5
6
7
8
...
24
Older →

Jump to page: