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

ensure: and assignments RB Rule
by stepharo Sept. 8, 2015

Sept. 8, 2015

Hi guys I'm revisiting all the RB rule and I'm puzzled by this one. Checks assignment to a variable that is the first statement inside the value block that is also used in the unwind block. [| `@temps | `var := `@object. `@.statements] ensure: [`var `@messages: `@args] Does anybody have an idea? Stef

7 14

NAtiveBoost error
by Alain Rastoul Aug. 1, 2015

Aug. 1, 2015

Hi, I have a problem with a nativeboost call, but I don't see what I do wrong. library function prototype is: int zmq_getsockopt (void *socket, int option_name, void *option_value, size_t *option_len); my calling method in pharo is: zmq_getsockopt: socket option_name: option_name option_value: option_value option_len: option_len <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode> ^self nbCall: #(int zmq_getsockopt (void *socket, int option_name, void * option_value, size_t* option_len) ) when I call it with ... optionValue := (NBExternalArray ofType: 'int') externalNew: 1. optionLen := (NBExternalArray ofType: 'size_t' ) externalNew: 1. [ optionValue at: 1 put: 0 . optionLen at: 1 put: (NBExternalType sizeOf: 'int') . rc := self zmq_getsockopt: socket option_name: option_name option_value: optionValue option_len: optionLen . value := optionValue at: 1 . ] ensure: [ optionValue free. optionLen free ]. ... I allways get an exception: "error during FFI call : nil" After stepping in NBFFICallout generation, I found something strange, the code generation seems not to be called because lastError stays at nil ? handleFailureIn: aContext nativeCode: aBlock lastError := self getErrorFrom: aContext lastError: NativeBoost lastError. >>getErrorFrom: aContext lastError: errorCode ... checks pragmas etc >>getErrorFrom: aContext lastError: errorCode ... lastError := aContext tempAt: method numTemps. => lastError = nil ??? shouldn't be ErrNoNativeCodeInMethod ? "install native code and retry the send" lastError = ErrNoNativeCodeInMethod ifTrue: [ ^ self generateCode: aBlock andRetry: aContext ]. never gets called ... "ok, we're out of options, signal an error here" ^ self signalError: lastError Could it be because I use this image on windows and unix ? Or because I had an exception at prototype parsing the first time because I forgot a ; at the end of the prototype ? Is my prototype correct or is it the origin of the error ? Is there a way to reset the lastError (aContext tempAt: method numTemps) ? I will try to reset it in debugger but may be there is a cleaner way ? would it be ok to change the test in handleFailure to (lastError = ErrNoNativeCodeInMethod) or:[ lastError isNil ] ? (I can open a bug in this case ) Any idea or comment is welcome Thanks in advance Alain

11 55

New methods for the String class
by Daniela Meneses July 31, 2015

July 31, 2015

Hi to all, As you may know I'm working on in some improvements for the String class. Until now I implemented some missing tests. Right now I'm looking forward to add new methods that could be useful based on Ruby API ( http://www.ruby-doc.org/core-2.1.0/String.html) These are a few of the methods that I'm planning to implement: - chomp(separator=$/) -> new_str - chop() -> new_str - ljust(integer, padstr='') ->new_str - next -> new_str - partition(sep) -> [head, sep, tail] Could you help to find out if these methods are already available for the String class? If you have any idea of new methods for the string class, will be really welcome. -- Cheers , Daniela Meneses

16 34

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

Playground and its current usability in Pharo4.0 Latest update: #40307
by Torsten Bergmann April 24, 2015

April 24, 2015

While I like that GTTools are in Pharo 4 now (thanks!!!) and allow all kind of neat things I basically ask myself if we forgot to remember usability on a few places: 1. the world menu item "Workspace" opens a window "Playground" including also a tab with the same name "Playground". => CONFUSING I would suggest that we rename the window "Workspace" and keep "Playground" for the initial tab. This is easy to fix and would also fulfill the expectation when a beginner grabbed an existing Smalltalk or Pharo book. 2. While in all UI interfaces (Windows, Linux, Mac) the order in the context menu is "Cut", "Copy", "Paste" the playground menu uses a different order "Copy", "Cut" "Paste". => CONFUSING again I would suggest to use the well known order "Cut","Copy","Paste". 3. When one uses "Inspect it" from the context menu it means - to run the code - and the resulting object is then "inspectable" in a new window On the other side "Do it and go" from the context menu means - to run the code - and the resulting object is then "inspectable" in a new pane (but same window) The intention of both menu items and also the result is the same, but the naming is different ("go" vs. "inspect"). But the only notable difference is that in one case the inspectable object is opening right to the existing pane in the other case a new window is opened. => CONFUSING and inconsistent This is harder to solve. Possible solutions are: 3a. We keep the "inspect" concept and name the menu items "Do and Inspect it" and "Inspect in new window" 3b. We keep "Do it" as before to run the code, also "Inspect it" which opens the new pane to the left in the same window. If someone wants to open a new inspector window he should keep SHIFT key pressed while running "Inspect it". This is a concept known from web browsers and other tools today, clicking on a link while pressing SHIFT opens a new window. 4. The icons in the context menu of Playground are not the same as the ones in the Pharo browsers. => CONFUSING and inconsistent They are just black and if one switches to the Pharo dark theme they stay black and therefore looking ugly and make nearly no sense on the dark grey menu background. For now we should use the known icons that we already have. Maybe currently they are hardcoded and may conflict with Moose vs. Pharo icons - but this could be solved with the Icon Theming. (In the long term I would like to see scalable icons in Pharo menues (instead of bitmaps) similar to "Fontawesome" in web browsers (two colors) or SVG based ones (more colors) as currently the icon does not scale when changing the menue font size). Sorry if it sound like a rant - but the intention of this mail is that we discuss (and hopefully fix) in order to improve. Maybe it is written too early after the initial integration, but I think the mentioned points should be easy to address. Unfortunately I'm additionally confused with the changed contribution process that has exceptions for specific packages like GT to fix it myself with the usualy bugs/slice cycle. Thanks T.

11 18

[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

Duration year
by Hilaire March 26, 2015

March 26, 2015

I saw some discussion about Duration and year calculus in the list Given that it is impossible to determine the number of days in a year without the calendar years, should not 365.25 be used in place of 365 to minimize the error ? So it could look like: Duration class >> years: aNumber ^ self days: (aNumber * 365.25) truncated seconds: 0 Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

12 22

Super fast delay
by Norbert Hartl March 10, 2015

March 10, 2015

I just recognized that Delay is working in a strange way on my linux box $ time pharo-vm-nox ./Pharo.image eval "(Delay forSeconds: 5) wait" a Delay(5000 msecs) real 0m0.158s user 0m0.136s sys 0m0.020s I use the vm from the ppa. What do you get when you execute it? Norbert

10 31

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