Squeak-dev December 2023

squeak-dev@lists.squeakfoundation.org

26 participants
124 discussions

The Inbox: Kernel-ct.1538.mcz
by commits＠source.squeak.org 07 Dec '23

07 Dec '23

Christoph Thiede uploaded a new version of Kernel to project The Inbox: http://source.squeak.org/inbox/Kernel-ct.1538.mcz ==================== Summary ==================== Name: Kernel-ct.1538 Author: ct Time: 5 December 2023, 8:41:07.361911 pm UUID: d08b63ac-7ec2-304f-bbb9-cb939ebe37fb Ancestors: Kernel-dtl.1537 Makes MessageSend and WeakMessageSend fully polymorphous. =============== Diff against Kernel-dtl.1537 =============== Item was added: + ----- Method: MessageSend>>asMessageSend (in category 'converting') ----- + asMessageSend + ^MessageSend receiver: self receiver selector: selector arguments: (Array withAll: self arguments) + ! Item was added: + ----- Method: WeakMessageSend>>asMessage (in category 'converting') ----- + asMessage + ^ Message selector: selector arguments: arguments.! Item was added: + ----- Method: WeakMessageSend>>cull: (in category 'evaluating') ----- + cull: firstArg + "Send the message with these optional arguments and answer the return value" + + selector numArgs >= 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg + "Send the message with these optional arguments and answer the return value" + + | numArgs | + (numArgs := selector numArgs) >= 2 ifTrue: [ ^self value: firstArg value: secondArg ]. + numArgs = 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg cull: thirdArg + "Send the message with these optional arguments and answer the return value" + + | numArgs | + (numArgs := selector numArgs) >= 2 ifTrue: [ + numArgs >= 3 ifTrue: [ ^self value: firstArg value: secondArg value: thirdArg ]. + ^self value: firstArg value: secondArg ]. + numArgs = 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull:cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg cull: thirdArg cull: fourthArg + "Send the message with these optional arguments and answer the return value" + + | numArgs | + (numArgs := selector numArgs) >= 3 ifTrue: [ + numArgs >= 4 ifTrue: [ + ^self value: firstArg value: secondArg value: thirdArg value: fourthArg ]. + ^self value: firstArg value: secondArg value: thirdArg ]. + numArgs = 2 ifTrue: [ ^self value: firstArg value: secondArg ]. + numArgs = 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull:cull:cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg cull: thirdArg cull: fourthArg cull: fifthArg + "Send the message with these optional arguments and answer the return value" + + ^ selector numArgs caseOf: { + [5] -> [self value: firstArg value: secondArg value: thirdArg value: fourthArg value: fifthArg]. + [4] -> [self value: firstArg value: secondArg value: thirdArg value: fourthArg]. + [3] -> [self value: firstArg value: secondArg value: thirdArg]. + [2] -> [self value: firstArg value: secondArg]. + [1] -> [self value: firstArg]. + [0] -> [self value] }! Item was added: + ----- Method: WeakMessageSend>>numArgs (in category 'accessing') ----- + numArgs + ^ selector numArgs! Item was added: + ----- Method: WeakMessageSend>>value: (in category 'evaluating') ----- + value: firstArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg}! Item was added: + ----- Method: WeakMessageSend>>value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg}! Item was added: + ----- Method: WeakMessageSend>>value:value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg value: thirdArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg. thirdArg}! Item was added: + ----- Method: WeakMessageSend>>value:value:value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg value: thirdArg value: fourthArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg. thirdArg. fourthArg}! Item was added: + ----- Method: WeakMessageSend>>value:value:value:value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg value: thirdArg value: fourthArg value: fifthArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg. thirdArg. fourthArg. fifthArg}! Item was added: + ----- Method: WeakMessageSend>>valueWithPossibleArgs: (in category 'evaluating') ----- + valueWithPossibleArgs: anArray + "Send selector to the receiver with arguments in anArray. Only use enough arguments for the arity of the selector; supply nils for missing ones." + + ^self + withEnsuredReceiverDo: [ :r | + r + perform: selector + withEnoughArguments: anArray ] + otherwise: [ ]!

3 7

The Trunk: Kernel-ct.1538.mcz
by commits＠source.squeak.org 07 Dec '23

07 Dec '23

