July 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

[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

Can't open image file without write access
by Damien Cassou Sept. 6, 2013

Sept. 6, 2013

Hi, if I try to launch a Pharo image and the current user only has read access, I see a black window that never disappears. How can I launch an image without having write access to it? This is a problem for all pharo-based applications that companies will produce because they will probably be placed in read-only directories such as /usr/bin or /Applications or c:\program files -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

4 5

[Pharo-project] Issue 3015: When a test is restarted in the debugger, #tearDown and #setUp and not send
by Hernan Wilkinson Aug. 28, 2013

Aug. 28, 2013

Hi, I added a new issue (that I think it could be see as an improvement, not an issue) that is related to debugging a test case written with SUnit. The problem is that when you restart a test in the debugger (either by pressing the restart button or compiling the method again) the changes made by the test to the objects initialized in the #setUp are not rollbacked. This change sends the messages #tearDown and #setUp to the test when restarting it, therefore letting the test in the same state as when it was run in the first place. I uploaded the solution to this issue (or improvement) to pharo inbox under SLICE-Issue-3015-RestartingATestFromTheDebuggerSendsTearDownAndSetUp-HernanWilkinson.2 I hope you like it! Hernan. -- *HernÃ¡n Wilkinson Agile Software Development, Teaching & Coaching Mobile: +54 - 911 - 4470 - 7207 email: hernan.wilkinson(a)10Pines.com site: http://www.10Pines.com <http://www.10pines.com/>*

3 3

Large images reasons [WAS] Re: [Pharo-users] Pharo 2.0 with Seaside + DBXTalk + GlorpDBX + Magritte 3 + TWBS is getting slower and slower
by Mariano Martinez Peck Aug. 19, 2013

Aug. 19, 2013

OK, this was was my experiment.... Image fresh with all my app and dependencies loades: 30MB After using it for some days/weeks: 160MB. SpaceTally new printSpaceAnalysis showed: Class code space # instances inst space percent inst average size ByteString 2785 413144 116244078 69.90 281.36 Array 3712 181772 8466668 5.10 46.58 ByteArray 8574 1319 8186802 4.90 6206.82 Bitmap 3653 303 6656340 4.00 21968.12 CompiledMethod 22467 90554 5685374 3.40 62.78 After executing ImageCleaner cleanUpForRelease: 36MB Then...I searched which part of #cleanUpForRelease: was making the difference, and it was: Smalltalk cleanUp: true except: #() confirming: false. So now it was time to know WHICH class did the diference, so I modified #cleanUp: aggressive except: exclusions confirming: aBool in these lines: "Run the cleanup code" classes do:[:aClass| Transcript show: 'Image size before cleaning ', aClass name, ' : ', Smalltalk imagePath asFileReference size asString. aClass cleanUp: aggressive. 3 timesRepeat: [Smalltalk garbageCollect]. Smalltalk snapshot: true andQuit: false. Transcript show: 'Image size after cleaning ', aClass name, ' : ', Smalltalk imagePath asFileReference size asString. ] displayingProgress: [:aClass| 'Cleaning up in ', aClass name]. I then opened a Transcript, and evaluated Smalltalk cleanUp: true except: #() confirming: false. I went to prepare Mate, and when I come back, the result was, of course: "Image size after cleaning MCFileBasedRepository : 39744008" That clean up ends up doing: flushAllCaches self allSubInstancesDo: [:ea | ea flushCache] So it sends #flushCache to all instances of MCHttpRepository and MCFileBasedRepository. Now what I wanted to see if it there was a particular repo that could take most of the space (like package-cache). And indeed, it was...I modified #flushCaches to: flushAllCaches | file | file := 'repos.txt' asFileReference writeStream text. self allSubInstancesDo: [:each | file nextPutAll: 'Image size before cleaning ', each printString, ' : ', Smalltalk imagePath asFileReference size asString; cr. each flushCache. 3 timesRepeat: [Smalltalk garbageCollect]. Smalltalk snapshot: true andQuit: false. file nextPutAll: 'Image size after cleaning ', each printString, ' : ', Smalltalk imagePath asFileReference size asString;cr. ]. file flush; close. And then I looked in the 'repos.txt' file. My package cache repo cleaned 60 MB. Glorp cleaned 35MB. Seaside30 cleaned 10MB. So...cleaning cache of just 3 repos frees approx 100MB. The question is....can we flush the cache safely? If they are called "cache", then I guess yes, we can. Thoughts? Thanks, On Wed, Jul 31, 2013 at 10:48 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Guys, I have images also with seaside, magritte, glorp, postgresV2, etc > and it is also around 200MB. > I will try to do some research today and let you know. > > Cheers, > > > On Tue, Jul 30, 2013 at 8:55 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> >> On Jul 30, 2013, at 1:49 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> >> wrote: >> >> > the changes file contained passwords and I replaced the text. So >> offsets may be wrong due to that. >> > >> Yes, the first thing I wanted to do is to recompile everything. Does not >> work. >> >> > Memorymonitor is not doing fanct stuff. It just counts instances. >> > >> Yes, but maybe it holds on to these instances? >> >> Marcus >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

6 17

New PharoVM built
by Esteban Lorenzano Aug. 1, 2013

Aug. 1, 2013

Hi, I builded new versions of the vm, integrating latest changes from Eliot. This integration should fix some issues, between them the annoying "SmallInteger" problem. You can find it here: wget -O- get.pharo.org/20+vmLatest or directly here: http://files.pharo.org/vm/pharo/ (choose the one that fits the best for you, always the "latest") can you download and check? thanks, Esteban

4 12