Squeak-dev February 2020

squeak-dev@lists.squeakfoundation.org

32 participants
305 discussions

The Inbox: Morphic-ct.1636.mcz
by commits＠source.squeak.org 29 Feb '20

29 Feb '20

Christoph Thiede uploaded a new version of Morphic to project The Inbox: http://source.squeak.org/inbox/Morphic-ct.1636.mcz ==================== Summary ==================== Name: Morphic-ct.1636 Author: ct Time: 29 February 2020, 1:39:06.752872 pm UUID: a0a951d1-1df6-6243-9671-b4ebec0afa85 Ancestors: Morphic-mt.1631 Adds protection against event-handling errors as proposed by Marcel et al. in [1]. I did not note any subjective performance impact, but we might want to write measures/tests for this. Please review! Minimum example (don't execute this BEFORE loading this commit): c := Morph newSubclass. c compile: 'handleMouseMove: evt ^self error'. m := c new. m openInHand. [1] http://forum.world.st/bug-in-a-ToolBuilder-Squeak5-3rc2-tp5112536p5112551.h… =============== Diff against Morphic-mt.1631 =============== Item was changed: ----- Method: HandMorph>>fullDrawOn: (in category 'drawing') ----- fullDrawOn: aCanvas "A HandMorph has unusual drawing requirements: 1. the hand itself (i.e., the cursor) appears in front of its submorphs 2. morphs being held by the hand cast a shadow on the world/morphs below The illusion is that the hand plucks up morphs and carries them above the world." "Note: This version caches an image of the morphs being held by the hand for better performance. This cache is invalidated if one of those morphs changes." | disableCaching subBnds | self visible ifFalse: [^self]. (aCanvas isVisible: self fullBounds) ifFalse: [^self]. + ((self hasProperty: #errorOnDraw) or: [self hasProperty: #errorOnEvent]) + ifTrue: [^self drawErrorOn: aCanvas]. - (self hasProperty: #errorOnDraw) ifTrue:[^self drawErrorOn: aCanvas]. disableCaching := false. disableCaching ifTrue: [self nonCachingFullDrawOn: aCanvas. ^self]. submorphs isEmpty ifTrue: [cacheCanvas := nil. ^self drawOn: aCanvas]. "just draw the hand itself" "special handling of a single submorph that wants to do its own thing when being dragged" (submorphs size = 1 and: [submorphs first handledOwnDraggingBy: self on: aCanvas]) ifTrue: [^ self drawOn: aCanvas]. subBnds := Rectangle merging: (submorphs collect: [:m | m fullBounds]). self updateCacheCanvas: aCanvas. (cacheCanvas isNil or: [cachedCanvasHasHoles and: [cacheCanvas depth = 1]]) ifTrue: ["could not use caching due to translucency; do full draw" self nonCachingFullDrawOn: aCanvas. ^self]. "draw the shadow" aCanvas asShadowDrawingCanvas translateBy: self shadowOffset during: [:shadowCanvas | cachedCanvasHasHoles ifTrue: ["Have to draw the real shadow of the form" shadowCanvas paintImage: cacheCanvas form at: subBnds origin] ifFalse: ["Much faster if only have to shade the edge of a solid rectangle" (subBnds areasOutside: (subBnds translateBy: self shadowOffset negated)) do: [:r | shadowCanvas fillRectangle: r color: Color black]]]. "draw morphs in front of the shadow using the cached Form" cachedCanvasHasHoles ifTrue: [aCanvas paintImage: cacheCanvas form at: subBnds origin] ifFalse: [aCanvas drawImage: cacheCanvas form at: subBnds origin sourceRect: cacheCanvas form boundingBox]. self drawOn: aCanvas "draw the hand itself in front of morphs"! Item was added: + ----- Method: KeyboardEvent>>isHighFrequentEvent (in category 'testing') ----- + isHighFrequentEvent + + ^ false! Item was changed: ----- Method: Morph>>buildDebugMenu: (in category 'debug and other') ----- buildDebugMenu: aHand "Answer a debugging menu for the receiver. The hand argument is seemingly historical and plays no role presently" | aMenu aPlayer | aMenu := MenuMorph new defaultTarget: self. aMenu addStayUpItem. (self hasProperty: #errorOnDraw) ifTrue: [aMenu add: 'start drawing again' translated action: #resumeAfterDrawError. aMenu addLine]. + (self hasProperty: #errorOnEvent) ifTrue: + [aMenu add: 'start event handling again' translated action: #resumeAfterEventError. + aMenu addLine]. (self hasProperty: #errorOnStep) ifTrue: [aMenu add: 'start stepping again' translated action: #resumeAfterStepError. aMenu addLine]. aMenu add: 'inspect morph' translated action: #inspectInMorphic:. aMenu add: 'inspect owner chain' translated action: #inspectOwnerChain. Smalltalk isMorphic ifFalse: [aMenu add: 'inspect morph (in MVC)' translated action: #inspect]. self isMorphicModel ifTrue: [aMenu add: 'inspect model' translated target: self model action: #inspect; add: 'explore model' translated target: self model action: #explore]. (aPlayer := self player) ifNotNil: [aMenu add: 'inspect player' translated target: aPlayer action: #inspect]. aMenu add: 'explore morph' translated target: self selector: #exploreInMorphic:. aMenu addLine. aPlayer ifNotNil: [ aMenu add: 'viewer for Player' translated target: self player action: #beViewed. aMenu balloonTextForLastItem: 'Opens a viewer on my Player -- this is the same thing you get if you click on the cyan "View" halo handle' translated ]. aMenu add: 'viewer for Morph' translated target: self action: #viewMorphDirectly. aMenu balloonTextForLastItem: 'Opens a Viewer on this Morph, rather than on its Player' translated. aMenu addLine. aPlayer ifNotNil: [aPlayer class isUniClass ifTrue: [ aMenu add: 'browse player class' translated target: aPlayer selector: #haveFullProtocolBrowsedShowingSelector: argumentList: #(nil)]]. aMenu add: 'browse morph class' translated target: self selector: #browseHierarchy. + self isMorphicModel - (self isMorphicModel) ifTrue: [aMenu add: 'browse model class' target: self model selector: #browseHierarchy]. aMenu addLine. self addViewingItemsTo: aMenu. aMenu add: 'make own subclass' translated action: #subclassMorph; add: 'save morph in file' translated action: #saveOnFile; addLine; add: 'call #tempCommand' translated action: #tempCommand; add: 'define #tempCommand' translated action: #defineTempCommand; addLine; add: 'control-menu...' translated target: self selector: #invokeMetaMenu:; add: 'edit balloon help' translated action: #editBalloonHelpText. ^ aMenu! Item was changed: ----- Method: Morph>>fullDrawOn: (in category 'drawing') ----- fullDrawOn: aCanvas "Draw the full Morphic structure on the given Canvas" self visible ifFalse: [^ self]. + (aCanvas isVisible: self fullBounds) ifFalse: [^self]. + ((self hasProperty: #errorOnDraw) or: [self hasProperty: #errorOnEvent]) + ifTrue: [^self drawErrorOn: aCanvas]. + + "Note: At some point we should generalize this into some sort of multi-canvas so that we can cross-optimize some drawing operations." - (aCanvas isVisible: self fullBounds) ifFalse:[^self]. - (self hasProperty: #errorOnDraw) ifTrue:[^self drawErrorOn: aCanvas]. - "Note: At some point we should generalize this into some sort of - multi-canvas so that we can cross-optimize some drawing operations." "Pass 1: Draw eventual drop-shadow" self hasDropShadow ifTrue: [self drawDropShadowOn: aCanvas]. (self hasRolloverBorder and: [(aCanvas seesNothingOutside: self bounds) not]) ifTrue: [self drawRolloverBorderOn: aCanvas]. "Pass 2: Draw receiver itself" (aCanvas isVisible: self bounds) ifTrue:[aCanvas drawMorph: self]. self drawSubmorphsOn: aCanvas. self drawOverlayOn: aCanvas.! Item was changed: ----- Method: Morph>>handleEvent: (in category 'events-processing') ----- handleEvent: anEvent "Apply event filters and then handle the resulting event. We have to return the event to chain filters." | filteredEvent | + (self hasProperty: #errorOnEvent) ifTrue: [^ anEvent]. filteredEvent := self sendFilterEventBubble: anEvent for: self. filteredEvent wasIgnored ifFalse: [filteredEvent sentTo: self]. ^ filteredEvent! Item was changed: ----- Method: Morph>>resumeAfterDrawError (in category 'debug and other') ----- resumeAfterDrawError self changed. + self removeProperty: #errorOnDraw. - self removeProperty:#errorOnDraw. self changed.! Item was added: + ----- Method: Morph>>resumeAfterEventError (in category 'debug and other') ----- + resumeAfterEventError + + self removeProperty: #errorOnEvent. + self changed.! Item was changed: ----- Method: Morph>>resumeAfterStepError (in category 'debug and other') ----- resumeAfterStepError "Resume stepping after an error has occured." self startStepping. "Will #step" + self removeProperty: #errorOnStep. "Will remove prop only if #step was okay" - self removeProperty:#errorOnStep. "Will remove prop only if #step was okay" ! Item was added: + ----- Method: MorphicEvent>>isHighFrequentEvent (in category 'testing') ----- + isHighFrequentEvent + "A high frequent event is one that occurs really often. If an event handler raises an error each time it receives a particular event, this could stall your image. For this reason, we handle high frequent events with extra care. On the contrary, cathing too many event errors would restrict convenience of tools (ex: a menu item that raises an error). See WorldState >> #processEventsSafely:." + + ^ true! Item was added: + ----- Method: MorphicProject>>fatalEventHandlingError: (in category 'scheduling & debugging') ----- + fatalEventHandlingError: errMsg + "Morphic event handling failed and could not be recovered. So we end up here." + + self primitiveError: errMsg. + + "Hm... we should jump into a 'safe' worldState here, but how do we find it?!!"! Item was added: + ----- Method: MouseButtonEvent>>isHighFrequentEvent (in category 'testing') ----- + isHighFrequentEvent + + ^ false! Item was changed: ----- Method: WorldState>>displayWorldSafely: (in category 'update cycle') ----- displayWorldSafely: aWorld "Update this world's display and keep track of errors during draw methods." + ^ self + doSafely: [aWorld displayWorld] + onErrorThat: [:error | true] + setErrorFlag: #errorOnDraw + ifFatal: [:error | Project current fatalDrawingError: error] + afterErrorDo: [aWorld fullRepaintNeeded]! - | finished classesWithErrors | - finished := false. - - [finished] whileFalse: [ - [aWorld displayWorld. finished := true] on: Error, Halt, Warning do: [:ex | - "Handle a drawing error" - | err rcvr errCtx errMorph | - err := ex description. - rcvr := ex receiver. - - errCtx := thisContext. - [ - errCtx := errCtx sender. - "Search the sender chain to find the morph causing the problem" - [errCtx notNil and:[(errCtx receiver isMorph) not]] - whileTrue:[errCtx := errCtx sender]. - "If we're at the root of the context chain then we have a fatal drawing problem" - errCtx ifNil:[^Project current fatalDrawingError: err]. - errMorph := errCtx receiver. - "If the morph causing the problem has already the #drawError flag set, - then search for the next morph above in the caller chain." - errMorph hasProperty: #errorOnDraw - ] whileTrue. - errMorph setProperty: #errorOnDraw toValue: true. - - "Catch all errors, one for each receiver class." - classesWithErrors ifNil: [classesWithErrors := IdentitySet new]. - (classesWithErrors includes: rcvr class) ifFalse: [ - classesWithErrors add: rcvr class. - ToolSet debugException: ex]. - - "Repaint all to catch all errors now and not if the debugger will appear." - aWorld fullRepaintNeeded. - ]].! Item was changed: ----- Method: WorldState>>doOneCycleNowFor: (in category 'update cycle') ----- doOneCycleNowFor: aWorld "Immediately do one cycle of the interaction loop. This should not be called directly, but only via doOneCycleFor:" | capturingGesture | DisplayScreen checkForNewScreenSize. capturingGesture := false. "self flag: #bob. " "need to consider remote hands in lower worlds" "process user input events" LastCycleTime := Time millisecondClockValue. self handsDo: [:h | ActiveHand := h. + self processEventsSafely: h. - h processEvents. capturingGesture := capturingGesture or: [ h isCapturingGesturePoints ]. ActiveHand := nil ]. "the default is the primary hand" ActiveHand := self hands first. "The gesture recognizer needs enough points to be accurate. Therefore morph stepping is disabled while capturing points for the recognizer" capturingGesture ifFalse: [aWorld runStepMethods. "there are currently some variations here" self displayWorldSafely: aWorld]. ! Item was added: + ----- Method: WorldState>>doSafely:onErrorThat:setErrorFlag:ifFatal:afterErrorDo: (in category 'update cycle') ----- + doSafely: aBlock onErrorThat: errorPredicate setErrorFlag: errorFlag ifFatal: fatalErrorBlock afterErrorDo: postErrorBlock + "Evaluate aBlock and keep track of errors during morph invocations." + + | finished classesWithErrors | + finished := false. + classesWithErrors := IdentitySet new. + [finished] whileFalse: [ + [aBlock value. finished := true] on: Error, Halt, Warning do: [:ex | + | err rcvr errCtxt errMorph | + (errorPredicate cull: ex) + ifFalse: [ex pass]. + err := ex description. + rcvr := ex receiver. + + errCtxt := thisContext. + [ + errCtxt := errCtxt sender. + "Search the sender chain to find the morph causing the problem" + [errCtxt notNil and: [(errCtxt receiver isMorph) not]] + whileTrue: [errCtxt := errCtxt sender]. + "If we're at the root of the context chain then we have a fatal problem" + errCtxt ifNil: [^ fatalErrorBlock cull: err]. + errMorph := errCtxt receiver. + "If the morph causing the problem has already the error flag set, then search for the next morph above in the caller chain." + errMorph hasProperty: errorFlag + ] whileTrue. + errMorph setProperty: errorFlag toValue: true. + + "Catch all errors, one for each receiver class." + (classesWithErrors includes: rcvr class) ifFalse: [ + classesWithErrors add: rcvr class. + ToolSet debugException: ex]. + + postErrorBlock cull: err. + ]].! Item was added: + ----- Method: WorldState>>processEventsSafely: (in category 'update cycle') ----- + processEventsSafely: aHandMorph + + ^ self + doSafely: [aHandMorph processEvents] + onErrorThat: [:error | ActiveEvent isHighFrequentEvent] + setErrorFlag: #errorOnEvent + ifFatal: [:error | Project current fatalEventHandlingError: error] + afterErrorDo: []!

1 0

Bug in PolygonMorph>>#filledForm
by Stéphane Rollandin 28 Feb '20

28 Feb '20

Hello, Investigating why I had trouble raising the halo on a PolygonMorph, I found that its #filledForm method is broken. To see this, evaluate the following, which will display a triangle that has plenty of holes: (PolygonMorph new setVertices: {100@100. 300@100. 300@300}) filledForm asMorph openInHand So the filled form is not quite filled, and as a consequence #containsPoint: is broken for PolygonMorph. Note that the holes have a different pattern on 32bit and 64bits images. This is on Windows, last tested with current trunk images. Stef

12 27

5.3 release
by Nicolas Cellier 28 Feb '20

28 Feb '20

Hi all, I've just noticed that stable still points to 5.1 http://files.squeak.org/current_stable/ No urge to fix now that we are close to 5.3, but we must not forget... Wow, I also did not notice that 5.2 did continue to receive patches quite lately: http://files.squeak.org/5.2/

2 1

The Trunk: ReleaseBuilder-mt.207.mcz
by commits＠source.squeak.org 28 Feb '20

28 Feb '20

Marcel Taeumel uploaded a new version of ReleaseBuilder to project The Trunk: http://source.squeak.org/trunk/ReleaseBuilder-mt.207.mcz ==================== Summary ==================== Name: ReleaseBuilder-mt.207 Author: mt Time: 28 February 2020, 2:28:15.257195 pm UUID: 892206e4-0670-1243-ae83-f66bfbff7888 Ancestors: ReleaseBuilder-mt.206 Bumps Squeak version to 5.3rc3 --- Yay! :-) =============== Diff against ReleaseBuilder-mt.206 =============== Item was changed: ----- Method: ReleaseBuilder class>>initialize (in category 'class initialization') ----- initialize QAndA ifNil: [self clearQAndA]. "We have to be after AutoStart so that Morphic is up and running." Smalltalk addToStartUpList: ReleaseBuilder after: AutoStart. + SystemVersion newVersion: 'Squeak5.3rc3'! - SystemVersion newVersion: 'Squeak5.3rc2'!

