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

Pharo 3.0 on Windows 8.1
by Sven Van Caekenberghe Feb. 27, 2014

Feb. 27, 2014

Pharo 3.0 on Windows 8.1 Installing and running Pharo 3.0 on a blank Windows 8.1 machine in under 1 minute. http://www.youtube.com/watch?v=FKokxrQtrg0 With an extra minute to demo some basic interactions. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

2 1

Pharo 3.0 on Mac OS X 10.9
by Sven Van Caekenberghe Feb. 27, 2014

Feb. 27, 2014

Pharo 3.0 on Mac OS X 10.9 The out of the box experience. Installing and running Pharo 3.0 on a blank Mac OS X 10.9 account in 40 seconds. https://www.youtube.com/watch?v=xxljgugI4c4 With 3 extra minutes to demo some networking and image manipulation interactions. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

4 4

How to upload some version from the package-cache to a StHub project
by Gabriel Cotelli Feb. 27, 2014

Feb. 27, 2014

Hi, I have a whole package history in my local package cache and I want to upload it to a new SmalltalkHub project. I've tried using the Monticello browser but it insists in creating a new version of the package when I do the "Save" to the new repository. Is there some option to do something like this? Or some script? I don't want to loose the history. Regards, Gabriel

4 4

Fwd: [squeak-dev] Fwd: Floats problem with SIXX between Pharo and GemStone
by Nicolas Cellier Feb. 26, 2014

Feb. 26, 2014

---------- Forwarded message ---------- From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> Date: 2014-02-27 0:15 GMT+01:00 Subject: Re: [squeak-dev] Fwd: [Pharo-dev] Floats problem with SIXX between Pharo and GemStone To: The general-purpose Squeak developers list < squeak-dev(a)lists.squeakfoundation.org> 2014-02-26 23:38 GMT+01:00 Tobias Pape <Das.Linux(a)gmx.de>: Can we get this into trunk please? > Ie, > > SqNumberPasrser>>exponentLetters > "current comment" > ^'edqEDQ' > > > Best > -Tobias > > You mean modifying Smalltalk syntax? That's a possible option, and it would work in Pharo too. Note that 1.0E2 was previously interpreted as send #E2 to 1.0, so it might change... ...not much thing : the problem is highly hypothetical, we don't use a leading uppercase letter in selectors usually, and we also put a space before a unary or keyword message - one rare exception I encountered was Complex "constants" like 1+2i ... Begin forwarded message: > > *From: *Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > *Subject: **Re: [Pharo-dev] Floats problem with SIXX between Pharo and > GemStone* > *Date: *26. Februar 2014 23:14:10 MEZ > *To: *Pharo Development List <pharo-dev(a)lists.pharo.org> > *Reply-To: *Pharo Development List <pharo-dev(a)lists.pharo.org> > > > > > 2014-02-26 23:08 GMT+01:00 Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com>: > >> That's exactly for this kind of reasons that I developped an >> ExtendedNumberParser connected to Number class>>readFrom:, to allow a >> variety of formats used in the rest of the world. >> >> It would have been easy to allow upper letter exponents in this parser, >> but the class was considered superfluous and removed from Pharo 3.0... >> >> super easy is just redefine: > > ExtendedNumberParser>>exponentLetters > ^'edqEDQ' > > and then Float readFrom: '1.0000000000000000E-02' works as expected, that > is in Squeak at least... > > > > > > >

1 0

Pharo is cool
by Norbert Hartl Feb. 26, 2014

Feb. 26, 2014

The best smalltalk/pharo moments you get if you try things you want to have just in order to see they are already there. Today FileBrowser. I switched one of my servers to dump to stack with fuel to disk if an exception occurs. Today I copied the files from the server to my local machine and opened a workspace starting to write an expression to open them. Then I thought it would be cool if I could use the file browser for it. So I opened it and navigated to the directory with the fuel filesâ¦et voilÃ â¦as soon as I clicked on a fuel file a button âmaterializeâ appeared which showed the stack from the server right away. Just brilliant! Well done! Norbert

5 13

test failures in downloaded image 30733
by btc＠openinworld.com Feb. 26, 2014

Feb. 26, 2014

For diligence and curiosity leading up to the Pharo3 release, I downloaded build image 30733 (with PharoLauncher) and immediately ran all tests, which reported 7 failures and 1 error (see attached snapshot). Now presumably these did not occur in the CI build since otherwise it would not have been available to PharoLauncher, so this raises a few questions/ideas: 1. Why the discrepancy / how did these slip through ? Perhaps some difference in local environment / difference in VM? Can anyone else reproduce this for 30733? I've logged an new case [1] for this where I plan to either link to existing cases or add a subcase for each failure. Please add your results there, particularly if you see a known issue. Here are my failures... BlockClosureTest>>#testTrace JobTest>>#testCurrent MetacelloRepositorySqueakCommonTestCase>>#testAsRepositorySpecFor MetacelloRepositorySqueakCommonTestCase>>#testDirectoryRepository MetacelloRepositorySqueakCommonTestCase>>#testFileTreeRepository ReleaseTest>>#testObsoleteClasses SimmulateMouseSpecification>>#testSimulateRightClick and errors... OpenToolTest>>#testOpenBrowseOnInstalledTraitMethod 2. How is the PharoLauncher VM synced with that used to test the Pharo CI builds ? (My VM comes from the PharoLauncher Windows Installer) 3. Assuming Pharo3 will go through a Release Candidate phase, apart from functionality testing which anyone may-or-not have time for, as many spectators as possible should download those Release Candidate images an just run All Tests. 4. It might be good for a small number of releases between now and Release Candidate to be designated for the community to similarly run All Tests - to reduce surprises at Release Candidate time? 5. I've seen times before when some failures as transitory/random (which had to do with unordered Sets being used by a test that presumed order). So at times when there are a lot of Pharoers together, such as at a Sprint, maybe the convention could be for everyone to run All Tests at the start of the day to provide broad comparison (and know you're starting with a clean slate) cheers -ben [1] https://pharo.fogbugz.com/f/cases/12770/

6 19

expected failures
by btc＠openinworld.com Feb. 26, 2014

Feb. 26, 2014

I'd like to better understand the semantics of "expected failures" in TestRunner. It seems to me that if you want to ensure that a certain operation fails, in a test you'd wrap it as follows... shouldFailed=false. [ self operationThatShouldFail ] on: Error do: [ shouldFailed := true ]. self assert: shouldFailed. So is tagging methods with pragma <expectedFailure> or in method #expectedFailures a temporary measure used to bypass a failing test when the judgment is that it is not critical to fix immediately? What is the process for tacking and resolving expected failures. It would give a warm fuzzy feeling if no expected failures are reported in TestRunner. Otherwise it leaves some residual uncertainty that something is wrong, even though a failure is "expected". cheers -ben

4 5

Pharo 3.0 on Windows 8.1
by Sven Van Caekenberghe Feb. 26, 2014

Feb. 26, 2014

Pharo 3.0 on Windows 8.1 Installing and running Pharo 3.0 on a blank Windows 8.1 machine in under 1 minute. http://www.youtube.com/watch?v=FKokxrQtrg0 With an extra minute to demo some elementary interactions. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

4 5

In Praise of Small Commits | Dr Dobb's
by Sven Van Caekenberghe Feb. 26, 2014

Feb. 26, 2014

http://www.drdobbs.com/architecture-and-design/in-praise-of-small-commits/2… << With smaller commits, teams accelerate code reviews and builds, while shrinking the delay between committing and feedback. That's a lot of payback for a simple practice. >> >From an integration standpoint, I love small and clean Slices. Sven

2 1

Re: [Pharo-dev] easier start with Phobos
by Stephan Eggermont Feb. 26, 2014

Feb. 26, 2014

This doesnât work on a mac (running Mavericks) c := PipeableOSProcess command: 'cd PhobosDemo.app/Contents; mkdir Frameworks; cd Frameworks; tar -jxvf ../../../xulrunner.tar.bz2'.

2 1