August 2014 - Pharo-dev - lists.pharo.org

MongoTalk: new place on smalltalkhub
by FranÃ§ois Stephany July 23, 2015

July 23, 2015

Hi, I've just created a new team for MongoTalk on SmalltalkHub: http://www.smalltalkhub.com/#!/~MongoTalkTeam The old repo (http://www.smalltalkhub.com/#!/~francois/MongoTalk) will stay just in case some scripts rely on it but you should update to the new repo: http://www.smalltalkhub.com/#!/~MongoTalkTeam/mongotalk I've created a version 1.5.1 in the Metacello configuration to reflect the repo migration. Shout at me if I missed something! Cheers, Fa (Many thanks to Norbert for pushing the migration ;)

5 6

ctrl+a is seen as ctrl+home windows
by Tudor Girba May 31, 2015

May 31, 2015

Hi, I am on Windows, using Pharo 3.0, and I am trying to get the keybindings to work in Rubric using Windows convention (so, Ctrl instead of Cmd as a modifier), It worked reasonably well, but the problem is that somehow Ctrl+a is mapped to Ctrl+Home. The problem is not specific to Rubric as I can detect the same behavior in the regular PluggableTextMorph. Does anyone have an idea of where the problem comes from? Doru -- www.tudorgirba.com "Every thing has its own flow"

5 11

[Pharo-project] RTF reader/writer
by StÃ©phane Ducasse April 8, 2015

April 8, 2015

Hi guys Do you know if there is a library somewhere in Smalltalk to deal with RTF writing/saving? Stef

7 10

Keyboard Event Weirdness
by Sean P. DeNigris March 2, 2015

March 2, 2015

I put the following halt in HandMorph>>#handleEvent: anEvent isKeyboard ifTrue: [Transcript show: anEvent printString, ' keyChar: ', anEvent keyCharacter asString, ' keyValue: ', anEvent keyValue asString; cr]. Then I typed 'hi' in a Workspace and hit Cmd+a. Look at the weird Transcript output... [keyDown ''] keyChar: keyValue: 4 [keystroke 'h'] keyChar: h keyValue: 104 [keyUp ''] keyChar: keyValue: 4 [keyDown ''] keyChar: keyValue: 34 [keystroke 'i'] keyChar: i keyValue: 105 [keyUp ''] keyChar: keyValue: 34 [keyDown '<Cmd->'] keyChar: keyValue: 0 [keystroke '<Cmd-a>'] keyChar: a keyValue: 97 [keyUp '<Cmd->'] keyChar: keyValue: 0 It seems the keyUp/Downs do not have the correct charCode and the keyValue is different than the keystroke for the same key. What's going on here? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Keyboard-Event-Weirdness-tp4737056.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 6

[DEV] Systemd socket activation patch for the VM
by Max Leske Nov. 14, 2014

Nov. 14, 2014

Hi folks As promised a long time ago my colleague Nik Lutz has finalized the patch for the VM that enables socket activation with Systemd. I will quickly go over what the patch is supposed to achieve, how we plan to use socket activation and what (minimal) changes are necessary. Systemd Socket Activation: Systemd opens a (network-) socket and waits for connections. When the first client connects the assotiated service (VM) is started. Systemd indicates via environment variable (LISTEN_FDS) that it opened a network socket. Detailed documentation on socket activation with Systemd can be found here: http://0pointer.de/blog/projects/socket-activation.html Our scenario for socket activation: At Cmsbox we have hundereds of images running on a server, all of which listen on a dedicated network port for incoming connections. The server is powerful enough to run all these processes concurrently, especially since not every image receives requests all the time. With socket activation we could further lower the server load and free up resources for images with a high request rate. Images that donât receive any requests for a specified amount of time can be suspended automatically and reactivated when a request comes in. The VM Patch: The attached patch tries hard to be minimal. It defines a new socket type (ProvidedTCPSocketType) which you will also find in the image (Socket>>newSystemd). ProvidedTCPSocketType is special in that it can refer to an existing TCPSocket and does not necessarily entail the creation of a new socket. The changes in the image: - Socket>>newSystemd tries to open a new Systemd socket. - TCPListener>>haveSystemdAssignedPort tests if the LISTEN_FDS environment variable has been set by Systemd for the current process. - TCPListener>>primEnvironmentAtSymbol is a utility method that we need to check for the environment variable (IMPORTANT: copied from OSProcess; uses the OSProcess plugin) - TCPListener>>pvtNewListener: has been modified to include the check for the Systemd port. If the socket has been assigned by Systemd, use a Systemd socket, a TCP socket otherwise Quick Howto: - Adapt path to vm and image in pharo@.service - Take a Seaside image and FileIn systemd.cs (tested with http://seaside.st/distributions/Seaside-2.8.4.zip) - Save as 9999.image - Copy pharo@.service and pharo@.socket to /etc/systemd/system - As root run: systemctl daemon-reload systemctl start pharo(a)9999.socket - Open http://localhost:9999/seaside/config [- systemctl stop pharo(a)9999.socket] -> Upon connection pharo(a)9999.socket starts: pharo(a)9999.service (which would start .../9999.image) You can see this in action in the following screencast: http://youtu.be/MVPLZNKg5j8 We hope that this patch (or some version of it) will find its way into the VM. If you have any questions please feel free to ask. Cheers, Max (on behalf of Nik and the rest of Netstyle.ch)

5 4

Catch Response 500 error in ZnClient
by Nicolai Hess Oct. 3, 2014

Oct. 3, 2014

How to catch a ZnResponse(500 Internal Server Error) ? (see fogbugz issue 13905) I tried to add a ifFail:[....] block but it does not get called on this response. Nicolai

2 3

blogging about Pharo stuff? send me your link!
by Esteban Lorenzano Oct. 3, 2014

Oct. 3, 2014

I know, there are several concentrator pages like http://planet.smalltalk.org, etc. but I want to put your blog here: http://pharo.org/blogs So, please send me (in private, to not pollute this list) your Pharo related blog :) Esteban

5 8

Phexample: API Change Proposal (was Phexample: Image Destroying Bug)
by Sean P. DeNigris Sept. 25, 2014

Sept. 25, 2014

Reverting EyeInspector>>#updateList revealed the error when Phexample is used in latest Pharo 3.0... PhexMatcher uses #= as part of it's DSL e.g. "1 should = 1". Because it doesn't respond normally to #=, #hash is implemented to signal an error (self error: 'Don''t put a matcher into a dictionary. It does not behave ordinarily on ='). I guess the receiver inspector on the bottom left of the debugger keeps the items in a dictionary, so #hash gets called and everything blows up. The first thought that comes to my mind is that #= is "too cute" as a DSL. #= is too deep of a smalltalk concept to justify hijacking, AFAICT to avoid writing equals:. I removed #= and #hash from PhexMatcher, adding an #equals: with the former #= implementation, and everything seems to work. I don't have write access to http://smalltalkhub.com/mc/Phexample/Phexample/main/ and realize it's a big API change, so I committed the fix to http://smalltalkhub.com/mc/SeanDeNigris/SeansOutbox/main/ : Name: Phexample-SeanDeNigris.71 MAJOR API CHANGE: - change matcher #= to #equal: e.g. "1 should = 1" would now be written "1 should equal: 1" - update all code to use new API Motivation: the #= magic made it impossible to store matchers in dictionaries, and #hash was implemented to signal an error explaining as much. Unfortunately, #= and #hash are deeply ingrained Smalltalk concepts, and are assumed to work as expected. In Pharo 3.0, the debugger tried to put matchers in a dictionary, causing an infinite error loop whenever a matcher failed. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Phexample-API-Change-Proposal-was-Phexample-Image-Des… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 9

Re: [Pharo-dev] GToolkit in Pharo 4?
by Stephan Eggermont Sept. 22, 2014

Sept. 22, 2014

Just fix the configuration. Nothing there for pharo 4.x And as baseline012 refers to #development everywhere, you'll need to check all dependencies too Stephan

5 4

[issue tracker] back porting 4 to 3
by Marcus Denker Sept. 22, 2014

Sept. 22, 2014

Hi, When there are issues that people wan to have back ported, the easiest (which worked very nicely last year) is this: 1) add the âback portâ issue as the *parent* of the main issue tracker entry. 2) make sure to do a slice early, itâs very easy to do when it is not yet integrated in Pharo4 (by looking at the diff). Issue 13494: Backport Pharo3 Issue 13494: some fixe â> Issue 13494: some fix Then first the slice will be validated on Pharo4, then it will get integrated there. After that, the Issue for Pharo3 will get validate by the monkey, and the is ready integration. This makes sure that fixes are put to use and validated in Pharo4 before we even think about adding them to the stable release. Marcus

3 5