Squeak-dev January 2019

squeak-dev@lists.squeakfoundation.org

41 participants
152 discussions

The Trunk: Chronology-Tests-dtl.20.mcz
by commits＠source.squeak.org 28 Jan '19

28 Jan '19

David T. Lewis uploaded a new version of Chronology-Tests to project The Trunk: http://source.squeak.org/trunk/Chronology-Tests-dtl.20.mcz ==================== Summary ==================== Name: Chronology-Tests-dtl.20 Author: dtl Time: 27 January 2019, 6:02:53.312815 pm UUID: 005bcc36-75cd-4ade-82b4-9cbef7dbf8fb Ancestors: Chronology-Tests-dtl.19 Add TimespanTest>>testBeCanonical to document the behavior as implemented in Chronology prior to the recent UTC updates. =============== Diff against Chronology-Tests-dtl.19 =============== Item was added: + ----- Method: TimespanTest>>testBeCanonical (in category 'Tests') ----- + testBeCanonical + + | start ts1 ts2 ts3 | + start := '2019-01-27T17:11:40.061188-05:00' asDateAndTime. + ts1 := Timespan starting: start duration: 123456 seconds. + ts2 := ts1 deepCopy. + ts3 := ts2 beCanonical. + self assert: ts2 + identical: ts3 + description: 'beCanonical modifies the receiver, not a copy thereof'. + self deny: ts3 = ts1. + self assert: '2019-01-27T17:11:40.061188-05:00' asDateAndTime + equals: ts1 start + description: 'original timespan start is not modified'. + self assert: ts1 duration + equals: ts3 duration + description: 'duration does not change'. + self assert: '2019-01-27T17:11:40.061188+00:00' asDateAndTime + equals: ts3 start. + self deny: ts1 start = ts3 start + description: 'magnitude of start time is changed'. + self assert: 5 hours + equals: start - ts3 start + description: 'magnitude of start time is changed'. + self assert: 0 seconds + equals: ts3 start offset + description: 'time zone offset is zero'. + self assert: 5 hours negated + equals: ts1 start offset + description: 'original timezone was -18000'. + !

1 0

The Trunk: Chronology-Tests-dtl.19.mcz
by commits＠source.squeak.org 27 Jan '19

27 Jan '19

David T. Lewis uploaded a new version of Chronology-Tests to project The Trunk: http://source.squeak.org/trunk/Chronology-Tests-dtl.19.mcz ==================== Summary ==================== Name: Chronology-Tests-dtl.19 Author: dtl Time: 27 January 2019, 4:43:34.528077 pm UUID: 00b997fd-2217-4b95-b2d3-ca2a4198f6b9 Ancestors: Chronology-Tests-dtl.18 Revert to the original version of DateAndTimeLeapTest to restore its author initials and timestamp (tlk 1/2/2004 22:05). The test now now passes, so remove it as an expected failure. Chronology tests are green. =============== Diff against Chronology-Tests-dtl.18 =============== Item was removed: - ----- Method: DateAndTimeLeapTest>>expectedFailures (in category 'failures') ----- - expectedFailures - - ^ #(testAsSeconds)! Item was changed: ----- Method: DateAndTimeLeapTest>>testAsSeconds (in category 'testing') ----- testAsSeconds + self assert: aDuration asSeconds = 48780. + self assert: aDateAndTime asSeconds = 3255507180 + + ! - self assert: aDuration asSeconds = 48780. - self assert: aDateAndTime asSeconds = 3255507180!

1 0

The Trunk: Chronology-Tests-dtl.18.mcz
by commits＠source.squeak.org 27 Jan '19

27 Jan '19

David T. Lewis uploaded a new version of Chronology-Tests to project The Trunk: http://source.squeak.org/trunk/Chronology-Tests-dtl.18.mcz ==================== Summary ==================== Name: Chronology-Tests-dtl.18 Author: dtl Time: 27 January 2019, 1:21:59.414215 pm UUID: 5411396e-c5fc-4517-97ef-5cf9e7aa5dea Ancestors: Chronology-Tests-pre.17 Do not use #makeUTC in DateAndTimeTest>>testGetSeconds because it modifies magnitude. =============== Diff against Chronology-Tests-pre.17 =============== Item was changed: ----- Method: DateAndTimeTest>>testGetSeconds (in category 'Tests') ----- testGetSeconds "Verify that getSeconds represents whole seconds in the local time zone. For a given instance of DateAndTime, changing the time zone offset changes the local representation, but does not affect magnitude (time since a defiined epoch). Therefore, if time zone offset changes, the asSeconds value should not change, and the getSeconds value should change to reflect local timezone." | dt s1 id stSeconds seconds1 seconds2 | s1 := '2019-01-12T10:07:05.18743-05:00'. dt := s1 asDateAndTime. self assert: 18000 seconds negated equals: dt offset. seconds1 := dt getSeconds. self assert: 36425 equals: seconds1. id := dt identityHash. stSeconds := dt asSeconds. + dt localOffsetSeconds: 0. "make the receiver's timezone GMT, do not change magnitude" - dt makeUTC. "make the receiver's timezone GMT, do not change magnitude" self assert: id equals: dt identityHash. "same object, not a copy" self assert: '2019-01-12T15:07:05.18743+00:00' equals: dt asString. self assert: stSeconds equals: dt asSeconds. "magnitude unchanged" self assert: '2019-01-12T10:07:05.18743-05:00' asDateAndTime equals: dt. "still equal" seconds2 := dt getSeconds. self deny: seconds1 equals: seconds2. self assert: 54425 equals: seconds2. !

1 0

The Trunk: Chronology-Core-dtl.38.mcz
by commits＠source.squeak.org 27 Jan '19

27 Jan '19

David T. Lewis uploaded a new version of Chronology-Core to project The Trunk: http://source.squeak.org/trunk/Chronology-Core-dtl.38.mcz ==================== Summary ==================== Name: Chronology-Core-dtl.38 Author: dtl Time: 27 January 2019, 1:21:28.699596 pm UUID: 1b64f41b-a799-4f9d-9037-cab677271baa Ancestors: Chronology-Core-dtl.33 Change DateAndTime>>makeUTC to behave as in prior versions of Chronology, and expand its comment to explain that both magniitude and timezone offset are changed in the receiver. Update DateAndTime>>asUTC to avoid use of makeUTC.Fixes three failing unit tests. =============== Diff against Chronology-Core-dtl.33 =============== Item was changed: ----- Method: DateAndTime>>asUTC (in category 'ansi protocol') ----- asUTC localOffsetSeconds = 0 ifTrue: [ ^self ]. + ^self copy localOffsetSeconds: 0.! - ^self copy makeUTC! Item was changed: ----- Method: DateAndTime>>makeUTC (in category 'squeak protocol') ----- makeUTC + "Make the receiver's timezone UTC. This adjusts both the magnitude and + local offset of the receiver such that self asString remains unchanged + except for a zero timezone offset." + + ^ self + utcMicroseconds: localOffsetSeconds * 1000000 + utcMicroseconds + offset: 0 + ! - "Make the receiver's timezone UTC." - localOffsetSeconds := 0!

1 0

Howto use Nebraska properly?
by Philip Bernhart 27 Jan '19

27 Jan '19

Hello, I simply found Nebraska and by Hand opened a Nebraska Server on my local machine just to test screen sharing capabilities of squeak. But... I couldn't find out of how to connect a client to that server. After I went down the rabbit hole for two hours, I still don't know of how to connect a different squeak image to the server. I looked into the Nebraska entry in the swiki https://wiki.squeak.org/squeak/1356 and was still puzzled as it seems to reference times long gone. So how to use that thing or is it broken beyond repair? Thanks, Philip

2 1

The Inbox: Collections-JH.814.mcz
by commits＠source.squeak.org 26 Jan '19

26 Jan '19

A new version of Collections was added to project The Inbox: http://source.squeak.org/inbox/Collections-JH.814.mcz ==================== Summary ==================== Name: Collections-JH.814 Author: JH Time: 24 January 2019, 10:32:33.157023 am UUID: 2981cec1-a155-7840-bbff-827a8f3387bb Ancestors: Collections-eem.806 Add check to FloatArray primitive fallback code to ensure that receiver and argument have the same size (argument was previously allowed to be larger than receiver, which does not make sense mathematically). =============== Diff against Collections-eem.806 =============== Item was changed: ----- Method: FloatArray>>primAddArray: (in category 'primitives-plugin') ----- primAddArray: floatArray <primitive: 'primitiveAddFloatArray' module: 'FloatArrayPlugin'> + self size = floatArray size ifFalse:[^self error:'Must be equal size']. 1 to: self size do:[:i| self at: i put: (self at: i) + (floatArray at: i)].! Item was changed: ----- Method: FloatArray>>primDivArray: (in category 'primitives-plugin') ----- primDivArray: floatArray <primitive: 'primitiveDivFloatArray' module: 'FloatArrayPlugin'> + self size = floatArray size ifFalse:[^self error:'Must be equal size']. 1 to: self size do:[:i| self at: i put: (self at: i) / (floatArray at: i)].! Item was changed: ----- Method: FloatArray>>primMulArray: (in category 'primitives-plugin') ----- primMulArray: floatArray <primitive: 'primitiveMulFloatArray' module: 'FloatArrayPlugin'> + self size = floatArray size ifFalse:[^self error:'Must be equal size']. 1 to: self size do:[:i| self at: i put: (self at: i) * (floatArray at: i)].! Item was changed: ----- Method: FloatArray>>primSubArray: (in category 'primitives-plugin') ----- primSubArray: floatArray <primitive: 'primitiveSubFloatArray' module: 'FloatArrayPlugin'> + self size = floatArray size ifFalse:[^self error:'Must be equal size']. 1 to: self size do:[:i| self at: i put: (self at: i) - (floatArray at: i)].!

6 5

Re: [squeak-dev] Proposal: Geometry Classes
by karl ramberg 25 Jan '19

25 Jan '19

+1 It's quite hard to get a grasp over how to draw stuff so this sound like a step in the right direction. Best, Karl On Tue, Jan 22, 2019 at 6:32 PM <patrick.rein(a)hpi.uni-potsdam.de> wrote: > Hi everyone, > > during some recent clean-up an issue with geometry objects came up. As a > result the following idea came up which I thereby would like to put out for > an initial discussion. > > In case we find that this might be useful, I would continue by > implementing a first prototype of the package as a foundation of a more > in-depth discussion later on. > > Bests > Patrick > > # Squeak Change Proposal - Geometry Package > > ## Why? > Squeak implements basic geometry logic in too many different places. For > example intersection of different kinds of geometric objects is implemented > all over Morphic, ST80, Balloon, Graphics, and Etoys. Such extensive > scattering across packages and classes impedes modularity, that is, > readability and extensibility. An example for this recently came up when we > discovered an issue with testing for graphical intersections between > PolygonMorph and RectangleMorph. It was not possible to compute that > overlapping area because the class Rectangle omits to provide an important > method. A quick fix would entail unnecessary dependencies (here: Morphic -> > Balloon) or duplicated code (see also > http://bugs.squeak.org/view.php?id=7872). Consequently, we might want to > modularize the geometry objects and operations. As a side effect, dependent > packages such as Morphic can be simplified a little bit (more). > > ## Scope > The proposed package should cover basic 2D geometric objects and their > operations represented by the following classes: > - Point > - Line > - LineSegment > - Polygon > - Rectangle (as an optimization as it could be represented as a special > Polygon already) > > Most classes could simply be moved from their previous packages. > Afterwards the interfaces would need to be made consistent with each other > to allow interoperability of all geometry classes within the new package. > > ### Affected classes: > - All classes in ST80-Paths > - LineSegement, Bezier2Segment, Bezier3Segment (Balloon-Geometry) > - Rectangle, Quadrangle, Point (Graphics-Primitives) > - LineIntersections, LineIntersectionSegment, LineIntersectionEvent > (Etoys-Squeakland-Graphics-Tools-Intersection) > > ## Open questions > - Should this become a single new package or a subcategory in the Graphics > package? > - Should the package contain an Ellipses class? > - Should we model curved line segments as BezierLineSegments, > CurvedLineSegment, or Arc? > > ## Risks > - This would potentially deprecate the existing ST80 geometry classes > (ST80-Paths) > - Some of the new classes will cause name clashes with existing classes. > For example Line is currently in ST-80 and represents a line segment, and > the class LineSegment is a line segment but not in the geometric sense as > it also incorporates arcs. Both names might then be used by new classes > with different meanings. This might be mitigated by introducing a > pre-/postfix for the names of the new classes. > >

3 3

Array(Object)>>errorSubscriptBounds: 777
by karl ramberg 25 Jan '19

25 Jan '19

Hi, I'm on Lubuntu and get a weird error from keyboard entering. It's an old swedish laptop with a button with two dots: ¨ for entering umlauts U+0308. When I press that key followed by a Ctrl I get the error Array(Object)>>errorSubscriptBounds: 777 Log attatched

2 1

[Off Topic] Michel Bauwens on the history and immediate future of work
by Eliot Miranda 25 Jan '19

25 Jan '19

Hi All, I find this talk profound and key to making functional open source communities as we try and survive. I’ve skipped an introduction in Portuguese and some slide control issues. https://youtu.be/vDjazcMm-eE?t=4m40s _,,,^..^,,,_ (phone)

2 1

Unload 45Deprecated and 46Deprecated?
by marcel.taeumel 25 Jan '19

25 Jan '19

Hi, there. Is it time to unload the packages "45Deprecated" and "46Deprecated" to see how it works out in the next weeks and months? Best, Marcel -- Sent from: http://forum.world.st/Squeak-Dev-f45488.html

3 2

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

Jump to page: