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

[pharo-project/pharo-core] af3deb: 30469

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: af3deb0b3937e1730056b41633589f50a0a1ac77 https://github.com/pharo-project/pharo-core/commit/af3deb0b3937e1730056b416… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-10 (Thu, 10 Oct 2013) Changed paths: R CollectionsTests-Abstract.package/TEmptySequenceableTest.class/instance/tests - sequence isempty/testSequenceAbleIfEmptyifNotEmptyDo.st R CollectionsTests-Abstract.package/TEmptySequenceableTest.class/instance/tests - sequence isempty/testSequenceIfEmptyifNotEmptyDo.st R CollectionsTests-Abstract.package/TEmptySequenceableTest.class/instance/tests - sequence isempty/testSequenceIfNotEmptyDo.st R CollectionsTests-Abstract.package/TEmptySequenceableTest.class/instance/tests - sequence isempty/testSequenceIfNotEmptyDoifNotEmpty.st R CollectionsTests-Abstract.package/TEmptyTest.class/instance/tests - empty/testIfEmptyifNotEmptyDo.st R CollectionsTests-Abstract.package/TEmptyTest.class/instance/tests - empty/testIfNotEmptyDo.st R CollectionsTests-Abstract.package/TEmptyTest.class/instance/tests - empty/testIfNotEmptyDoifNotEmpty.st M Kernel-Classes.package/Categorizer.class/instance/accessing/changeFromCategorySpecs_.st M Kernel-Classes.package/Categorizer.class/instance/accessing/sortCategories.st M Kernel-Classes.package/ClassBuilder.class/instance/class definition/silentlyMoveInstVarNamed_from_to_after_.st R Kernel-Job.package/JobStartNotification.class/class/as yet unclassified/on_.st A Kernel-Job.package/JobStartNotification.class/class/instance creation/on_.st M Kernel-Methods.package/CompiledMethod.class/instance/accessing/originMethod.st M Kernel-Methods.package/CompiledMethod.class/instance/testing/isInstalled.st R Kernel-Methods.package/MessageCatcher.class/instance/as yet unclassified/doesNotUnderstand_.st R Kernel-Methods.package/MessageCatcher.class/instance/as yet unclassified/privAccumulator.st R Kernel-Methods.package/MessageCatcher.class/instance/as yet unclassified/privAccumulator_.st A Kernel-Methods.package/MessageCatcher.class/instance/private/privAccumulator.st A Kernel-Methods.package/MessageCatcher.class/instance/private/privAccumulator_.st A Kernel-Methods.package/MessageCatcher.class/instance/reflective operations/doesNotUnderstand_.st R Kernel-Methods.package/RelativeInstructionPrinter.class/instance/as yet unclassified/pushClosureCopyNumCopiedValues_numArgs_blockSize_.st A Kernel-Methods.package/RelativeInstructionPrinter.class/instance/instruction decoding/pushClosureCopyNumCopiedValues_numArgs_blockSize_.st R Kernel-Methods.package/SimulationExceptionWrapper.class/class/as yet unclassified/signalForException_.st A Kernel-Methods.package/SimulationExceptionWrapper.class/class/signalling/signalForException_.st R Kernel-Numbers.package/Integer.class/instance/as yet unclassified/asShortcut.st M Kernel-Objects.package/Object.class/instance/error handling/explicitRequirement.st R Kernel-Pragmas-Collector.package/PragmaCollectorReset.class/class/as yet unclassified/collector_.st A Kernel-Pragmas-Collector.package/PragmaCollectorReset.class/class/instance creation/collector_.st A Kernel-Pragmas-Collector.package/PragmaCollectorReset.class/instance/accessing/collector.st A Kernel-Pragmas-Collector.package/PragmaCollectorReset.class/instance/accessing/collector_.st R Kernel-Pragmas-Collector.package/PragmaCollectorReset.class/instance/as yet unclassified/collector.st R Kernel-Pragmas-Collector.package/PragmaCollectorReset.class/instance/as yet unclassified/collector_.st M Kernel-Processes.package/Process.class/definition.st R Kernel-Processes.package/ProcessLocalVariable.class/instance/as yet unclassified/value_.st A Kernel-Processes.package/ProcessLocalVariable.class/instance/evaluating/value_.st M KeyChain-UI.package/UserEditor.class/instance/private/ok.st M KeyChain.package/KeyChain.class/instance/protocol/setEncryptorDecryptor_.st M KeyChain.package/KeyChain.class/instance/protocol/setPassword_.st M KeyChain.package/UsernamePassword.class/instance/printing/printOn_.st A Keymapping-KeyCombinations.package/extension/Integer/instance/asShortcut.st M MonticelloConfigurations.package/MCConfiguration.class/instance/private/depsSatisfying_versionDo_displayingProgress_.st M MonticelloConfigurations.package/MCConfiguration.class/instance/private/versionNamed_for_from_.st M Polymorph-Widgets.package/extension/SystemWindow/instance/aboutText.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script124.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30469.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30469 11842 Trivia critic cleanup in Kernel https://pharo.fogbugz.com/f/cases/11842 11845 Do not use the *do: versions of #*ifNotEmpty* https://pharo.fogbugz.com/f/cases/11845 11843 Trivial critic cleanup in keychain https://pharo.fogbugz.com/f/cases/11843 http://files.pharo.org/image/30/30469.zip

