July 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] TextEditor initialization

by Marcus Denker

> On 30 Jul 2015, at 11:15, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Is there a specific reason why > > TextEditor>>initWithMorph: aMorph > > super initialize. > morph := aMorph. > self resetState. > > calls super initialize instead of self initialize? #initialize seems to be not implemented in the hierarchy anyway. > > TextMorph uses that with its subclass SmalltalkEditor as > > TextEditor class>>forMorph: aMorph > > ^ self basicNew initWithMorph: aMorph > I would - change basicNew to new in forMorph: - remove the call to #initialize in #initWithMorph: as it is done by #new Marcus

July 30, 2015

[pharo-project/pharo-core] db63f9: 50200

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: db63f9fc993f7c531eac4e84f906adbb794706ab https://github.com/pharo-project/pharo-core/commit/db63f9fc993f7c531eac4e84… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-07-30 (Thu, 30 Jul 2015) Changed paths: R AST-Core.package/RBConfigurableFormatter.class/README.md R AST-Core.package/RBConfigurableFormatter.class/class/accessing/cascadedMessageInsideParentheses.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/cascadedMessageInsideParentheses_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/formatAsYouReadPolicy.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/formatAsYouReadPolicy_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/formatCommentWithStatements.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/formatCommentWithStatements_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/indentString.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/indentString_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/indentsForKeywords.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/indentsForKeywords_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/keepBlockInMessage.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/keepBlockInMessage_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/lineUpBlockBrackets.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/lineUpBlockBrackets_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/maxLineLength.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/maxLineLength_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/methodSignatureOnMultipleLines.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/methodSignatureOnMultipleLines_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/minimumNewLinesBetweenStatements.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/minimumNewLinesBetweenStatements_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/multiLineMessages.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/multiLineMessages_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLineAfterCascade.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLineAfterCascade_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLineBeforeFirstCascade.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLineBeforeFirstCascade_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLineBeforeFirstKeyword.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLineBeforeFirstKeyword_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLinesAfterMethodComment.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLinesAfterMethodComment_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLinesAfterMethodPattern.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLinesAfterMethodPattern_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLinesAfterTemporaries.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/newLinesAfterTemporaries_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/numberOfArgumentsForMultiLine.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/numberOfArgumentsForMultiLine_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/oneLineMessages.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/oneLineMessages_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/periodsAsTerminators.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/periodsAsTerminators_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/periodsAtEndOfBlock.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/periodsAtEndOfBlock_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/periodsAtEndOfMethod.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/periodsAtEndOfMethod_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/retainBlankLinesBeforeComments.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/retainBlankLinesBeforeComments_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/retainBlankLinesBetweenStatements.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/retainBlankLinesBetweenStatements_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/stringFollowingReturn.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/stringFollowingReturn_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/stringInsideBlocks.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/stringInsideBlocks_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/stringInsideParentheses.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/stringInsideParentheses_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/traditionalBinaryPrecedence.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/traditionalBinaryPrecedence_.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/useTraditionalBinaryPrecedenceForParentheses.st R AST-Core.package/RBConfigurableFormatter.class/class/accessing/useTraditionalBinaryPrecedenceForParentheses_.st R AST-Core.package/RBConfigurableFormatter.class/class/initialization/initialize.st R AST-Core.package/RBConfigurableFormatter.class/class/public/format_.st R AST-Core.package/RBConfigurableFormatter.class/class/public/format_withIndents_.st R AST-Core.package/RBConfigurableFormatter.class/class/settings/settingsOn_.st R AST-Core.package/RBConfigurableFormatter.class/definition.st R AST-Core.package/RBConfigurableFormatter.class/instance/initialization/initialize.st R AST-Core.package/RBConfigurableFormatter.class/instance/initialize-release/indent_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatArray_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatBlockArgumentsFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatBlock_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatCommentsFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatMethodBodyFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatMethodCommentFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatMethodPatternFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatPragmasFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatSelectorAndArguments_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatSelectorAndArguments_firstSeparator_restSeparator_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatSequenceCommentsFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatSequenceNodeStatementsFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/formatStatementCommentsFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/handleLineForSelector_withSeparatorBlock_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private-formatting/isMultiLineMessage_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/addNewLinesBeforeStatementStartingAt_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/bracketWith_around_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/currentLineLength.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/formatTemporariesFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/formattedSourceFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/indentAround_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/indent_around_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/isLineTooLong_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/needsParenthesisFor_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/newLine.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/newLinesBeforeStartingAt_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/newLines_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/precedenceOf_greaterThan_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/space.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/willBeMultiline_.st R AST-Core.package/RBConfigurableFormatter.class/instance/private/writeString_.st R AST-Core.package/RBConfigurableFormatter.class/instance/public interface/containerWidth_.st R AST-Core.package/RBConfigurableFormatter.class/instance/public interface/format_.st R AST-Core.package/RBConfigurableFormatter.class/instance/utility/with_and_do_separatedBy_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitArrayNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitAssignmentNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitBlockNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitCascadeNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitLiteralArrayNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitLiteralNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitMessageNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitMethodNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitPatternBlockNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitPatternWrapperBlockNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitPragmaNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitReturnNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitSequenceNode_.st R AST-Core.package/RBConfigurableFormatter.class/instance/visiting/visitVariableNode_.st M AST-Core.package/RBProgramNode.class/class/accessing/formatterClass.st M AST-Tests-Core.package/RBParserTest.class/instance/accessing/exampleClasses.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50199.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50200.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50199.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50200.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Tools-Test.package/WorkspaceTest.class/instance/tests/testStyling.st Log Message: ----------- 50200 16062 WorkspaceTest>>#testStyling is failing https://pharo.fogbugz.com/f/cases/16062 16060 remove empty packages GroupManager and GroupManagerUI https://pharo.fogbugz.com/f/cases/16060 16011 Remove old Pretty Printer https://pharo.fogbugz.com/f/cases/16011 http://files.pharo.org/image/50/50200.zip

