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

Re: [Pharo-dev] pharo intro slides?

by Damir Majer

+1 thatÂ´s what IÂ´ve looking for! thx Damien Cassou-2 wrote > Damir Majer < > damir@ > > writes: > >> Hi NG, >> >> IÂ´m searching for slides which explains >> - what is pharo? >> - how pharo works? >> - ... >> >> Do you have some tips / links where I can find 'pharo Intro' slides? > > the Pharo MOOC contains everything you need: > > https://ci.inria.fr/pharo-contribution/job/PharoMooc/lastSuccessfulBuild/ar… > > Look in particular at Week1 which contains the introductory courses. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill ----- -- Damir Majer ... be agile: www.majcon.de -- View this message in context: http://forum.world.st/pharo-intro-slides-tp4881101p4881222.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 26, 2016

removing of TestReviver

by Pavel Krivanek

Hi, TestReviver that is a part of HudsonBuildTools20 and it is a tool that can process Fuel files generated by CI server. It is an UI tool dependent on Spec so it adds some mess to headless images without GUI that need to use HudsonBuildTools for SUnit reports. I propose to remove it from the standard image and move it to a separate SmalltalkHub project. It is not used directly in Pharo and will be easy to load it from the Catalog by people who need such functionality. Cheers, -- Pavel

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Alexandre Bergel

