September 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Sept. 18, 2016

Sept. 18, 2016

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

1 0

[pharo-project/pharo-core] c99d2f: 60228
by GitHub Sept. 18, 2016

Sept. 18, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: c99d2f375b0cb5cb410026c84a125e0600cb5738 https://github.com/pharo-project/pharo-core/commit/c99d2f375b0cb5cb410026c8… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-18 (Sun, 18 Sep 2016) Changed paths: M EpiceaBrowsers.package/EpAbsentItem.class/instance/populating browser/icon.st M EpiceaBrowsers.package/EpFetchMoreItem.class/instance/populating browser/icon.st M EpiceaBrowsers.package/EpIconVisitor.class/instance/private/additionIcon.st M EpiceaBrowsers.package/EpIconVisitor.class/instance/private/emptyIcon.st A EpiceaBrowsers.package/EpIconVisitor.class/instance/private/iconNamed_.st M EpiceaBrowsers.package/EpIconVisitor.class/instance/private/modificationIcon.st M EpiceaBrowsers.package/EpIconVisitor.class/instance/private/removalIcon.st M EpiceaBrowsers.package/EpLogBrowser.class/instance/initialization/initializeTabs.st M EpiceaBrowsers.package/EpLogBrowserItem.class/definition.st M EpiceaBrowsers.package/EpLogNodesModel.class/instance/initialization/initializeRefreshButtonModel.st M EpiceaBrowsers.package/EpLogNodesModel.class/instance/initialization/initializeSelectedDirectoryButtonModel.st M EpiceaBrowsers.package/EpMonitorModel.class/instance/initialization/initializePresenter.st M EpiceaBrowsers.package/EpMonitorModel.class/instance/refreshing/refresh.st M EpiceaBrowsers.package/EpSelection.class/definition.st M EpiceaBrowsers.package/EpSelection.class/instance/populating menu/filtersSubMenu.st M EpiceaBrowsers.package/EpSelection.class/instance/populating menu/populateMenu_.st M Komitter.package/KomitLeaf.class/instance/accessing/icon.st M Komitter.package/KomitPackageNode.class/instance/api/icon.st M Komitter.package/KomitPackageNode.class/instance/initialization/initialize.st M Komitter.package/KomitRemote.class/definition.st M Komitter.package/RemotesManager.class/instance/initialization/initializeWidgets.st M NautilusRefactoring.package/PackageAndClassChooser.class/instance/accessing - tree/iconFor_.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/checkboxSelectedForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/checkboxUnselectedForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/menuPinForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/newCheckboxMarkerForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/newRadioButtonMarkerForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/newWindowCloseForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/newWindowMaximizeForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/newWindowMenuForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/newWindowMenuPassiveForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/newWindowMinimizeForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/radioButtonForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/radioButtonSelectedForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/windowClosePassiveForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/windowMaximizePassiveForm.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/forms/windowMinimizePassiveForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/checkboxSelectedForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/checkboxUnselectedForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/menuPinForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/newCheckboxMarkerForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/newRadioButtonMarkerForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/newWindowCloseForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/newWindowMaximizeForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/newWindowMenuForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/newWindowMenuPassiveForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/newWindowMinimizeForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/radioButtonForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/radioButtonSelectedForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/windowClosePassiveForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/windowMaximizePassiveForm.st M Polymorph-Widgets.package/Pharo3Theme.class/instance/forms/windowMinimizePassiveForm.st M Polymorph-Widgets.package/UITheme.class/definition.st M QualityAssistant.package/QAFeedbackMorph.class/instance/initialization/initializeNegativeFeedback.st M QualityAssistant.package/QAFeedbackMorph.class/instance/initialization/initializePositiveFeedback.st M Reflectivity-Tools.package/WatchpointWindow.class/instance/initialization/setupMenu.st M Renraku.package/ReAbstractCritique.class/instance/accessing/icon.st M Renraku.package/ReAbstractCritique.class/instance/actions/actions.st M Renraku.package/ReProperty.class/definition.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60227.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60228.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60227.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60228.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M ShoreLine-Report-UI.package/SlReportWindow.class/instance/initialization/initializeControls.st M Tool-DependencyAnalyser-UI.package/DAAddPackageModel.class/instance/initialization/initializeWidgets.st M Tool-DependencyAnalyser-UI.package/DAAssemblyNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAClassToDependencyNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DACycleNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DADependentPackageNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAExtensionDependencyNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAInheritanceDependencyNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAManuallyAddedDependentPackageNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAMessageSendNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAMethodImplementationNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAMissingMethodNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAPackageAnalyzerTreeModel.class/instance/initialization/initializeButtons.st M Tool-DependencyAnalyser-UI.package/DAPackageDependenciesWelcome.class/instance/initialization/initializeButtons.st M Tool-DependencyAnalyser-UI.package/DAPackageItemDiffNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAPackageTreeModel.class/instance/initialization/initializeWidgets.st M Tool-DependencyAnalyser-UI.package/DAPackageUnderAnalysisNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAPotentialDependenciesNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAReferenceDependencyNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAReverseDependentPackageNode.class/instance/accessing/icon.st M Tool-DependencyAnalyser-UI.package/DAReversePackageNode.class/instance/accessing/icon.st M Tool-FileList.package/FileDirectoryWrapper.class/instance/accessing/icon.st M Versionner-Spec-Browser.package/VSDetailsLeafNode.class/instance/accessing/icon.st M Versionner-Spec-Browser.package/VSGroupNode.class/instance/accessing/icon.st M Versionner-Spec-Browser.package/VSPackageNode.class/instance/accessing/icon.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/initialization/initializeWidgets.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/ui/iconForVersion_.st M Versionner-Spec-Browser.package/VersionnerProjectPackagesPanel.class/instance/initialization/initializeWidgets.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/initialization/initializeGroupsWidget.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/initialization/initializeProjectsWidget.st M Versionner-Spec-Browser.package/VersionnerProjectToolBar.class/instance/initialization/initializeWidgets.st Log Message: ----------- 60228 19102 Another clean iconNamed: phase... https://pharo.fogbugz.com/f/cases/19102 http://files.pharo.org/image/60/60228.zip