July 30, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50200 Home: https://github.com/pharo-project/pharo-core

July 30, 2015

TextEditor initialization

by Stephan Eggermont

Is there a specific reason why TextEditor>>initWithMorph: aMorph super initialize. morph := aMorph. self resetState. calls super initialize instead of self initialize? TextMorph uses that with its subclass SmalltalkEditor as TextEditor class>>forMorph: aMorph ^ self basicNew initWithMorph: aMorph Stephan

July 30, 2015

Re: [Pharo-dev] missing cairo library in CI

by Peter UhnÃ¡k

Since I am using pharo-contribution I don't have any control over slaves, I just have a job; but last 10 builds were all built on pharo-contribution-raspberrypi-linux. Thanks, Peter On Thu, Jul 30, 2015 at 10:49 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > late answeringâ¦ > think is pharovm does not include libcairo in linux because we expect they > are already installed or can be installed using apt-get (the usual linux > way). > the ppa for ubuntu has it as requirement, but I do not think CI slaves are > using itâ¦ so we need to take care of it at hand. > > please, tell me which slave is failing and I will try to install cairo > there. > > Esteban > > On 18 Jul 2015, at 10:27, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > bump > > anyone CI knowledgable has any idea? > > The previous link is dead, but the description remains. > > What's even better now is that the CI server itself is crashing on > displaying XML outputs... > https://ci.inria.fr/pharo-contribution/job/DynaCASE/46/PHARO=40,VERSION=dev… > > Thanks, > Peter > > On Wed, Jul 1, 2015 at 1:09 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Hi all, >> >> not sure if this is best directed at pharo or CI mailing list... >> >> I've created a new job in pharo-contribution and my Pharo project uses >> Cairo library... >> however when CI ran the tests it failed on >> >> "Cannot locate cairo library. Please check if it installed on your system" >> ( >> https://ci.inria.fr/pharo-contribution/job/DynaCASE/2/PHARO=40,VERSION=deve… >> ) >> >> is it something I need to enable or disable somewhere? >> >> I'm pretty sure Athens also uses Cairo ( >> https://ci.inria.fr/pharo-contribution/job/Athens/) and it works just >> fine. >> >> Any pointers appreciated, >> Peter >> > > >

July 30, 2015

Re: [Pharo-dev] [Issue tracker] *Please* look at your old reported issues!

by phil＠highoctane.be

Adding to that: no incentive to move to 4.x or 5.x for that very project. For my own stuff, this is a different story. Phil On Thu, Jul 30, 2015 at 11:07 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 30 Jul 2015, at 10:27, phil(a)highoctane.be wrote: > > > > Most of the feedback is "won't fix" or "done in 4.x or 5.x" > > All nice but hard to look at as day to day work is in 3.0 > > You have to move, you are missing out on all the nice stuff ! > > Seriously, I understand that you stay at what you know because things are > probably already complex enough, but really upgrading is often easier than > you think. > > > This effect will only get worse over time I guess. > > > > On Thu, Jul 30, 2015 at 9:04 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > > Hi, > > > > We have 622 open issues. There are *a lot* of old issues that nobody > will ever look at. > > Please check those that *you* submitted to see what the status is! > > > > If it is just âwould be niceâ, but not even on a level that you yourself > are willing to even > > send a mail to the mailing list to get people interested in helping you > to push the case > > forward, maybe you could think about closing the issue? > > > > Maybe someone asked a question? If you submit an issue and there is a > question not answered > > for a month, we should close it: How important can it be? Why should *I* > spend the time to fix > > this issue if *you* are not even willing to answer a question in a > minute? > > > > It makes no sense to have lots and lots of issues that are not important > even for the submitter. > > > > Another thing is that issues get fixed, subsystems replaced, code > removedâ¦ and the amazing thing > > is that *never* the submitter of the original report closes it, even in > these obvious cases. > > > > The issue tracker is not a one way street! > > > > Marcus > > > > > > > > >

July 30, 2015

Re: [Pharo-dev] [Issue tracker] *Please* look at your old reported issues!

by phil＠highoctane.be

Not with the tons of configs I load and the fact that Roassal2 has been moving under my feet. Phil On Thu, Jul 30, 2015 at 11:07 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 30 Jul 2015, at 10:27, phil(a)highoctane.be wrote: > > > > Most of the feedback is "won't fix" or "done in 4.x or 5.x" > > All nice but hard to look at as day to day work is in 3.0 > > You have to move, you are missing out on all the nice stuff ! > > Seriously, I understand that you stay at what you know because things are > probably already complex enough, but really upgrading is often easier than > you think. > > > This effect will only get worse over time I guess. > > > > On Thu, Jul 30, 2015 at 9:04 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > > Hi, > > > > We have 622 open issues. There are *a lot* of old issues that nobody > will ever look at. > > Please check those that *you* submitted to see what the status is! > > > > If it is just âwould be niceâ, but not even on a level that you yourself > are willing to even > > send a mail to the mailing list to get people interested in helping you > to push the case > > forward, maybe you could think about closing the issue? > > > > Maybe someone asked a question? If you submit an issue and there is a > question not answered > > for a month, we should close it: How important can it be? Why should *I* > spend the time to fix > > this issue if *you* are not even willing to answer a question in a > minute? > > > > It makes no sense to have lots and lots of issues that are not important > even for the submitter. > > > > Another thing is that issues get fixed, subsystems replaced, code > removedâ¦ and the amazing thing > > is that *never* the submitter of the original report closes it, even in > these obvious cases. > > > > The issue tracker is not a one way street! > > > > Marcus > > > > > > > > >

July 30, 2015

Re: [Pharo-dev] [Issue tracker] *Please* look at your old reported issues!

by Sven Van Caekenberghe

> On 30 Jul 2015, at 10:27, phil(a)highoctane.be wrote: > > Most of the feedback is "won't fix" or "done in 4.x or 5.x" > All nice but hard to look at as day to day work is in 3.0 You have to move, you are missing out on all the nice stuff ! Seriously, I understand that you stay at what you know because things are probably already complex enough, but really upgrading is often easier than you think. > This effect will only get worse over time I guess. > > On Thu, Jul 30, 2015 at 9:04 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > We have 622 open issues. There are *a lot* of old issues that nobody will ever look at. > Please check those that *you* submitted to see what the status is! > > If it is just âwould be niceâ, but not even on a level that you yourself are willing to even > send a mail to the mailing list to get people interested in helping you to push the case > forward, maybe you could think about closing the issue? > > Maybe someone asked a question? If you submit an issue and there is a question not answered > for a month, we should close it: How important can it be? Why should *I* spend the time to fix > this issue if *you* are not even willing to answer a question in a minute? > > It makes no sense to have lots and lots of issues that are not important even for the submitter. > > Another thing is that issues get fixed, subsystems replaced, code removedâ¦ and the amazing thing > is that *never* the submitter of the original report closes it, even in these obvious cases. > > The issue tracker is not a one way street! > > Marcus > > >

July 30, 2015

[Pharo5] Update #200!

by Marcus Denker

Hi, Update #200 is done! The issue tracker lists 621 closed issues for Pharo5. Marcus

July 30, 2015

Re: [Pharo-dev] [Issue tracker] *Please* look at your old reported issues!

by Marcus Denker

> On 30 Jul 2015, at 10:42, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Yes, there is not enough man power, we maintain one version back. This means that > everything people backport to Pharo4 will be integrated. > > With âindefiniteâ manpower this might be different, but even then you are in a lot of danger to reach a point where âmaintaining Pharo3â will turn into the same amount of change that is âPharo4â. Change is hard. Marcus

July 30, 2015