Marcel Taeumel uploaded a new version of Kernel to project The Trunk: http://source.squeak.org/trunk/Kernel-ct.1538.mcz ==================== Summary ==================== Name: Kernel-ct.1538 Author: ct Time: 5 December 2023, 8:41:07.361911 pm UUID: d08b63ac-7ec2-304f-bbb9-cb939ebe37fb Ancestors: Kernel-dtl.1537 Makes MessageSend and WeakMessageSend fully polymorphous. =============== Diff against Kernel-dtl.1537 =============== Item was added: + ----- Method: MessageSend>>asMessageSend (in category 'converting') ----- + asMessageSend + ^MessageSend receiver: self receiver selector: selector arguments: (Array withAll: self arguments) + ! Item was added: + ----- Method: WeakMessageSend>>asMessage (in category 'converting') ----- + asMessage + ^ Message selector: selector arguments: arguments.! Item was added: + ----- Method: WeakMessageSend>>cull: (in category 'evaluating') ----- + cull: firstArg + "Send the message with these optional arguments and answer the return value" + + selector numArgs >= 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg + "Send the message with these optional arguments and answer the return value" + + | numArgs | + (numArgs := selector numArgs) >= 2 ifTrue: [ ^self value: firstArg value: secondArg ]. + numArgs = 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg cull: thirdArg + "Send the message with these optional arguments and answer the return value" + + | numArgs | + (numArgs := selector numArgs) >= 2 ifTrue: [ + numArgs >= 3 ifTrue: [ ^self value: firstArg value: secondArg value: thirdArg ]. + ^self value: firstArg value: secondArg ]. + numArgs = 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull:cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg cull: thirdArg cull: fourthArg + "Send the message with these optional arguments and answer the return value" + + | numArgs | + (numArgs := selector numArgs) >= 3 ifTrue: [ + numArgs >= 4 ifTrue: [ + ^self value: firstArg value: secondArg value: thirdArg value: fourthArg ]. + ^self value: firstArg value: secondArg value: thirdArg ]. + numArgs = 2 ifTrue: [ ^self value: firstArg value: secondArg ]. + numArgs = 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull:cull:cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg cull: thirdArg cull: fourthArg cull: fifthArg + "Send the message with these optional arguments and answer the return value" + + ^ selector numArgs caseOf: { + [5] -> [self value: firstArg value: secondArg value: thirdArg value: fourthArg value: fifthArg]. + [4] -> [self value: firstArg value: secondArg value: thirdArg value: fourthArg]. + [3] -> [self value: firstArg value: secondArg value: thirdArg]. + [2] -> [self value: firstArg value: secondArg]. + [1] -> [self value: firstArg]. + [0] -> [self value] }! Item was added: + ----- Method: WeakMessageSend>>numArgs (in category 'accessing') ----- + numArgs + ^ selector numArgs! Item was added: + ----- Method: WeakMessageSend>>value: (in category 'evaluating') ----- + value: firstArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg}! Item was added: + ----- Method: WeakMessageSend>>value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg}! Item was added: + ----- Method: WeakMessageSend>>value:value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg value: thirdArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg. thirdArg}! Item was added: + ----- Method: WeakMessageSend>>value:value:value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg value: thirdArg value: fourthArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg. thirdArg. fourthArg}! Item was added: + ----- Method: WeakMessageSend>>value:value:value:value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg value: thirdArg value: fourthArg value: fifthArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg. thirdArg. fourthArg. fifthArg}! Item was added: + ----- Method: WeakMessageSend>>valueWithPossibleArgs: (in category 'evaluating') ----- + valueWithPossibleArgs: anArray + "Send selector to the receiver with arguments in anArray. Only use enough arguments for the arity of the selector; supply nils for missing ones." + + ^self + withEnsuredReceiverDo: [ :r | + r + perform: selector + withEnoughArguments: anArray ] + otherwise: [ ]!

1 0

The Trunk: Kernel-mt.1539.mcz
by commits＠source.squeak.org 07 Dec '23

07 Dec '23