1 0

[ANN] Pillar 4.0.0
by Thibault ARLOING Sept. 17, 2016

Sept. 17, 2016

Hello, I'm happy to announce the latest release of Pillar. This release has been possible because of the hard work of Damien Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. What did it bring and what are the largest changes ? * Huge cleaning of code and Dependencies * Many bug fixes * Huge refactoring of internal parts * Extract phase management into an external project (LightPhaser) * Transformers and Phases are all Pipes Remove Compilation cycle * Remove template handling from Pillar * Remove generation of pillarpostExport.sh * Pillar now exports files to JSON format * Command for pillar archetypes "./pillar archetype book", book can be replaced by other archetype names (see Pillar documentation) * Possibility to load an archetype with a Makefile to compile pillar files Features * Check phase to check syntax * EPub exporter for e-books (use pillar archetypes for this) * Semantic links to Youtube and Wikipedia * Citations for LaTeX * Structures (see Pillar documentation) * Footnotes for HTML, Markdown, LaTeX and AsciiDoc * Improvement of parsing configuration failure message Major changes * Metadata field in configuration to separate data from configuration properties * Support files in configuration does no longer exists * "disableTransformers" property is now named "disabledPhases" * AsciiDoc file extension is now ".asciidoc" * Pillar now manages one input file, not a collection of input files anymore * Parameter inputFiles is now replaced by inputFile The documentation of Pillar will be update as soon as possible to fit those changes. Cheers, Thibault

5 9

Author / TestRunner interaction in fresh image
by Ben Coman Sept. 16, 2016

Sept. 16, 2016

