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

ZnEasy and https?
by StÃ©phane Ducasse Oct. 23, 2013

Oct. 23, 2013

hi sven I would like to fetch a file stored on github ZnEasy client url: 'https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics…'; get; response Else I tried to read zodiac code but I missed some examples. I tried to read the tests but I failed. Stef

2 3

[update 3.0] #30516
by Marcus Denker Oct. 23, 2013

Oct. 23, 2013

30516 ----- 11694 Trait methods wrong after recompiling the image https://pharo.fogbugz.com/f/cases/11694 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-MarcusDenker.584.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke…

3 5

The new fogbugz mails look nice :)
by Benjamin Oct. 23, 2013

Oct. 23, 2013

Just to say :P Ben

3 3

[pharo-project/pharo-core]
by GitHub Oct. 23, 2013

Oct. 23, 2013

Branch: refs/tags/30517 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 97519b: 30517
by GitHub Oct. 23, 2013

Oct. 23, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 97519bf22e86a3b42c647e4b4fe44a30921d2ec0 https://github.com/pharo-project/pharo-core/commit/97519bf22e86a3b42c647e4b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-23 (Wed, 23 Oct 2013) Changed paths: M OpalCompiler-Core.package/OCASTTranslatorForEffect.class/instance/visitor-double dispatching/visitArrayNode_.st M OpalCompiler-Core.package/OCASTTranslatorForEffect.class/instance/visitor-double dispatching/visitBlockNode_.st M OpalCompiler-Core.package/OCAbstractLocalVariable.class/instance/read%2Fwrite usage/isUninitialized.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/isRead.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/isUnused.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/markRead.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/markWrite.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script172.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30517.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30517 11975 Sync with Opal Repository https://pharo.fogbugz.com/f/cases/11975 http://files.pharo.org/image/30/30517.zip

1 0

Release mails and update summary
by Torsten Bergmann Oct. 23, 2013

Oct. 23, 2013

Marcus wrote: >do it. The problem is that not everything that would be nice can be done just because the day >has just 24 hours. No need to say this. We know that each others plate if full - but we all try to move Pharo forward. We all did in the past and hopefully will be able to continue to do so. But currently I'm completely LOST to even know in which direction the release management moves, its current state and what is planned for it. Just for demonstration: I only stumbled by accident on your mail regarding the release mails and that they will not be sent anymore. http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-October/085… Is it because you have no time to write them, is it because there is a "grand plan" to switch to a different process to make the updates reproducible? I dont know. Anything I know now from the mail is that I should now have to watch out for Github mails and need to find out more out the current github activities - before getting even a glue on whats going on or how to help. another example: Camillo talkes about "a complete fogbugz api written in pharo" - I can not find it when searching "fogbugz" on SmalltalkHub => I'm LOST again It's really hard to follow all the activities ...

2 2

Pharo-project.org success stories link to be revised a bit...
by phil＠highoctane.be Oct. 23, 2013

Oct. 23, 2013

As Doru mentioned, marketing of Pharo should be improved to get more traction. Now, on http://www.pharo-project.org/about/success-stories a serious bunch of links are not working, point to projects that are abandoning Smalltalk for Javascript (Language of Languages) - link goes to a page saying so -- bad karma. Even Esteban's Lawsuit Tracker is not the right URL (right one is * http://smallworks.com.ar/web/projects/lawsuitTracker)*. Looks like other projects are not there anymore, click on the links for issys or Ilon SA and end up waiting with nothing showing up. 2denker's http://taskfor.us/ is dead: 404 So, some fixing needed. Are there new things in progress? I guess that QCMagritte guys could show us something sexy. I am currently working on a new thing but it is too early to show. Anyway, who has web apps not listed should give a link and a screenshot or two. Phil

4 8

[pharo-project/pharo-core] 10bbe9: 30516
by GitHub Oct. 23, 2013

Oct. 23, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 10bbe99db39f5f25348dc1c9b74dd9755f1da1fc https://github.com/pharo-project/pharo-core/commit/10bbe99db39f5f25348dc1c9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-22 (Tue, 22 Oct 2013) Changed paths: M OpalCompiler-Core.package/extension/TBehavior/instance/compileAllFrom_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script171.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30516.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Traits.package/TBehavior.class/instance/accessing method dictionary/localSelectors.st A Traits.package/TBehavior.class/instance/accessing method dictionary/localSelectorsDo_.st Log Message: ----------- 30516 11694 Trait methods wrong after recompiling the image https://pharo.fogbugz.com/f/cases/11694 http://files.pharo.org/image/30/30516.zip

1 0

[pharo-project/pharo-core]
by GitHub Oct. 23, 2013

Oct. 23, 2013

Branch: refs/tags/30516 Home: https://github.com/pharo-project/pharo-core

1 0

Error-eating troll
by Igor Stasenko Oct. 22, 2013

Oct. 22, 2013

I got quite confused, why i got error in strange place, the culprit is this one: computeFullBounds [ self doLayoutIn: self layoutBounds ] on: Error do: [ :ex | "This should do it unless you don't screw up the bounds" fullBounds := bounds. ex pass ] used by this: fullBounds "Return the bounding box of the receiver and all its children. Recompute the layout if necessary." fullBounds ifNotNil: [ ^ fullBounds ]. "Errors at this point can be critical so make sure we catch 'em all right" self computeFullBounds. "This should do it unless you don't screw up the bounds" ^ fullBounds So, if error happens, it leaves fullBounds==nil and as result, any code which follows, tries to do something with that nil.. Sure thing it is much more fun figuring out why your morph is broken and where, when such nasty code hides errors. -- Best regards, Igor Stasenko.

1 2