November 2017 - Pharo-users

Re: [Pharo-users] PharoLauncher directories

by stephan

On 09-11-17 11:49, Christophe Demarey wrote: > Stephan, could you open an issue for that on GH? https://github.com/pharo-project/pharo-launcher/issues/51 Stephan

Nov. 9, 2017

Re: [Pharo-users] Unable to load SmaCC on pharo6 (or pharo5)

by Federico.Balaguer

It works! Thanks a lot and I will be asking questions for sure. Thanks for your quick reply Federico -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 9, 2017

Re: [Pharo-users] Unable to load SmaCC on pharo6 (or pharo5)

by Thierry Goubier

Hi Frederico, could you try in a Pharo6.1 image Metacello new baseline: 'SmaCC'; repository: 'github://ThierryGoubier/SmaCC'; load SmaCC has a fairly complex set of dependencies, so loading it via the baseline should be the preferred way. Don't hesitate to ask if you have questions on SmaCC. Regards, Thierry Le 09/11/2017 Ã 19:06, Federico.Balaguer a Ã©critÂ : > I would like to check if I need to use SmaCC for a project. I tried to > install it on Pharo 6.1 32bits with iceberg but I was not able to do it. > > Then I tried to get SmaCC on an Pharo5 and Pharo6 images with "Catalog > Browser" but I was not able to do it neither. The tool did pop up a message > saying that Smacc was not tested for Pharo6 which was nice. > > Then I tried to clone the git repository to my local machine, I pointed > iceberg to that local repository and then I loaded each package by hand. I > was able to load BaselineOfSmaccBrowser but SmaCC-Rewrite-Engine failed to > load with a debugger with a list of classes and methods that are missing > (they are listed at the end of this message). > > Could some give an idea how to fix this? > > Thanks. Federico > > > This package depends on the following classes: > SmaCCStringInterval > SmaCCParseNodeVisitor > SmaCCScanner > SmaCCParseNode > SmaCCParser > SmaCCString > You must resolve these dependencies before you will be able to load these > definitions: > SmaCCAnnotatedString > SmaCCAnnotatedString>>#addAnnotationTo: > SmaCCAnnotatedString>>#intervalClass > SmaCCAnnotatedString>>#newIntervalFor: > SmaCCAnnotatedString>>#node > SmaCCAnnotatedString>>#node: > SmaCCAnnotatedString>>#removeInterval: > SmaCCAnnotatedString>>#rule > SmaCCAnnotatedString>>#rule: > SmaCCAnnotatedStringInterval > SmaCCAnnotatedStringInterval>>#addAllAnnotations: > SmaCCAnnotatedStringInterval>>#addAnnotation: > SmaCCAnnotatedStringInterval>>#annotations > SmaCCAnnotatedStringInterval>>#annotations: > SmaCCAnnotatedStringInterval>>#canBeMergedWith: > SmaCCAnnotatedStringInterval>>#postCopy > SmaCCCodeReplaceExpression > SmaCCCodeReplaceExpression>>#acceptVisitor: > SmaCCCodeReplaceExpression>>#code > SmaCCCodeReplaceExpression>>#code: > SmaCCCodeReplaceExpression>>#evaluateInContext: > SmaCCCodeReplaceExpression>>#method > SmaCCCodeReplaceExpression>>#tokenVariables > SmaCCCompositeReplaceExpression > SmaCCCompositeReplaceExpression>>#acceptVisitor: > SmaCCCompositeReplaceExpression>>#compositeNodeVariables > SmaCCCompositeReplaceExpression>>#evaluateInContext: > SmaCCCompositeReplaceExpression>>#expressions > SmaCCCompositeReplaceExpression>>#expressions: > SmaCCCompositeReplaceExpression>>#initialize > SmaCCNodeReplaceExpression > SmaCCNodeReplaceExpression>>#acceptVisitor: > SmaCCNodeReplaceExpression>>#addPostfixTo:inContext: > SmaCCNodeReplaceExpression>>#addPrefixTo:inContext: > SmaCCNodeReplaceExpression>>#afterPostfix > SmaCCNodeReplaceExpression>>#afterPostfix: > SmaCCNodeReplaceExpression>>#afterWhitespace > SmaCCNodeReplaceExpression>>#afterWhitespace: > SmaCCNodeReplaceExpression>>#beforePrefix > SmaCCNodeReplaceExpression>>#beforePrefix: > SmaCCNodeReplaceExpression>>#beforeWhitespace > SmaCCNodeReplaceExpression>>#beforeWhitespace: > SmaCCNodeReplaceExpression>>#evaluateInContext: > SmaCCNodeReplaceExpression>>#name > SmaCCNodeReplaceExpression>>#name: > SmaCCNodeReplaceExpression>>#postfix > SmaCCNodeReplaceExpression>>#postfix: > SmaCCNodeReplaceExpression>>#prefix > SmaCCNodeReplaceExpression>>#prefix: > SmaCCNodeReplaceExpression>>#tokenVariables > SmaCCReplaceExpression > SmaCCReplaceExpression>>#acceptVisitor: > SmaCCReplaceExpression>>#evaluateInContext: > SmaCCReplaceExpressionParser > SmaCCReplaceExpressionParser>>#cacheId > SmaCCReplaceExpressionParser>>#definitionComment > SmaCCReplaceExpressionParser>>#scannerClass > SmaCCReplaceExpressionParser>>#startingStateForExpression > SmaCCReplaceExpressionParser>>#reduceActionForCodeReplace1: > SmaCCReplaceExpressionParser>>#reduceActionForExpression1: > SmaCCReplaceExpressionParser>>#reduceActionForNodeReplace1: > SmaCCReplaceExpressionParser>>#reduceActionForPostfixModifiers1: > SmaCCReplaceExpressionParser>>#reduceActionForPrefixModifiers1: > SmaCCReplaceExpressionParser>>#reduceActionForPrefixModifiers2: > SmaCCReplaceExpressionParser>>#reduceActionForRewriteExpression3: > SmaCCReplaceExpressionParser>>#reduceActionForRewriteExpressions1: > SmaCCReplaceExpressionParser>>#reduceActionForRewriteExpressions2: > SmaCCReplaceExpressionParser>>#reduceActionForStringReplace1: > SmaCCReplaceExpressionParser>>#reduceActionForSwitchStateToCode1: > SmaCCReplaceExpressionParser>>#reduceActionForSwitchStateToDefault1: > SmaCCReplaceExpressionParser>>#reduceActionForSwitchStateToExpression1: > SmaCCReplaceExpressionParser>>#reduceTable > SmaCCReplaceExpressionParser>>#symbolNames > SmaCCReplaceExpressionParser>>#symbolTypes > SmaCCReplaceExpressionParser>>#transitionTable > SmaCCReplaceExpressionScanner > SmaCCReplaceExpressionScanner>>#codeExpressionId > SmaCCReplaceExpressionScanner>>#emptySymbolTokenId > SmaCCReplaceExpressionScanner>>#errorTokenId > SmaCCReplaceExpressionScanner>>#isValidCode > SmaCCReplaceExpressionScanner>>#next > SmaCCReplaceExpressionScanner>>#scanCode > SmaCCReplaceExpressionScanner>>#scanForToken > SmaCCReplaceExpressionScanner>>#scanForTokenX1 > SmaCCReplaceExpressionVisitor > SmaCCReplaceExpressionVisitor>>#visitCodeReplace: > SmaCCReplaceExpressionVisitor>>#visitCompositeReplace: > SmaCCReplaceExpressionVisitor>>#visitNodeReplace: > SmaCCReplaceExpressionVisitor>>#visitReplace: > SmaCCReplaceExpressionVisitor>>#visitStringReplace: > SmaCCRewriteRuleFileParser > SmaCCRewriteRuleFileParser>>#cacheId > SmaCCRewriteRuleFileParser>>#definitionComment > SmaCCRewriteRuleFileParser>>#fileExtension > SmaCCRewriteRuleFileParser>>#fileExtensionType > SmaCCRewriteRuleFileParser>>#parseFile: > SmaCCRewriteRuleFileParser>>#scannerClass > SmaCCRewriteRuleFileParser>>#startingStateForFile > SmaCCRewriteRuleFileParser>>#filename: > SmaCCRewriteRuleFileParser>>#lookupClass: > SmaCCRewriteRuleFileParser>>#reduceActionForComment2: > SmaCCRewriteRuleFileParser>>#reduceActionForFile1: > SmaCCRewriteRuleFileParser>>#reduceActionForImport1: > SmaCCRewriteRuleFileParser>>#reduceActionForMatch1: > SmaCCRewriteRuleFileParser>>#reduceActionForMatch2: > SmaCCRewriteRuleFileParser>>#reduceActionForMatch3: > SmaCCRewriteRuleFileParser>>#reduceActionForMatch4: > SmaCCRewriteRuleFileParser>>#reduceActionForParserClass1: > SmaCCRewriteRuleFileParser>>#reduceActionForRule1: > SmaCCRewriteRuleFileParser>>#reduceActionForRule2: > SmaCCRewriteRuleFileParser>>#reduceActionForRule3: > SmaCCRewriteRuleFileParser>>#reduceActionForRules1: > SmaCCRewriteRuleFileParser>>#reduceActionForRules2: > SmaCCRewriteRuleFileParser>>#reduceActionForRules3: > SmaCCRewriteRuleFileParser>>#reduceActionForRules4: > SmaCCRewriteRuleFileParser>>#reduceActionForStartSmalltalkExpression1: > SmaCCRewriteRuleFileParser>>#reduceActionForStartStringExpression1: > SmaCCRewriteRuleFileParser>>#reduceActionForTransformation1: > SmaCCRewriteRuleFileParser>>#reduceActionForTransformation2: > SmaCCRewriteRuleFileParser>>#reduceActionForVariable1: > SmaCCRewriteRuleFileParser>>#reduceActionForVariable2: > SmaCCRewriteRuleFileParser>>#reduceActionForVariableList1: > SmaCCRewriteRuleFileParser>>#reduceActionForVariableList2: > SmaCCRewriteRuleFileParser>>#reduceTable > SmaCCRewriteRuleFileParser>>#scanSmalltalkExpression > SmaCCRewriteRuleFileParser>>#scanStringExpression > SmaCCRewriteRuleFileParser>>#symbolNames > SmaCCRewriteRuleFileParser>>#transitionTable > SmaCCRewriteRuleFileParser>>#tryAllTokens > SmaCCRewriteRuleFileScanner > SmaCCRewriteRuleFileScanner>>#initializeKeywordMap > SmaCCRewriteRuleFileScanner>>#rewriter > SmaCCRewriteRuleFileScanner>>#rewriter: > SmaCCRewriteRuleFileScanner>>#emptySymbolTokenId > SmaCCRewriteRuleFileScanner>>#errorTokenId > SmaCCRewriteRuleFileScanner>>#fixExpression: > SmaCCRewriteRuleFileScanner>>#isValidSmalltalk: > SmaCCRewriteRuleFileScanner>>#scan1 > SmaCCRewriteRuleFileScanner>>#scan2 > SmaCCRewriteRuleFileScanner>>#scan3 > SmaCCRewriteRuleFileScanner>>#scan4 > SmaCCRewriteRuleFileScanner>>#scanForToken > SmaCCRewriteRuleFileScanner>>#scanForTokenX1 > SmaCCRewriteRuleFileScanner>>#scanForTokenX2 > SmaCCRewriteRuleFileScanner>>#scanForTokenX3 > SmaCCRewriteRuleFileScanner>>#scanForTokenX4 > SmaCCRewriteRuleFileScanner>>#scanForTokenX5 > SmaCCRewriteRuleFileScanner>>#scanForTokenX6 > SmaCCRewriteRuleFileScanner>>#scanForTokenX7 > SmaCCRewriteRuleFileScanner>>#scanSmalltalkExpression > SmaCCRewriteRuleFileScanner>>#scanStringExpression > SmaCCRewriteRuleFileScanner>>#tokenActions > SmaCCStringReplaceExpression > SmaCCStringReplaceExpression>>#acceptVisitor: > SmaCCStringReplaceExpression>>#evaluateInContext: > SmaCCStringReplaceExpression>>#string > SmaCCStringReplaceExpression>>#string: > SmaCCStringReplaceExpression>>#tokenVariables > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Nov. 9, 2017

