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

Re: [Pharo-project] Magritte and Spec

by stephane ducasse

:) is it based on Magritte 3 > Since I'm using Spec for all my Pharo UIs, I'm interested in having Spec as the backend to Magritte. If anyone is interested, I started an experiment at http://ss3.gemstone.com/ss/SpdPlayground/ . Look for the Magritte-Spec package. > > Cheers, > Sean

Feb. 20, 2013

Re: [Pharo-project] New Issue Tracker

by stephane ducasse

thanks christophe :) For me this would be ok. Is there an API for scripting it? Stef > Hi all, > > I quickly developed a basic importer (Google code => Jira) so that everyone can play a bit with real data. > There is still a lot of missing stuff that we can import (ex: labels, author) but I will only do that once we agree on the new bugtracker to choose. > > So, we have a free Jira instance available at https://pharo-project.atlassian.net/browse/DEMO (there is already a Pharo project but I prefer to not pollute it with tests). > Direct acces to issues: https://pharo-project.atlassian.net/issues/?jql=project%20%3D%20DEMO > I configured the minimum. We can tune this portal if needed. > > If you want to play, first register and ask me to become a project member. > > Cheers, > Christophe. > > Le 12 fÃ©vr. 2013 Ã 14:16, Camillo Bruni a Ã©crit : > >> After a discussion with Christophe which is in favor of JIRA ;) we decided to put a >> wiki page online where we should list all the requirements (not just the ones I think >> are important :P) >> >> https://code.google.com/p/pharo/wiki/NewIssueTracker >

Feb. 20, 2013

Re: [Pharo-project] Metacello issues on Pharo 2.0

by stephane ducasse

I could not load in Pharo 2.0 latest (ConfigurationOfMetacello project version: '1.0-beta.32') load: 'Tests' Stef

Feb. 20, 2013

Re: [Pharo-project] Metacello issues on Pharo 2.0

by stephane ducasse

