- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12207
by StÃ©phane Ducasse Oct. 23, 2010

Oct. 23, 2010

12207 ----- starting to clean systemNavigation and to make sure that it can work on an environment. Tx Luc Fabresse Stef

1 0

Re: [Pharo-project] pregunta mundo Pharo
by Mariano Martinez Peck Oct. 23, 2010

Oct. 23, 2010

2010/10/23 Carlos Lombardi <carlombardi(a)gmail.com> > Mariano > > ante todo buenos dÃas. Â¡Buenos dÃas! > Que haces carlono!! todo bien? espero que si :) > > Ahora el asunto. Si quiero pedir al mundo que se agregue algo a Pharo, Â¿hay > algÃºn medio adecuado y sencillo? > > Lo mas facil es mandar un mail a la lista: pharo-project(a)lists.gforge.inria.fr Si no te queres subscrbir, podes postear desde: http://forum.world.st/Pharo-Smalltalk-f1294837.html O registrate en la mailing list y deci que no te manden mails y listo. DespuÃ©s, depende de lo que querias agregar. Si es al "Core", si es una extension a paquetes externos (OB, RB, Shout, OCompletion, etc), o si queres que directamente un nuevo paquete venga preinstalado en las imagenes Pharo. De chusma, que queres poner? abrazo mariano

1 1

[Pharo-project] [update 1.2] #12206
by Marcus Denker Oct. 23, 2010

Oct. 23, 2010

12206 ----- Issue 2876: setStandardClass: aClass methodSymbol: methodSym (part2) Issue 3116: Reduce DecompilerTest failures to three legitimate failures. Issue 3140: Utilities removing -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] akuhn/SUnit: run faster tests first & step through tests
by Adrian Kuhn Oct. 23, 2010

Oct. 23, 2010

Hi Pharo list, The lastest akuhn/SUnit runs fasters tests first. When running your test suite for the second time, faster tests are run first. For the whole 9000 tests in the dev image, this means that the first 8000 tests are run in like 10 milliseconds. Also I fixed the menues in the test runner, you can now mark either all or single tests are expected defect. If you mark expected defects through the UI they are stored on the class side. The #expectedFailures method on the instance side is still taken into account for compatibility, but storing expected defects on the class side is the preferred way to do it now. I also cleared up the vocabulary. There are no more history on the class side, rather there are two histories one called "last run" and one called "expected defects" that both serve different purposes. The "last run" history is used to mark test results in the browser. The "expected defects" history is used to keep track of expected / unexpected defects. (As far I know, the icons in O2 show this as well.) Plus I added the ability to step through a failed tests. This stops right before the actual test method, rather than at the failed assertion. To step through a failed test, run your tests with the test runner and use the menu of test failures or errors. (OB and O2 might consider adding this option as well. In particular in combination with running fasters tests first a "run and debug/step-through first failure" might be interesting.) To load akuhn/SUnit gofer SystemChangeNotifier uniqueInstance noMoreNotificationsFor: TestCase. Gofer it disablePackageCache; squeaksource: 'akuhn'; package: 'SUnit'; package: 'SUnitGUI'; load. Thank you all for the awesome feedback last time! More is welcome :) --AA

3 5

Re: [Pharo-project] a useful check
by StÃ©phane Ducasse Oct. 23, 2010

Oct. 23, 2010

What is the way to fix that? > SystemNavigation new browseAllSelect: > [:m| | is | > is := InstructionStream on: m. > is scanFor: [:b| b = 143 and: [(m at: is thirdByte * 256 + is fourthByte + is pc + 4) = 135]]] lookForCode: code ifDifferent: handleBlock "We are expecting a certain numeric code next. However, in the FTP protocol, multiple lines are allowed. If the response is multi-line, the fourth character of the first line is a $- and the last line repeats the numeric code but the code is followed by a space. So it's possible that there are more lines left of the last response that we need to throw away. We use peekForAll: so that we don't discard the next response that is not a continuation line." "check for multi-line response" (self lastResponse size > 3 and: [(self lastResponse at: 4) = $-]) ifTrue: ["Discard continuation lines." [ | headToDiscard | headToDiscard := self lastResponse first: 4. [[self stream peekForAll: headToDiscard] whileTrue: [self stream nextLine]] on: Exception do: [:ex | ^handleBlock value: nil]]]. ^ super lookForCode: code ifDifferent: handleBlock

2 1

[Pharo-project] if you want to join the pharo sprint
by StÃ©phane Ducasse Oct. 23, 2010

Oct. 23, 2010

skype stducasse, we chat there. Stef

1 0

[Pharo-project] Pharo article in linuxMag fr
by StÃ©phane Ducasse Oct. 23, 2010

Oct. 23, 2010

> > > Just to say that recently, there were/are 2 articles about Pharo in GNU Linux Magazine (http://www.gnulinuxmag.com/) a french mag. > One was publish in the n130, about a presentation of Pharo. > One will be published in one week in the n132, about Gofer. > > Cheers, > --- > Jannik Laval >

4 4

[Pharo-project] [update 1.2] #12205
by Marcus Denker Oct. 23, 2010

Oct. 23, 2010

12205 ----- Issue 2619: ignore vm parameters with nil value in MessageTally, so it can be used in Cog Issue 1885: Disable Scroll Wrapping in PluggableListMorph Issue 3142: Updater package has no repository Issue 2876: setStandardClass: aClass methodSymbol: methodSym (first part) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Oct. 23, 2010

Apparently when we browse Compiler-eem.155 from the squeak trunk (ScriptLoader new addExtraRepositories) we get a problem because there is a nil in the set. Can you have a look? Stef

1 0

[Pharo-project] [update 1.2] #12204
by Marcus Denker Oct. 23, 2010

Oct. 23, 2010

12204 ----- Issue 2868: allClassesUsingPool: allClassesUsingPoolVariable: for systemNavigation Issue 3046: BUG: LineMorph class>>from:to:color:width: returns a PolygonMorph Issue 3130: MethodReference >> #isLocalSelector should not be part of Monticello package Issue 3095: Character isLiteral is in wrong category Issue 3134: Cleaning uniclasses from smartRefStream -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0