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

Re: [Pharo-dev] collaborActive book refers to SS

by stephane ducasse

On May 16, 2013, at 11:23 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > http://book.pharo-project.org/book/Tidbits/FAQ/Packages/ > > talks about how you can create a SqueakSource project. Presumably we > want this to explain either how to create an SS3 project or a StHub > project? > > If all I need to do is issue a pull request to > https://github.com/SquareBracketAssociates/PharoByExample-english/ I'm > happy to update it to whichever you prefer. please do :) > > frank >

May 16, 2013

Re: [Pharo-dev] vm fixes

by stephane ducasse

On May 16, 2013, at 4:04 AM, btc(a)openInWorld.com wrote: > Could this be used make Pharo dual-screened ? If yes, what would be the limitations ? no you cannot. Rght now the trick is just to set up the size of the hostwindow to the one of a morph. Stef > > cheers -ben > > Benjamin wrote: >> In the following picture, instead of doing the classical MessageBrowser new openWithSpec, and get a Morphic window inside the os window of Pharo >> >> I do >> MessageBrowser openWorldWithSpec >> And here the message browser window *is* the system window. >> Basically, it sticks the morph on the world, do some magic around, and voilÃ . >> The cool part is that the rest of the code do not change at all, and still it opens a the good size, the title is properly updated etc >> >> >> >> Ben >> >> On May 14, 2013, at 10:28 PM, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> > This sounds intriguing. Can you be more specific? :) >> > >> > Doru >> > >> > >> > On May 14, 2013, at 10:23 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com > <mailto:benjamin.vanryseghem.pharo@gmail.com>> wrote: >> > >> >> Thank you :) >> >> >> >> This fix goes with pair with >> >> https://pharo.fogbugz.com/default.asp?10619 >> >> >> >> Thanks to Esteban, one can now deploy a Spec widget with the os window as >> window :) >> >> >> >> Ben >> >> >> >> On May 14, 2013, at 10:19 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> >> >> >>> thanks esteban! >> >>> >> >>> On May 14, 2013, at 9:54 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> I just pushed fix for a weird bug in cocoa cog vm. >> >>>> It was crashing image when resizing using DisplayScreen>>#hostWindowSize: >>>> but even worst, some times was crashing also when dragging a window >>>> outside the world screen... >> >>>> >> >>>> The fix is there, but you will need to wait until tomorrow to have it in >>>> zeroconf (because of weird mac jenkins slave permissions). >> >>>> >> >>>> This increases a bit more the VM stability, still not perfect, but we are >>>> getting closer :) >> >>>> >> >>>> Esteban >> >>> >> >>> >> >> >> > >> > -- >> > www.tudorgirba.com <http://www.tudorgirba.com> >> > >> > "Presenting is storytelling." >> > >> > >> >> > > >

May 16, 2013

Re: [Pharo-dev] Monkey Validation

by Frank Shearar

On 16 May 2013 10:22, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > 2013/5/16 Frank Shearar <frank.shearar(a)gmail.com> >> >> On 16 May 2013 09:33, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> > Camillo we should really spend some time updating the plots in the >> > jenkins >> > job : https://ci.inria.fr/pharo/job/Pharo-3.0-CodeCritics-Beta/ . >> > >> > Because then for Pharo 3.0 release we could advertse saying look at the >> > plots it is the code quality improvements for this release. >> >> What does "unpackaged code" mean in the Pharo (Kernel only) analysis? > > > It supposed to be code that has no Monticello package I think. But it cannot > happen in Pharo, so this graph was useless. But you cannot remove easily old > graph data with the current jenkins plot plugin. Ah, OK. I'd suspected that's what it meant. Just wanted to make sure. >> (Otherwise, that's a really nice thing to see, those graphs!) >> > > Yeah it is nice, but it should be improved :). Everything always does :) frank

May 16, 2013

collaborActive book refers to SS

by Frank Shearar