Unable to load SmaCC on pharo6 (or pharo5)

by Federico.Balaguer

I would like to check if I need to use SmaCC for a project. I tried to install it on Pharo 6.1 32bits with iceberg but I was not able to do it. Then I tried to get SmaCC on an Pharo5 and Pharo6 images with "Catalog Browser" but I was not able to do it neither. The tool did pop up a message saying that Smacc was not tested for Pharo6 which was nice. Then I tried to clone the git repository to my local machine, I pointed iceberg to that local repository and then I loaded each package by hand. I was able to load BaselineOfSmaccBrowser but SmaCC-Rewrite-Engine failed to load with a debugger with a list of classes and methods that are missing (they are listed at the end of this message). Could some give an idea how to fix this? Thanks. Federico This package depends on the following classes: SmaCCStringInterval SmaCCParseNodeVisitor SmaCCScanner SmaCCParseNode SmaCCParser SmaCCString You must resolve these dependencies before you will be able to load these definitions: SmaCCAnnotatedString SmaCCAnnotatedString>>#addAnnotationTo: SmaCCAnnotatedString>>#intervalClass SmaCCAnnotatedString>>#newIntervalFor: SmaCCAnnotatedString>>#node SmaCCAnnotatedString>>#node: SmaCCAnnotatedString>>#removeInterval: SmaCCAnnotatedString>>#rule SmaCCAnnotatedString>>#rule: SmaCCAnnotatedStringInterval SmaCCAnnotatedStringInterval>>#addAllAnnotations: SmaCCAnnotatedStringInterval>>#addAnnotation: SmaCCAnnotatedStringInterval>>#annotations SmaCCAnnotatedStringInterval>>#annotations: SmaCCAnnotatedStringInterval>>#canBeMergedWith: SmaCCAnnotatedStringInterval>>#postCopy SmaCCCodeReplaceExpression SmaCCCodeReplaceExpression>>#acceptVisitor: SmaCCCodeReplaceExpression>>#code SmaCCCodeReplaceExpression>>#code: SmaCCCodeReplaceExpression>>#evaluateInContext: SmaCCCodeReplaceExpression>>#method SmaCCCodeReplaceExpression>>#tokenVariables SmaCCCompositeReplaceExpression SmaCCCompositeReplaceExpression>>#acceptVisitor: SmaCCCompositeReplaceExpression>>#compositeNodeVariables SmaCCCompositeReplaceExpression>>#evaluateInContext: SmaCCCompositeReplaceExpression>>#expressions SmaCCCompositeReplaceExpression>>#expressions: SmaCCCompositeReplaceExpression>>#initialize SmaCCNodeReplaceExpression SmaCCNodeReplaceExpression>>#acceptVisitor: SmaCCNodeReplaceExpression>>#addPostfixTo:inContext: SmaCCNodeReplaceExpression>>#addPrefixTo:inContext: SmaCCNodeReplaceExpression>>#afterPostfix SmaCCNodeReplaceExpression>>#afterPostfix: SmaCCNodeReplaceExpression>>#afterWhitespace SmaCCNodeReplaceExpression>>#afterWhitespace: SmaCCNodeReplaceExpression>>#beforePrefix SmaCCNodeReplaceExpression>>#beforePrefix: SmaCCNodeReplaceExpression>>#beforeWhitespace SmaCCNodeReplaceExpression>>#beforeWhitespace: SmaCCNodeReplaceExpression>>#evaluateInContext: SmaCCNodeReplaceExpression>>#name SmaCCNodeReplaceExpression>>#name: SmaCCNodeReplaceExpression>>#postfix SmaCCNodeReplaceExpression>>#postfix: SmaCCNodeReplaceExpression>>#prefix SmaCCNodeReplaceExpression>>#prefix: SmaCCNodeReplaceExpression>>#tokenVariables SmaCCReplaceExpression SmaCCReplaceExpression>>#acceptVisitor: SmaCCReplaceExpression>>#evaluateInContext: SmaCCReplaceExpressionParser SmaCCReplaceExpressionParser>>#cacheId SmaCCReplaceExpressionParser>>#definitionComment SmaCCReplaceExpressionParser>>#scannerClass SmaCCReplaceExpressionParser>>#startingStateForExpression SmaCCReplaceExpressionParser>>#reduceActionForCodeReplace1: SmaCCReplaceExpressionParser>>#reduceActionForExpression1: SmaCCReplaceExpressionParser>>#reduceActionForNodeReplace1: SmaCCReplaceExpressionParser>>#reduceActionForPostfixModifiers1: SmaCCReplaceExpressionParser>>#reduceActionForPrefixModifiers1: SmaCCReplaceExpressionParser>>#reduceActionForPrefixModifiers2: SmaCCReplaceExpressionParser>>#reduceActionForRewriteExpression3: SmaCCReplaceExpressionParser>>#reduceActionForRewriteExpressions1: SmaCCReplaceExpressionParser>>#reduceActionForRewriteExpressions2: SmaCCReplaceExpressionParser>>#reduceActionForStringReplace1: SmaCCReplaceExpressionParser>>#reduceActionForSwitchStateToCode1: SmaCCReplaceExpressionParser>>#reduceActionForSwitchStateToDefault1: SmaCCReplaceExpressionParser>>#reduceActionForSwitchStateToExpression1: SmaCCReplaceExpressionParser>>#reduceTable SmaCCReplaceExpressionParser>>#symbolNames SmaCCReplaceExpressionParser>>#symbolTypes SmaCCReplaceExpressionParser>>#transitionTable SmaCCReplaceExpressionScanner SmaCCReplaceExpressionScanner>>#codeExpressionId SmaCCReplaceExpressionScanner>>#emptySymbolTokenId SmaCCReplaceExpressionScanner>>#errorTokenId SmaCCReplaceExpressionScanner>>#isValidCode SmaCCReplaceExpressionScanner>>#next SmaCCReplaceExpressionScanner>>#scanCode SmaCCReplaceExpressionScanner>>#scanForToken SmaCCReplaceExpressionScanner>>#scanForTokenX1 SmaCCReplaceExpressionVisitor SmaCCReplaceExpressionVisitor>>#visitCodeReplace: SmaCCReplaceExpressionVisitor>>#visitCompositeReplace: SmaCCReplaceExpressionVisitor>>#visitNodeReplace: SmaCCReplaceExpressionVisitor>>#visitReplace: SmaCCReplaceExpressionVisitor>>#visitStringReplace: SmaCCRewriteRuleFileParser SmaCCRewriteRuleFileParser>>#cacheId SmaCCRewriteRuleFileParser>>#definitionComment SmaCCRewriteRuleFileParser>>#fileExtension SmaCCRewriteRuleFileParser>>#fileExtensionType SmaCCRewriteRuleFileParser>>#parseFile: SmaCCRewriteRuleFileParser>>#scannerClass SmaCCRewriteRuleFileParser>>#startingStateForFile SmaCCRewriteRuleFileParser>>#filename: SmaCCRewriteRuleFileParser>>#lookupClass: SmaCCRewriteRuleFileParser>>#reduceActionForComment2: SmaCCRewriteRuleFileParser>>#reduceActionForFile1: SmaCCRewriteRuleFileParser>>#reduceActionForImport1: SmaCCRewriteRuleFileParser>>#reduceActionForMatch1: SmaCCRewriteRuleFileParser>>#reduceActionForMatch2: SmaCCRewriteRuleFileParser>>#reduceActionForMatch3: SmaCCRewriteRuleFileParser>>#reduceActionForMatch4: SmaCCRewriteRuleFileParser>>#reduceActionForParserClass1: SmaCCRewriteRuleFileParser>>#reduceActionForRule1: SmaCCRewriteRuleFileParser>>#reduceActionForRule2: SmaCCRewriteRuleFileParser>>#reduceActionForRule3: SmaCCRewriteRuleFileParser>>#reduceActionForRules1: SmaCCRewriteRuleFileParser>>#reduceActionForRules2: SmaCCRewriteRuleFileParser>>#reduceActionForRules3: SmaCCRewriteRuleFileParser>>#reduceActionForRules4: SmaCCRewriteRuleFileParser>>#reduceActionForStartSmalltalkExpression1: SmaCCRewriteRuleFileParser>>#reduceActionForStartStringExpression1: SmaCCRewriteRuleFileParser>>#reduceActionForTransformation1: SmaCCRewriteRuleFileParser>>#reduceActionForTransformation2: SmaCCRewriteRuleFileParser>>#reduceActionForVariable1: SmaCCRewriteRuleFileParser>>#reduceActionForVariable2: SmaCCRewriteRuleFileParser>>#reduceActionForVariableList1: SmaCCRewriteRuleFileParser>>#reduceActionForVariableList2: SmaCCRewriteRuleFileParser>>#reduceTable SmaCCRewriteRuleFileParser>>#scanSmalltalkExpression SmaCCRewriteRuleFileParser>>#scanStringExpression SmaCCRewriteRuleFileParser>>#symbolNames SmaCCRewriteRuleFileParser>>#transitionTable SmaCCRewriteRuleFileParser>>#tryAllTokens SmaCCRewriteRuleFileScanner SmaCCRewriteRuleFileScanner>>#initializeKeywordMap SmaCCRewriteRuleFileScanner>>#rewriter SmaCCRewriteRuleFileScanner>>#rewriter: SmaCCRewriteRuleFileScanner>>#emptySymbolTokenId SmaCCRewriteRuleFileScanner>>#errorTokenId SmaCCRewriteRuleFileScanner>>#fixExpression: SmaCCRewriteRuleFileScanner>>#isValidSmalltalk: SmaCCRewriteRuleFileScanner>>#scan1 SmaCCRewriteRuleFileScanner>>#scan2 SmaCCRewriteRuleFileScanner>>#scan3 SmaCCRewriteRuleFileScanner>>#scan4 SmaCCRewriteRuleFileScanner>>#scanForToken SmaCCRewriteRuleFileScanner>>#scanForTokenX1 SmaCCRewriteRuleFileScanner>>#scanForTokenX2 SmaCCRewriteRuleFileScanner>>#scanForTokenX3 SmaCCRewriteRuleFileScanner>>#scanForTokenX4 SmaCCRewriteRuleFileScanner>>#scanForTokenX5 SmaCCRewriteRuleFileScanner>>#scanForTokenX6 SmaCCRewriteRuleFileScanner>>#scanForTokenX7 SmaCCRewriteRuleFileScanner>>#scanSmalltalkExpression SmaCCRewriteRuleFileScanner>>#scanStringExpression SmaCCRewriteRuleFileScanner>>#tokenActions SmaCCStringReplaceExpression SmaCCStringReplaceExpression>>#acceptVisitor: SmaCCStringReplaceExpression>>#evaluateInContext: SmaCCStringReplaceExpression>>#string SmaCCStringReplaceExpression>>#string: SmaCCStringReplaceExpression>>#tokenVariables -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 9, 2017