1 0

The Trunk: Morphic-mt.1631.mcz
by commits＠source.squeak.org 28 Feb '20

28 Feb '20

Marcel Taeumel uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-mt.1631.mcz ==================== Summary ==================== Name: Morphic-mt.1631 Author: mt Time: 28 February 2020, 2:27:25.148195 pm UUID: f9a7fa6d-87fc-074a-a23b-1eee0bd4772a Ancestors: Morphic-mt.1630 Prepare 5.3rc3 --- Clean up event stats during release building. =============== Diff against Morphic-mt.1630 =============== Item was added: + ----- Method: HandMorph class>>cleanUp: (in category 'initialization') ----- + cleanUp: aggressive + + aggressive ifTrue: [EventStats := nil].!

1 0

The Trunk: System-mt.1137.mcz
by commits＠source.squeak.org 28 Feb '20

28 Feb '20

Marcel Taeumel uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-mt.1137.mcz ==================== Summary ==================== Name: System-mt.1137 Author: mt Time: 28 February 2020, 2:26:26.058195 pm UUID: dc9de28f-3e13-e94d-a21b-1fdbf6ca003a Ancestors: System-mt.1136 Prepare 5.3rc3 --- Updates year in Squeak license. Properly clean up the clipboard. =============== Diff against System-mt.1136 =============== Item was changed: ----- Method: Clipboard class>>cleanUp: (in category 'initialize-release') ----- cleanUp: aggressive + aggressive ifTrue: [self default reset].! - aggressive ifTrue: [self default delete].! Item was changed: ----- Method: Clipboard>>initialize (in category 'initialize') ----- initialize + + super initialize. + self reset.! - contents := '' asText. - recent := OrderedCollection new.! Item was added: + ----- Method: Clipboard>>reset (in category 'initialize') ----- + reset + "Prepare or clean-up internal buffers, but keep external (or host) clipboard as is." + + contents := '' asText. + recent := OrderedCollection new.! Item was changed: ----- Method: SmalltalkImage>>license (in category 'license') ----- license "This method was automatically generated. Edit it using:" "SqueakLicenseHelp edit: #officialLicense" ^ ( 'The current release of Squeak is a combination of source code originating from Apple which Apple agreed to license under the Apache License and more recent contributions licensed under the MIT license. The vast majority of the code is under the MIT License: MIT License + Copyright (c) The individual, corporate, and institutional contributors who have collectively contributed elements to this software ("The Squeak Community"), 1996-2020 All rights reserved. - Copyright (c) The individual, corporate, and institutional contributors who have collectively contributed elements to this software ("The Squeak Community"), 1996-2019 All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Portions of Squeak are covered by the Apache License: Apache License, Version 2.0 Copyright (c) Xerox Corp. 1981, 1982 All rights reserved. Copyright (c) Apple Computer, Inc. 1985-1996 All rights reserved. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. !! ]style[(258 1 11 1216 53 2 27 297 42 308)c159159159,,b,,c159159159,,b,,Rhttp://www.apache.org/licenses/LICENSE-2…;,!!' readStream nextChunkText)!

1 0

The Trunk: Tools-mt.942.mcz
by commits＠source.squeak.org 28 Feb '20

28 Feb '20

Marcel Taeumel uploaded a new version of Tools to project The Trunk: http://source.squeak.org/trunk/Tools-mt.942.mcz ==================== Summary ==================== Name: Tools-mt.942 Author: mt Time: 28 February 2020, 2:25:27.228195 pm UUID: 60de91cf-f275-744b-91f0-58f80225d512 Ancestors: Tools-mt.941 Prepare 5.3rc3 --- All those "----" entries (SNAPSHOT, QUIT, etc.) in the changes file should not be of type #doIt, because that can cause Compiler/Parser errors. Change it to #misc instead. We might want to remove any other " if begins with ----" checks later, too. =============== Diff against Tools-mt.941 =============== Item was changed: ----- Method: ChangeList>>scanFile:from:to: (in category 'scanning') ----- scanFile: aFile from: startPosition to: stopPosition file := aFile. changeList := OrderedCollection new. list := OrderedCollection new. listIndex := 0. file position: startPosition. 'Scanning ', aFile localName, '...' displayProgressFrom: startPosition to: stopPosition during: [:bar | | prevChar itemPosition item | [file position < stopPosition] whileTrue: [bar value: file position. [file atEnd not and: [file peek isSeparator]] whileTrue: [prevChar := file next]. (file peekFor: $!!) ifTrue: [(prevChar = Character cr or: [prevChar = Character lf]) ifTrue: [self scanCategory]] ifFalse: [itemPosition := file position. item := file nextChunk. file skipStyleChunk. item size > 0 ifTrue: + [(item beginsWith: '----') + ifTrue: + [self addItem: (ChangeRecord new + file: file position: itemPosition type: #misc) + text: 'misc: ' , (item contractTo: 50)] + ifFalse: + [self addItem: (ChangeRecord new + file: file position: itemPosition type: #doIt) + text: 'do it: ' , (item contractTo: 50)]]]]]. - [self addItem: (ChangeRecord new file: file position: itemPosition type: #doIt) - text: 'do it: ' , (item contractTo: 50)]]]]. listSelections := Array new: list size withAll: false!

1 0

The Trunk: Help-Squeak-Project-mt.79.mcz
by commits＠source.squeak.org 28 Feb '20

28 Feb '20