> Assertions are used in standard java framework, but have hard side effects : stopping the program immediately. > (cf > http://www.oracle.com/us/technologies/java/assertions-139853.html > "...The program will be aborted if the expression evaluates to false..") > With java it is possible, since the IDE and program are separated. > > With Pharo you cannot, if you assert or throw an error in a sensible place, you are likely to hang your image or to go for multiple errors poping everywhere since you will break the state of an important object. I do not think so. It is like putting a "self haltâ (or âHalt nowâ). It is all done using exceptions. > Another thing is that with dbc paradigm (assertions about your code), there is no 'one invariant' but lots of, you will not be able to express them in a single method, even if you could it would be hundreds lines and you would have to copy them in all methods you will want to check. > The complete horror to maintain when you change your code. I would not be that pessimistic. > The use of pragmas make it possible to activate or deactivate those contracts at compilation time, there will no overhead in standard execution without contracts. > Think of the pragmas as a way to "inject" invariant compiled code into the compiled method for testing, then you recompile without for release. > > Adding invariants will have *big* performance impact, probably several orders of magnitude, I'll measure. > The overhead will of course come from calls of the checking framework, but no doubt that with run-time reflexivity checking, you will have something as sluggish too and you'll want to deactivate them at compile time â¦ currently, the class Object define the method: -=-=-=-=-=-=-=-=-= Object>>assert: aBlock "Throw an assertion error if aBlock does not evaluates to true. We check for true explicitly to make the assertion fail for non booleans" aBlock value == true ifFalse: [AssertionFailure signal: 'Assertion failedâ] -=-=-=-=-=-=-=-=-= It looks like a pretty convenient way to handle assertion. Nearly the same as in standard Java. Java offers the âassertâ keywords, that you can disable by setting adequate option in the JVM. If you want to disable the assertions in your class, you can simply redefine #asset: that does nothing. Sure, you can imagine a solution using pragmas, but sincerely, I do not think it will be more flexible than using #assert:. Again, Javaâs assertions are very similar to what we have now. However, I am pretty convinced there are great opportunities on writing assertions. It is really hard to write them, which is why not many are doing so. Cheers, Alexandre > -- > > Alain > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Damien Cassou

Alexandre Bergel <alexandre.bergel(a)me.com> writes: > But, all in all, what are we using pragmas here? > I can always do: > self assert: [ â¦ ] description: â¦ you can do that for preconditions, but for postconditions it is harder because there can be several exit points in a method. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Feb. 26, 2016

Re: [Pharo-dev] Run time checking with design by contract assertions

by Damien Cassou

Alexandre Bergel <alexandre.bergel(a)me.com> writes: > I still do not understand. I would imagine something like: > > foo > <precondition: #invariant> > <postcondition: #invariant> > self bar I have the same feeling. It looks strange to me that the precondition itself decides where it applies. I have the impression that each method should list its preconditions. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Feb. 26, 2016

[pharo-project/pharo-core] d37f4c: 50616

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d37f4c4a5a71b7c6c8f367283212d4a8a8a16626 https://github.com/pharo-project/pharo-core/commit/d37f4c4a5a71b7c6c8f36728… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-26 (Fri, 26 Feb 2016) Changed paths: M ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/symbolic versions/stable_.st A ConfigurationOfVersionner.package/ConfigurationOfVersionner.class/instance/versions/version2138_.st A Morphic-Examples.package/PluggableButtonMorphExample.class/class/examples/exampleButtonFont.st M Morphic-Widgets-Basic.package/PluggableButtonMorph.class/definition.st A Morphic-Widgets-Basic.package/PluggableButtonMorph.class/instance/accessing/font.st A Morphic-Widgets-Basic.package/PluggableButtonMorph.class/instance/accessing/font_.st A Morphic-Widgets-Basic.package/PluggableButtonMorph.class/instance/accessing/getFontSelector.st A Morphic-Widgets-Basic.package/PluggableButtonMorph.class/instance/accessing/getFontSelector_.st M Morphic-Widgets-Basic.package/PluggableButtonMorph.class/instance/accessing/label_.st M Morphic-Widgets-Basic.package/PluggableButtonMorph.class/instance/accessing/newLabel.st M Morphic-Widgets-Basic.package/PluggableButtonMorph.class/instance/updating/update_.st M Network-Kernel.package/NetworkSystemSettings.class/class/settings/isAnExceptionFor_.st R OpalCompiler-Tests.package/OCPragmaTest.class/instance/method-tested/methodApicall.st R OpalCompiler-Tests.package/OCPragmaTest.class/instance/testing/testApicall.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50615.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50616.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50615.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50616.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/ButtonModel.class/definition.st A Spec-Core.package/ButtonModel.class/instance/api-events/whenFontChangedDo_.st A Spec-Core.package/ButtonModel.class/instance/api/font.st A Spec-Core.package/ButtonModel.class/instance/api/font_.st M Spec-Core.package/ButtonModel.class/instance/initialization/initialize.st M Spec-Examples.package/DynamicWidgetChange.class/instance/private/changeToButton.st M Spec-Examples.package/DynamicWidgetChange.class/instance/private/changeToList.st M Spec-MorphicAdapters.package/MorphicButtonAdapter.class/instance/factory/buildWidget.st A Spec-MorphicAdapters.package/MorphicButtonAdapter.class/instance/widget API/font.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/accessing-ui/requiredProjectMenu_.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/actions/browseSelectedProject.st Log Message: ----------- 50616 17311 Versionner, MNU if we try to fix version of a package in a load directive. https://pharo.fogbugz.com/f/cases/17311 17703 Failing test: OCPragmaTest>>#testApicall https://pharo.fogbugz.com/f/cases/17703 13183 Proxy exceptions not considered by ZnClient https://pharo.fogbugz.com/f/cases/13183 17707 PluggableButtonMorph should respond to font: (also spec) https://pharo.fogbugz.com/f/cases/17707 http://files.pharo.org/image/50/50616.zip

Feb. 26, 2016

[pharo-project/pharo-core]

by GitHub

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

Feb. 26, 2016

Re: [Pharo-dev] pharo intro slides?

by Damien Cassou

Damir Majer <damir(a)majcon.de> writes: > Hi NG, > > IÂ´m searching for slides which explains > - what is pharo? > - how pharo works? > - ... > > Do you have some tips / links where I can find 'pharo Intro' slides? the Pharo MOOC contains everything you need: https://ci.inria.fr/pharo-contribution/job/PharoMooc/lastSuccessfulBuild/ar… Look in particular at Week1 which contains the introductory courses. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Feb. 26, 2016

Re: [Pharo-dev] [Moose-dev] Re: Re: Call for action for Roassal

by Peter UhnÃ¡k

Hi Anne, I've just added a Roassal plugin with the GraphViz-based layout. Note that I had to hack it to work with RTMultiLine (it was originally designed for different lines which are currently not part of Roassal), so it's possible there will be some issues. You can load it (if you have latest Roassal installed) via the Roassal plugin menu, or by executing the following Metacello new baseline: 'GraphVizLayout'; repository: 'github://peteruhnak/graphviz-layout:master/repository'; load Then look at the class-side examples in RTGraphVizLayout. Finally if you use this, you shouldn't move elements within the layout (because graphviz layout hard-codes the pathing)â¦ we could probably change this in the future, but I am not sure how (ideally the layout would have to be recomputed, but that's expensive to do live), So to summarize: * you must have GraphViz installed in your system * you must use RTMultiLine for lines (because only they support bending) Let me know how it goes, â â Peter On Thu, Feb 25, 2016 at 2:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Oh, I missed this one :). So, now I can refactor the code that is still > using the RTEdge class side methods :). > > Great! > > Thanks, > Doru > > > > On Feb 25, 2016, at 1:59 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > > Oh, but this has been in Roassal for many months (I have implemented > since right after ESUG). You need to use #source:connectFrom:toAll: > > > > Here is an example that randomly generate a graph and render it using > this facility: > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > nbOfNodes := 40. > > nbOfRandomEdges := 40. > > > > nodes := 1 to: nbOfNodes. > > edges := (1 to: nbOfRandomEdges) > > collect: [ :notUsed | nodes atRandom -> > {nodes atRandom . nodes atRandom} ]. > > > > b := RTMondrian new. > > > > b shape circle color: (Color black alpha: 0.5). > > b nodes: nodes. > > > > b shape line color: (Color gray alpha: 0.3). > > b edges > > source: edges connectFrom: #key toAll: #value. > > > > b layout force. > > b > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > > <Screen Shot 2016-02-25 at 1.57.24 PM.png> > > > > Cheers, > > Alexandre > > > >> On Feb 25, 2016, at 1:37 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >> Hi, > >> > >> We discussed this before. Try to draw a hierarchy using classes and > inheritance objects (so, without using the class to superclass navigation). > Something like this: > >> > >> view := RTMondrian new. > >> view nodes: classes. > >> view edges objects: inheritances; connectFrom: #superclass to: > #subclass. > >> view layout tree. > >> view > >> > >> It wonât work. > >> > >> Cheers, > >> Doru > >> > >> > >>> On Feb 25, 2016, at 1:29 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > >>> > >>> Do you have an example? I am not sure to understand. > >>> > >>> Alexandre > >>> > >>> > >>>> On Feb 25, 2016, at 12:40 PM, Tudor Girba <tudor(a)tudorgirba.com> > wrote: > >>>> > >>>> This is very cool. We will all benefit from this documentation. > >>>> > >>>> One thing that I would still like to see fixed before the release is > the edge building (this problem of not being able to properly specify > random objects to be taken into account when building edges). Could we work > on that? > >>>> > >>>> Cheers, > >>>> Doru > >>>> > >>>> > >>>>> On Feb 24, 2016, at 9:51 AM, Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > >>>>> > >>>>> Dear community, > >>>>> > >>>>> As you may have seen, Roassal has entered a stabilization phase. The > book AgileVisualization.com will soon be released. After its release, > Roassal will go over a new development phase. In order to prepare it, I am > asking this question: > >>>>> > >>>>> What are the 3 aspects you would like to see improved in Roassal? > >>>>> > >>>>> You can answer publicly or by sending private messages. > >>>>> > >>>>> Kind regards, > >>>>> Alexandre > >>>>> -- > >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >>>>> Alexandre Bergel http://www.bergel.eu > >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Moose-dev mailing list > >>>>> Moose-dev(a)list.inf.unibe.ch > >>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev > >>>> > >>>> -- > >>>> www.tudorgirba.com > >>>> www.feenk.com > >>>> > >>>> âLive like you mean it." > >>>> > >>>> > >>> > >>> -- > >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >>> Alexandre Bergel http://www.bergel.eu > >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >>> > >>> > >>> > >>> _______________________________________________ > >>> Moose-dev mailing list > >>> Moose-dev(a)list.inf.unibe.ch > >>> https://www.list.inf.unibe.ch/listinfo/moose-dev > >> > >> -- > >> www.tudorgirba.com > >> www.feenk.com > >> > >> "Value is always contextual." > >> > >> > >> > >> > >> > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