Re: [Pharo-users] Why does the test runner show red when I correct a test?

by Richard Sargent

I saw this earlier and thought it was wrong to make that change. You cannot assign a colour to the test if it does not run all the way through without interruption. You cannot know whether it truly succeeded or not until you finally run it all the way through without error or interruption. Leave it uncoloured until you (can) know for certain. On Thu, Nov 9, 2017 at 9:29 AM, Tim Mackinnon <tim(a)testit.works> wrote: > Thanks for looking at this - there is an issue however - when you apply > that change (at least in a Pharo 6.1 image) - it shows green even when a > test fails? So I think its turned one problem into the opposite one. > > Unfortunately I havenât got a chance to look a bit deeper to help - but it > might be worth rolling back this change for now. We should fix it though - > and the answer must be in the area you have identified. > > tim > > On 9 Nov 2017, at 12:43, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > And now it is in latest Pharo > > 2017-11-09 12:16 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> Hi Tim. >> >> Fix is here 20661-Fixing-test-from-debugger-should-mark-test-as-gre >> en-when-proceed <https://github.com/pharo-project/pharo/pull/456> . >> Thank's for reporting. It forces me to fix. I always noticed it but never >> take it seriously :) >> >> 2017-11-09 11:32 GMT+01:00 Tim Mackinnon <tim(a)testit.works>: >> >>> Hi - I really like the build in test runner in the Pharo browsers, and I >>> was preparing a talk to show how great TDD is in Pharo and how we arenât >>> ashamed of our debugger when testing (it augments the experience in fact - >>> letting you poke around and get your thoughts straight). >>> >>> However - if I pick rerun in the test runner debugger - and step through >>> a test and then correct the failing code, and hit resume - the browser >>> always shows a red failure, even though the execution is now correct. I >>> have to run the test again. >>> >>> This doesnât seem right to me - are we missing a success event or >>> something? >>> >>> >>> Tim >>> >> >> > >