Marcel Taeumel uploaded a new version of Kernel to project The Trunk: http://source.squeak.org/trunk/Kernel-mt.1539.mcz ==================== Summary ==================== Name: Kernel-mt.1539 Author: mt Time: 7 December 2023, 12:40:17.241684 pm UUID: cbf2bf83-08df-3940-b367-09dec0f14945 Ancestors: Kernel-ct.1538 Refines Kernel-ct.1538 with some commentary and an extra: - Message >> #arguments: - MessageSend >> #sendTo: - WeakMessageSend >> #sendTo: For WeakMessageSend, guard #asMessageSend conversion with a warning if arguments or recevier got already collected. For WeakMessageSend, guard #asMessage conversion with a warning if arguments got already collected. =============== Diff against Kernel-dtl.1537 =============== Item was added: + ----- Method: Message>>arguments: (in category 'accessing') ----- + arguments: anArray + + args := anArray.! Item was changed: ----- Method: MessageSend>>asMessage (in category 'converting') ----- asMessage + "Convert the receiver into a message, which has its 'receiver' variable dropped. Note that messages are rather low-level objects and primarily used for #doesNotUnderstand: as they have a #lookupClass: as a special feature. The difference between #sendTo: and #sentTo: can be confusing. Therefore, be aware that you can always use message-sends with a temporary 'nil' receiver." + + ^ Message selector: selector arguments: arguments! - ^ Message selector: selector arguments: arguments.! Item was added: + ----- Method: MessageSend>>asMessageSend (in category 'converting') ----- + asMessageSend + + ^ self + ! Item was added: + ----- Method: MessageSend>>asWeakMessageSend (in category 'converting') ----- + asWeakMessageSend + "Convert the receiver into a similar representation, but which only references weakly to its receiver and arguments." + + ^ WeakMessageSend + receiver: self receiver + selector: self selector + arguments: (Array withAll: self arguments) + ! Item was added: + ----- Method: MessageSend>>sendTo: (in category 'sending') ----- + sendTo: anotherReceiver + "Compatibility with Message protocol. Evaluate the receiver (i.e., message send) with anotherReceiver instead of the current 'receiver' instVar." + + | originalReceiver | + originalReceiver := self receiver. + ^ [self receiver: anotherReceiver. self value] + ensure: [self receiver: originalReceiver]! Item was changed: ----- Method: MessageSend>>valueOtherwise: (in category 'evaluating') ----- valueOtherwise: aBlock + "Compatibility with WeakMessageSend. Send the message and answer the return value" - "Send the message and answer the return value" ^self value! Item was changed: ----- Method: MessageSend>>valueWithArguments:otherwise: (in category 'evaluating') ----- valueWithArguments: anArray otherwise: aBlock + "Compatibility with WeakMessageSend." ^ self valueWithArguments: anArray! Item was changed: ----- Method: WeakMessageSend class>>new (in category 'instance creation') ----- new + "Overwritten to use the first (weak) slot for the receiver. Arguments are managed dynamically with an extra weak array." + + ^ self new: 1 - ^self new: 1 ! Item was added: + ----- Method: WeakMessageSend>>asMessage (in category 'converting') ----- + asMessage + "Convert the receiver into a message, which has its 'receiver' variable dropped. Note that messages are rather low-level objects and primarily used for #doesNotUnderstand: as they have a #lookupClass: as a special feature. The difference between #sendTo: and #sentTo: can be confusing. Therefore, be aware that you can always use message-sends with a temporary 'nil' receiver." + + self isAnyArgumentGarbage ifTrue: [self notify: 'Should not convert. Some arguments got collected. Proceed with caution.' translated]. + ^ Message selector: selector arguments: arguments! Item was changed: ----- Method: WeakMessageSend>>asMessageSend (in category 'converting') ----- asMessageSend + "Convert the receiver into a similar representation, but which references strongly to its receiver and arguments. Raise a warning if objects got already garbage-collected. Use #on:do: if you automatically want to ignore this warning." + + self isReceiverOrAnyArgumentGarbage ifTrue: [self notify: 'Should not convert. Receiver or some arguments got collected. Proceed with caution.' translated]. ^MessageSend receiver: self receiver selector: selector arguments: (Array withAll: self arguments) ! Item was added: + ----- Method: WeakMessageSend>>asWeakMessageSend (in category 'converting') ----- + asWeakMessageSend + + ^ self! Item was added: + ----- Method: WeakMessageSend>>cull: (in category 'evaluating') ----- + cull: firstArg + "Send the message with these optional arguments and answer the return value" + + selector numArgs >= 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg + "Send the message with these optional arguments and answer the return value" + + | numArgs | + (numArgs := selector numArgs) >= 2 ifTrue: [ ^self value: firstArg value: secondArg ]. + numArgs = 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg cull: thirdArg + "Send the message with these optional arguments and answer the return value" + + | numArgs | + (numArgs := selector numArgs) >= 2 ifTrue: [ + numArgs >= 3 ifTrue: [ ^self value: firstArg value: secondArg value: thirdArg ]. + ^self value: firstArg value: secondArg ]. + numArgs = 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull:cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg cull: thirdArg cull: fourthArg + "Send the message with these optional arguments and answer the return value" + + | numArgs | + (numArgs := selector numArgs) >= 3 ifTrue: [ + numArgs >= 4 ifTrue: [ + ^self value: firstArg value: secondArg value: thirdArg value: fourthArg ]. + ^self value: firstArg value: secondArg value: thirdArg ]. + numArgs = 2 ifTrue: [ ^self value: firstArg value: secondArg ]. + numArgs = 1 ifTrue: [ ^self value: firstArg ]. + ^self value! Item was added: + ----- Method: WeakMessageSend>>cull:cull:cull:cull:cull: (in category 'evaluating') ----- + cull: firstArg cull: secondArg cull: thirdArg cull: fourthArg cull: fifthArg + "Send the message with these optional arguments and answer the return value" + + ^ selector numArgs caseOf: { + [5] -> [self value: firstArg value: secondArg value: thirdArg value: fourthArg value: fifthArg]. + [4] -> [self value: firstArg value: secondArg value: thirdArg value: fourthArg]. + [3] -> [self value: firstArg value: secondArg value: thirdArg]. + [2] -> [self value: firstArg value: secondArg]. + [1] -> [self value: firstArg]. + [0] -> [self value] }! Item was added: + ----- Method: WeakMessageSend>>numArgs (in category 'accessing') ----- + numArgs + ^ selector numArgs! Item was added: + ----- Method: WeakMessageSend>>sendTo: (in category 'sending') ----- + sendTo: anotherReceiver + "Compatibility with Message protocol. Evaluate the receiver (i.e., weak message send) with anotherReceiver instead of the current 'receiver' instVar." + + | originalReceiver | + originalReceiver := self receiver. + ^ [self receiver: anotherReceiver. self value] + ensure: [self receiver: originalReceiver]! Item was added: + ----- Method: WeakMessageSend>>value: (in category 'evaluating') ----- + value: firstArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg}! Item was added: + ----- Method: WeakMessageSend>>value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg}! Item was added: + ----- Method: WeakMessageSend>>value:value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg value: thirdArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg. thirdArg}! Item was added: + ----- Method: WeakMessageSend>>value:value:value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg value: thirdArg value: fourthArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg. thirdArg. fourthArg}! Item was added: + ----- Method: WeakMessageSend>>value:value:value:value:value: (in category 'evaluating') ----- + value: firstArg value: secondArg value: thirdArg value: fourthArg value: fifthArg + "Send the message with these arguments and answer the return value" + + ^ self valueWithArguments: {firstArg. secondArg. thirdArg. fourthArg. fifthArg}! Item was added: + ----- Method: WeakMessageSend>>valueWithPossibleArgs: (in category 'evaluating') ----- + valueWithPossibleArgs: anArray + "Send selector to the receiver with arguments in anArray. Only use enough arguments for the arity of the selector; supply nils for missing ones." + + ^self + withEnsuredReceiverDo: [ :r | + r + perform: selector + withEnoughArguments: anArray ] + otherwise: [ ]!

1 0

The Trunk: Collections-ct.1022.mcz
by commits＠source.squeak.org 07 Dec '23

07 Dec '23

Marcel Taeumel uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-ct.1022.mcz ==================== Summary ==================== Name: Collections-ct.1022 Author: ct Time: 21 October 2022, 2:24:04.563911 pm UUID: 6c7815e3-3bf9-be4b-a8cb-ae2373cb6658 Ancestors: Collections-nice.1021 Proposal: Adds PositionableStream>>#peek:. The implementation is taken from Damien Cassou (dc). [1] [1] https://github.com/hpi-swa/Squot/blob/4bf8e3b685ef9cbc195b7eca77d53a482833b… =============== Diff against Collections-nice.1021 =============== Item was added: + ----- Method: PositionableStream>>peek: (in category 'accessing') ----- + peek: anInteger + "Answer what would be returned if the message next: anInteger were sent to the receiver. If the receiver has less than anInteger more elements, only answer so many elements as available." + + | oldPosition result | + oldPosition := position. + result := self next: anInteger. + position := oldPosition. + ^ result!

1 0

The Trunk: System-codefrau.1437.mcz
by commits＠source.squeak.org 07 Dec '23

07 Dec '23

Vanessa Freudenberg uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-codefrau.1437.mcz ==================== Summary ==================== Name: System-codefrau.1437 Author: codefrau Time: 6 December 2023, 5:36:49.489134 pm UUID: e437daf4-9ac8-4645-85b0-e285113f09ab Ancestors: System-mt.1436 Reset WordSize on snapshot, for VMs capable of converting the image between 64 and 32 bits (like SqueakJS). =============== Diff against System-mt.1436 =============== Item was changed: ----- Method: SmalltalkImage>>cleanUpSystemAttributeCaches (in category 'housekeeping') ----- cleanUpSystemAttributeCaches "Reset platform-specific values. This MUST BE called directly before the image is snapshotted. Note that this can't safely be done on start-up because Smalltalk is too late in the start-up sequence. See commentary in #getSystemAttribute:." self flag: #discuss. "mt: Such caches might better be managed by the VM itself. A primitive-based cache protocol could help. On a fresh (VM) start-up, those values would then be nil (or uninitialized) automatically." + EndianCache := WordSize := PlatformNameCache := nil.! - EndianCache := PlatformNameCache := nil.!

1 0

Squeak Robotics
by Jon Hylands 06 Dec '23

06 Dec '23

Hi everyone, I've been working on a 4-legged walking robot for quite a few years, but in the last couple months I have been porting the code to Squeak. [image: Roz-Standing.jpg] The robot is controlled by a Raspberry pi zero 2 w, running a headless squeak 6.0 image. I start up a base Squeak image on the pi, and load in the latest version of a Monticello package from a folder on the pi that is rsync'd from my linux desktop. It does real time inverse kinematics and gait stepping, and the servos are all controlled directly from Squeak (they are serial bus servos) over a USB virtual serial port. All of the other sensors in use are also available over the same serial bus. Here's a short video showing its first "walk" using Squeak: https://www.youtube.com/watch?v=QngE8yyWzk8 This is a longer video that shows some of the hardware and software details of the robot: https://www.youtube.com/watch?v=A0TRIFQKuSM - Jon

4 4

Problem with PipeableOSProcess
by Javier Diaz-Reinoso 06 Dec '23

06 Dec '23

I am updating a program from 4.5 to 6.0, the program read some text and then speak it, in 4.5 using the macOS AppleScript package but that package was based in 32 bit Carbon so do not work in 64 bit VM or after Mojave, it seems that in python are a beta of a package which can be ported to squeak but for the meantime I am using PipeableOSProcess to call the unix program osascript and that works. The problem occurs because some text are large or not interesting so the program can interrupt the speak with a key for implement that I use a "terminate" in the processProxy and that also work, but now in the Process Browser appear an AioEventHandler>>handleExceptions:readEvents:writeEvents: process and after more interruptions a debuger in ExternalPipe(Object)>>error: with a message of 'cannot create OS pipe' appears. So I need to know the correct way to kill the unix process or perhaps PipeableOSProcess is not the way. TIA

2 2

The Trunk: Collections-mt.1058.mcz
by commits＠source.squeak.org 06 Dec '23

06 Dec '23

Marcel Taeumel uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-mt.1058.mcz ==================== Summary ==================== Name: Collections-mt.1058 Author: mt Time: 6 December 2023, 1:18:51.582488 pm UUID: 3c908f5b-b914-0e41-9363-6864544802c6 Ancestors: Collections-mt.1057 Complements Morphic-mt.2147. Removes (never ever used?) #stringhash. =============== Diff against Collections-mt.1057 =============== Item was added: + ----- Method: RunArray>>intervalsAndValuesDo: (in category 'enumerating') ----- + intervalsAndValuesDo: aBlock + "Enumerate the receiver with an absolute representation for each run, which makes it useful for other scenarios compared to #runsAndValuesDo:." + + | index | + index := 0. + self runsAndValuesDo: [:run :value | + aBlock + value: (index + 1 to: (index := index + run)) + value: value].! Item was removed: - ----- Method: String>>stringhash (in category 'private') ----- - stringhash - - ^ self hash. - !

1 0

The Inbox: Help-Squeak-Project-ct.100.mcz
by commits＠source.squeak.org 06 Dec '23

06 Dec '23

Christoph Thiede uploaded a new version of Help-Squeak-Project to project The Inbox: http://source.squeak.org/inbox/Help-Squeak-Project-ct.100.mcz ==================== Summary ==================== Name: Help-Squeak-Project-ct.100 Author: ct Time: 5 December 2023, 11:00:06.139337 pm UUID: e5d36ed2-bc14-8249-8d27-c3241476d8e7 Ancestors: Help-Squeak-Project-ct.99 Minor revisions to the first five pages of Squeak Help: * spell-check everything, fix plenks, typogaphic slips, and use Oxford comma consistently * fix formatting slips caused by blinkParen * rename Dock -> docking bar * add "become" link to implementors of become primitive * change "web" link from WebClient to WebServer * mention preferences for internalizing changes and sources * spread some emphasis * other very minor changes =============== Diff against Help-Squeak-Project-ct.99 =============== Item was changed: ----- Method: SqueakHelp class>>introduction (in category 'pages') ----- introduction "This method was automatically generated. Edit it using:" "SqueakHelp edit: #introduction" <generated> ^(HelpTopic title: 'Welcome' contents: 'Welcome to Squeak + Visit https://www.squeak.org for the latest information. - Visit https://www.squeak.org for the lastest information. + Squeak is a modern, open-source Smalltalk programming system with fast execution environments 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. They cover a wide range of domains such as education, multimedia, gaming, research, and commerce. Squeak is fast, flexible, and free. - Squeak is a modern, open-source Smalltalk programming system with fast execution environments 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. They cover 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 + The standard VM for Squeak, Cog Spur, has the most advanced object representation yet devised for Smalltalk. Spur has direct pointers, a compact object header, and efficiently implements become (Smalltalk''s object mutation primitive) via lazy forwarding. Spur provides pinning, and a segmented heap, releasing memory back to the OS after global garbage collection. Cog Spur''s JIT combines context-to-stack mapping, aggressive in-line message caching, a register-based calling convention, and Spur''s object representation to provide the fastest production Smalltalk VM. Cog Spur is developed in Smalltalk, in a uniquely productive VM development environment. There are other important Squeak VMs. Examples include SqueakJS, which runs in web browsers, and research VMs such as TruffleSqueak (based on GraalVM and a method JIT using partial evaluation) and RSqueak/VM (based on PyPy''s meta-tracing JIT). - The standard VM for Squeak, Cog Spur, has the most advanced object representation yet devised for Smalltalk. Spur has direct pointers, a compact object header, and efficiently implements become (Smalltalk''s object mutation primitive) via lazy forwarding. Spur provides pinning, and a segmented heap, releasing memory back to the OS after global garbage collection. Cog Spur''s JIT combines context-to-stack mapping, aggressive in-line message caching, a register based calling convention, and Spur''s object representation to provide the fastest production Smalltalk VM. Cog Spur is developed in Smalltalk, in a uniquely productive VM development environment. There are other important Squeak VMs. Examples include SqueakJS, which runs in web browsers, and research VMs such as TruffleSqueak (based on GraalVM and a method JIT using partial evaluation) and RSqueak/VM (based on PyPy''s meta-tracing JIT). 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 22 28 439 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 29 8 151 6 196 24 13 23 43 28 111 26 28 10 19 8 55 13 11 7 48 10 11 6 21 15 22 7 5 4 18 3 163 22 122)a0b,a0,a0b,Rhttps://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,,Rhttps://github.com/OpenSmalltalk/opensmalltalk-vm#readme;,,Rcode… + self systemNavigation browseAllImplementorsOfList: #(become: becomeForward: becomeForward:copyHash:) title: ''become implementors'';,,Rhttp://lists.squeakfoundation.org/pipermail/squeak-dev/2021-January/213418.html;,,Rhttp://www.mirandabanda.org/cogblog/2011/03/01/build-me-a-jit-as-fast-as-you-can/;,,Rhttp://www.mirandabanda.org/cogblog/2013/09/05/a-spur-gear-for-cog/;,,Rhttps://www.researchgate.net/publication/328509577_Two_Decades_of_Smalltalk_VM_Development_Live_VM_Development_through_Simulation_Tools;,,Rhttps://squeak.org/development/#virtual-machines;,,Rhttps://squeak.js.org;,,Rhttps://github.com/hpi-swa/trufflesqueak/;,,Rhttps://www.graalvm.org/;,,Rhttps://github.com/hpi-swa/RSqueak/;,,Rhttps://www.pypy.org/;,,i,,Rhttp://www.seaside.st/;,,Rhttp://www.aidaweb.si/;,,Rcode://WebServer;,,i,!!' readStream nextChunkText) - 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 22 29 438 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 29 8 353 24 13 23 43 28 111 26 28 10 19 8 56 13 11 7 48 10 11 6 21 15 22 7 5 4 18 3 163 22 121)a0b,a0,a0b,Rhttps://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,,Rhttps://github.com/OpenSmalltalk/opensmalltalk-vm#readme;,,Rhttp… /#virtual-machines;,,Rhttps://squeak.js.org;,,Rhttps://github.com/hpi-swa/trufflesqueak/;,,Rhttps://www.graalvm.org/;,,Rhttps://github.com/hpi-swa/RSqueak/;,,Rhttps://www.pypy.org/;,,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>>extendingTheSystem (in category 'pages') ----- extendingTheSystem "This method was automatically generated. Edit it using:" "SqueakProjectHelp edit: #extendingTheSystem" <generated> ^(HelpTopic title: 'Extending The System' contents: 'SqueakMap is an integrated catalog of external applications for Squeak. It is accessible from the "Apps" menu. This catalog does not host the projects, it merely documents the load scripts required to correctly bring them into the image. Many SqueakMap packages use Installer, which defines several packages in its package-definitions protocol. Any of these can be loaded with an expression like the following: Installer new merge: #graphQlEngine Change #graphQlEngine to the selector name of the package you want to load. The latest version of that package and all of its prerequisites will be merged into the image. Merging a package is no different from loading it unless the package is already loaded, in which case it is upgraded to the latest version in a way that preserves any local changes you may already have made. Other packages can be loaded through Metacello. If you come across a project providing either a MetacelloConfiguration or MetacelloBaseline, you can install or update Metacello through Metacello new. "or" Installer ensureRecentMetacello. Here are some examples for installing packages via Metacello: Metacello new configuration: ''OCompletion''; load. Metacello new configuration: ''FFI''; load. Metacello new configuration: ''RefactoringTools''; load. --------------- The source code for the Squeak, Cuis, and Pharo virtual machines (VM) is generated from a package called ''VMMaker''. MCHttpRepository location: ''https://source.squeak.org/VMMaker'' user: '''' password: '''' The source code for the VM is written in a subset of Smalltalk called ''Slang''. It is translated to C. The VMMaker.oscog fork generates the recent VM included in this release. + The generated VM code and the platform support code are at: https://opensmalltalk.org/ + See the README file there.!! + ]style[(9 309 19 266 6 126 8 130 9 879 27 27)Rcode://SMLoaderPlus open;,,Rcode://ToolSet browseClass: Installer category: ''package-definitions'';,,i,,u,,Rhttps://github.com/metacello/metacello;,,Rhttps://opensmalltalk.org/ ;,!!' readStream nextChunkText) - The generated VM code and the platform support code is at: https://opensmalltalk.org/ - See README file there.!! - ]style[(9 309 19 266 6 126 8 130 9 878 27 23)Rcode://SMLoaderPlus open;,,Rcode://ToolSet browseClass: Installer category: ''package-definitions'';,,i,,u,,Rhttps://github.com/metacello/metacello;,,Rhttps://opensmalltalk.org/ ;,!!' readStream nextChunkText) key: #extendingTheSystem; shouldStyle: false; yourself! Item was changed: ----- Method: SqueakProjectHelp class>>squeakResourcesOnline (in category 'pages') ----- squeakResourcesOnline "This method was automatically generated. Edit it using:" "SqueakProjectHelp edit: #squeakResourcesOnline" <generated> ^(HelpTopic title: 'Squeak Resources Online' contents: 'Web sites Main site of Squeak https://www.squeak.org Issue Tracker for bug reports and other feedback https://bugs.squeak.org Weekly Squeak https://news.squeak.org Downloads for many versions https://www.squeak.org/downloads Main site of OpenSmalltalk VM https://github.com/OpenSmalltalk/opensmalltalk-vm Mailing lists beginners This is the place to ask even the most basic questions. Don''t be afraid. Just ask. The community will help you get started with Squeak. https://lists.squeakfoundation.org/mailman/listinfo/beginners squeak-dev + This is the main Squeak mailing list. Join that list to be part of the community. Subscribe to the mail server or read on a forum. - This is the main Squeak mailing list. Join that list to be part in the community. Subscribe to the mail server or read on a forum. https://lists.squeakfoundation.org/mailman/listinfo/squeak-dev + For more information on the community and the contribution process, check out the tutorial Contributing to Squeak on the following pages. - For more information on the community and the contribution process, check out the tutorial Contributing to Squeak in the following pages. vm-beginners This is the entry point for people who want to learn more about how Squeak runs on your operating system. You may ask even basic questions. :-) https://lists.squeakfoundation.org/mailman/listinfo/vm-beginners vm-dev This is the place where discussions about the OpenSmalltalk virtual machine happen. Join that list the be a part of the community. https://lists.squeakfoundation.org/mailman/listinfo/vm-dev Books Squeak By Example + A beginners textbook about Squeak''s environment, language, tools, and the Morphic framework, currently based on Squeak 6.0. Available as a colored paperback at Lulu and as a free PDF here. The content is maintained on GitHub. - A beginners textbook about Squeak''s environment, language, tools, and the Morphic framework, currently based on Squeak 6.0. Available as a colored paperback at lulu and as a free PDF here. The content is maintained on GitHub. Other books Many books about Squeak and Smalltalk in general have been made available: https://squeak.org/documentation/#books!! ]style[(11 19 1 23 48 1 23 1 14 23 1 27 1 32 1 29 1 49 1 1 13 1 1 10 135 1 61 1 1 10 1 131 62 92 22 25 1 13 144 64 1 1 6 1 131 58 1 1 5 2 17 1 160 4 19 4 31 6 2 1 11 1 75 39)b,I0i,I0,Rhttps://www.squeak.org;I1,I0i,I0,Rhttps://bugs.squeak.org;I1,I… queak.org/documentation/#books;I1!!' readStream nextChunkText) key: #squeakResourcesOnline; 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" <generated> ^(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. + 1. Red button, yellow button; buttons on mice, trackpads, and wheels - what do they do? - 1. Red button, Yellow Button; buttons on mice, trackpads and wheels - what do they do? + Smalltalk has been around for 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 one 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. 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. - 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). - 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. - 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 (accessible from the docking bar -> Help -> Keyboard Shortcuts menu). 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 (accesible from the Dock -> Help -> Keyboard Shortcuts menu). 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 docking bar - 3. The Dock + Across the top of the screen lies the docking bar; a mix of a menu bar, toolbar, 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 docking bar 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 menus: + a) pull-down menus - like those that you see on the docking bar; + 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; - 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. + To exit a project (and return to its parent project), choose "previous project" from the screen menu. - 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. - To exit a project (and return to its parent project), choose ''previous project'' from the screen menu. 6. Morphic Halos + 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 o ne. - 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. 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" 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, and then drop the object at the desired position in the flap.!! + ]style[(25 126 89 1831 18 172 25 139 20 142 5 127 20 430 5 5 4 421 10 41 15 50 12 116 8 81 18 339 13 221 16 674 16 142 15 843 7 693 13 47 15 523)b,,i,,Rcode://PreferenceBrowser open;,,i,,i,,i,,i,,i,,i,,i,,i,,i,,i,,i,,i,,Rcode://(ProjectViewMorph newProjectViewInAWindowFor: MorphicProject new) openInWorld;,,i,,Rcode://SystemWindow topWindow addHalo;,,i,,i,,Rcode://Project current world activateObjectsTool;,!!' readStream nextChunkText) - 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 134 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) 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" <generated> ^(HelpTopic title: 'Working with Squeak' contents: + 'Take a 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. - '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 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. 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 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 "Squeak6.0". - 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. - 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. - - 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. - 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 from where it was last saved - except for objects representing outside resources. External files, for example, may not exist when an image is restarted, perhaps on another machine. 3. The Sources File + Smalltalk traditionally includes the source code in the running system. However, keeping multiple copies of the same source code in all image 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 to this file, which is read on the fly to present the 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 "SqueakV60.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 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 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 the ''versions'' button in code browsers). This encourages experimentation since you can easily revert to the original versions of any set of methods. - 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). You can also disable both files in the preferences and have all sources managed in the image. - 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 - 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. - 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. 7. More information + This extremely brief explanation cannot explain everything; consider reading the Squeak by Example book!!!!!! + ]style[(226 24 98 15 610 18 89 18 236 19 173 6 165 6 179 9 39 17 594 19 589 19 1442 44 192 11 53 7 303 34 194 19 106),b,,i,,i,,i,,i,,b,,b,,b,,b,,b,,b,,b,,b,,Rcode://PackageInfo;,,Rhttp://w…,!!' readStream nextChunkText) - This extremely brief explanation cannot expleain everything; consider reading the Squeak by Example book!!!!!! - ]style[(224 24 98 15 611 18 90 18 236 19 173 6 165 6 178 9 39 17 592 19 591 19 1354 44 189 11 364 34 194 19 107),b,,i,,i,,i,,i,,b,,b,,b,,b,,b,,b,,b,,b,,Rhttp://wiki.squeak.org/squeak/…,!!' readStream nextChunkText) key: #workingWithSqueak; shouldStyle: false; yourself!

2 1

The Inbox: Collections-ct.1059.mcz
by commits＠source.squeak.org 05 Dec '23

05 Dec '23

Christoph Thiede uploaded a new version of Collections to project The Inbox: http://source.squeak.org/inbox/Collections-ct.1059.mcz ==================== Summary ==================== Name: Collections-ct.1059 Author: ct Time: 2 December 2023, 11:00:10.616859 pm UUID: 62d4569c-f11d-e84a-8052-ded6a3d2e42f Ancestors: Collections-ct.1056 Adds yellow button menu for editing TextURLs. =============== Diff against Collections-ct.1056 =============== Item was changed: ----- Method: TextURL>>analyze: (in category 'initialize-release') ----- analyze: aString + | list | - | list answer | list := super analyze: aString. - - answer := Project uiManager multiLineRequest: 'URL to open' translated centerAt: Sensor cursorPoint initialAnswer: (list at: 1) answerHeight: 200. - answer isEmptyOrNil ifTrue: [^ nil]. - url := answer. + url := list at: 1. + self editUrlOrCancel: [^ nil]. + ^ list at: 2! Item was added: + ----- Method: TextURL>>editUrl (in category 'as yet unclassified') ----- + editUrl + + ^ self editUrlOrCancel: nil! Item was added: + ----- Method: TextURL>>editUrlOrCancel: (in category 'as yet unclassified') ----- + editUrlOrCancel: cancelBlock + + | answer | + answer := Project uiManager + multiLineRequest: 'URL to open' translated + centerAt: Sensor cursorPoint + initialAnswer: url + answerHeight: 200. + answer isEmptyOrNil ifTrue: [^ cancelBlock value]. + url := answer.! Item was added: + ----- Method: TextURL>>menu (in category 'as yet unclassified') ----- + menu + + | builder menu | + builder := ToolBuilder default. + menu := builder pluggableMenuSpec new + add: 'edit url...' translated target: self selector: #editUrl argumentList: #(); + yourself. + ^ builder build: menu!

2 2