Marcel Taeumel uploaded a new version of Help-Squeak-Project to project The Trunk: http://source.squeak.org/trunk/Help-Squeak-Project-mt.79.mcz ==================== Summary ==================== Name: Help-Squeak-Project-mt.79 Author: mt Time: 28 February 2020, 2:22:13.400195 pm UUID: 47033dd7-4332-6842-9975-62e21bc34506 Ancestors: Help-Squeak-Project-mt.78 Prepare 5.3rc3 --- Fixes some texts in the welcome window. =============== Diff against Help-Squeak-Project-mt.78 =============== Item was changed: ----- Method: SqueakHelp class>>introduction (in category 'pages') ----- introduction "This method was automatically generated. Edit it using:" "SqueakHelp edit: #introduction" ^(HelpTopic title: 'Welcome' contents: 'Welcome to Squeak Visit http://www.squeak.org for the lastest information. Squeak is an open-source Smalltalk programming system available for all major platforms. It features the Morphic framework, which promotes low effort graphical, interactive application development and maintenance. Many projects have been successfully created with Squeak in a wide range of domains such as education, multimedia, gaming, research, and commerce. Squeak is fast, flexible and free. It''s Smalltalk!!!! Everything is an object. Objects collaborate by sending messages to achieve the desired application behavior. The Smalltalk programming language has a concise syntax and simple execution semantics. The Smalltalk system is implemented in itself: Compiler, debugger, programming tools, and so on are all Smalltalk code the user can read and modify. Novice programmers can get started easily and experts can engineer elegant solutions at large. Morphic UI Framework All graphical objects are tangible and interactively changeable. This promotes short feedback loops and low-effort application development. Morphic thus leverages the live programming experience of traditional Smalltalk environments from a mainly text-focused domain to a graphical one. Powerful Tooling The dynamic Squeak environment provides a variety of tools for browsing, writing, executing, and versioning Smalltalk code. Multiple debugging sessions can be served concurrently. Thanks to Morphic, tool customization can be achieved with reasonable effort. Fast Virtual Machine There are several fast Squeak VMs that also support other languages of the Smalltalk family. Meta-tracing, just-in-time compilation, stack-to-register mapping, and aggressive in-line message caching yield efficiency in executing Smalltalk code. Web Development With frameworks like Seaside and AIDA, Squeak can be a web server. It provides a layered set of abstractions over HTTP and HTML that let you build highly interactive web applications quickly, reusably, and maintainably. Multi-Platform Support + Squeak supports Windows, Linux (X86, X64 and ARM), and macOS and is preinstalled on C.H.I.P., Raspberry Pi, and OLPC XO.!! + ]style[(19 5 1 21 29 399 15 18 6 33 8 87 14 80 8 2 8 2 17 161 20 27 8 254 16 64 8 11 9 6 10 152 20 247 15 22 7 5 4 18 3 163 22 121)a0b,a0,a0b,Rhttp://www.squeak.org;,a0,,i,,Rcode://Object;,,Rcode://MessageSend;,,Rcode://HelpBrowser openOn: TerseGuideHelp;,,Rcode://Compiler;,,Rcode://Debugger;,,Rcode://Browser;,,i,,Rcode://Morph new openInHand;,,i,,Rcode://ToolSet browse: String selector: #findTokens:;,,Rcode://7/0;,,Rcode://MCWorkingCopyBrowser new show;,,i,,i,,Rhttp://www.seaside.st/;,,Rhttp://www.aidaweb.si/;,,Rcode://WebClient;,,i,!!' readStream nextChunkText) - Squeak supports Windows, Linux (X86, X64 and ARM), and OS X and is preinstalled on C.H.I.P., Raspberry Pi, and OLPC XO.!! - ]style[(19 5 1 21 29 399 15 18 6 33 8 87 14 80 8 2 8 2 17 161 20 27 8 254 16 64 8 11 9 6 10 152 20 247 15 22 7 5 4 18 3 163 22 120)a0b,a0,a0b,Rhttp://www.squeak.org;,a0,,i,,Rcode://Object;,,Rcode://MessageSend;,,Rcode://HelpBrowser openForCodeOn: TerseGuideHelp;,,Rcode://Compiler;,,Rcode://Debugger;,,Rcode://Browser;,,i,,Rcode://Morph new openInHand;,,i,,Rcode://ToolSet browse: String selector: #findTokens:;,,Rcode://7/0;,,Rcode://MCWorkingCopyBrowser new show;,,i,,i,,Rhttp://www.seaside.st/;,,Rhttp://www.aidaweb.si/;,,Rcode://WebClient;,,i,!!' readStream nextChunkText) key: #introduction; shouldStyle: false; yourself! Item was changed: ----- Method: SqueakProjectHelp class>>squeakUserInterface (in category 'pages') ----- squeakUserInterface "This method was automatically generated. Edit it using:" "SqueakProjectHelp edit: #squeakUserInterface" ^(HelpTopic title: 'Squeak User Interface' contents: 'The Squeak User Interface + The Squeak UI has some unusual elements that you may not have seen before. Here is a brief introduction to those elements. - The Squeak UI has some unusual elements that you may not have seen before. Here is a brief introduction to those elements. 1. Red button, Yellow Button; buttons on mice, trackpads and wheels - what do they do? + Smalltalk has been around a long time; since before most people had any idea that computers could have graphical screens or that devices such as mice existed. Smalltalk''s UI expects three button mice and to some extent still sticks with the ancient PARC tradition of naming them Red (left), Yellow (middle) and Blue (right). You''ll see these names in code referring to things like ''blueButtonActivity''. - Smalltalk has been around a long time; since before most people had any idea that computers could have graphical screens or that devices such as mice existed. Smalltalk''s UI expects three button mice and to some extent still sticks with the ancient PARC tradition of naming them Red (left), Yellow (middle) and Blue (right). You''ll see these names in code referring to things like ''blueButtonActivity''. + Of course, not many mice used these days actually have the buttons colored, and quite a few have different numbers of buttons and even scroller wheels or trackpad surfaces; all of which can make it confusing to explain what button needs to be used. Laptops tend to have trackpads with perhaps a button, or two, or perhaps require a ctl or alt or cmd key to be pressed at the same time as the trackpad. To try to help work around the potential for confusion, think of the actions as <Select>, <Menu> and <Halo>. - Of course, not many mice used these days actually have the buttons colored, and quite a few have different numbers of buttons and even scroller wheels or trackpad surfaces; all of which can make it confusing to explain what button needs to be used. Laptops tend to have trackpads with perhaps a button, or two, or perhaps require a ctl or alt or cmd key to be pressed at the same time as the trackpad. To try to help work around the potential for confusion, think of the actions as <Select>, <Menu> and <Halo>. a) <Select> is the fairly obvious ''select an item in a list'', or ''select a place in some text'', or press a screen button'' action. In many cases you can also hold down the button to drag the pointer to select a range of text, or double-click to perform some other action. b) <Menu> will normally open a pop-up menu that is specific to the location of the pointer. c) <Halo> normally displays the Morphic Halo (see below) that lets you perform many actions on the morph (a UI element) + In general on a Mac you can also hold the alt key down to get the <Menu> button action when simply pressing on a trackpad (or even one of the rare single-button mice) , or the cmd key for the Halo Button action. On a Windows laptop you can typically use the alt key for <Menu> and the ctl key for Halo. On the assorted unix systems out there you are on your own; the choice of window manager etc. can change anything. - In general on a Mac you can also hold the alt key down to get the <Menu> button action when simply pressing on a trackpad (or even one of the rare single-button mice) , or the cmd key for the Halo Button action. On a Windows laptop you can typically use the alt key for <Menu> and the ctl key for Halo. On the assorted unix systems out there you are on your own; the choice of window manager etc can change anything. In the Preference Browser you can ''swap mouse buttons'' to swap the <Menu> and <Halo> buttons if you prefer; this may feel more familiar for users of systems where a right button press opens menus. 2. Keyboard shortcuts + Squeak has a number of keyboard shortcuts available (which, like everything else are changeable by users) that can be found listed on the ''Command Key Mappings'' page. Some will seem very familiar and some will appear quite strange. Cmd-y, for example swaps the characters on the left and right of the text election; a surprisingly useful key for small tpyos ;-) - Squeak has a number of keyboard shortcuts available (which, like everything else are changeable by users) that can be found listed on the ''Command Key Mappings'' page. Some will seem very familiar and some will appear quite strange. Cmd-y, for example swaps the characters on the left and right of the text election; a surprisingly useful key for small tpyos. 3. The Dock + Across the top of the screen lies the Dock; a mix of menu bar, tool bar and search interface. At the extreme left is the Squeak logo, which if clicked will open a menu that gives easy access to updating Squeak, checking your system configuration, and saving and/or quitting. The other headings at the left of the screen provide menus giving access to assorted tools and other facilities; you will probably mostly use the Tools and Apps items. To the right end of the Dock is the search interface, a quick way to search for message names and classes. Type a message (or a partial message, or a class name and press <Return> to see what it finds. There is also a clock and lastly a button that will expand the Squeak window to fill the screen - if possible it will take over the entire screen. Click on it again to return to the previous window size. - Across the top of the screen lies the Dock; a mix of menu bar, tool bar and search interface. At the extreme left is the Squeak logo, which if clicked will open a menu that gives easy access to updating Squeak, checking your system configuration, and saving and/or quitting. The other headings at the left of the screen provide menus giving access to assorted tools and other facilities; you will probably mostly use the Tools and Apps items. To the right end of the Dock is the search interface, a quick way to search for message names and classes. Type a message (or a partial message, or a class name and press <Return> to see what it finds. There is also a clock and lastly a button that will expand the Squeak window to fill the screen - if possible it will take over the entire screen. Click on it again to return to the previous window size. 4. Menus Squeak uses several sorts of menu. a) the pull-down menus - like those that you see on the Dock. b) pop-up menus that appear where the pointer is located (sometimes shifted to fit on-screen) c) menus where some entries have an ellipsis (the ...) which tells you that clicking on the entry will open another menu d) hierarchical menus where entries with a right-pointing triangle icon automatically open another menu, usually to the right of the original menu. As above, this may be modified to fit the new menu on the screen. As with most GUIs these days clicking on a menu item will choose that action and clicking outside the menu will close the menu(s) and do nothing. 5. Projects + A project is an entire Squeak desktop full of windows and is akin to the desktop spaces used in some window systems. Projects can be used to change quickly from one task to another. An inactive project is represented by a project window, which shows a thumbnail of its state. Project windows are actually more like doors than windows, since you can enter the project just by clicking on them. Each project maintains its own set of windows and other information. - A project is an entire Squeak desktop full of windows and is akin to the desktop spaces used in some window systems. Projects can be used to change quickly from one task to another. An inactive project is represented by a project window, which shows a thumbnail of its state. Project windows are actually more like doors than windows, since you can enter the project just by clicking on them. Each project maintains its own set of windows and other information. + You can create a new project by choosing ''Create MVC Project'' or ''Create Morphic Project'' from the dock menu. The MVC projects use the older MVC type windows - the original windowing system. Note that not all tools work well - or at all - in MVC projects and you should generally use Morphic projects. The default project is a Morphic project. - You can create a new project by choosing ''Create MVC Project'' or ''Create Morphic Project'' from the dock menu. The MVC projects use the older MVC type windows - the original windowing system. Note that not all tools work well - or at all - in MVC projects and you should generllly use Morphic pjojects. The default project is a Morphic project. To exit a project (and return to its parent project), choose ''previous project'' from the screen menu. 6. Morphic Halos + In a orphic project, pressing the <Halo> Button (see above!!!!) on a graphical object (e.g. a window) will surround it with a constellation of colored circles. These are called "halo handles." Additional clicks will cycle through the halos for the other graphical objects in the nesting structure. If you hold down the Shift key while <Halo>-clicking, the nested morphs will be traversed from innermost outward. Clicking Select or Menu will dismiss the halo. While the halo is up, letting the cursor linger over one of the halo handles for a few seconds will cause a balloon to pop up with the name of that handle. Three useful handles are the top-left "X" handle (delete), the bottom-right yellow handle (resize), and the brown handle (slide the object within its containing object). Halos allow complex graphical objects to be explored - or even disassembled (using the black halo handle). Usually no harm results from taking apart an object; you can just discard the pieces and create a new on e. - In a morphic project, pressing the <Halo> Button (see above!!!!) on a graphical object (e.g. a window) will surround it with a constellation of colored circles. These are called "halo handles." Additional clicks will cycle through the halos for the other graphical objects in the nesting structure. If you hold down the Shift key while <Halo>-clicking, the nested morphs will be traversed from innermost outward. Clicking Select or Menu will dismiss the halo. While the halo is up, letting the cursor linger over one of the halo handles for a few seconds will cause a balloon to pop up with the name of that handle. Three useful handles are the top-left "X" handle (delete), the bottom-right yellow handle (resize), and the brown handle (slide the object within its containing object). Halos allow complex graphical objects to be explored - or even disassembled (using the black halo handle). Usually no harm results from taking apart an object; you can just discard the pieces and create a new one. 7. Flaps + The Flaps are a sort of sliding menu - a drawer - containing tools etc as one way to access them. To enable Flaps, red-click on the desktop background to show the world menu, choose the "Flaps..." menu and "show shared tabs". Tabs labeled "Squeak", "Tools", "Supplies", etc., will appear around the edges of the Squeak desktop. Click on any tab to open the corresponding flap. Drag a tab to resize the flap and to relocate the tab. Bring up the halo on any tab and click on its menu handle to be presented with many options relating to the flap. Use the "Flaps..." menu, reached via the desktop menu, to control which flaps are visible and for other flap-related options and assistance. - The Flaps are a sort of sliding menu - a drawer - containing tools etc as one way to access them. To enable Flaps, red-click on the desktop background to show the world menu, choose the "Flaps..." menu and "show shared tabs". Tabs labeled "Squeak", "Tools", "Supplies", etc., will appear around the edges of the Squeak desktop. Click on any tab to open the corresponding flap. Drag a tab to resize the flap and to relocate the tab. Bring up the halo on any tab and click on its menu handle to be presented with many options relating to the flap. Use the "Flaps..." menu, reached via the desktop menu, to control which flaps are visible and for other flap-related options and assistance. 8. Parts Bins + You can obtain new objects in many ways. The "Objects Catalog" (choose "objects'' from the world menu or open the objects flap) and several of the standard flaps (e.g. "Tools" and "Supplies") serve as "Parts Bins" the for new objects. Drag any icon you see in a Parts Bin and a fresh copy of the kind of object it represents will appear "in your hand"; click to deposit the new object anywhere you wish. You can also add your own objects to any of the flaps - just drag your object over the tab, wait for the flap to pop open, then drop the object at the desired position in the flap. - You can obtain new objects in many ways. The "Objects Catalog" (choose "objects'' from the world menu or open the objects flap) and several of the standard flaps (e.g. "Tools" and "Supplies") serve as "Parts Bins" the for new objects. Drag any icon you see in a Parts Bin and a fresh copy of the kind of object it represents will appear "in your hand"; click to deposit the new object anywhere you wish. You can also add your own objects to any of the flaps - just drag your object over the tab, wait for the flap to pop open, then drop the object at the desired position in the flap. !! + ]style[(25 126 88 283 1 14 1 17 1 1008 1 59 1 137 1 492 25 52 1 86 20 73 5 126 13 421 5 5 4 130 1 282 10 156 1 81 1 415 1 19 13 221 16 675 16 49 1 91 15 843 7 691 13 47 15 523)b,,i,,b,,b,,b,,b,,b,,b,,i,,b,,i,,i,,i,,i,,i,,b,,i,,b,,b,,b,,i,,Rcode://(ProjectViewMorph newProjectViewInAWindowFor: MorphicProject new) openInWorld;,,i,,b,,Rcode://SystemWindow topWindow addHalo;,,i,,i,,Rcode://Project current world activateObjectsTool;,!!' readStream nextChunkText) - ]style[(25 127 88 284 1 14 1 17 1 1011 1 59 1 137 1 493 25 52 1 86 20 73 5 123 13 422 5 5 4 132 1 283 10 156 1 81 1 415 1 19 13 223 16 679 16 50 1 91 15 851 7 696 13 48 15 525)b,,i,,b,,b,,b,,b,,b,,b,,i,,b,,i,,i,,i,,i,,i,,b,,i,,b,,b,,b,,i,,Rcode://(ProjectViewMorph newProjectViewInAWindowFor: MorphicProject new) openInWorld;,,i,,b,,Rcode://SystemWindow topWindow addHalo;,,i,,i,,Rcode://Project current world activateObjectsTool;,!!' readStream nextChunkText) key: #squeakUserInterface; shouldStyle: false; yourself! Item was changed: ----- Method: SqueakProjectHelp class>>workingWithSqueak (in category 'pages') ----- workingWithSqueak "This method was automatically generated. Edit it using:" "SqueakProjectHelp edit: #workingWithSqueak" ^(HelpTopic title: 'Working with Squeak' contents: 'Take few minutes and get familiar with the image concept of the Squeak/Smalltalk system. This includes starting and quitting the image, learning where all the objects live, and understanding where your source code resides. 1. Starting and Quitting + Like most Smalltalks, the machine-executable portion is a relatively small program known as the virtual machine (VM). The VM''s job is to provide services from the physical machine to the Smalltalk system; services like memory management; input from keyboards, mice, and networks; output to screens, files, and networks. The Smalltalk system, including all data and code, is a system of objects built from the ground up, and interpreted by this virtual computer. This affords a Smalltalk system platform portability. - Like most Smalltalks, the machine-executable portion is a relatively small program known as the "virtual machine" (VM). The VM''s job is to provide services from the physical machine to the Smalltalk system; services like memory management; input from keybords, mice, and networks; output to screens, files, and networks. The Smalltalk system, including all data and code, is a system of objects built from the ground up, and interpreted by this virtual computer. This affords a Smalltalk system platform portability. + Smalltalk cannot run without the VM. The VM can''t do anything useful except process Smalltalk systems. They belong together like Rebo and Zooty. - Smalltalk cannot run without the VM. The VM can''t do anything useful except process Smalltalk systems. They belong together like Rebo and Zooty. To start the system + - On most OS you can double-click on the ''*.image'' file and the OS file type handler will start the VM with that image file. + - On many OS, drag the ''*.image'' file to the VM executable application, typically named "Squeak" plus some version name such as "Squeak5.3". + - Where a command line terminal or shell is used, there are several command-line options for starting the system. Typically you can run ''squeak --help'' for some help. - - on most OS you can double-click on the ''.image'' file and the OS file type handler will start the VM with that image file. - - on many OS, drag the ".image" data file to the VM executable application, typically named "Squeak"+ some version name such as "Squeak5.3. - - where a command line terminal or shell is used, there are several command-line options for starting the system. typically you can run `squeak --help` for some help. By default, the system will open on the screen in a single OS hosted window, though there are options for headless usage. + To quit a Squeak session + - Choose ''quit'' from the Squeak-logo menu at the left of the menu bar (the Dock) at the top of the window. That will close the session and you will lose any work you did. + - If you ''save'', the image file will be overwritten and resume from that place the next time it''s launched. + - In general you should not over-write the delivered image file but instead use the ''save as'' option to create your own work copy. - To quit a Squeak session, choose ''quit'' from the Squeak-logo menu at the left of the menu bar (the Dock) at the top of the window. That will close the session and you will lose any work you did. - If you ''save'', the image file will be overwritten and resume from that place the next time it''s launched. - In general you should not over-write the delivered image file but instead use the ''save as'' option to create your own work copy. 2. The Image File Squeak is an environment built in its own objects from the ground up, including one or more end-user applications. All of the objects in the system -- Classes, Dictionaries, Windows, Customers and other objects that make up the Squeak environment are stored in a binary ".image" file. This is the "object-data file" loaded by the VM when Squeak is launched. When an image is started, every object resumes exactly from where it was last saved. 3. The Sources File + Smalltalk is traditionally includes the source code in the running system. However, keeping multiple copies of the same source code in all images files is wasteful. Therefore, the source code itself is kept in a read-only .sources file and accessed by all images. The image files merely have pointers into this file, which is read on-the-fly to present original source code. - Smalltalk is traditionally includes the source code in the running system. However, keeping multiple copies of the same source code in all images files is wasteful. Therefore, the source code itself is kept in a read-only .sources file and accessed by all images. The image files merely have pointers into this file, which is read on-the-fly to present original source code. + The code of the base system is stored in the file "SqueakV50.sources". This file does not change except between releases of Squeak. Normally this file should be placed in the folder containing the VM executable. - The code of the base system is stored in the file "SqueakV50.sources". This file does not change except between releases of Squeak. Normally this file should be placed in the folder containing the VM executable. 4. The Changes File The purpose of Squeak is to develop new programs and systems. Code changes to the running system are effective immediately. But since multiple images can be running, they could not all update the .sources file safely. Therefore, each image file is accompanied by a ".changes" file which contains source code changes for that and only that Smalltalk system.. The changes file is important for project work. It keeps a sequential log of development activity for the purpose of recovering work performed since the last image-save. Any of several events could lead to the need to recover work, including a power-outage or making an erroneous change to code required to keep the system running. The changes file does not consume memory space, so Squeak is able to keep a complete history of all program changes. This makes it easy to examine or even reinstate older versions of methods (see ''versions'' option in browser selector pane). This encourages experimentation, since you can easily revert to the original versions of any set of methods. In extreme cases where sources and/or changes files are not available, the system can still run, and will automatically decompile the bytecode methods in image memory, if necessary, into readable and editable versions of the original source code (only comments and temporary variable names are lost). 5. Transferring Code-Snippets Between Images In addition to the ''save'' command that saves the entire state of the system, the code of individual methods, categories or classes may be ''filed out'' and then filed-in to another image. 6. Packages + The code of an entire project is encapsulated in a Package. This allows users to share their code with other users. Code of packages are delineated by the categories of their classes, and methods. The Monticello browser is then used to wrap that code into a Package object which can be saved to a Monticello repository. Visit the Squeak Swiki for more info - http://wiki.squeak.org/squeak/1287 - The code of an entire project is encapsulated in a Package. This allows users to share their code with other users. Code of packages are delineated by the categories of their classes, and methods. The Monticello browser is then used to wrap that code into a Package object which can be saved to a Monticello repository. Visit the Squeak swiki for more info - http://wiki.squeak.org/squeak/1287 + Some projects end up using the resources provided by several packages, resulting in a hierarchy of packages that make up a system. The ''Installer'' class can be used to install such systems.!! + ]style[(224 24 98 15 611 18 90 18 236 19 173 6 165 6 178 9 39 17 449 19 591 19 1354 44 189 11 364 34 192),b,,i,,i,,i,,i,,b,,b,,b,,b,,b,,b,,b,,b,,Rhttp://wiki.squeak.org/squeak/…;,!!' readStream nextChunkText) - Some projects end up using the resources provided by several packages, resulting in a hierarchy of packages that make up a system. The ''Installer'' class can be used to install such systems.!!' readStream nextChunkText) key: #workingWithSqueak; shouldStyle: false; yourself!