In a freshly downloaded build 60224, I open TestRunner and run all tests. At run 418 I get a dialogue asking for the Author. To me that seems wrong. I don't want any code changes made during testing to have my normal identification on them. Tests invoked from Test Runner should be author-tagged something like 'TestRunner' or 'TestRunner-BenComan'. The question arises in this particular case due to... RPackageMonticelloSynchronisationTest >> setUp ... Author fullName ifNil: [ Author fullName: 'Tester' ]. Minor point... this check actually is a bit pointless since #fullName invokes #requestFullName that presents the dialog. And #fullName will *never* return nil. At a minimum it returns 'Anonymous'. First step would seem to be wrapping TestCase>>runCase: with Author useAuthor: 'TestRunner' during: [ .... ] But further. I envisage a time when TestRunner doesn't block the UI, so I can happily browse around the system and code while TestRunner is doing its thing. Obviously the system is not set up to have two parties (myself and TestRunner) both updating code in the system, but changing the state of the global Author uniqueInstance like this... Author>>useAuthor: aString during: aBlock ^ self uniqueInstance useAuthor: aString during: aBlock would itself seem to a big impediment. It would be good if "Author" was dependent on the context of the call chain. This would seem a requirement for one day having two people working in the one Image (is this a possible use case where someone is using a remote debugger while another person is using the standard UI?) So my second proposal is for Author>>fullName to invoke a Notification mechanism to determine #fullName. Something like... Notification subclass: AuthorRequest Author>>#fullName ^ AuthorRequest new signal instanceVariables: 'contextFullName'. Author>>useAuthor: tempAuthorFullname during: aBlock [ block ] on: AuthorRequest do: [ :noti | noti contextFullName: tempAuthorFullname ] with only unhandled AuthorRequests returning "Author uniqueInstance basicFullname". Thus code changes are not constrained to be assigned to a global author. Not that we *yet* have multiple people working in one image, but one more impediment is removed - step by step. What concerns would there be? cheers -ben

6 10

Re: [Pharo-dev] Call for design for a literal programming doc similar to PythonDocTest
by philippe.back＠highoctane.be Sept. 16, 2016

Sept. 16, 2016

