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

[Pharo-project] [Ann] New version of Mocketry
by Denis Kudriashov Jan. 22, 2013

Jan. 22, 2013

Hello. I upload new version of Mocketry 2.1 to smalltalkhub http://www.smalltalkhub.com/#!/~dionisiy/Mocketry . Changes: 1) All code now migrated to smalltalkhub repository. New configuration with version 2.1 implemented accordingly. 2) State specs extracted to separate project "StateSpecs" with separate configuration. This project contains all object state specifications and validation stuff. Mocketry depends on it and only implements behaviour specs and mock objects. StateSpecs can be used in different projects. I use it in Presenty to describe data fields validness. 3) Main new feature is stub behaviour. You can teach mock for stubs with: mock stub someMessage willReturn: 'result' And then mock can receive #someMessage everywhere anytimes. So you don't need scenario block if you only need stubs behaviour. 4) Few state specs like dictionary should include: item at: #key It will be cool if Mocketry become part of Pharo tools. What I can do for this? Mock objects to me is main tool to design and implement flexible object systems. And Mocketry simplifies mock objects technique very much. Best regards, Denis

3 4

[Pharo-project] Closing unresolved issues
by Sean P. DeNigris Jan. 22, 2013

Jan. 22, 2013

For example... Issue 5656: Large fonts make tools slow http://code.google.com/p/pharo/issues/detail?id=5656 This issue has not been resolved, but the issue was closed, leading to this experience... - I just upgraded a project to 2.0 - I notice that the UI is very slow - a simple Spec dialog window with a few text fields and buttons takes ~4 seconds to open - I check the issue tracker because I remember I reported the bug already, but I don't find it in the open issues - I waste time because I think it must be something else - I finally expand my search through the issues and find my report was closed as invalid I'm not saying that this is wrong, just that I don't understand and want to share another perspective and come to the best solution... What benefit are we getting from closing these that is significant enough to justify this kind of experience (I'm sure I'm not the only one). Cheers, Sean -- View this message in context: http://forum.world.st/Closing-unresolved-issues-tp4664420.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 4

[Pharo-project] Fwd: [Moose-dev] ZnUrl, Encoding
by H. Hirzel Jan. 22, 2013

Jan. 22, 2013

I assume this question is better placed here .... I am interested in the answer as well. --Hannes ---------- Forwarded message ---------- From: Dennis Schenk <d.schenk(a)students.unibe.ch> Date: Tue, 22 Jan 2013 14:00:06 +0100 Subject: [Moose-dev] ZnUrl, Encoding To: Moose-related development <moose-dev(a)iam.unibe.ch> Hi all, I stumpled upon a problem with encoding of URLs in Pharo. I am using the Google Geocoding API. For example I want to get the result of: http://maps.googleapis.com/maps/api/geocode/json?address=Willemstad,+CuraÃ§… When one enters this in a Browser a correct JSON response is returned. If I do the following: *(Url absoluteFromText: ' http://maps.googleapis.com/maps/api/geocode/json?address=Willemstad,+CuraÃ§…<http://maps.googleapis.com/maps/api/geocode/json?address=Willemstad,+Cura%C…>') retrieveContents contents.* I get an error back grom Google. When digging through the code I found that in ZnHTTPSocketFacade the following happens: *' http://maps.googleapis.com/maps/api/geocode/json?address=Willemstad,+CuraÃ§…<http://maps.googleapis.com/maps/api/geocode/json?address=Willemstad,+Cura%C…>' asZnUrl * And the result of this is: http://maps.googleapis.com/maps/api/geocode/json?address=Willemstad,+Cura%C… * * Which Google does not know how to handle and then returns an error. Does anyone have an idea how I could get contents from a URL which has special chars like '*Ã§'?* Or is there a way to convert all special chars to to their 'normal' counterparts, like *Ã§ -> c?* * * Cheers, Dennis

2 1

[Pharo-project] [Issue Tracker] Status
by Marcus Denker Jan. 22, 2013

Jan. 22, 2013

Overall open issues: http://code.google.com/p/pharo/issues/list?can=2 Issues tagged 2.0: http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D2.0 It would be nice if everyone would check the issues that she/he is involved with and answer the question: "What needs to be done as the next step to move this issue forward to a state where we can close the entry?" If there are issues where *You* where supposed to do something for the last 6 Month but it turned out to be so non-important that you never did, please consider that maybe the report itself is not important enough to stay open. Marcus

2 2

[Pharo-project] What are the messages where we should always have a super send?
by StÃ©phane Ducasse Jan. 22, 2013

Jan. 22, 2013

Hi While looking at SmallLint rule, I saw a rule that ensures that a given method always performs a super send. Here is the current list: ^#(#release #postCopy #preBuildWith: #postOpenWith: #noticeOfWindowClose: #initialize postBuildWith:) and I'm cleaning the list because there are VW elements such as postBuildWith: but do we have some other to add? Stef

4 6

[Pharo-project] [ANN] Headless support for Cog Cocoa VM
by Mariano Martinez Peck Jan. 22, 2013

Jan. 22, 2013

Hello there, For a long time, Pharaoers and Squakers have been asking for headless support in the Cocoa VMs just as we have with Carbon VMs. Carbon is becoming a legacy framework so people needed this. I wanted to thanks Square [i] International <http://www.square-i.net/> for sponsoring me to implement such a support. Not only have they sponsored the development but they have also agreed to release it under MIT license for the community. This headless support will be included in the official Pharo VM and will be, therefore, accessible to everybody. The project is not yet finished but I do have a demo/prototype that I wanted to share with you so that you can test it and give me feedback. This VM should only work starting at OSX 10.6. *How to use it?* Basically it works this way: to have headless, just edit the Info.plist and set the flag LSBackgroundOnly to 1 (add the key if it is not present): <key>LSBackgroundOnly</key> <true/> When doing this, you don't even need the -headless anymore since, setting LSBackgroundOnly to 1, will cause the same effect (being the flag almost mandatory). If you don't want headless, put it to false or don't even put the key. If you don't set LSBackgroundOnly to 1 but send -headless, the VM will still be headless but you will see a little flash. If this flash bothers you, then set the flag. I am trying to get a way to avoid the "flash" while also avoiding to set LSBackgroundOnly to 1, but I still couldn't find it. Anyway, I think we can live with the current situation. *How to test it?* You should run the image with something like RFB or Seaside or whatever you can and then confirm if it is working even if you are headless. As a matter of testing, I saved an image with seaside running in the port 5555. You can get both, this Seaside image and the VM with headless from: https://www.dropbox.com/sh/r7qk49bxywk2xce/6N7-fdyx6V So if you run the VM headless with that image and go to localhost:5555, you should see that Seaside is running. I would appreciate if you can test it. And please let me know in which version of OSX you tried. Of course, the more of you who can test it, the better. Notice that this VM was compiled with LLVM GCC 4.2 and it may have some problems in older OSX versions (but I think it shouldn't). I still couldn't compile a VM with GNU GCC 4.2 as I get a crash :( *Expected results?* In headless mode, anything should be displayed (no window, no menu, no item in the dock and nothing appear when switching apps). When running headfull, everything should be normal. *Where is the code? *The code I have modified to the VM is committed to my own fork of the VM: https://gitorious.org/~marianopeck/cogvm/marianopecks-blessed Once the code is ready, I will do a pull request so that it can be integrated. Thanks everyone for the testing and feedback. Once again, thanks Square [i] International for sponsoring this great feature. Also thanks Esteban Lorenzano and Mark Smith for their incredible help. This was just the first prototype. I will keep you informed about possible progress. Best regards, -- Mariano http://marianopeck.wordpress.com

4 7

[Pharo-project] a test :) yet another one.
by StÃ©phane Ducasse Jan. 22, 2013

Jan. 22, 2013

2 1

[Pharo-project] is the list working?
by Tudor Girba Jan. 22, 2013

Jan. 22, 2013

Hi, I did not receive any mails today from the pharo-project mailing list (21.01.2013). Is it still working? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

3 2

[Pharo-project] ping
by Camillo Bruni Jan. 22, 2013

Jan. 22, 2013

1 0

[Pharo-project] [update 2.0] #20482
by Marcus Denker Jan. 22, 2013

Jan. 22, 2013

20482 ----- Issue 7261: Improve PharoUser>>#retrieveGravatarFromMail:size: ZnClient usage http://code.google.com/p/pharo/issues/detail?id=7261 Issue 7267: Update Pharo License String to 2013 http://code.google.com/p/pharo/issues/detail?id=7267 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.761.diff http://ss3.gemstone.com/ss/Pharo20/KeyChain-MarcusDenker.27.diff

1 0