Nov. 9, 2017

Re: [Pharo-users] Why does the test runner show red when I correct a test?

by Tim Mackinnon

Thanks for looking at this - there is an issue however - when you apply that change (at least in a Pharo 6.1 image) - it shows green even when a test fails? So I think its turned one problem into the opposite one. Unfortunately I havenât got a chance to look a bit deeper to help - but it might be worth rolling back this change for now. We should fix it though - and the answer must be in the area you have identified. tim > On 9 Nov 2017, at 12:43, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > And now it is in latest Pharo > > 2017-11-09 12:16 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>>: > Hi Tim. > > Fix is here 20661-Fixing-test-from-debugger-should-mark-test-as-green-when-proceed <https://github.com/pharo-project/pharo/pull/456> . > Thank's for reporting. It forces me to fix. I always noticed it but never take it seriously :) > > 2017-11-09 11:32 GMT+01:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > Hi - I really like the build in test runner in the Pharo browsers, and I was preparing a talk to show how great TDD is in Pharo and how we arenât ashamed of our debugger when testing (it augments the experience in fact - letting you poke around and get your thoughts straight). > > However - if I pick rerun in the test runner debugger - and step through a test and then correct the failing code, and hit resume - the browser always shows a red failure, even though the execution is now correct. I have to run the test again. > > This doesnât seem right to me - are we missing a success event or something? > > > Tim > >

