September 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] A solution to manage units like inches and centimeters in Pharo?
by Guillaume Larcheveque April 29, 2014

April 29, 2014

Does something exists because I looked and don't find anything. -- *Guillaume Larcheveque*

10 15

[Pharo-project] PluggableListMorph error, how to debug ?
by laurent laffont Jan. 13, 2014

Jan. 13, 2014

Hi, sometimes I have a PluggableListMorph that displays a big red square (see attached screenshot). How can I debug why this happens ? [image: Inline image 1] Cheers, Laurent

7 10

[Pharo-project] Suggestion about Phexample and StateSpecs(Mocketry) integration
by Denis Kudriashov Nov. 30, 2013

Nov. 30, 2013

Hello I think you read about Mocketry and know that It provides same "should syntax" DSL like project Phexample. There is problem between two projects. We both implement #should message in Object class. So when somebody want Phexample Mocketry become broken and vice versa. In the past I actually only read about Phexample tests reusage idea with #given message. And I didn't know that It provides "should syntax" too. Now I read about it and look at code (thank's Yuriy Tymchuk) and I have some suggestions about it. First few words about state of Mocketry project. Mocketry is not based on SSpec (I was google such wrong opinion). It is just implement SSpec idea about executable specifications and "should syntax". And specifications part with DSL was extracted from Mocketry to StateSpecs project. So Mocketry is only about mocks and behaviour specs. Idea of executable specifications is not about replacement "assert syntax" with "should syntax". It is about building reusable first class objects which can validate domain objects. For example there are EqualitySpec, ElementsCountSpec, ClassSpec. All this specs present "valid state" of objects. They know how to validate objects. State specs can be used in tests, UI and any other domain where you want put descriptions about what it mean "valid object". I start use StateSpecs in Presenty to build object editor. With specs I put requirements on model aspects. I am sure Magritte provides something similar in description objects. So StateSpecs solve very general problem: how to describe validation rules for objects and how to make such descriptions reusable. To make it convenient and readable StateSpecs provides two kind of DSL: - should syntax to immediately check object state - first class words to create spec instances with more readable way: Instance of: SomeClass, Equal to: #some, Containing item: arrayItem and others First option can be used in tests instead #assert: expressions. Last can be used in mock message arguments. StateSpecs provide very simple way to extend it DSL based on pragmas: Instance of: aClass <syntax: #(be an instance of:)> ^ClassSpec for: aClass Equal to: anObject <syntax: #(equal:)> <syntax: #(be equal:)> ^self return: (EqualitySpec pattern: anObject) Containing item: anObject <syntax: #(include:)> ^ElementContainmentSpec requiredElement: anObject And with this you can write: object should be an instance of: SomeClass object should equal: #some object should be equal: #some array should include: item. So with such approach both kind of DSL extended at one place. Ok. Now my main suggestion. Let's Phexample use StateSpecs for "should syntax". I can provide all "should protocol" of Phexample in StateSpecs. So it will be transparent for current users. It just few extra pragmas and classes in StateSpecs-DSL package. Maybe it is already done by Yuriy Tymchuk. With such integration both projects will just improved. What do you think? Best regards, Denis

6 19

Re: [Pharo-project] How to encrypt a password?
by Paul DeBruicker Nov. 22, 2013

Nov. 22, 2013

Hi Mariano, I've made a FFI library on Squeaksource that works on Linux. http://www.squeaksource.com/Cryptography/PasswordHashingFFI-PaulDeBruicker.… You need to install the 32 bit versions of libcrypt and libxcrypt if you're using a 64 bit linux os. Using crypt can hash passwords using MD5, DES, SHA256, SHA512. Using libxcrypt can hash passwords using bcrypt. If its for a new installation use bcrypt or SHA512 to hash the passwords. bcrypt is better because its slower, and allegedly future proof. to get a hashed password use BCryptLinuxFFI bcrypt:'mypassword' to check it against a stored hash use: BCryptLinuxFFI check:'mypassword' against: storedHash

4 10

[Pharo-project] TextAttribute, TextAction and TextDoIt or TextURL: not working
by phil＠highoctane.be Nov. 6, 2013

Nov. 6, 2013

I've been investigating with text. I found things that do work like: ((Text withAll: 'foo') , (Text string: '*' attribute: (TextAnchor new anchoredMorph: EllipseMorph new)) , (Text withAll: 'bar')) asMorph openInWorld. ((Text withAll: 'foo') , (Text string: '*' attribute: (TextAnchor new anchoredMorph: ThemeIcons confirmIcon)) , (Text withAll: 'bar')) asMorph openInWorld. But doing: ((Text withAll: 'foo') , (Text string: 'some link' attribute: (TextURL new url:'http://philippeback.eu')) , (Text withAll: 'bar')) asMorph openInWorld. gives me a nice purple 'some link' bit but clicking on it fails with MessageNotUnderstood: TextURL>>actOnClick:for:in:editor: Damn! Ideas on how to tackle this? TIA Philippe Back

5 7

About SqNumberParser
by StÃ©phane Ducasse Oct. 30, 2013

Oct. 30, 2013

Hi nicolas We would really like to have only one number parser in Pharo as well as handling the 1.0s syntax marcus raised a question that I could not answer. Do you habve nfrmation to share with us so that we can take a decision? Stef so the strange thing is that this is *explicitly* implemented in SqNumberParser to not allow 2.0s - do not allow single s without following digits as ScaledDecimal It is not explained why this is a good idea. In general, we need to merge the whole NumberParser hierarchy into one class, i don't understand why we have three classes now.

5 10

11635: Race condition in SequenceableCollection>>shuffle
by Max Leske Oct. 30, 2013

Oct. 30, 2013

Sven suggested posting this on the list for discussion, so here you go: > Maybe this should be discussed on the list, your are going to break API. > > Note that there is also #sort and #sorted with similar copy behavior. > > Also, I am not sure that basic operations should use mutexes to protect themselves by default: there is a cost when you are a single threaded user. Even in Java there are synchronized and non-synchronized versions of collections. IMHO, the protection should happen in your app, and basic collections do not have to be thread safe. > > Sven > >> #shuffle does not use Collection>>mutexForPicking as other users of #randomForPicking demonstrate. This can lead to race conditions (found in our application). >> >> In addition, there are now #shuffle, #shuffled, #shuffleBy: and #shuffledBy: where #shuffled and #shuffledBy: shuffle a copy and answers that. This is very confusing. >> >> I propose a fix where #shuffled and #shuffledBy: are renamed to #copyShuffle and #copyShuffledBy: and moved to the "copying" protocol. #shuffle and #copyShuffle will use the mutex to prevent race conditions.

6 17

[Pharo-project] Render images - Porting from Cincom VW to Pharo
by Emilia Oct. 15, 2013

Oct. 15, 2013

Hello! I'm porting code from Cincom Smalltalk to Pharo. It's a web application so I've got several WAComponent instances and one component which inherits from WAFileLibrary that renders images. In the original code ( the one that runned in VW) i had the following instance method in the component that inherits from WAFileLibrary: logoJpg ^ByteArray asPackagedString: '?=#?8@@PR$YIQ @A@ D@X@A @@C?8P))QW!)Y @@RT$*@@ @@@@G@AHA@0@......etc etc' But now when i run it in Pharo the debbugger doesn't recognize #asPackagedString: message. Does anyone know which method should I use in order to render that image? Thanks in advance! Mercy beaucoup! Emilia

4 5

Oct. 8, 2013

Hi paul I do not think that it is wise in the long term to have split repository. For example it does not really make sense to me to have a part of XMLSupport in your private project and another part in squeaksource. So we should - update soup to use XMLReader in SmalltalkHub - and publish gemstone package in their corresponding base project Managing conifguration is complex enough to make things as simple as we can. So are you interested in helping? Stef baseline14: spec <version: '1.4-baseline'> spec for: #squeakCommon do: [ spec blessing: #baseline. spec description: 'Migrated to SmalltalkHub'. spec author: 'StephaneDucasse'. spec timestamp: '21/02/2013'. spec repository: 'http://www.smalltalkhub.com/mc/PharoExtras/Soup/main'. spec package: 'Soup-Core' with: [ spec requires: 'XMLSupport' ]; package: 'Soup-Tests-Core' with: [ spec requires: 'Soup-Core' ]; package: 'Soup-Help' with: [ spec requires: 'Soup-Core' ]; package: 'Soup-XPath' with: [ spec requires: 'Soup-Core' ]; package: 'Soup-Zinc' with: [ spec requires: 'Soup-Core' ]. spec project: 'XMLSupport' with: [ spec className: 'ConfigurationOfXMLSupport'; versionString: #stable; repository: 'http://www.squeaksource.com/XMLSupport' ]. spec group: 'default' with: #('Core' 'Tests'); group: 'Core' with: #('Soup-Core' 'Soup-XPath'); group: 'Tests' with: #('Soup-Tests-Core') ]. spec for: #gemstone do: [ spec repository: 'http://www.smalltalkhub.com/mc/PharoExtras/Soup/main'. spec project: 'XMLSupport' with: [ spec className: 'ConfigurationOfXMLSupport'; versionString: #stable; repository: 'http://www.smalltalkhub.com/mc/pdebruic/XMLSupport/main' ]. spec package: 'SoupGemstone-Core' with: [ spec requires: 'XMLSupport' ]; package: 'Soup-Tests-Core' with: [ spec requires: 'SoupGemstone-Core' ]; package: 'Soup-Help' with: [ spec requires: 'SoupGemstone-Core' ]; package: 'Soup-XPath' with: [ spec requires: 'SoupGemstone-Core' ]; package: 'Soup-Zinc' with: [ spec requires: 'SoupGemstone-Core' ]. spec group: 'default' with: #('Core' 'Tests'); group: 'Core' with: #('SoupGemstone-Core'); group: 'Tests' with: #('Soup-Tests-Core') ].

3 4

How to test the same behavior with different data
by Noury Bouraqadi Oct. 7, 2013

Oct. 7, 2013

Hi, Last ESUG I attended the cool katas session organized by Stephan Eggermont and Laurent Laffont. That was a good opportunity to step back and think about my TDD practices . To experiment with the style proposed by Laurent, I started writing tests for a pong. I ended up having groups of nearly identical tests: -they use exactly the same objects, send the same messages, -but they differ only by values. An example, is testing the motion of the ball towards different directions or collisions with obstacles at different locations or speeds. Now, I wonder what is the best way to express those similar tests? In a short discussion before I leave, Stephane told me about tables of values. It seem that there is such a support in the ruby world in the cucumber framework. Do we have anything similar in Smalltalk world? BTW, the full ESUG conference was great. Thanx to local organizers, and all people that contributed to make it a success. Thanx, Noury Ecole des Mines de Douai http://car.mines-douai.fr/noury --

6 10