How is all of this PackageManifest mechanism working? Doc anywhere? Phil Le 16 sept. 2016 17:02, "Nicolai Hess" <nicolaihess(a)gmail.com> a Ã©crit : 2016-09-16 0:19 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > I'd be more interested with a package level doc than a class doc or test. > > Package level doc is quite useful to outline how some things are working > together, something which is quite hard to figure out except by reading > external doc or inferring things by walking through the code or a running > test. > Why don't we have yet package comments ? I see there is some support for it in PackageManifest, I remember there was some work (people working) on support for Nautilus, no? maybe something like this, (see attached file) Nautilus comment pane on class selection -> show class comment no class selection -> show package comment (class side #description of package manifest of this package) you can even add or change the (package) comment, it will compile a proper #description method on the manifest class) > > Having the ability to read about a package would be very useful. > Basically, this is what Java provides. > > http://docs.oracle.com/javase/7/docs/technotes/tools/solaris > /javadoc.html#packagecomment > > Phil > > > On Thu, Sep 15, 2016 at 8:45 PM, stepharo <stepharo(a)free.fr> wrote: > >> Hi all >> >> I want something similar in the spirit to PythonDocTest >> https://docs.python.org/2/library/doctest.html >> >> I'm talking about >> >> basename >> "Returns the base of the basename, >> i.e. >> /foo/gloops.taz basename is 'gloops.taz' >> / basename is '/'" >> >> Pragmas do not work well i.e., >> basename >> "Returns the base of the basename" >> <expr: '''/foo/gloops.taz'' asFileReference basename' result: >> 'gloops.taz'> >> >> >> We should invent a syntax to be put inside comments and that we can >> easily parse because we need to improve >> the use and discovery of the library. >> >> I was thinking about >> >> basename >> "Returns the base of the basename" >> " >> '/foo/gloops.taz' asFileReference basename >> >>> 'gloops.taz' >> " >> >> Do you have any idea? >> >> I cannot not do anything and just complain that our methods are not that >> well documented. >> We as a community should take this and build an super cool system. >> >> I tried and defined >>> on Object to see if it works! >> >> Object >>> aResultingObject >> "If the method comment contains >>> then it is a pharo documentated >> test. We can check that it is true." >> >> " >> '/foo/gloops.taz' asFileReference basename >> >>> 'gloops.taz' >> " >> >> ^ self = aResultingObject >> >> >> Stef >> >> >> >

1 0

[ANN] RProjectConnector V2.1
by Blondeau Vincent Sept. 16, 2016

Sept. 16, 2016

Hello everyone, I am glad to announce the release of version 2.1 of the RProjectConnector. The binding between Pharo and R (https://www.r-project.org/) is now translated to UFFI and so to Pharo 6.0. You can call directly your R methods from Pharo. For example, with the famous iris clustering example: iris := 'eval' asREval: {RObject findVar: 'iris'}. 'plot' asREval: {(iris at: 'Petal.Length'). (iris at: 'Petal.Width'). (#pch -> 21). (#xlab -> 'length'). (#ylab -> 'Width'). (#bg ->((iris at: 'Species') collect: [ :value | {'red'. 'green3'. 'blue'} at: value ])). (#main -> 'Edgar Anderson''s Iris Data')}. iris inspect. To use it, you should install R and copy the R libraries near the Pharo VM (see the documentation on SmalltalkHub (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for how to proceed). Don't forget to relaunch Pharo after the installation to be able to use the connector. Only basic features are implemented yet, but you can participate to its extension! Cheers, Vincent Blondeau !!!************************************************************************************* "Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

3 10

Maintainer of TxText: action needed
by Marcus Denker Sept. 16, 2016

Sept. 16, 2016

Hi, Whoever maintains TxTxt: there is a fix ready since 19 July 2016. Can we get this into the system, please? https://pharo.fogbugz.com/f/cases/18788/TxTextStyler-do-not-work (or we should give up in this being maintained âexternallyâ)

3 2

[pharo-project/pharo-core]
by GitHub Sept. 16, 2016

Sept. 16, 2016

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

1 0

[pharo-project/pharo-core] b402df: 60227
by GitHub Sept. 16, 2016

Sept. 16, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b402df88fd1de5a005362c220e24808cbf004c27 https://github.com/pharo-project/pharo-core/commit/b402df88fd1de5a005362c22… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-16 (Fri, 16 Sep 2016) Changed paths: M FuelTools-Debugger.package/FuelOutStackDebugAction.class/class/serialization/serializeTestFailureContext_toFileNamed_.st A Kernel.package/Context.class/instance/system simulation/stepToHome_.st M Kernel.package/Process.class/instance/changing suspended state/stepToHome_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60226.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60227.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60226.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60227.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/MessageBrowser.class/instance/api/selectedClass.st Log Message: ----------- 60227 16877 another endless debugger loop https://pharo.fogbugz.com/f/cases/16877 19097 Move to instance side refactoring of class method in the sender list is mispelled https://pharo.fogbugz.com/f/cases/19097 19098 FuelOutStackDebugAction uses incorrect debugger API https://pharo.fogbugz.com/f/cases/19098 http://files.pharo.org/image/60/60227.zip

1 0

60224 TestRunner warning Collections-Arithmetic manually resolved dependency not detected as a dependency!
by Ben Coman Sept. 16, 2016

Sept. 16, 2016

This curious warning appeared when running TestRunner in a fresh 60224.image... Collections-Abstract: Collections-Arithmetic dependency declared in the package Manifest as manuallyResolvedDependencies not detected as a dependency! There is... ManifestCollectionsArithmetic class >> dependencies ^ #(#'Collections-Native' #'Collections-Unordered' #'Collections-Sequenceable' #Kernel #'Collections-Abstract') and removing the last element makes the error go away, but I was wondering if that was the RightThing or the warning was a symptom for something else? btw, was is "manually resolved" ? Is it just adding elements to #dependencies? cheers -ben

2 1