Nov. 9, 2017

Re: [Pharo-users] LiteratureResearcher - where graphs, PDFs, and BibTex happily live together

by Manuel Leuenberger

Hi everyone, The estimation of packaging everything over the weekend was overly optimistic. There were just too many issues with portability and dependencies, leading to a long chain of installation requirements. Nevertheless, I decided to publish what I have so far, maybe some of you have more experience in making Pharo applications like this portable, especially Python is giving me a headache (literally). So, here are two source repositories and a all-in-one package, which may work for some of you (still macOS only): LiteratureResearcher sources https://github.com/maenu/LiteratureResearcher <https://github.com/maenu/LiteratureResearcher> contains the main sources and make scripts. Installation through Metacello should make the project, takes a while. PharoUriScheme source https://github.com/maenu/PharoUriScheme <https://github.com/maenu/PharoUriScheme> contains the sources for the pharo:// protocol wrapper. This is mainly an Xcode project, which introduces the platform dependency. This project can also be extended to support Linux and Windows. The all-in-one package https://figshare.com/articles/LiteratureResearcher_All-in-one/5584837 <https://figshare.com/articles/LiteratureResearcher_All-in-one/5584837> contains the LiteratureResearcher, still requires Java, Python 2.7, and virtualenv (shame on you, Python). Might work for some. Comments and contributors are very welcome, post issues, fork, create PRs, extend! Cheers, Manuel > On 2 Nov 2017, at 20:33, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > > Hi Stef, > > The PDF integration consists of three parts: > > 1. CERMINE (https://github.com/CeON/CERMINE <https://github.com/CeON/CERMINE>) is fed with the PDF and outputs metadata as BibTex and a structured XML (title, authors, affiliations, abstract, keyword, references, â¦). This is not perfect, but way better than any other metadata extractor I could find. > 2. From the metadata I generate hyperlinks that are anchored in the PDF by a text key. pdf-linker (https://github.com/maenu/pdf-linker <https://github.com/maenu/pdf-linker>) then searches for the anchors in the PDF text, using heuristics, as PDF has a document model that is primarily intended for rendering and printing, but not for processing. The hyperlinks are then inserted using the awesome Apache PDFBox (https://pdfbox.apache.org/ <https://pdfbox.apache.org/>). > 3. Those hyperlinks point to an URI like âpharo://handle/clickReference.in.?args=1&args=2 <pharo://handle/clickReference.in.?args=1&args=2>â to represent a reference 1 in the paper 2. Now comes the magic part: The OS allows you to register custom handlers for custom URI schemes like pharo://. For that I created a simple Objective-C app that handles the event and passes it over as a HTTP message to a server running in Pharo (https://github.com/maenu/PharoUriScheme <https://github.com/maenu/PharoUriScheme>). The OS will even start the application if it is not yet running. > > While the custom URI scheme approach is super powerful, it has critical drawbacks. Any application can request to be the receiver of a URI scheme, just as browser are for http://. Especially on mobile devices with limited access to the OS, this opens up an attack point for malware apps that replicate original apps that make use of schemes like facebook:// and eavesdrop all interactions. If an original app transmits any unencrypted secrets or user data encoded in those URIs, malware can easily intercept it without the user noticing the leak. I guess this is the reason why many PDF viewer just support the standard http:// and mailto:// schemes. E.g., macOS Preview gives just an audible beep when I click on a pharo:// link, Chromes viewer doesnât even bother giving any feedback. Only Adobe Acrobat allows you to relax security settings to make them work (How could it be someone else than Adobe, when itâs a security issue? ;). > > I finished basic packaging today and will continue with some READMEs and a nearly-all-in-one distribution tomorrow, Iâll keep you posted in this thread. > > Cheers, > Manuel > >> On 2 Nov 2017, at 18:08, Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: >> >> Hi manuel >> >> this is super cool :) >> Could you describe how you did the pdf integration? >> And yes please package it :) >> I want to try it. >> >> Stef >> >> On Wed, Nov 1, 2017 at 10:16 PM, Manuel Leuenberger >> <leuenberger(a)inf.unibe.ch <mailto:leuenberger@inf.unibe.ch>> wrote: >>> Hi everyone, >>> >>> I was experimenting in the last few weeks with my take on literature >>> research. For me, the corpus of scientific papers form an interconnected >>> graph, not those plain lists and tables we keep in our bibliographies. So, >>> here is the first prototype that has Google Scholar integration for search, >>> can fetch PDFs from IEEE and ACM, extracts metadata from PDFs - all this >>> results in hyperlinked PDFs! >>> >>> See a demo here: https://youtu.be/EcK3Pt_WnEw <https://youtu.be/EcK3Pt_WnEw> >>> Also slides from the SCG seminar here: >>> http://scg.unibe.ch/download/softwarecomposition/2017-10-31-Leuenberger-ILE… <http://scg.unibe.ch/download/softwarecomposition/2017-10-31-Leuenberger-ILE…> >>> >>> I plan on packaging it, so that those who are interested can check it out >>> themselves (help wanted!). Currently, it only works on macOS. >>> >>> What do you think of my approach? Which use cases should be added? >>> >>> Cheers, >>> Manuel >>> >> >

