- Pharo-dev - lists.pharo.org

Github and Pharo
by kilon alios Nov. 4, 2013

Nov. 4, 2013

So any information on how Pharo can be used with Github ? all I have is this https://github.com/dalehenrich/FSGit I dont need much, just basic git pull, push, clone, add and rm should do fine for starter. But of course I am interesting into learning what can be done, what is available , who needs help with what. Github is something really important for me, so I am willing to contribute as much I can into bringing Pharo closer to it. My interest is using Github in place of smalltalkhub and squeaksource. I was planning to implement something like an App Store (not the purchase system) for Pharo libraries and I would love to use github as a backend to it and git of course.

9 28

Duplicate IVs | Bug or feature?
by Noury Bouraqadi Nov. 4, 2013

Nov. 4, 2013

Hi, In Pharo2.0 #20625 it's possible to create two classes, one inheriting from the other, and declaring the exact same IV (attached code). It turns out that instances of the subclass hold two IVs with the exact name. When accessing the IV in the superclass, the first IV is used, while in the subclass the second IV is accessed. Bug or feature? Noury Ecole des Mines de Douai http://car.mines-douai.fr/noury -- Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

4 4

About BitBlt current -> BitBlt (Fuel)
by StÃ©phane Ducasse Nov. 4, 2013

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

moving moose to pharo 3.0
by Tudor Girba Nov. 4, 2013

Nov. 4, 2013

Hi, We essentially finished moving Moose to Pharo 3.0 (we still have 6 yellow tests but they needed attention anyway). It took about 4 people looking into issues for a total probably around 2 man-days of effort. The largest impediment was actually SmalltalkHub being down for one day :). What posed problems: - RB visitor now has correct visit* methods instead of accept* methods. The deprecation messages helped quite a bit. This meant (1) that we had to rename in our visitors the methods, and (2) that we had to change the old accept* messages. - RB nodes do not answer to #isLiteral anymore. Instead, they answer correctly to #isLiteralNode so that to avoid confusion with Object>>#isLiteral. This is good, and this meant that we had to hunt all #isLiteral usages in Moose. - Categories are no longer mapped on RPackages through 1-to-1. This is also good because it is an important step in Pharo. Although originally we said we want to keep 1-to-1, this is probably a better solution now. For Moose, this meant that some of our older tests setup had to be modified a bit to rely on RPackage only. - Some Morphs rely now on Announcements, and this had a little impact on the assumptions we make when we suspend announcements (to avoid infinite loops) that are being sent between Morphic and Glamour. We fixed this in Glamour. - In FileSystem #ensureDirectory was renamed to #ensureCreateDirectory without a deprecation. For this one, we should add a deprecation for the old method. - flatCollect had a conflicting behavior in Pharo. We are now integrating the Moose version so that it returns the same species. - The new SpecDebugger expects the registered Inspector to be based on Spec, and this causes problems with the GTInspector. This problem still has to be fixed in Pharo. All in all, we encountered no significant problems and the problems we faced came from deep into Pharo. So, if your code is not relying directly on RB, RPackage or the Debugger, you are likely to have a smooth transition. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

4 4

Re: [Pharo-dev] WhatsUp from: 2013-11-04 until: 2013-11-17
by Stephan Eggermont Nov. 4, 2013

Nov. 4, 2013

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: Put out CFP for FOSDEM2014 devroom Lots of improvements to PetitDelphi http://www.flickr.com/photos/35787002@N03/sets/72157634356004836/ First step in making QCMagritte use new Bootstrap ### What's next, until 2013-11-17 (*): Handling of compiler directives for PetitDelphi, first ifdefs and includes Still a lot of parse errors to fix Diego & Stephan

2 1

[pharo-project/pharo-core]
by GitHub Nov. 4, 2013

Nov. 4, 2013

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

1 0

[pharo-project/pharo-core] b9350c: 30546
by GitHub Nov. 4, 2013

Nov. 4, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: b9350cb501d63bc764ddf6ac110d7f53977a798a https://github.com/pharo-project/pharo-core/commit/b9350cb501d63bc764ddf6ac… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-04 (Mon, 04 Nov 2013) Changed paths: M Fuel.package/extension/LargeNegativeInteger/instance/fuelAccept_.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/beginTestCase_time_.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/endTestCase.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/stackTraceString_of_.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/writeError_stack_.st M HudsonBuildTools20.package/HDTestReport.class/instance/private/writeFailure_stack_.st M HudsonBuildTools20.package/HDTestReport.class/instance/running/setUp.st M HudsonBuildTools20.package/HDTestReport.class/instance/running/tearDown.st M Morphic-Base.package/TextAnchor.class/instance/visiting/emphasizeScanner_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script201.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30546.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30546 12052 Fuel could store LargeNegativeInteger up to 32bits magnitude https://pharo.fogbugz.com/f/cases/12052 12067 A TextAnchor should never try to placeEmbeddedObject: by itself https://pharo.fogbugz.com/f/cases/12067 11906 HDTestReport measures the wrong duration https://pharo.fogbugz.com/f/cases/11906 http://files.pharo.org/image/30/30546.zip

1 0

https://gitorious.org/cogvm
by Camillo Bruni Nov. 4, 2013

Nov. 4, 2013

I cannot update the repository description on gitorious: https://gitorious.org/cogvm Who is in charge of the cogvm project on gitorious? Can the owner please add a link to the new github repository? #Moved to <http://github.com/pharo-project/pharo-vm>

1 0

Nov. 4, 2013

3 2

[pharo-project/pharo-core]
by GitHub Nov. 4, 2013

Nov. 4, 2013

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

1 0