http://book.pharo-project.org/book/Tidbits/FAQ/Packages/ talks about how you can create a SqueakSource project. Presumably we want this to explain either how to create an SS3 project or a StHub project? If all I need to do is issue a pull request to https://github.com/SquareBracketAssociates/PharoByExample-english/ I'm happy to update it to whichever you prefer. frank

May 16, 2013

Re: [Pharo-dev] Monkey Validation

by ClÃ©ment Bera

2013/5/16 Frank Shearar <frank.shearar(a)gmail.com> > On 16 May 2013 09:33, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > Camillo we should really spend some time updating the plots in the > jenkins > > job : https://ci.inria.fr/pharo/job/Pharo-3.0-CodeCritics-Beta/ . > > > > Because then for Pharo 3.0 release we could advertse saying look at the > > plots it is the code quality improvements for this release. > > What does "unpackaged code" mean in the Pharo (Kernel only) analysis? > It supposed to be code that has no Monticello package I think. But it cannot happen in Pharo, so this graph was useless. But you cannot remove easily old graph data with the current jenkins plot plugin. > > (Otherwise, that's a really nice thing to see, those graphs!) > > Yeah it is nice, but it should be improved :). > frank > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

May 16, 2013

Re: [Pharo-dev] vm fixes

by Benjamin

I am afraid not to understand your question Ben On May 16, 2013, at 4:04 AM, btc(a)openInWorld.com wrote: > Could this be used make Pharo dual-screened ? If yes, what would be the limitations ? > > cheers -ben > > Benjamin wrote: >> In the following picture, instead of doing the classical MessageBrowser new openWithSpec, and get a Morphic window inside the os window of Pharo >> >> I do >> MessageBrowser openWorldWithSpec >> And here the message browser window *is* the system window. >> Basically, it sticks the morph on the world, do some magic around, and voilÃ . >> The cool part is that the rest of the code do not change at all, and still it opens a the good size, the title is properly updated etc >> >> >> >> Ben >> >> On May 14, 2013, at 10:28 PM, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> > This sounds intriguing. Can you be more specific? :) >> > >> > Doru >> > >> > >> > On May 14, 2013, at 10:23 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com > <mailto:benjamin.vanryseghem.pharo@gmail.com>> wrote: >> > >> >> Thank you :) >> >> >> >> This fix goes with pair with >> >> https://pharo.fogbugz.com/default.asp?10619 >> >> >> >> Thanks to Esteban, one can now deploy a Spec widget with the os window as >> window :) >> >> >> >> Ben >> >> >> >> On May 14, 2013, at 10:19 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> >> >> >>> thanks esteban! >> >>> >> >>> On May 14, 2013, at 9:54 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> I just pushed fix for a weird bug in cocoa cog vm. >> >>>> It was crashing image when resizing using DisplayScreen>>#hostWindowSize: >>>> but even worst, some times was crashing also when dragging a window >>>> outside the world screen... >> >>>> >> >>>> The fix is there, but you will need to wait until tomorrow to have it in >>>> zeroconf (because of weird mac jenkins slave permissions). >> >>>> >> >>>> This increases a bit more the VM stability, still not perfect, but we are >>>> getting closer :) >> >>>> >> >>>> Esteban >> >>> >> >>> >> >> >> > >> > -- >> > www.tudorgirba.com <http://www.tudorgirba.com> >> > >> > "Presenting is storytelling." >> > >> > >> >> > > >

May 16, 2013

Re: [Pharo-dev] Monkey Validation

by Frank Shearar

On 16 May 2013 09:33, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Camillo we should really spend some time updating the plots in the jenkins > job : https://ci.inria.fr/pharo/job/Pharo-3.0-CodeCritics-Beta/ . > > Because then for Pharo 3.0 release we could advertse saying look at the > plots it is the code quality improvements for this release. What does "unpackaged code" mean in the Pharo (Kernel only) analysis? (Otherwise, that's a really nice thing to see, those graphs!) frank

May 16, 2013

Re: [Pharo-dev] Monkey Validation

by ClÃ©ment Bera

Camillo we should really spend some time updating the plots in the jenkins job : https://ci.inria.fr/pharo/job/Pharo-3.0-CodeCritics-Beta/ . Because then for Pharo 3.0 release we could advertse saying look at the plots it is the code quality improvements for this release. 2013/5/16 Camillo Bruni <camillobruni(a)gmail.com> > I spent some time yesterday evening with ben to compile a set of nice > validation rules for the monkey, this is what we came up with ;) : > > CIRunTestsRule & "Only after the tests succeeded validate anything > else" > ( "Hard rules that lead to immediate WorkNeeded > state:" > RBUnclassifiedMethodsRule harden, > RBUndeclaredReferenceRule harden, > RBNoClassCommentRule harden, > RBDefinesEqualNotHashRule harden, > RBEquivalentSuperclassMethodsRule harden, > RBJustSendsSuperRule harden, > RBSubclassResponsibilityNotDefinedRule harden, > RBTempVarOverridesInstVarRule harden, > RBUndeclaredReferenceRule harden, > RBVariableNotDefinedRule harden, > RBEqualNotUsedRule harden, > RBOnlyReadOrWrittenTemporaryRule harden, > RBPrecedenceRule harden, > RBSendsDeprecatedMethodToGlobalRule harden, > RBSizeCheckRule harden, > RBUnconditionalRecursionRule harden, > RBUnoptimizedToDoRule harden, > RBBetweenAndRule harden, > RBCodeCruftLeftInMethodsRule harden, > > "Soft rules that only lead to warnings:" > RBInstanceVariableCapitalizationRule, > RBClassVariableCapitalizationRule, > RBMissingSubclassResponsibilityRule, > RBOverridesSpecialMessageRule, > RBRefersToClassRule, > RBBadMessageRule, > RBUsesTrueRule, > RBSendsDifferentSuperRule, > RBInconsistentMethodClassificationRule, > RBInstVarInSubclassesRule, > RBSentNotImplementedRule, > RBLongMethodsRule, > RBCollectionProtocolRule, > RBConsistencyCheckRule, > RBContainsRule, RBDetectContainsRule, > RBEmptyExceptionHandlerRule, > RBEndTrueFalseRule, > RBEqualsTrueRule, > RBExtraBlockRule, > RBFileBlocksRule, > RBFloatEqualityComparisonRule, > RBLiteralArrayCharactersRule, > RBMissingYourselfRule, > RBModifiesCollectionRule, > RBReturnsIfTrueRule, > RBSearchingLiteralRule, > RBUnnecessaryAssignmentRule, > RBNotEliminationRule, > RBAtIfAbsentRule, > RBAllAnyNoneSatisfyRule, > RBClassNameInSelectorRule ); > > > Don't be scared nor offended if your issue submission will get a lot of > feedback in the near future. > We're tweaking the rules to get decent feedback and not just blind noise. > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

May 16, 2013

Monkey Validation

by Camillo Bruni

I spent some time yesterday evening with ben to compile a set of nice validation rules for the monkey, this is what we came up with ;) : CIRunTestsRule & "Only after the tests succeeded validate anything else" ( "Hard rules that lead to immediate WorkNeeded state:" RBUnclassifiedMethodsRule harden, RBUndeclaredReferenceRule harden, RBNoClassCommentRule harden, RBDefinesEqualNotHashRule harden, RBEquivalentSuperclassMethodsRule harden, RBJustSendsSuperRule harden, RBSubclassResponsibilityNotDefinedRule harden, RBTempVarOverridesInstVarRule harden, RBUndeclaredReferenceRule harden, RBVariableNotDefinedRule harden, RBEqualNotUsedRule harden, RBOnlyReadOrWrittenTemporaryRule harden, RBPrecedenceRule harden, RBSendsDeprecatedMethodToGlobalRule harden, RBSizeCheckRule harden, RBUnconditionalRecursionRule harden, RBUnoptimizedToDoRule harden, RBBetweenAndRule harden, RBCodeCruftLeftInMethodsRule harden, "Soft rules that only lead to warnings:" RBInstanceVariableCapitalizationRule, RBClassVariableCapitalizationRule, RBMissingSubclassResponsibilityRule, RBOverridesSpecialMessageRule, RBRefersToClassRule, RBBadMessageRule, RBUsesTrueRule, RBSendsDifferentSuperRule, RBInconsistentMethodClassificationRule, RBInstVarInSubclassesRule, RBSentNotImplementedRule, RBLongMethodsRule, RBCollectionProtocolRule, RBConsistencyCheckRule, RBContainsRule, RBDetectContainsRule, RBEmptyExceptionHandlerRule, RBEndTrueFalseRule, RBEqualsTrueRule, RBExtraBlockRule, RBFileBlocksRule, RBFloatEqualityComparisonRule, RBLiteralArrayCharactersRule, RBMissingYourselfRule, RBModifiesCollectionRule, RBReturnsIfTrueRule, RBSearchingLiteralRule, RBUnnecessaryAssignmentRule, RBNotEliminationRule, RBAtIfAbsentRule, RBAllAnyNoneSatisfyRule, RBClassNameInSelectorRule ); Don't be scared nor offended if your issue submission will get a lot of feedback in the near future. We're tweaking the rules to get decent feedback and not just blind noise.

May 16, 2013

Re: [Pharo-dev] [3.0][Opal] Compiler Options!

by Marcus Denker

This is now in 3.0 (starting from 3.0 #133). There is now even an example for the use of #optIlineNone Do this: SmalltalkImage compilerClass: OpalCompiler. OpalCompiler allowNonBooleanReceivers: true. 1 ifFalse: [ 'ups' ] you get a DNU that SmallInteger does not understand #ifTrue: Of course this does not turn of the inling in general, it just recompiled the send (kind of like a doit) on-optimized and executes that in #mustBeBooleanIn: in the right context with all variables correctly looked up in the context. (it is only a proof of concept right now and not working for anything more complex.) Marcus On May 14, 2013, at 4:02 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > In 3.0, when using the new Compiler, there is now a new way to set options that the compile > chain can act on (Opal takes care to hand them through all the stages). > > For now, the there are two cases where we use options: controlling inlining and to generate > long ivar access bytecodes even when short ones would be enough: > > defaultOptions > ^ #( > "by default we inline all optimized constructs" > + optInlineIf > + optInlineIfNil > + optInlineAndOr > + optInlineWhile > + optInlineToDo > + optInlineCase > > - optIlineNone "to turn off all. Overrides the others" > - optLongIvarAccessBytecodes "special for Contexts" > ) > > > There are two ways to set compiler options. One is per Class Hierarchy. For example, in > InstructionStream class, there is this method: > > > compiler > > ^super compiler options: #(+ optLongIvarAccessBytecodes) > > The other way to use it is with a pragma: > > test > <compilerOptions: #(-optInlineIf)> > > > ^1 < 2 ifTrue: [ 'Hello!' ] > > > The options API idea is taken from NativeBoost: > > #( + option1 option2 - option3 ... ) > > each time the #+ is seen, the options which follow it will be subject for inclusion > and, correspondingly, if #- seen, then they will be excluded. > > By default, (if none of #+ or #- specified initially), all options are subject for inclusion. > > Like NativeBoost it uses #doesNotUnderstand, so e.g. if you want to have a flag for your own > Compiler Plugin, just set it and query the compilationContext by sending the flag symbol as > a message. > > Next: AST Transformation Pluginsâ¦ ready later this week. > > Marcus > > >

May 16, 2013