Nov. 9, 2017

Re: [Pharo-users] Writing "powerpoint" like presentations in Pharo?

by Andrew Glynn

People mistake my notion of a platform having a stable core so that it can be built on, with never changing that core one bit. A stable, evolving core is precisely what allows rapid and flexible new product improvement. Wasnât that the whole point of deprecation rather than replacement? It gives developers of a given product a version or two to update their code when the base evolves. Itâs a mystery to me overall though, as well. Andrew From: Marcus Denker Sent: Thursday, November 9, 2017 8:48 AM To: Any question about pharo is welcome Subject: Re: [Pharo-users] Writing "powerpoint" like presentations in Pharo? On 9 Nov 2017, at 14:22, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: Sophie looked very promising... Unfortunately it was not open source and died before porting it to Java (following the Illuminati conspiracy of porting Smalltalk break througts to "inferior" technology, as happens once and again :-P). Sophie was one of the reason I got so, umm, upset? about Squeakâ¦ I mean even though the project failed, the results where on a level that they could have been used to improve Squeak quite radically. All the base technology was more or less finished and workingÂ (maybe a bit complex at times, cf. Tweakâ¦). I still do not understand why everyone back then had this âSqueak is untouchable, you can only build on top or you are an evil personâ view of the world. Just imagine the people who did Sophie would have done their work by *contributing* to Squeak in a serious way (in the sense of evolving it into the next thing). The resulting system would have been amazing.Â The fact that Sophie failed as a project would have been not important *at all*. You could finance an amazing platform by just doing failed projects. As long as you do them open source and feed back the results. The same happened with everything Etoys, with everything Croquet. And even though there where people working on all these things at the same time. To me this is a mystery. It made no sense, at all.Â Marcus

Nov. 9, 2017

Re: [Pharo-users] Writing "powerpoint" like presentations in Pharo?

by Marcus Denker

> On 9 Nov 2017, at 14:22, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Sophie looked very promising... Unfortunately it was not open source and died before porting it to Java (following the Illuminati conspiracy of porting Smalltalk break througts to "inferior" technology, as happens once and again :-P). > > Sophie was one of the reason I got so, umm, upset? about Squeakâ¦ I mean even though the project failed, the results where on a level that they could have been used to improve Squeak quite radically. All the base technology was more or less finished and working (maybe a bit complex at times, cf. Tweakâ¦). I still do not understand why everyone back then had this âSqueak is untouchable, you can only build on top or you are an evil personâ view of the world. Just imagine the people who did Sophie would have done their work by *contributing* to Squeak in a serious way (in the sense of evolving it into the next thing). The resulting system would have been amazing. The fact that Sophie failed as a project would have been not important *at all*. You could finance an amazing platform by just doing failed projects. As long as you do them open source and feed back the results. The same happened with everything Etoys, with everything Croquet. And even though there where people working on all these things at the same time. To me this is a mystery. It made no sense, at all. Marcus

Nov. 9, 2017

Re: [Pharo-users] Writing "powerpoint" like presentations in Pharo?

