Squeak-dev April 2014

squeak-dev@lists.squeakfoundation.org

44 participants
77 discussions

Daily Commit Log
by commits＠source.squeak.org 20 Apr '14

20 Apr '14

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2014-April/007000.html Name: KernelTests-dtl.265 Ancestors: KernelTests-nice.264 Add DateAndTimeTest>>testAsStringFromString to verify parsing and printing across a wide time range. Fix DateAndTimeTest>>testReadFrom to restore its apparent original intent. =============================================

1 0

open paren/brace/bracket...
by Eliot Miranda 19 Apr '14

19 Apr '14

Hi All, first, excuse the venting. Who the %*&^$# decided to inflict the "always type a matching open/close pair" when typing any of ( [ { etc on us? Would that person please consider commiting hara kiri? OK, now slightly calmer, I find it /exceedingly/ annoying. Is this really an appropriate default? How does one turn it off? The cases that send me up my *&%$^# tree are when I intend to add a single one in front of some string when I go back to edit some text (e.g. add an exception handler around some phrase). Here, typing the pair *is just broken*. Doing it at the end of a text or at the end of line is defensible. Doing it always IS F*&^%$*G BROKEN. -- unhappily, Eliot

10 31

The Trunk: KernelTests-dtl.265.mcz
by commits＠source.squeak.org 19 Apr '14

19 Apr '14

David T. Lewis uploaded a new version of KernelTests to project The Trunk: http://source.squeak.org/trunk/KernelTests-dtl.265.mcz ==================== Summary ==================== Name: KernelTests-dtl.265 Author: dtl Time: 18 April 2014, 9:40:18.546 pm UUID: b53640c7-174e-4b68-8298-a4886b8b4098 Ancestors: KernelTests-nice.264 Add DateAndTimeTest>>testAsStringFromString to verify parsing and printing across a wide time range. Fix DateAndTimeTest>>testReadFrom to restore its apparent original intent. =============== Diff against KernelTests-nice.264 =============== Item was added: + ----- Method: DateAndTimeTest>>testAsStringFromString (in category 'Tests') ----- + testAsStringFromString + "Convert to string then back, verify same date and time. Skip years in the + range 0 to 99 because they are interpreted relative to 2000." + + | day hour dt min mo nano offset sec dtNew s | + mo := 12. + day := 2. + hour := 2. + min := 3. + sec := 4. + nano := 5. + offset := 6 hours. + (-2000 to: -1) , (100 to: 5000) do: [:yr | + dt := DateAndTime + year: yr month: mo day: day + hour: hour minute: min second: sec nanoSecond: nano + offset: offset. + s := dt asString. + dtNew := DateAndTime fromString: s. + self assert: dt equals: dtNew]. + ! Item was changed: ----- Method: DateAndTimeTest>>testReadFrom (in category 'Tests') ----- testReadFrom + self assert: '-1199-01-05T20:33:14.321-05:00' equals: (DateAndTime readFrom: '-1199-01-05T20:33:14.321-05:00' readStream) printString. + self assert: '-1199-01-05T20:33:14.321-05:00' equals: '-1199-01-05T20:33:14.321-05:00' asDateAndTime printString. + self assert: '2002-05-16T17:20:45.1+01:01' equals: '2002-05-16T17:20:45.1+01:01' asDateAndTime printString. + self assert: '2002-05-16T17:20:45.02+01:01' equals: ' 2002-05-16T17:20:45.02+01:01' asDateAndTime printString. + self assert: '2002-05-16T17:20:45.000000009+01:01' equals: '2002-05-16T17:20:45.000000009+01:01' asDateAndTime printString. + self assert: '2002-05-16T17:20:00+00:00' equals: ' 2002-05-16T17:20' asDateAndTime printString. + self assert: '2002-05-16T17:20:45+00:00' equals: '2002-05-16T17:20:45' asDateAndTime printString. + self assert: '2002-05-16T17:20:45+01:57' equals: ' 2002-05-16T17:20:45+01:57' asDateAndTime printString. + self assert: '2002-05-16T17:20:45-02:34' equals: ' 2002-05-16T17:20:45-02:34' asDateAndTime printString. + self assert: '2002-05-16T17:20:45+00:00' equals: '2002-05-16T17:20:45+00:00' asDateAndTime printString. + self assert: '1997-04-26T01:02:03+01:02:3' equals: '1997-04-26T01:02:03+01:02:3' asDateAndTime printString! - self assert: ((DateAndTime readFrom: '-1199-01-05T20:33:14.321-05:00' readStream) printString = '-1199-01-05T20:33:14.321-05:00'). - - - !

1 0

handlesMouseStillDown:
by Chris Muller 18 Apr '14

18 Apr '14

I have a custom morph that overrides handlesMouseStillDown: to return true. Simply by doing only that, it causes WorldState>>#drawWorld:submorphs:invalidAreasOn: to send #fullDrawMorph: with my Morph as the argument on every MouseMove event over my morph, regardless whether any button is down or not. I only noticed it because the rapid redrawing causes a slight flickering in my Morph. Setting handlesMouseStillDown: back to false, my morph's redrawing code is not executed at all when I move through it. I have no idea why simply handling this event causes the rapid redrawing. Thanks for any suggestions..

3 2

[Q] This is a bug ?
by Edgar J. De Cleene 17 Apr '14

17 Apr '14

Folks: I trying to revive a old network game based in Risk. I have a very old 3.10 .image working When I do Socket initializeNetwork. self ip: NetNameResolver localAddressString. Have '192.168.1.100' as value. In recent Squeak have '0.0.0.0' as value. This is know ? I doing some wrong ? Edgar

2 2

Re: [squeak-dev] how to break 4.5...
by Lawson English 16 Apr '14

16 Apr '14

Great! and thanks for the listing (I keep forgetting to save my workspace code from the videos :-/) Am I right in thinking this really shouldn't permanently lock things up , even though its an obvious bug in my code? It would be a common noob mistake and pretty awful to have happen as your first encounter with a Squeak bug. L On 4/15/14, 3:19 PM, gettimothy wrote: > First, thanks for an awesome vid. Very informative. > > > |myMorphs| > myMorphs := Array new: 360. > 0 to: 359 by:15 do:[:i | myMorphs at: i+1 put:((NCCurveMorph new) > extent: 20@20; > openInWorld; > center: (450@330) + (300 *((i degreesToRadians cos)@(i > degreesToRadians sin))); yourself)]. > > > 1 to:(myMorphs size - 1) do:[:i | > i+1 to: myMorphs size do:[:j | > ((myMorphs at:i ) ~= nil and:(myMorphs at:j ) ~= nil) > ifTrue:[NCAAConnectorMorph fromMorph: (myMorphs at:i) > toMorph:(myMorphs at:j)]]] > > "tty Debug Lock" > NCAAConnectorMorph allInstances do:[:each | each lock:True]. > "This locks it" > NCAAConnectorMorph allInstances inspect. > "about 285 instances" > Transcript clear. > NCAAConnectorMorph allInstances do:[:each | Transcript show: (each > bounds);cr. ]. "works" > NCAAConnectorMorph allInstances do:[:each | Transcript show: (each > bounds);cr. each lock:true ]. "works" > NCAAConnectorMorph allInstances do:[:each | each lock:true]. "works" > True inspect. > true inspect. > NCAAConnectorMorph allInstances do:[:each | each lock:(True > initializedInstance)]. "works" > > > I was able to recreate the lockup you described. > Changing the lock:True to lock:true (all lowercase) does not cause the > lock up. > > You can work through the reasoingin with the "tty Debug Lock" section > in the above code. > > If you do the two inspect statements at the bottom, you will see you > where passing the "True class" instead of the instance "True". > > cordially, > > tty > > > > -- Squeak from the very start (introduction to Squeak and Pharo Smalltalk for the (almost) complete and compleate beginner). https://www.youtube.com/playlist?list=PL6601A198DF14788D&feature=view_all "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian Kernighan

2 1

how to break 4.5...
by Lawson English 16 Apr '14

16 Apr '14

Well, maybe not break, but definitely make unusable for me with no way to back out that I am aware of. First, install the Connectors package then, create the fully-connected graph that I create in: https://www.youtube.com/watch?v=JwwjOO84Sn8 Now, try to disable any kind of user interaction for edges of the graph by doing: NCAAConnectorMorph allInstances do: [:ea| ea lock: True]. Yes, its the wrong syntax. Yes I'm stupid. But Squeak is now permanently locked, and I can't get around it except by force-quiting that I can see. Squeak appears to freeze. numerous cmd-periods bring up a buncha "NonBooleanReceiver: proceed for truth" messages, none of which can be interacted with (not close window, not click any button, etc) and eventually cmd-period doesn't do anything either. No menus work, etc. Clicking inside the Squeak window actually slows down the Mac GUI when dragging the Squeak window for a while. It seems clear the interpreter is still running, but interface via the GUI is hosed. Eep. In case you were wondering, I was trying to see if I could disable mouse-interaction with the edges of the graph as a way of speeding up and making more reliable, interaction with the nodes... Lawson -- Squeak from the very start (introduction to Squeak and Pharo Smalltalk for the (almost) complete and compleate beginner). https://www.youtube.com/playlist?list=PL6601A198DF14788D&feature=view_all "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian Kernighan

2 1

SqueakMap server
by Chris Muller 15 Apr '14

15 Apr '14

>> ... >> 3. I'm interested in hearing what you have to say about the design of a >> new SMServer, even if you're hysterical about. But I would appreciate it if >> you would allow me to respond in my own time. As you may know, I put a lot of time and thought and work into SqueakMap. The goal has always been for the community to have one single source for information about all or most Squeak-based software, to the extent that, anyone who wants published software to be noticed by Squeaker's will want it to be "in Squeak's app store" too. When you first said replace the server, I thought you meant replace the implementation and look-and-feel of the web-UI per your discretion. That would be great. Not only would the community end up with a new SM server running on 4.5/Cog, it'd also be a signature-example of a web-app to learn from that has browse, search, user-accounts and a callout API. Then when I saw your revamp of the requirements and that something about the "closet" and, remembering past events, I wondered while I was reading it whether all my work had already gone "poof". Had to check. Whew! Downloaded a backup of entire SqueakMap. We don't have to be friends to do good for the SqueakMap server (though it would be preferable, of course). I've had this on my own to-do list to replace because I want to learn web and it's a good example-app. I don't think it'll be a "quick-and-done" at all, because all the requirements serve a needed purpose and integrate into a overall process. If you're willing to retain "SqueakMap" as we know it today, with the domain model and all the critical functionality intact, I'd welcome that.

4 12

Re: The new site looks great! [EOM]
by Chris Cunnington 15 Apr '14

15 Apr '14

>There have recently been some very impressive announcements from Michael Perscheid about the Path Tools Framework OK. I'll add a link in the Projects section. Eliot's right about the link to squeakvm.org. It's the first at the bottom of the Virtual Machine page. Chris

4 4

old school 4.5 and is cog now the standard VM for Squeak 4.5 all-in-one?
by Lawson English 14 Apr '14

14 Apr '14

So, the question is: how does one create the old school Squeak distribution of source/image/chages files + a VM application? There's no documentation for that on the new website that I can find, and while I'm pretty sure I can sorta tease things apart in the Mac all-in-one and combine them properly in a folder, I'd prefer a standardized way to do it that I can point people to. Also, is it true that Squeak 4.5 all-in-one is now using the Cog VMs? Is that standard on all platforms, and is it the stack interpreter or the accelerated version? How does one make sure that the fastest version is being used, BTW? Thanks. Lawson -- Squeak from the very start (introduction to Squeak and Pharo Smalltalk for the (almost) complete and compleate beginner). https://www.youtube.com/playlist?list=PL6601A198DF14788D&feature=view_all "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian Kernighan

4 3