Feb. 26, 2016

[pharo-project/pharo-core] 10879b: 50615

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 10879b838b4cea37930122fd56c09daf7a6e8e29 https://github.com/pharo-project/pharo-core/commit/10879b838b4cea37930122fd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-26 (Fri, 26 Feb 2016) Changed paths: M AST-Core.package/ASTCache.class/class/class initialization/initialize.st R AST-Core.package/ASTCache.class/class/class initialization/release.st M Balloon.package/ShortIntegerArray.class/class/initialize-release/initialize.st R Balloon.package/ShortIntegerArray.class/class/initialize-release/release.st M FileSystem-Core.package/FileLocator.class/class/class initialization/initialize.st R FileSystem-Core.package/FileLocator.class/class/class initialization/release.st R Files.package/FileStream.class/class/initialize-release/release.st M Files.package/MultiByteFileStream.class/class/class initialization/initialize.st R Kernel.package/Delay.class/class/initialize-release/release.st M Kernel.package/SmallInteger.class/class/initialize-release/initialize.st R Kernel.package/SmallInteger.class/class/initialize-release/release.st M MonticelloFileTree-Core.package/extension/MCFileRepositoryInspector/instance/refresh.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/actions/load.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/actions/merge.st A MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/invalidatePackageAncestryCache.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/versionHighlightEmphasis_.st R NonInteractiveTranscript.package/NonInteractiveTranscript.class/class/class initialization/release.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50614.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50615.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50614.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50615.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Clipboard.package/Clipboard.class/class/initialization/initialize.st R System-Clipboard.package/Clipboard.class/class/initialization/release.st M System-VMEvents.package/InputEventFetcher.class/class/class initialization/install.st M System-VMEvents.package/InputEventSensor.class/class/class initialization/installEventSensorFramework_.st M Tool-ImageCleaner.package/ImageCleaner.class/instance/api/cleanUpForRelease.st M Tool-ProcessBrowser.package/CPUWatcher.class/class/class initialization/initialize.st Log Message: ----------- 50615 17711 Reset Registry of MetacelloProjectRegistration to remove Obsolete configuration instances https://pharo.fogbugz.com/f/cases/17711 17712 clean old startup mechanism - part 1 https://pharo.fogbugz.com/f/cases/17712 17655 Changes in package loading behavior https://pharo.fogbugz.com/f/cases/17655 http://files.pharo.org/image/50/50615.zip

Feb. 26, 2016