by Andrew Glynn

Search and ye shall receive! â¦ Or find, or whatever â¦ Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. ((Smalltalk at: #ConfigurationOfFFI) project latestVersion) load. Gofer new squeaksource: 'SophieGoldDig'; package: 'SpdQT'; load. Warning, this was last tested as far as I can tell in Pharo 1.1.1. Andrew From: Offray Vladimir Luna CÃ¡rdenas Sent: Thursday, November 9, 2017 8:23 AM To: pharo-users(a)lists.pharo.org Subject: Re: [Pharo-users] Writing "powerpoint" like presentations in Pharo? Sophie looked very promising... Unfortunately it was not open source and died before porting it to Java (following the Illuminati conspiracy of porting Smalltalk break througts to "inferior" technology, as happens once and again :-P). Offray On 09/11/17 02:40, Norbert Hartl wrote: Everytime I read such discussions I wonder what happened to the Sophie code. There be might be some gems in it to achieve what you want Norbert Am 09.11.2017 um 03:49 schrieb Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com>: I remember using CompendiumNG some time ago, but not for presentations. Hopefully, we will have something better, with metamedium capabilities, including embedding other media and make it programmable in Pharo, without going to the "disastrous" slide metaphor. Cheers, Offray On 08/11/17 20:31, Andrew Glynn wrote: I agree with you â on the rare occasions I do still do presentations I tend to use CompendiumNG, which is similar to a mind map but can contain any content, including multimedia content.Â It was an Open University project but was used sufficiently elsewhere that when the Open University decided they were done with it the project was forked and continued by others. Â Itâs written in Java, currently I believe thereâs no binary although itâs easy to build.Â If you just wanted the installer jar to try it out though let me know. Â Honestly though Iâd probably still use Director if it werenât for Adobeâs pricing. Â Andrew Glynn Â Sent from Mail for Windows 10 Â From: Offray Vladimir Luna CÃ¡rdenas Sent: Wednesday, November 8, 2017 7:45 AM To: pharo-users(a)lists.pharo.org Subject: Re: [Pharo-users] Writing "powerpoint" like presentations in Pharo? Â Â Â On 07/11/17 19:39, Sean P. DeNigris wrote: > Offray Vladimir Luna CÃ¡rdenas-2 wrote >> The idea of slides seems >> pretty anachronistic/boring for making presentations. > Amen, brother! Alan Kay would be proud :) >Â Â Maybe. I refer the whole aesthetics of slides (even the ones with animations or simulations). You go in slide at the time, bullet point by bullet point, loosing context and perspective. My usual approach is mind maps. In [1] you can see the exported SVG version of the one I use in a Grafoscopio workshop. Source code is in [2]. Â [1] http://mutabit.com/grafoscopio/Docs/En/Talks/Overview/grafoscopio-mapa.svg [2] http://mutabit.com/grafoscopio/Docs/En/Talks/Overview/grafoscopio-mapa.mm Â Cheers, Â Offray Â Â

Nov. 9, 2017