Squeak-dev January 2020

squeak-dev@lists.squeakfoundation.org

43 participants
227 discussions

Faster fibonacci
by tim Rowledge 28 Jan '20

28 Jan '20

I've been involved in a long and sometimes weird discussion on the RaspberryPi forums about fibonacci implementations in different languages and using assorted algorithms. I'd never really thought about alternatives to recursive approaches before but it turns out there is massively faster way. Clearly, this is not to replace the benchFib code since that has a specific use, but if anyone with an interest in numerics wants a faster way to generate fib(8577) for example, this is how - Integer >> fastDoublingFib "derived from https://www.nayuki.io/page/fast-fibonacci-algorithms" "(1 to: 20) collect:[:i| i fastDoublingFib]" "testing a quite large one - " "8577 fastDoublingFib= 13724780954457889052017147206983806244049002655849289934662148526555403650297300643609932653364630032094175733360509578504423049114004867523161091564824674600978308740378989479162611031273424686573759784740689516901416473328655422390895971263265867635819510949686102571388751758998017349379498918930220900180038324615253426530740473855269056304380498630108126734047701362218655030270360608989081398866489746698916626888016696892691933237089180504631788915650757757515944644732966345269202761471025651071790297611079540881155092137592980230998234868586211881093892491570520577408961869977892273540956424095750855208529072246641778982103984467921868950012668004047986803017482248992968482737462668300684879633714025755790485860328854796518843956263863014632532331145699658530054942590047273403691531821918862996422405159427262092477196755988981309029424760342802374213122162727840557722145891090413688461745240415668189577836068480363407847582529735341950500636735281963089675493707159434777756081146452522323681782226760627277553296721358921412115264845467834979154061137421532609247762981818564578019888974692581079593575783553856910367568474613323528337733872069223030834774749130478360574004172522316484339530942110067893000847800932306298725285623628731149337468217751734165148732164148285915275115006479682658150442259002271790547596033006363411193653337536041106069912826015502035140618407668385378737477702597473151509972754111640855347958033314453349633268543893894677097708945041254623018915871109789412793709229204261914803477697183287924195770678873001065036313926288444791424871512110658175954743584548831946767673488152740675550518235698898217693311515366329280005757014637854214769152690638778904780724293185353992279724740604674926819294787586671833537117545443846365508358918882" | a b c | a := 0. b := 1. self highBit to: 1 by: -1 do:[:i||d e| d := (b bitShift: 1) - a * a. e := a squared + b squared. a := d. b := e. (self bitAt: i) = 1 ifTrue:[ c := a + b. a := b. b := c] ]. ^a I bet it could be sped up more, but a simply spyOn run just allocated all the primitive time to delay waiting. Didn't we improve that some time ago? tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Strange OpCodes: BYEBYE: Store in Write-Only Storage

9 35

The Inbox: Graphics-tobe.425.mcz
by commits＠source.squeak.org 27 Jan '20

27 Jan '20

A new version of Graphics was added to project The Inbox: http://source.squeak.org/inbox/Graphics-tobe.425.mcz ==================== Summary ==================== Name: Graphics-tobe.425 Author: tobe Time: 27 January 2020, 5:11:45.257843 pm UUID: 2f66f6ea-c0d5-4487-bc4d-af76d67acc2e Ancestors: Graphics-pre.424 Fixes an issue causing an infinite text composition loop when placing embedded morphs which exceed the current composition rectangle's width. The fix entails consistently returning Booleans which indicate whether the morph still fits. =============== Diff against Graphics-pre.424 =============== Item was changed: ----- Method: CharacterScanner>>embeddedObject (in category 'stop conditions') ----- embeddedObject pendingKernX := 0. ((text attributesAt: lastIndex) reject: [:each | each anchoredMorph isNil]) + ifNotEmpty: [:attributes | (self placeEmbeddedObjectsFrom: attributes) ifTrue: [^ true]]. - ifNotEmpty: [:attributes | self placeEmbeddedObjectsFrom: attributes]. self setFont. "Note: if ever several objects are embedded on same character, only indent lastIndex once" lastIndex := lastIndex + 1. ^false! Item was changed: ----- Method: CharacterScanner>>placeEmbeddedObjectsFrom: (in category 'private-text-anchor') ----- placeEmbeddedObjectsFrom: textAttributes textAttributes do: [:attr | "Try to placeEmbeddedObject: - if it answers false, then there's no place left" + (self placeEmbeddedObjectFrom: attr) ifFalse: [^ self crossedX]]. + ^ false! - (self placeEmbeddedObjectFrom: attr) ifFalse: [^ self crossedX]]!

1 0

The Inbox: Kernel-ct.1296.mcz
by commits＠source.squeak.org 27 Jan '20

27 Jan '20

A new version of Kernel was added to project The Inbox: http://source.squeak.org/inbox/Kernel-ct.1296.mcz ==================== Summary ==================== Name: Kernel-ct.1296 Author: ct Time: 27 January 2020, 12:59:15.057199 pm UUID: e60f4637-b4fc-9947-94d3-50e7aa58ab82 Ancestors: Kernel-tonyg.1293 Fixes context simulation bug in #contextEnsure: and #contextOn:do: As ctxt is *not* a top context as required by #jump, we need to put a (fake) return value (nil) on its stack. Otherwise, #jump will pop something different from the stack. Concretely, this caused the bug described in [1] (Scenario 1) because the latest stack top was the closure vector {chain}. This closure vector was accidently popped away so that in the final return statement, #pushRemoteTemp:inVectorAt: raised an error subscript bounds (because the next stack item was not variable). Read the linked bug report for more details. [1] http://forum.world.st/BUG-s-in-Context-control-jump-runUntilErrorOrReturnFr… =============== Diff against Kernel-tonyg.1293 =============== Item was changed: ----- Method: Context class>>contextEnsure: (in category 'special context creation') ----- contextEnsure: block "Create an #ensure: context that is ready to return from executing its receiver" | ctxt chain | ctxt := thisContext. + [chain := thisContext sender cut: ctxt. + ctxt push: nil. + ctxt jump] ensure: block. - [chain := thisContext sender cut: ctxt. ctxt jump] ensure: block. "jump above will resume here without unwinding chain" ^ chain! Item was changed: ----- Method: Context class>>contextOn:do: (in category 'special context creation') ----- contextOn: exceptionClass do: block "Create an #on:do: context that is ready to return from executing its receiver" | ctxt chain | ctxt := thisContext. + [chain := thisContext sender cut: ctxt. + ctxt push: nil. + ctxt jump] on: exceptionClass do: block. - [chain := thisContext sender cut: ctxt. ctxt jump] on: exceptionClass do: block. "jump above will resume here without unwinding chain" ^ chain!

2 1

The Inbox: KernelTests-ct.376.mcz
by commits＠source.squeak.org 27 Jan '20

27 Jan '20

Christoph Thiede uploaded a new version of KernelTests to project The Inbox: http://source.squeak.org/inbox/KernelTests-ct.376.mcz ==================== Summary ==================== Name: KernelTests-ct.376 Author: ct Time: 27 January 2020, 1:08:37.013199 pm UUID: 7ed66f25-b6e3-1743-a84c-d8a571a6d1e7 Ancestors: KernelTests-ct.375 Tests #contextEnsure: and #contextOn:do:. Includes regression tests for Kernel-ct.1296. =============== Diff against KernelTests-ct.375 =============== Item was added: + ----- Method: ContextTest>>simulate: (in category 'private') ----- + simulate: aBlock + + | result | + [result := aBlock value] newProcess runUntil: [:ctxt | false]. + ^ result! Item was added: + ----- Method: ContextTest>>testContextEnsure (in category 'tests') ----- + testContextEnsure + + | sideEffect block result | + block := [ + sideEffect := nil. "if the ensure block would be evaluated too early, this would raise an error" + thisContext insertSender: ( + Context contextEnsure: [ + sideEffect := sideEffect + 1]). + sideEffect := 0]. + + result := block value. + self assert: 0 equals: result. + self assert: 1 equals: sideEffect.! Item was added: + ----- Method: ContextTest>>testContextEnsureSimulation (in category 'tests') ----- + testContextEnsureSimulation + "Regression test for http://forum.world.st/BUG-s-in-Context-control-jump-runUntilErrorOrReturnFr…" + + | sideEffect block result | + block := [ + sideEffect := nil. "if the ensure block would be evaluated too early, this would raise an error" + thisContext insertSender: ( + Context contextEnsure: [ + sideEffect := sideEffect + 1]). + sideEffect := 0]. + + self shouldnt: [result := self simulate: block] raise: Error. "this wrapper is important for avoiding a debugger chain when testing" + self assert: 0 equals: result. + self assert: 1 equals: sideEffect.! Item was added: + ----- Method: ContextTest>>testContextEnsureSimulationWithError (in category 'tests') ----- + testContextEnsureSimulationWithError + "Regression test for http://forum.world.st/BUG-s-in-Context-control-jump-runUntilErrorOrReturnFr…" + + | sideEffect block result | + block := [ + sideEffect := nil. "if the ensure block would be evaluated too early, this would raise an error" + thisContext insertSender: ( + Context contextEnsure: [ + sideEffect := sideEffect + 1]). + sideEffect := 0. + self error]. + + self + shouldnt: [result := self simulate: [[block value] on: Error do: [42]]] + raise: Error. "this wrapper is important for avoiding a debugger chain when testing" + self assert: 42 equals: result. + self assert: 1 equals: sideEffect.! Item was added: + ----- Method: ContextTest>>testContextEnsureWithError (in category 'tests') ----- + testContextEnsureWithError + + | sideEffect block result | + block := [ + sideEffect := nil. "if the ensure block would be evaluated too early, this would raise an error" + thisContext insertSender: ( + Context contextEnsure: [ + sideEffect := sideEffect + 1]). + sideEffect := 0. + self error]. + + result := [block value] on: Error do: [42]. + self assert: 42 equals: result. + self assert: 1 equals: sideEffect.! Item was added: + ----- Method: ContextTest>>testContextOnDo (in category 'tests') ----- + testContextOnDo + + | sideEffect block result | + block := [ + sideEffect := nil. "if the ensure block would be evaluated too early, this would raise an error" + thisContext insertSender: ( + Context contextOn: Error do: [ + sideEffect := sideEffect + 1]). + sideEffect := 0]. + + result := block value. + self assert: 0 equals: result. + self assert: 0 equals: sideEffect.! Item was added: + ----- Method: ContextTest>>testContextOnDoSimulation (in category 'tests') ----- + testContextOnDoSimulation + "Regression test for http://forum.world.st/BUG-s-in-Context-control-jump-runUntilErrorOrReturnFr…" + + | sideEffect block result | + block := [ + sideEffect := nil. "if the ensure block would be evaluated too early, this would raise an error" + thisContext insertSender: ( + Context contextOn: Error do: [ + sideEffect := sideEffect + 1]). + sideEffect := 0]. + + self shouldnt: [result := self simulate: block] raise: Error. "this wrapper is important for avoiding a debugger chain when testing" + self assert: 0 equals: result. + self assert: 0 equals: sideEffect.! Item was added: + ----- Method: ContextTest>>testContextOnDoSimulationWithError (in category 'tests') ----- + testContextOnDoSimulationWithError + "Regression test for http://forum.world.st/BUG-s-in-Context-control-jump-runUntilErrorOrReturnFr…" + + | sideEffect block result | + block := [ + sideEffect := nil. "if the ensure block would be evaluated too early, this would raise an error" + thisContext insertSender: ( + Context contextOn: Error do: [ + sideEffect := sideEffect + 1. + 42]). + sideEffect := 0. + self error]. + + self shouldnt: [result := self simulate: block] raise: Error. "this wrapper is important for avoiding a debugger chain when testing" + self assert: 42 equals: result. + self assert: 1 equals: sideEffect.! Item was added: + ----- Method: ContextTest>>testContextOnDoWithError (in category 'tests') ----- + testContextOnDoWithError + + | sideEffect block result | + block := [ + sideEffect := nil. "if the ensure block would be evaluated too early, this would raise an error" + thisContext insertSender: ( + Context contextOn: Error do: [ + sideEffect := sideEffect + 1. + 42]). + sideEffect := 0. + self error]. + + result := block value. + self assert: 42 equals: result. + self assert: 1 equals: sideEffect.!

1 0

The Inbox: KernelTests-ct.375.mcz
by commits＠source.squeak.org 27 Jan '20

27 Jan '20

Christoph Thiede uploaded a new version of KernelTests to project The Inbox: http://source.squeak.org/inbox/KernelTests-ct.375.mcz ==================== Summary ==================== Name: KernelTests-ct.375 Author: ct Time: 27 January 2020, 1:07:33.390199 pm UUID: 5bbc6392-5860-6943-bfb0-62deea913111 Ancestors: KernelTests-nice.373 Complements Kernel-eem.1078 (rename MethodContext to Context) by renaming test case as well =============== Diff against KernelTests-nice.373 =============== Item was added: + TestCase subclass: #ContextTest + instanceVariableNames: 'aCompiledMethod aReceiver aSender aContext' + classVariableNames: '' + poolDictionaries: '' + category: 'KernelTests-Methods'! + + !ContextTest commentStamp: 'ct 1/27/2020 13:03' prior: 0! + I am an SUnit Test of Context. See also BlockClosureTest. + See pages 430-437 of A. Goldberg and D. Robson's Smalltalk-80 The Language (aka the purple book), which deal with Contexts. My fixtures are from their example. To see how blocks are implemented in this version of Squeak see http://www.mirandabanda.org/cogblog/2008/06/07/closures-part-i/ and http://www.mirandabanda.org/cogblog/2008/07/22/closures-part-ii-the-bytecod…. (The Squeak V3 byte codes are not quite the same as Smalltalk-80, and the SistaV1 byetcodes are quite different.) + My fixtures are: + aReceiver - just some arbitrary object, "Rectangle origin: 100@100 corner: 200@200" + aSender - just some arbitrary object, thisContext + aCompiledMethod - just some arbitrary method, "Rectangle rightCenter". + aContext - just some arbitray context ... + + ! Item was added: + ----- Method: ContextTest>>privRestartTest (in category 'private') ----- + privRestartTest + "This tests may loop endlessly if incorrect, so call it from another method testing it does not time out" + |a firstTimeThrough | + firstTimeThrough := true. + a := 10. + + self assert: 30 equals: [|b| + self assert: 10 = a . + self assert: nil == b. + b := a + 20. + firstTimeThrough ifTrue: [ + firstTimeThrough := false. + thisContext restart.]. + b] value + ! Item was added: + ----- Method: ContextTest>>setUp (in category 'running') ----- + setUp + super setUp. + aCompiledMethod := Rectangle methodDict at: #rightCenter. + aReceiver := 100@100 corner: 200@200. + aSender := thisContext. + aContext := Context sender: aSender receiver: aReceiver method: aCompiledMethod arguments: #(). ! Item was added: + ----- Method: ContextTest>>testActivateReturnValue (in category 'tests') ----- + testActivateReturnValue + self assert: (aSender activateReturn: aContext value: #()) isContext. + self assert: ((aSender activateReturn: aContext value: #()) receiver = aContext).! Item was added: + ----- Method: ContextTest>>testCopyStack (in category 'tests') ----- + testCopyStack + self assert: aContext copyStack printString = aContext printString.! Item was added: + ----- Method: ContextTest>>testFindContextSuchThat (in category 'tests') ----- + testFindContextSuchThat + self assert: (aContext findContextSuchThat: [:each| true]) printString = aContext printString. + self assert: (aContext hasContext: aContext). ! Item was added: + ----- Method: ContextTest>>testMethodContext (in category 'tests') ----- + testMethodContext + self assert: aContext home notNil. + self assert: aContext receiver notNil. + self assert: aContext method isCompiledMethod.! Item was added: + ----- Method: ContextTest>>testMethodIsBottomContext (in category 'tests') ----- + testMethodIsBottomContext + self assert: aContext bottomContext = aSender. + self assert: aContext secondFromBottom = aContext.! Item was added: + ----- Method: ContextTest>>testRestart (in category 'tests') ----- + testRestart + self should: [self privRestartTest] notTakeMoreThan: 0.1 second! Item was added: + ----- Method: ContextTest>>testReturn (in category 'tests') ----- + testReturn + "Why am I overriding setUp? Because sender must be thisContext, i.e, testReturn, not setUp." + aContext := Context sender: thisContext receiver: aReceiver method: aCompiledMethod arguments: #(). + self assert: (aContext return: 5) = 5! Item was added: + ----- Method: ContextTest>>testSetUp (in category 'tests') ----- + testSetUp + "Note: In addition to verifying that the setUp worked the way it was expected to, testSetUp is used to illustrate the meaning of the simple access methods, methods that are not normally otherwise 'tested'" + self assert: aContext isContext. + self deny: aContext isExecutingBlock. + self deny: aContext isClosure. + self deny: aContext isDead. + "self assert: aMethodContext home = aReceiver." + "self assert: aMethodContext blockHome = aReceiver." + self assert: aContext receiver = aReceiver. + self assert: aContext method isCompiledMethod. + self assert: aContext method = aCompiledMethod. + self assert: aContext methodNode selector = #rightCenter. + self assert: (aContext methodNodeFormattedAndDecorated: true) selector = #rightCenter. + self assert: aContext client printString = 'ContextTest>>#testSetUp'. + ! Item was removed: - TestCase subclass: #MethodContextTest - instanceVariableNames: 'aCompiledMethod aReceiver aMethodContext aSender' - classVariableNames: '' - poolDictionaries: '' - category: 'KernelTests-Methods'! - - !MethodContextTest commentStamp: 'eem 3/30/2017 17:42' prior: 0! - I am an SUnit Test of Context. See also BlockClosureTest. - See pages 430-437 of A. Goldberg and D. Robson's Smalltalk-80 The Language (aka the purple book), which deal with Contexts. My fixtures are from their example. To see how blocks are implemented in this version of Squeak see http://www.mirandabanda.org/cogblog/2008/06/07/closures-part-i/ and http://www.mirandabanda.org/cogblog/2008/07/22/closures-part-ii-the-bytecod…. (The Squeak V3 byte codes are not quite the same as Smalltalk-80, and the SistaV1 byetcodes are quite different.) - My fixtures are: - aReceiver - just some arbitrary object, "Rectangle origin: 100@100 corner: 200@200" - aSender - just some arbitrary object, thisContext - aCompiledMethod - just some arbitrary method, "Rectangle rightCenter". - aMethodContext - just some arbitray context ... - - ! Item was removed: - ----- Method: MethodContextTest>>privRestartTest (in category 'private') ----- - privRestartTest - "This tests may loop endlessly if incorrect, so call it from another method testing it does not time out" - |a firstTimeThrough | - firstTimeThrough := true. - a := 10. - - self assert: 30 equals: [|b| - self assert: 10 = a . - self assert: nil == b. - b := a + 20. - firstTimeThrough ifTrue: [ - firstTimeThrough := false. - thisContext restart.]. - b] value - ! Item was removed: - ----- Method: MethodContextTest>>setUp (in category 'running') ----- - setUp - super setUp. - aCompiledMethod := Rectangle methodDict at: #rightCenter. - aReceiver := 100@100 corner: 200@200. - aSender := thisContext. - aMethodContext := Context sender: aSender receiver: aReceiver method: aCompiledMethod arguments: #(). ! Item was removed: - ----- Method: MethodContextTest>>testActivateReturnValue (in category 'tests') ----- - testActivateReturnValue - self assert: (aSender activateReturn: aMethodContext value: #()) isContext. - self assert: ((aSender activateReturn: aMethodContext value: #()) receiver = aMethodContext).! Item was removed: - ----- Method: MethodContextTest>>testCopyStack (in category 'tests') ----- - testCopyStack - self assert: aMethodContext copyStack printString = aMethodContext printString.! Item was removed: - ----- Method: MethodContextTest>>testFindContextSuchThat (in category 'tests') ----- - testFindContextSuchThat - self assert: (aMethodContext findContextSuchThat: [:each| true]) printString = aMethodContext printString. - self assert: (aMethodContext hasContext: aMethodContext). ! Item was removed: - ----- Method: MethodContextTest>>testMethodContext (in category 'tests') ----- - testMethodContext - self assert: aMethodContext home notNil. - self assert: aMethodContext receiver notNil. - self assert: aMethodContext method isCompiledMethod.! Item was removed: - ----- Method: MethodContextTest>>testMethodIsBottomContext (in category 'tests') ----- - testMethodIsBottomContext - self assert: aMethodContext bottomContext = aSender. - self assert: aMethodContext secondFromBottom = aMethodContext.! Item was removed: - ----- Method: MethodContextTest>>testRestart (in category 'tests') ----- - testRestart - self should: [self privRestartTest] notTakeMoreThan: 0.1 second! Item was removed: - ----- Method: MethodContextTest>>testReturn (in category 'tests') ----- - testReturn - "Why am I overriding setUp? Because sender must be thisContext, i.e, testReturn, not setUp." - aMethodContext := Context sender: thisContext receiver: aReceiver method: aCompiledMethod arguments: #(). - self assert: (aMethodContext return: 5) = 5! Item was removed: - ----- Method: MethodContextTest>>testSetUp (in category 'tests') ----- - testSetUp - "Note: In addition to verifying that the setUp worked the way it was expected to, testSetUp is used to illustrate the meaning of the simple access methods, methods that are not normally otherwise 'tested'" - self assert: aMethodContext isContext. - self deny: aMethodContext isExecutingBlock. - self deny: aMethodContext isClosure. - self deny: aMethodContext isDead. - "self assert: aMethodContext home = aReceiver." - "self assert: aMethodContext blockHome = aReceiver." - self assert: aMethodContext receiver = aReceiver. - self assert: aMethodContext method isCompiledMethod. - self assert: aMethodContext method = aCompiledMethod. - self assert: aMethodContext methodNode selector = #rightCenter. - self assert: (aMethodContext methodNodeFormattedAndDecorated: true) selector = #rightCenter. - self assert: aMethodContext client printString = 'MethodContextTest>>#testSetUp'. - !

1 0

variable assignments button
by Ralph Boland 26 Jan '20

26 Jan '20

In the Browsers there is a line of buttons: "browse", "senders" etc. One of the buttons is "vars" which when pressed brings up a GUI that allows you to select a variable and then a list of all methods using that variable is brought up from which you can select a method to inspect. Sometimes I only want to view the subset of the methods in which the variable is assigned. I have implemented this feature (new button to the right of "vars" labeled ":=") and find it to be very useful. I am wondering if this feature can be added to the next version of Squeak. I can send my code changes if someone is willing to do this but the changes required are small so my help may not be needed. If some do not like this feature (it's great really!) then perhaps it could be turned on or off depending on a Preferences setting. If this feature happens to be in 5.3 then my apologies for wasting peoples time. Ralph Boland

7 21

Time To VOTE!
by Ron Teitelbaum 25 Jan '20

25 Jan '20

YOUR VOTE MATTERS! It is time to vote! We have 7 candidates for 7 board positions but your voting is still really important to show support for your board! Please take the time to look for the ballot in your email. You might find that it is in your spam folder. Don't just move it but mark the email as NOT SPAM. The email comes from Ron Teitelbaum (CIVS poll supervisor) It has the subject: *Poll: Squeak Oversight Board 2020 * and it was sent on: *1/20/2020. * Some of you may have received multiple emails. There was an email that was preventing the emails from going out to everyone. You only need to vote once and the system will only allow you to vote one time. If you have any questions or can not find your ballot please let me know. I can send it to you again. The voting goes on for 2 weeks to make sure everyone has time to vote. The election will end on Tuesday 4th of February 2020 4 PM (21.00 UTC) Please don't wait until the last minute to vote do it now while it is on the top of your email! Thank you everyone for your participation! We have a great community and terrific candidates for the Squeak Oversight Board! All the best, Ron Teitelbaum

2 1

Re: [squeak-dev] Squeak Oversight Board Election 2020
by Marcel Taeumel 25 Jan '20

25 Jan '20

Hi Ron, hi all! I was just looking at my last year's proposal, and I am eager to reuse those words as they reflect my ongoing enthusiasm for the Squeak ecosystem. :-) I would really like to continue serving on the Squeak Oversight Board in 2020! *** My main interests include user interaction (Morphic), code modularity (readability/extensibility), backwards compatibility (Etoys), and programming/productivity tools. During the past years, there has been a healthy mix of promising ideas, enlightening discussions, and challenging viewpoints. I do value such programming experiences as a great addition to my daily life. Squeak's community is great! Thank you. :-) Let us continue shaping Squeak for many opportunities to come! It is an intriguing programming system with its liveness promoting exploratory working habits. What a time to be a programmer! Best, Marcel

3 3

Re: [squeak-dev] The Inbox: Kernel-eem.1295.mcz
by Thiede, Christoph 25 Jan '20

25 Jan '20

But wouldn't you want to have each independent inbox commit be based on the latest Trunk version? Unless I misunderstood every admonition I have been told since I started contributing to Squeak, the current ancestry makes it impossible to merge Kernel-eem.1295 into Trunk *without* Kernel-eem.1294, or am I wrong? And btw, is it also intended that Kernel-eem.1294 has two ancestors? :) Best, Christoph ________________________________ Von: Squeak-dev <squeak-dev-bounces(a)lists.squeakfoundation.org> im Auftrag von Eliot Miranda <eliot.miranda(a)gmail.com> Gesendet: Samstag, 25. Januar 2020, 03:19 An: The general-purpose Squeak developers list Betreff: Re: [squeak-dev] The Inbox: Kernel-eem.1295.mcz On Fri, Jan 24, 2020 at 12:38 PM Thiede, Christoph <Christoph.Thiede(a)student.hpi.uni-potsdam.de<mailto:Christoph.Thiede@student.hpi.uni-potsdam.de>> wrote: Is the history clean? This commit does not really depend on Kernel-eem.1294, does it? No. I just committed it straight after committing 1294. ________________________________ Von: Squeak-dev <squeak-dev-bounces(a)lists.squeakfoundation.org<mailto:squeak-dev-bounces@lists.squeakfoundation.org>> im Auftrag von commits(a)source.squeak.org<mailto:commits@source.squeak.org> <commits(a)source.squeak.org<mailto:commits@source.squeak.org>> Gesendet: Freitag, 24. Januar 2020 21:09:17 An: squeak-dev(a)lists.squeakfoundation.org<mailto:squeak-dev@lists.squeakfoundation.org> Betreff: [squeak-dev] The Inbox: Kernel-eem.1295.mcz A new version of Kernel was added to project The Inbox: http://source.squeak.org/inbox/Kernel-eem.1295.mcz ==================== Summary ==================== Name: Kernel-eem.1295 Author: eem Time: 24 January 2020, 12:09:14.247651 pm UUID: 1f1fc6c8-7160-4101-9c48-56ec5784616f Ancestors: Kernel-eem.1294 Fix comment typo for perform:with:with:with:with:with: =============== Diff against Kernel-eem.1294 =============== Item was changed: ----- Method: Object>>perform:with:with:with:with:with: (in category 'message handling') ----- perform: aSymbol with: firstObject with: secondObject with: thirdObject with: fourthObject with: fifthObject "Send the selector, aSymbol, to the receiver with the given arguments. + Fail if the number of arguments expected by the selector is not five. - Fail if the number of arguments expected by the selector is not four. Primitive. Optional. See Object documentation whatIsAPrimitive." <primitive: 83> ^ self perform: aSymbol withArguments: { firstObject. secondObject. thirdObject. fourthObject. fifthObject }! -- _,,,^..^,,,_ best, Eliot

2 1

The Trunk: System-cmm.1130.mcz
by commits＠source.squeak.org 25 Jan '20

25 Jan '20

Chris Muller uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-cmm.1130.mcz ==================== Summary ==================== Name: System-cmm.1130 Author: cmm Time: 24 January 2020, 4:10:56.786823 pm UUID: e3403284-49d1-4d18-9c7f-b0c051a3b4c4 Ancestors: System-cmm.1129 Fix Community (dark) theme balloons not easily seen due to matching color on MC and SqueakMap browsers. =============== Diff against System-cmm.1129 =============== Item was changed: ----- Method: CommunityTheme class>>addDarkDialogs: (in category 'instance creation') ----- addDarkDialogs: aUserInterfaceTheme "self createDark apply." aUserInterfaceTheme set: #borderColor for: #DialogWindow to: self dbSelection; set: #color for: #DialogWindow to: (self dbBlue adjustSaturation: -0.20 brightness: -0.30); set: #titleColor for: #DialogWindow to: self dbBlue twiceDarker; set: #titleTextColor for: #DialogWindow to: Color veryLightGray; set: #textColor for: #DialogWindow to: (Color gray: 0.9); set: #okColor for: #DialogWindow to: self dbGreen; set: #cancelColor for: #DialogWindow to: self dbOrange; set: #buttonColor for: #DialogWindow to: Color darkGray; set: #selectionModifier for: #DialogWindow to: [ [:c | self dbSelection twiceDarker ] ]. "The List Chooser is a dialog, too." aUserInterfaceTheme set: #addColor for: #ListChooser to: self dbBlue; set: #disabledColor for: #ListChooser to: Color transparent. "And the system progress bar." aUserInterfaceTheme set: #color for: #SystemProgressBarMorph to: Color transparent; set: #barColor for: #SystemProgressBarMorph to: self dbSelection. "And the balloon morphs." aUserInterfaceTheme set: #borderColor for: #NewBalloonMorph to: Color transparent ; + set: #color for: #NewBalloonMorph to: (self dbLabel alpha: 0.9) ; - set: #color for: #NewBalloonMorph to: (self dbOrange twiceDarker alpha: 0.9) ; set: #textColor for: #NewBalloonMorph to: Color white .! Item was added: + ----- Method: CommunityTheme class>>dbLabel (in category 'colors by purpose') ----- + dbLabel + "Short notes and labels are meant for human consumption." + ^ self dbPink!

3 2

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

Jump to page: