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

[regression reporter]regression occurred
by no-reply＠ci.inria.fr June 19, 2013

June 19, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 1 regressions found. Tests.Release.ReleaseTest.testObsoleteBehaviors

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr June 19, 2013

June 19, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 2 regressions found. Tests.Release.ReleaseTest.testObsoleteBehaviors Tests.Release.ReleaseTest.testObsoleteClasses

1 0

[update 3.0] #30208
by Marcus Denker June 19, 2013

June 19, 2013

30208 ----- 10947 A method in Behavior needs to be recategorized https://pharo.fogbugz.com/f/cases/10947 10948 Add configuration for enable node navigation using arrows https://pharo.fogbugz.com/f/cases/10948 10965 BreakPoints do not work with new AST https://pharo.fogbugz.com/f/cases/10965 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1149.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/NodeNavigation-MarcusDenker.4… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1484.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-MarcusDenker.483.diff

1 0

Object>>#if:then:else:
by Camille Teruel June 19, 2013

June 19, 2013

Hello everyone. I see a lot of code that follows the following pattern: <a long expression> <aComplexTest> ifTrue: [ <a long expression> <something> ] ifFalse: [ <a long expression> <something else> ]. The classic refactoring is to store <a long expression> in a temp to avoid repetition: | temp | temp := <a long expression>. temp <aComplexTest> ifTrue: [ temp <something> ] ifFalse: [ temp <something else> ]. Then <a long expression> is evaluated once and the name of the temp can carry a meaningful name that helps reading the code. But this is more verbose than the first version. But if you add the following method in Object: if: conditionBlock then: trueBlock else: falseBlock ^ (conditionBlock cull: self) ifTrue: [ trueBlock cull: value ] ifFalse: [ falseBlock cull: value ] You can then rewrite it like that: <a long expression> if: [ :obj | obj <aComplexTest> ] then: [ :obj | <something> ] else: [ :obj | <something else> ] The names of the block args can give a meaningful name depending on the result of the test (something like ... if: #notEmpty then: [ :collection | ... ] else: [ :emptyCollection | ... ]). Using cull: for the three block also enable a good flexibility: you can omit the arg when irrelevant. Likewise, we could also have Object>>#while:do: while: conditionBlock do: actionBlock ^ [ conditionBlock cull: self ] whileTrue: [ actionBlock cull: self ] What do you think? Camille

12 21

Barcodes
by Torsten Bergmann June 19, 2013

June 19, 2013

>About barcodes generation, why don't use Artefact directly ? If you look at the implementation you will see that barcode generation is mostly about implementing the correct encoding (to get a string with 0s and 1s) With this one can easily draw the lines on a form, a morph/canvas or directly in PDF. An easy way now is by using a form, see "BarcodeEAN13 example asForm" and then display this form in PDF via Artefact or use "asMorph openInWorld" Bye T.

1 0

Block Printing in 3.0
by Sean P. DeNigris June 19, 2013

June 19, 2013

Why do we get [...] when Opal is not active? Why can't we keep the old behavior? Thanks, Sean ----- Cheers, Sean -- View this message in context: http://forum.world.st/Block-Printing-in-3-0-tp4693116.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

5 8

Also "create method" in traits
by Martin Dias June 19, 2013

June 19, 2013

Hi I informally reported this "feature requirement" today to Sebastian, but I wanted to post it to all. When the debugger is shown after a MNU, the developer can press the button "Create method". A list of the superclasses is shown to the developer, so he/she can choose in which class crate the method. In addition to superclasses, it would be nice to show the traits that the classes use, since developer might want to create the method there. Cheers, MartÃn

7 8

[update 3.0] #30207
by Marcus Denker June 19, 2013

June 19, 2013

30207 ----- 10944 Enable Opal in 3.0 https://pharo.fogbugz.com/f/cases/10944 Just does a SmalltalkImage compilerClass: OpalCompiler. OpalCompiler recompileAll. Yesâ¦ we managed to run out of known bugs. So let's find some moreâ¦ :-)

3 2

[update 3.0] #30206
by Marcus Denker June 19, 2013

June 19, 2013

30206 ----- 10949 Bug when a method is recategorized https://pharo.fogbugz.com/f/cases/10949 10963 Nautilus add accessors https://pharo.fogbugz.com/f/cases/10963 10962 NewList fix in deselectAll https://pharo.fogbugz.com/f/cases/10962 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-SystemIntegration-Ma… http://smalltalkhub.com/mc/Pharo/Pharo30/main/NewList-MarcusDenker.47.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-MarcusDenker.474.diff

1 0

Re: [Pharo-dev] Barcodes
by Stephan Eggermont June 18, 2013

June 18, 2013

Chris wrote: >You should be able to create a form, paint it white, draw on it with a barcode TTF font, export that form to JPEG, and >then use that JPEG into Artefact. That won't work. Barcode readers need clean black-white transitions and that is something JPEG compression cannot provide (unless printing large enough at high enough resolution, and low enough compression). To get good-working barcodes, you even need to align to printer pixels. Stephan

1 0