1 0

The Trunk: Collections-ul.877.mcz
by commits＠source.squeak.org 28 Feb '20

28 Feb '20

Marcel Taeumel uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-ul.877.mcz ==================== Summary ==================== Name: Collections-ul.877 Author: ul Time: 27 February 2020, 2:00:22.678898 pm UUID: df2c680a-81dd-49bf-a1c2-a0fec288ce0f Ancestors: Collections-mt.876 - recalculate tally in WeakIdentityDictionary >> #noCheckNoGrowFillFrom: to prevent it becoming greater than the maximum number of elements the dictionary can hold =============== Diff against Collections-mt.876 =============== Item was changed: ----- Method: WeakIdentityDictionary>>noCheckNoGrowFillFrom: (in category 'private') ----- noCheckNoGrowFillFrom: anArray "Add the elements of anArray except nils to me assuming that I don't contain any of them, they are unique and I have more free space than they require." + tally := 0. 1 to: anArray size do: [ :index | (anArray at: index) ifNotNil: [ :association | + association == vacuum ifFalse: [ + array - association == vacuum - ifFalse: [array at: (self scanForEmptySlotFor: association key) + put: association. + tally := tally + 1 ] ] ]! - put: association ] ] ]!

1 0

[bug] Squeak5.3rc2. Clicking on World's "paint background" Halo stalls the Smalltalk
by Vaidotas Didžbalis 28 Feb '20

28 Feb '20

Clicking on World's "paint background" Halo stalls the Smalltalk. Squeak5.3rc2 latest update: #19422 Image format 6521 (32 bit) Virtual Machine --------------- Open Smalltalk Cog[Spur] VM [CoInterpreterPrimitives VMMaker.oscog-eem.2597] Unix built on Jan 6 2020 16:11:12 Compiler: 5.4.0 20160609 platform sources revision VM: 201912311458 regards, Vaidotas

2 2

← Newer
1
...
4
5
6
7
8
9
10
...
31
Older →

Jump to page: