- Pharo-dev - lists.pharo.org

TWM and shortcuts
by phil＠highoctane.be March 25, 2014

March 25, 2014

In Pharo3, there seems to be new shortcuts going on. These do interfere with TWM ones (or the other way around). What to do to get this to work again? TWMKeyMapping>>buildKeyMappingOn: aBuilder <keymap> "See shortucts accessor to add/change a shortcut " self shortcutsActionAndKeysDo: [:action :keys| (aBuilder shortcut: action) category: self shortcutCategory default: keys do: [ self windowManager perform: action ]. ]. aBuilder attachShortcutCategory: self shortcutCategory to: PasteUpMorph.. TWMKeyMapping class>>shortcuts ^ { #minimizeAllWindows -> 'Minimize all windows' -> [$r command, $m command]. #maximizeAllWindows -> 'Maximize all windows' -> [$r command, $m shift command]. #tileVisibleWindows -> 'Tile visible windows' -> [$r command, $t command]. #tileLastUsedWindows -> 'Tile last used windows' -> [$r command, $l command]. #tileBrowsers -> 'Tile browsers' -> [$r command, $b command]. #tileWorkspaces -> 'Tile workspaces' -> [$r command, $z command]. #tileTesters -> 'Tile testers' -> [$r command, $u command]. #tileMonticellos -> 'Tile monticellos' -> [$r command, $c command]. #tileInspectors -> 'Tile inspectors' -> [$r command, $i command]. #tileDebuggers -> 'Tile debuggers' -> [$r command, $d command]. #tileChanges -> 'Tile changes' -> [$r command, $c shift command]. #tileTools -> 'Tile tools' -> [$r command, $t shift command]. #tileSystem -> 'Tile system windows' -> [$r command, $y command]. #snapshotWorld -> 'Snapshot current world state' -> [$r command, $s command]. #worldBackward -> 'Move to previous world state' -> [$r command, $p command]. #worldForward -> 'Move to next world state' -> [$r command, $n command]. #deleteCurrentSnapshot -> 'Delete current world state' -> [$r command, $d shift command]. #topWindowMoveLeft -> 'Move window to left area' -> [$r command, $1]. #topWindowMoveRight -> 'Move window to right area' -> [$r command, $2]. #topWindowMoveTop -> 'Move window to top area' -> [$r command, $3]. #topWindowMoveBottom -> 'Move window to bottom area' -> [$r command, $4]. #topWindowMoveTopLeft -> 'Move window to top left area' -> [$r command, $5]. #topWindowMoveTopRight -> 'Move window to top right area' -> [$r command, $6]. #topWindowMoveBottomLeft -> 'Move window to bottom left area' -> [$r command, $7]. #topWindowMoveBottomRight -> 'Move window to bottom right area' -> [$r command, $8]. #cycleClockwise -> 'Last visible window on stack come to top' -> [$r command, $>]. #cycleCounterClockwise -> 'First visible window on stack go to bottom' -> [$r command, $<]. #switchToNextWorld -> 'Switch to next world' -> [$r command, $r command] } Phil

1 0

Re: [Pharo-dev] threading in Pharo
by Stephan Eggermont March 25, 2014

March 25, 2014

Alexandre wrote: >I am working on a memory model for expandable collection in Pharo. Currently, OrderedCollection, Dictionary and other >expandable collections use a internal array to store their data. My new collection library recycle these array instead of letting >the garbage collector dispose them. I simply insert the arrays in an ordered collection when an array is not necessary >anymore. And I remove one when I need one. I hope you have large collections use multiple arrays? In other systems Iâve mostly found copying/moving the arrays to be more of a bottleneck. Why do you use 15% less memory? Stephan

1 0

Migration from Pharo 1.1 to 2.0
by Laurent Laffont March 24, 2014

March 24, 2014

Hi, is there a way to export / fileOut objects from Pharo 1.1 and reload them into Pharo 2.0 or 3.0 ? Cheers, Laurent

3 4

Just found, i can compile this:
by Igor Stasenko March 24, 2014

March 24, 2014

extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.

9 18

new website about Artefact
by olivier March 24, 2014

March 24, 2014

Hi, A website is now available about Artefact. Documentation and useful informations are grouped to help you to produce many and beautiful PDF documents with Pharo. https://sites.google.com/site/artefactpdf/ The pasta team

4 3

Created PetitParserExtension project
by Guillaume Larcheveque March 24, 2014

March 24, 2014

Hi everybody, I am using PetitParser a lot and had implemented some little tools that help me for writing or generating grammars. I put two of the most useful in the project PetitParserExtension ( http://smalltalkhub.com/#!/~Moose/PetitParserExtensions) the first one is useful when you generate grammars with lots of rules: A PPExtendedCompositeParser offers you a new way to create rules. Just define your rule as a method in the #rules protocol and it will be managed exactly like rules in PPCompositeParser. You will not have the limitation of 256 rules due to the instance variables limit but you will need to refer to your rule with the method #rule: in any other rule using it. You can mix PPCompositeParser and PPExtendedCompositeParser way to define rules. the second one is cool for token identification because it creates a parser that will parse in a time depending on token length and not the number of different tokens. A PPMultiStringParser is a tool able to create a really effective parser on a huge collection of Strings. This parser will match any string in this collection, and the longest one if two are matchable (( PPMultiStringParser on: #('tin' 'tintin')) parse: 'tintin' will match 'tintin' and not just 'tin') If someone else has implemented some tools around PetitParser, it will be great to put those all together so feel free to commit your tools in this project and to improve mines. -- *Guillaume Larcheveque*

1 0

Debugger acting up
by Diego Lont March 24, 2014

March 24, 2014

Hi all, I do not have a proper test case yet, but as I have seen it twice now I want to ask you guys if you have any problems with it. In a recent moose 5.0 image with seaside and some other suff loaded, the page would not load. Interrupting the image showed that the debugger was lost in the following loop: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: Originally it was a halt that caused the signal, and that should pop up the debugger, but instead of that it went into an infinite loop. Now I see that building Pier3 development on a pharo2 image also seems to causes this loop. The root cause is also in the mail, so maybe this is just the size of the stack ...: Startup Error: An attempt to use interactive tools detected, while in non-interactive mode Interactive Request: You are about to load new versions of the following packages that have unsaved changes in the image: Grease-Tests-Pharo20-Core If you continue, you will lose these changes: [0mNonInteractiveUIManager>>nonInteractiveWarning: NonInteractiveUIManager>>nonInteractiveRequest:title: NonInteractiveUIManager>>nonInteractiveRequest: NonInteractiveUIManager>>confirm:trueChoice:falseChoice:cancelChoice:default: MCMergeOrLoadWarning>>defaultAction UndefinedObject>>handleSignal: If anyone knows where this problem might come from, please put a mail on the mailing list. Cheers, Diego

2 1

Re: [Pharo-dev] FileSystemGit and Fuel final report
by Stephan Eggermont March 24, 2014

March 24, 2014

Great! I have a different (and lower priority) use case for the libgit2 bindings: Michael Feathers has done some history analysis on github repositories which weâve used at the SPA2011 egg race. Basically, commit info on method level for 4 ruby projects. I guess Iâd have to use the low level bindings to do similar things? Stephan

2 1

StHub Support Ticket
by Sven Van Caekenberghe March 24, 2014

March 24, 2014

Can someone please help Philippe Marschall who is having trouble saving to StHub ? His account is http://www.smalltalkhub.com/#!/~marschall He seems to be able to log in to the website part, but can't save anything. Not in the Seaside repositories, nor in a new Test repository that he just created. He was able to work normally until very recently (february). TIA, Sven

2 1

Re: [Pharo-dev] Mongo doc omits Smalltalk/Pharo
by Paul Davidowitz March 23, 2014

March 23, 2014

Sorry, I take it back -- it is mentioned here: http://docs.mongodb.org/ecosystem/drivers/community-supported-drivers/ (but may not be up to date). ----- Original message ----- From: Paul Davidowitz <pdavidow(a)fastmail.fm> To: pharo-dev(a)lists.pharo.org Subject: Mongo doc omits Smalltalk/Pharo Date: Sun, 23 Mar 2014 15:33:48 -0400 Smalltalk/Pharo should be mentioned here: http://docs.mongodb.org/ecosystem/drivers/

1 0