Oct. 11, 2013

Re: [Pharo-dev] Fwd: Small text composition bench

by Denis Kudriashov

Me too. What exactly doing this code? Paragraph new compose: tm text style: tm textStyle copy from: 1 in: Is it layout building stuff at new text model? 2013/10/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi Igor > > it would be good to see how the new text model perform. > > Stef > > > Begin forwarded message: > > *From: *Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > *Subject: **Fwd: Small text composition bench* > *Date: *October 10, 2013 10:46:42 PM GMT+02:00 > *To: *StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > > ---------- Forwarded message ---------- > From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > Date: 2013/10/10 > Subject: Small text composition bench > To: The general-purpose Squeak developers list < > squeak-dev(a)lists.squeakfoundation.org> > > > Here is a simple bench: > > (StringHolder new contents: (Compiler evaluate: (FileStream fileNamed: ' > text.st') contentsOfEntireFile )) openLabel: 'Working With Squeak 2' . > ((SystemWindow allSubInstances detect: [:e | e label = 'Working With > Squeak 2']) findDeepSubmorphThat: [:m | m class = PluggableTextMorphPlus] > ifAbsent: [] ) textMorph > ifNotNil: [:tm | MessageTally spyOn: [ > [100 timesRepeat: [(NewParagraph new) > compose: tm text > style: tm textStyle copy > from: 1 > in: tm container]] timeToRun]]. > > Before our changes: 162 ms > After our changes: 95 ms > And my Pharo 3.0 (#30417) (not up to date) : 364 ms > > The main gain is avoiding > - the stopConditions copy > - and the TextStopConditions indirection > - and of course the Multi* when not necessary (Pharo does not) > > Here is the test for Pharo variant: > > | text | > text := Compiler evaluate: (FileSystem workingDirectory parent parent > parent / 'text.st' ) readStream contentsOfEntireFile . > (StringHolder new contents: text) openLabel: 'Working With Squeak 2' . > ((SystemWindow allSubInstances detect: [:e | e label = 'Working With > Squeak 2']) findDeepSubmorphThat: [:m | m class = PluggableTextMorph] > ifAbsent: [] ) textMorph > ifNotNil: [:tm | MessageTally spyOn: [ > [100 timesRepeat: [(Paragraph new) > compose: text > style: tm textStyle copy > from: 1 > in: tm container]] timeToRun]]. > > > > > > >

Oct. 11, 2013

Fwd: Small text composition bench

by StÃ©phane Ducasse

Hi Igor it would be good to see how the new text model perform. Stef Begin forwarded message: > From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > Subject: Fwd: Small text composition bench > Date: October 10, 2013 10:46:42 PM GMT+02:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > > ---------- Forwarded message ---------- > From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > Date: 2013/10/10 > Subject: Small text composition bench > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > > Here is a simple bench: > > (StringHolder new contents: (Compiler evaluate: (FileStream fileNamed: 'text.st') contentsOfEntireFile )) openLabel: 'Working With Squeak 2' . > ((SystemWindow allSubInstances detect: [:e | e label = 'Working With Squeak 2']) findDeepSubmorphThat: [:m | m class = PluggableTextMorphPlus] ifAbsent: [] ) textMorph > ifNotNil: [:tm | MessageTally spyOn: [ > [100 timesRepeat: [(NewParagraph new) > compose: tm text > style: tm textStyle copy > from: 1 > in: tm container]] timeToRun]]. > > Before our changes: 162 ms > After our changes: 95 ms > And my Pharo 3.0 (#30417) (not up to date) : 364 ms > > The main gain is avoiding > - the stopConditions copy > - and the TextStopConditions indirection > - and of course the Multi* when not necessary (Pharo does not) > > Here is the test for Pharo variant: > > | text | > text := Compiler evaluate: (FileSystem workingDirectory parent parent parent / 'text.st' ) readStream contentsOfEntireFile . > (StringHolder new contents: text) openLabel: 'Working With Squeak 2' . > ((SystemWindow allSubInstances detect: [:e | e label = 'Working With Squeak 2']) findDeepSubmorphThat: [:m | m class = PluggableTextMorph] ifAbsent: [] ) textMorph > ifNotNil: [:tm | MessageTally spyOn: [ > [100 timesRepeat: [(Paragraph new) > compose: text > style: tm textStyle copy > from: 1 > in: tm container]] timeToRun]]. > > >

Oct. 11, 2013

Re: [Pharo-dev] Pharo for the Raspberry Pi]

by btc＠openinworld.com

Oct. 11, 2013

Re: [Pharo-dev] New Image Command Line Handlers

by Sean P. DeNigris

It doesn't really fit our "backport bug fixes only" policy. When I backported the completion stuff because it was too cool not to, it was a week-long hassle chasing collateral bugs. But what I've been doing for these types of things is merging into the released version, saving the packages online, and customizing my own images with them. It's been working pretty well since the released versions don't change very much. HTH -------- Original message -------- From: "philippeback [via Smalltalk]" <ml-node+s1294792n4713697h95(a)n4.nabble.com> Date: 10/10/2013 2:10 PM (GMT-05:00) To: "Sean P. DeNigris" <sean(a)clipperadams.com> Subject: Re: New Image Command Line Handlers Good news. If by default on Windows, it would be another default than pharo\ it would be great as it would be nicer with zeroconf fetching pharo-ui and pharo (headless) Are those changes going to find their way in Pharo 2.0? Phil On Thu, Oct 10, 2013 at 7:48 PM, Sean P. DeNigris <[hidden email]> wrote: We (Cami, Ben, and I) added some command line options to control preference loading, which seem useful e.g. for integrators and in my original use case of running an image off a USB stick on a foreign computer and not wanting to pick up those preferences There are two new flags: 1. --no-default-preferences = don't load from any of the default locations 2. --preference-file [/full/path/to/file.st] = load this one They are independent, so there are four options now: Â Â 1 Â Â | Â Â 2 Â Â | Â Â Â Â Â Â Â Â Â Â Â Â - current behavior Â Â x Â Â Â Â Â Â Â Â - don't load any preferences Â Â Â Â Â Â Â Â x Â Â Â - load the defaults and this additional Â Â x Â Â Â Â x Â Â Â - only load the specified file (not the defaults) ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-Image-Command-Line-Handlers-tp4713693.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. If you reply to this email, your message will be added to the discussion below: http://forum.world.st/New-Image-Command-Line-Handlers-tp4713693p4713697.html To unsubscribe from New Image Command Line Handlers, click here. NAML ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-Image-Command-Line-Handlers-tp4713693p4713738.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 11, 2013

Bug (and fix?) with #doSilently: and FileLibrary

by Mariano Martinez Peck

Hi guys, I noticed that when we add files to FileLibrary using provided methods like both methods are created, #selectorsToInclude and whatever you have updated, say, #myCss. However, if you go to Monticello Browser, only #selectorsToInclude appears. Digging a bit, I found out that Seaside ends up using Grease for that. And Grease does: GRPharoPlatform >>compile: aString into: aClass classified: aSymbol self doSilently: [ aClass compile: aString classified: aSymbol ] And then, of course, the doSilently, ends up doing: GRPharoPlatform >> doSilently: aBlock "Deals with a different between Pharo1.x and Pharo2.x" ^ (Smalltalk includesKey: #SystemChangeNotifier) ifTrue:[(Smalltalk at: #SystemChangeNotifier) uniqueInstance doSilently: aBlock] ifFalse:[(Smalltalk at: #SystemAnnouncer) uniqueInstance suspendAllWhile: aBlock] So...first, I don't like that a method named like #compile:into:classified: does a silently compilation. Normally, we have the "silently" as part of the selector (or a boolean parameter). Second, why would we want to compile silently? the idea is that after, we commit the FileLibrary...so if the method is not there, it is a problem. So, should we change the #compile:into:classified: to NOT do the silently? Thanks, -- Mariano http://marianopeck.wordpress.com

Oct. 10, 2013

Re: [Pharo-dev] [Pharo-users] Start with a trivial improvement!

by Facundo Vozzi

I like it Marcus. Good start point. Thanks On Thu, Oct 10, 2013 at 12:25 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > good idea > yes for the blog entry > > On Oct 10, 2013, at 1:42 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Thank you, Marcus! > > Could you post this on the Pharo blog? > > Doru > > > On Thu, Oct 10, 2013 at 1:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > >> +100 >> >> On 10 Oct 2013, at 13:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> > One nice way to get in the mood of doing (and at the same time testing >> the system) is to start >> > with trivial improvements. >> > >> > This is especially nice as a "starter" when you never contributed any >> change to Pharo. >> > >> > And by trivial I mean *really* mean trivial: >> > -> a typo in a comment >> > -> remove a temp not accessed >> > -> clean out some trivial dead code >> > -> do a simplistic refactoring of a bad smell, even inside a >> single method >> > -> document something >> > -> structure bad stuff better so it is easier to replace later >> > >> > Taken in itself, single changes like these have no influence, but: >> > >> > -> they get you in a mood of doing. >> > -> they make you feel that Pharo is "owned" by you. >> > -> take 1000 of those trivialities and they *do* make a >> difference. >> > -> next time something bothers you, you will have the context of >> "I can just fix it". >> > >> > The critic tools is one way of finding these places, another is to just >> note down every time >> > you see a triviality and later go through that list. The bug tracker >> can be source, too. >> > >> > >> > <wtfm.jpg> >> > >> > Marcus >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > >

Oct. 10, 2013

Re: [Pharo-dev] ShortRunArray not in Pharo 3.0 anymore, leading to problems with FFI-Kernel-tbn.25

by Esteban Lorenzano

yes, and we encourage people to try their stuff in Pharo3, to provide feedback, etc. bet definitively not for putting anything on production on it :) Esteban On Oct 10, 2013, at 5:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > philippeback wrote >> It is too complex for me to get things loaded in 3.0 and be delivering >> what >> we need to, so I am back to 2.0 now. > > I think that's the right decision even if you could get it loaded. I > wouldn't deploy on a beta version of Pharo (no matter how tempting all the > cool new features are!!)... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ShortRunArray-not-in-Pharo-3-0-anymore-leading-to-pro… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 10, 2013

Re: [Pharo-dev] New Image Command Line Handlers

by StÃ©phane Ducasse

excellent I will update the StartUp script chapter (except if somebody wants to do it). On Oct 10, 2013, at 7:48 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > We (Cami, Ben, and I) added some command line options to control preference > loading, which seem useful e.g. for integrators and in my original use case > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/New-Image-Command-Line-Handlers-tp4713693.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 10, 2013

Re: [Pharo-dev] ShortRunArray not in Pharo 3.0 anymore, leading to problems with FFI-Kernel-tbn.25

by StÃ©phane Ducasse

On Oct 10, 2013, at 5:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > philippeback wrote >> It is too complex for me to get things loaded in 3.0 and be delivering >> what >> we need to, so I am back to 2.0 now. > > I think that's the right decision even if you could get it loaded. I > wouldn't deploy on a beta version of Pharo (no matter how tempting all the > cool new features are!!)â¦ we are alpha :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ShortRunArray-not-in-Pharo-3-0-anymore-leading-to-pro… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 10, 2013