Hi christophe We should clear up this issue. Did you make progress on that front? The answer of dale are not really giving my hope. I do not want to base all our infrastructure on a tool that we do not know if it will be maintained. Stef On Feb 15, 2013, at 3:09 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Hi all, > > I have issues with Metacello on Pharo 2.0 > > If I load and run tests for the version used in Pharo1.4, it gives: > (ConfigurationOfMetacello project version: '1.0-beta.31.1.4') load: 'Tests' > > <Capture dâÃ©cran 2013-02-15 Ã 14.45.15.png> > > Metacello packages shipped with Pharo 2.0 are all packages derived from the latest stable Metacello baseline (1.0-beta.31.1.5) except the MetacelloToolBox. > If I load and run tests packages with version described in the latest stable Metacello baseline (1.0-beta.31.1.5), i.e. : > Metacello-TestsCore-DaleHenrichs.14 and > Metacello-TestsMC-dkh.351, > it gives (Pharo 2.0 #20547): > <Capture dâÃ©cran 2013-02-15 Ã 14.55.36.png> > > So, it seems there are some problems. Do we use the rigth versions of Metacello packages? > > Regards, > Christophe. > >

Feb. 20, 2013

Re: [Pharo-project] Metacello issues on Pharo 2.0

by StÃ©phane Ducasse

Dale We are investing massively on metacello so now this is important for us to know if you will continue to maintain it or not. Because if this is not the case then we will have to rethink our strategy. Stef > Christophe, > > I'm not exactly sure what your problem is ... > > I have to admit that I haven't kept up with Pharo2.0 since last summer when I couldn't use Pharo2.0 for development because of OsProcess issues. I know that recently those issues have been cleared up, but I haven't had the time to return to Pharo2.0 and check things out (I'm facing more issues with getting PHaro2.0 to work with travis-ci, etc. so it will be a big undertaking for me to fully support Pharo2.0). > > I've got a fairly recent Pharo2.0 image and it looks like there are pharo-specific versions for each of the packages loaded into Pharo2.0. I assume that the tests are all passing with those versions, although I can't say whether or not the tests had to be modified to pass in Pharo2.0 as well ... which is likely to be a source of one of the problems you are looking at ... > > I don't know where the configuration exists that is being used to manage the changes for Pharo2.0 and the tests, but that is probably a good starting point ... if you are not using the proper Pharo2.0 configuration, you won't be getting the proper packages loaded ... > > Dale > ----- Original Message ----- > | From: "Christophe Demarey" <Christophe.Demarey(a)inria.fr> > | To: metacello(a)googlegroups.com > | Cc: Pharo-project(a)lists.gforge.inria.fr > | Sent: Friday, February 15, 2013 6:09:27 AM > | Subject: [Pharo-project] Metacello issues on Pharo 2.0 > | > | Hi all, > | > | I have issues with Metacello on Pharo 2.0 > | > | If I load and run tests for the version used in Pharo1.4, it gives: > | (ConfigurationOfMetacello project version: '1.0-beta.31.1.4') load: 'Tests' > | > | > | > | Metacello packages shipped with Pharo 2.0 are all packages derived from the > | latest stable Metacello baseline (1.0-beta.31.1.5) except the > | MetacelloToolBox. > | If I load and run tests packages with version described in the latest stable > | Metacello baseline (1.0-beta.31.1.5), i.e. : > | Metacello-TestsCore-DaleHenrichs.14 and > | Metacello-TestsMC-dkh.351, > | it gives (Pharo 2.0 #20547): > | > | > | So, it seems there are some problems. Do we use the rigth versions of > | Metacello packages? > | > | Regards, > | Christophe. > | > | > | > Chr >

Feb. 20, 2013

Re: [Pharo-project] Travis CI and Pharo 2.0 Was: Metacello issues on Pharo 2.0

by Camillo Bruni

On 2013-02-20, at 17:28, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi Dale: > > On 20 Feb 2013, at 16:15, Dale Henrichs wrote: > >> I have to admit that I haven't kept up with Pharo2.0 since last summer when I couldn't use Pharo2.0 for development because of OsProcess issues. I know that recently those issues have been cleared up, but I haven't had the time to return to Pharo2.0 and check things out (I'm facing more issues with getting PHaro2.0 to work with travis-ci, etc. so it will be a big undertaking for me to fully support Pharo2.0). > > I have a working build with Travis. > Well, working in the sense that it executes my unit tests. > The tests actually fail for other reasons. > See https://travis-ci.org/smarr/LibGit > > I use basically the CI infrastructure provided by Pharo 2.0. Guess that's Camillo's work. > https://github.com/smarr/LibGit/blob/master/.travis.yml > > > I happen to use a makefile: > > libgit.image: latest.image > $(NBCOG) -headless $< config http://smalltalkhub.com/mc/StefanMarr/LibGit/main ConfigurationOfLibGit --install=bleedingEdge > mv latest.image libgit.image > mv latest.changes libgit.changes > > LibGit-Core-Tests-Test.xml: libgit.image > $(NBCOG) -headless $< test --junit-xml-output LibGit-Core-Tests > > The only problem for the build status is to report the correct error code to travis, I think. > > As I understand it, Travis doesn't actually care about parsing or understanding test results, which is a pity. If you run the normal cli test runner (without --junit-xml-output) you get colored test unit results on the terminal and a ext 1 if a test fails ;) But I think it stops on the first test failing...

Feb. 20, 2013

[Pharo-project] Travis CI and Pharo 2.0 Was: Metacello issues on Pharo 2.0

by Stefan Marr

Hi Dale: On 20 Feb 2013, at 16:15, Dale Henrichs wrote: > I have to admit that I haven't kept up with Pharo2.0 since last summer when I couldn't use Pharo2.0 for development because of OsProcess issues. I know that recently those issues have been cleared up, but I haven't had the time to return to Pharo2.0 and check things out (I'm facing more issues with getting PHaro2.0 to work with travis-ci, etc. so it will be a big undertaking for me to fully support Pharo2.0). I have a working build with Travis. Well, working in the sense that it executes my unit tests. The tests actually fail for other reasons. See https://travis-ci.org/smarr/LibGit I use basically the CI infrastructure provided by Pharo 2.0. Guess that's Camillo's work. https://github.com/smarr/LibGit/blob/master/.travis.yml I happen to use a makefile: libgit.image: latest.image $(NBCOG) -headless $< config http://smalltalkhub.com/mc/StefanMarr/LibGit/main ConfigurationOfLibGit --install=bleedingEdge mv latest.image libgit.image mv latest.changes libgit.changes LibGit-Core-Tests-Test.xml: libgit.image $(NBCOG) -headless $< test --junit-xml-output LibGit-Core-Tests The only problem for the build status is to report the correct error code to travis, I think. As I understand it, Travis doesn't actually care about parsing or understanding test results, which is a pity. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Feb. 20, 2013

[Pharo-project] method overiden ColorForm>>blankCopyOf: aRectangle scaledBy: scale

by jannik laval

Hi all, I do not understand why this method is redifined with a fixed class. Jsut see the method: ColorForm>>blankCopyOf: aRectangle scaledBy: scale ^Form extent: (aRectangle extent * scale) truncated depth: 32 where in Form, there is a better method: Form>>blankCopyOf: aRectangle scaledBy: scale ^ self class extent: (aRectangle extent * scale) truncated depth: depth My idea is just to remove this method. Is it ok ? The issue is Issue 7556<http://code.google.com/p/pharo/issues/detail?id=7556> -- ~~Dr. Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu

Feb. 20, 2013

Re: [Pharo-project] Inbox in SmalltalkHub ?

by Sean P. DeNigris

Nicolas Petton wrote > an inbox per project... will be back (and working this > time!) soon :) Hooray!! Thank you Nico, that will be very valuable :) -- View this message in context: http://forum.world.st/Inbox-in-SmalltalkHub-tp4670969p4671031.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 20, 2013

Re: [Pharo-project] Metacello issues on Pharo 2.0

by Dale Henrichs

Christophe, I'm not exactly sure what your problem is ... I have to admit that I haven't kept up with Pharo2.0 since last summer when I couldn't use Pharo2.0 for development because of OsProcess issues. I know that recently those issues have been cleared up, but I haven't had the time to return to Pharo2.0 and check things out (I'm facing more issues with getting PHaro2.0 to work with travis-ci, etc. so it will be a big undertaking for me to fully support Pharo2.0). I've got a fairly recent Pharo2.0 image and it looks like there are pharo-specific versions for each of the packages loaded into Pharo2.0. I assume that the tests are all passing with those versions, although I can't say whether or not the tests had to be modified to pass in Pharo2.0 as well ... which is likely to be a source of one of the problems you are looking at ... I don't know where the configuration exists that is being used to manage the changes for Pharo2.0 and the tests, but that is probably a good starting point ... if you are not using the proper Pharo2.0 configuration, you won't be getting the proper packages loaded ... Dale ----- Original Message ----- | From: "Christophe Demarey" <Christophe.Demarey(a)inria.fr> | To: metacello(a)googlegroups.com | Cc: Pharo-project(a)lists.gforge.inria.fr | Sent: Friday, February 15, 2013 6:09:27 AM | Subject: [Pharo-project] Metacello issues on Pharo 2.0 | | Hi all, | | I have issues with Metacello on Pharo 2.0 | | If I load and run tests for the version used in Pharo1.4, it gives: | (ConfigurationOfMetacello project version: '1.0-beta.31.1.4') load: 'Tests' | | | | Metacello packages shipped with Pharo 2.0 are all packages derived from the | latest stable Metacello baseline (1.0-beta.31.1.5) except the | MetacelloToolBox. | If I load and run tests packages with version described in the latest stable | Metacello baseline (1.0-beta.31.1.5), i.e. : | Metacello-TestsCore-DaleHenrichs.14 and | Metacello-TestsMC-dkh.351, | it gives (Pharo 2.0 #20547): | | | So, it seems there are some problems. Do we use the rigth versions of | Metacello packages? | | Regards, | Christophe. | | | Chr

Feb. 20, 2013