October 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

Smalltalkhub is exposing private information
by Norbert Hartl March 3, 2014

March 3, 2014

When you look at someones page you can read commit messages of packages that belong to a private project. You can't see the project nor the package but it is listed in recent activities. I filed a bug https://code.google.com/p/smalltalk-hub/issues/detail?id=32 Norbert

4 3

100% CPU usage on image resume
by Holger Hans Peter Freyther Feb. 16, 2014

Feb. 16, 2014

Hi, I saved an image and today I wanted to resume it. Everything comes up, for a second I can interact with it (e.g. move a window) but then the pharo VM goes to 100% CPU usage. I let it run while writing this email and it eventually aborted: C stack backtrace: ./pharo[0x80a0c0c] ./pharo(error+0x19)[0x80a0f69] ./pharo[0x80785d3] ./pharo[0x80786e1] ./pharo[0x8078f10] ./pharo[0x8090d97] ./pharo(ceStackOverflow+0x6a)[0x80946ea] [0x76ef122e] ./pharo(interpret+0x7a6)[0x8094f36] ./pharo(main+0x2b3)[0x80a18b3] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xf5)[0xb74bb8c5] Smalltalk stack dump: 0xbfd5c610 M SmallInteger(Number)>negative 0x3841=7200 0xbfd5c630 M SmallInteger(Integer)>* 0x3841=7200 0xbfd5c64c M SmallInteger>* 0x3841=7200 0xbfd5c668 M Duration>asNanoSeconds 0x790ddef4: a(n) Duration 0xbfd5c684 M Duration>= 0x7fe004a0: a(n) Duration 0xbfd5c6a0 M DateAndTime>asLocal 0x7fe00488: a(n) DateAndTime 0xbfd5c6c0 M DateAndTime>- 0x7fe0040c: a(n) DateAndTime 0xbfd5c6dc M DateAndTime>asSeconds 0x7fe0040c: a(n) DateAndTime 0xbfd5c700 M DateAndTime>< 0x78d2a5f8: a(n) DateAndTime 0xbfd5c71c M DateAndTime(Magnitude)>> 0x7fe0040c: a(n) DateAndTime 0xbfd5c73c M TimerScheduler>fireTimers: 0x77ef49ac: a(n) TimerScheduler 0xbfd5c764 I [] in TimerScheduler>runTimers 0x77ef49ac: a(n) TimerScheduler 0xbfd5c780 M BlockClosure>on:do: 0x78d2a60c: a(n) BlockClosure 0xbfd5c7a4 M [] in Dispatcher>dispatch 0x77ef4764: a(n) Dispatcher 0xbfd5c7c4 M BlockClosure>ensure: 0x78d2a798: a(n) BlockClosure 0xbfd5c7f0 I [] in Dispatcher>dispatch 0x77ef4764: a(n) Dispatcher 0xbfd5c810 I [] in BlockClosure>newProcess 0x78d2a634: a(n) BlockClosure Most recent primitives stack page bytes 4096 available headroom 3300 minimum unused headroom 3508 (last object overwritten) Aborted TimerScheduler/Dispatcher is code of mine but I wouldn't understand why this code is getting blocked and would eventually cause a stack overflow? holger

3 7

Call for Participation in the Smalltalk Devroom at FOSDEM2014
by Stephan Eggermont Jan. 13, 2014

Jan. 13, 2014

Call for Participation in the Smalltalk Devroom at FOSDEM 2014. http://www.fosdem.org, please forward " A devroom for the Pharo, Squeak, Amber, GST, EtoilÃ©, Seaside, Moose Smalltalk projects & Newspeak as derived language. Smalltalk environments offer a very high development productivity, unmatched by their successors. Come do some pair programming with us and experience yourself the advantages of a real OO environment" The meetup will take place Saturday, February 1, 2014, from 9AM until 5PM, building AW. This room has 72 seats, a VGA video projector and wireless internet. More information will be available later. If there are volunteers to record video content, the FOSDEM organization kindly offered to provide needed equipment & instructions. Please let me know if you would be willing to spend some time pointing a camera at a speaker. Proposals on content and format are welcome. People interested in running a session should send me an email at stephan ( @ ) stack ( dot ) nl with 'FOSDEM2014â in the subject and the following information: - Their name - The project they are associated with - A short bio, to be put on the website along with their speaker name - (optionally) a picture of themselves - The title of their session (which will go on the website and in the booklet) - A abstract describing the session in further detail. - The desired length of the session. - The desired time slot in which they want to hold the session. I will send out updates on a regular basis to the lists and anyone stating his interest. Suggested values for the duration are 55min, 25min, 6m40 (Pecha Kucha). The desired time slot is meant to help you prevent conflicts with other dev rooms in which you might have a talk or your travel arrangements. There are alternative, non smalltalk-specific tracks available: lightning talk and the main track The deadline for submissions is December 31, 23:00 GMT+1. Devroom related URLs: http://www.pharo-project.org http://www.squeak.org/ http://etoileos.com/ http://www.seaside.st/ http://smalltalk.gnu.org/ http://www.moosetechnology.org http://amber-lang.net http://newspeaklanguage.org/ http://www.esug.org First proposal already arrived: Stefan Marr proposed: I could give a presentation on SOM (Simple Object Machine) Smalltalk. I would especially go into detail of the Truffle-based and the RPython (PyPy) based implementations to show modern ways of language implementations with the goal of achieving high performance.

2 1

[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

Questions about Athens
by kilon alios Nov. 13, 2013

Nov. 13, 2013

I created a new subject About the problem to recreate it all it takes is a demo := AthensDemoMorph new openInWorld . It opens the morph with the Athens grey box, I save the image , close pharo, open pharo which reloads the image automagically and BOOM Red Box of Doom :) My other tries also are based on AthensDemoMorph since I cant find documentation to do things differently. So lets get to the questions 1) You say you have morphs using Athens that don't have this problem, care to explain further ? 2) How do I recreate automatically those surfaces ? 3) Do I need to instruct the image on load to reinitialize those objects ? 4) If yes How I do that ? You say its a major problem but yet its not an Athens bug. I know this is has to do with how image saves live objects and that NB calls are not part of the image hence creating the problem. 5) Are there ways to avoid the problem ? 6) Also why there is a Red Box of Doom in the first place ? 7) Why the debugger is not triggered as it should be ? 8) Is that critical a failure of Morphic ? 9) Why Athens even though is based largely on Cairo , and taking into consideration the intention to extend to other graphical interfaces, not following the Cairo design more closely so we can use the Cairo tutorials ? 10) Is the Cairo design so prohibiting / limiting for Athens ? Does Cairo do things so differently than other vector based libraries ? 11) How important is Athens to Pharo community , meaning further bug fixes, improvements , tutorials etc ? I hear there is an intention to gradual move Morphic to it. Is this true ? I really like Athens, I am asking all these questions because I need to make a fast decision whether I will continue to use Pharo or not for my project. Learning OpenGL and using NBOpenGL produced zero results for me. I was not even able to create a single triangle. My gpu driver because of Macos gave me close to zero errors, and Red Box of Doom made it impossible to debug opengl problems. In short close to zero error reporting made it a no go for me. So I fall back at much simpler solutions because I want to create my own GUI API. I see several solutions for this 1) Pharo Athens 2) Amber SVG / WebGL based Vector libs like Pixi / Athens / HTML5 + CSS 3) Python + PyQT + QT I rather stay with Pharo. But I already wasted months of doing nothing and going nowhere with NBOpenGL , I am tried of moving in circles. I am not frustrated cause I knew when I tried that OpenGL was very hard ( I was warned by several opengl people ) so failure was always an option , but I can no longer justify wasting my time getting nowhere. I dont need much from a graphic lib all I need is a) Stability . If it crashes regularly its no good b) Speed, if moving graphic elements around slows down (anything above 20%) dual cores , its no good c) Basic Feature set like , lines, curves , circles and ellipses , display of raster graphics, simple animations , import export of graphic formats, png , jpg and svg is enough. Looks like Athens satisfies b and c , I am not so sure about a. I am trying to understand Athens code from reading it, once again I am a big failure at understanding code. So is there any hope for someone like me , that he is not a very good coder, he is new to Pharo and he has a simple mind to use Athens to make a basic GUI API ? On Thu, Oct 31, 2013 at 6:07 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > On 31 October 2013 16:40, kilon alios <kilon.alios(a)gmail.com> wrote: > >> save the image while the morph is displayed, reload the image and in its >> place there is the big red box with the yellow X , reporting an error with >> Athens. I have reproduced the error on Windows too with the Athens >> examples. I assumed my explanation was clear , I hope its clear now. >> >> > no. not clear. which morph? what class, how you using it etc. > I have morphs which using Athens for drawing and i can save and load image > back and i don't have red squares of death. > > >> This means that its impossible to save an image with a morph using Athens >> displaying and have it reload back when the image is reloaded. >> >> The athens-surface, especially cairo surface is valid only within a > single session. > if you boot new image, you must recreate (or stop using) surface you used > in previous session. > Otherwise you will have red box of doom. > > And while i agree that this is pretty major problem (in terms of making > your morph to be session-aware > and in terms of managing external resources) i am far from calling it a > bug of Athens of any kind per se. > > > >> On Thu, Oct 31, 2013 at 5:05 PM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> >>> >>> On Oct 31, 2013, at 9:55 AM, kilon alios <kilon.alios(a)gmail.com> wrote: >>> >>> yes I am aware of the examples already, I am learning from them. Please >>> note I have found a bug with Athens, which looks to me pretty major. If I >>> save a morph using Athens >>> >>> >>> what do you mean save a morph >>> >>> and reload the image, >>> >>> >>> what do you mean? >>> >>> >>> I see the red box of doom. For example trying your example from >>> stackoverflow. Are you aware of this bug ? >>> >>> >>> On Thu, Oct 31, 2013 at 2:43 AM, Igor Stasenko <siguctua(a)gmail.com>wrote: >>> >>>> ah, yes , there's also examples in >>>> Athens-Examples package. >>>> >>>> >>>> On 31 October 2013 01:30, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> >>>>> >>>>> On 30 October 2013 23:02, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>> >>>>>> well I just asked if there is any kind of Documentation about Athens >>>>>> . Or should I just read the code and ask questions ? >>>>>> >>>>>> >>>>> the main source of documentation right now is class comments >>>>> and tutorial. >>>>> I've spent quite of a time commenting the central classes of athens, >>>>> hope that's helpful. >>>>> Of course this does not replacement for a well written docu, and that >>>>> needs to be done. >>>>> >>>>> >>>>>> >>>>>> On Wed, Oct 30, 2013 at 11:51 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: >>>>>> >>>>>>> i hope you satisfied with my answer. >>>>>>> you welcome to ask more, if you not :) >>>>>>> >>>>>>> >>>>>>> On 30 October 2013 22:32, dimitris chloupis <thekilon(a)yahoo.co.uk>wrote: >>>>>>> >>>>>>>> >>>>>>>> http://stackoverflow.com/questions/19694197/how-to-create-lines-with-athens >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Igor Stasenko. >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko. >>>>> >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>>> >>> >>> >>> >> > > > -- > Best regards, > Igor Stasenko. >

6 27

[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

Nov. 4, 2013

Hi I just pushed a change cleaning some strange usage. BitBlt was sometimes invoked via BitBlt current (which just returned the BitBlt class). Apparently in Squeak they removed it too. Now it touches Fuel so Fuel guys can you merge on your side too? https://pharo.fogbugz.com/f/cases/12009/BitBlt-current-BitBlt Stef

3 13