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

Re: [Pharo-dev] About "compileSilently"

by Thierry Goubier

2015-05-28 16:49 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > How silent should "compileSilently" be? > > no trace in the system : > 15314 <https://pharo.fogbugz.com/default.asp?15314> > compileSilently and method history / changes file > > not half silenlty > 13023 <https://pharo.fogbugz.com/default.asp?13023> > Test Cases should not do things half silently > > not "SystemAnnouncer-silent" > 10560 <https://pharo.fogbugz.com/default.asp?10560> > SystemAnnouncer and compileSilently > > > ? > > What do you think, what granularity of "silent" do we need. > I see at least three different use cases: > > - just an ordinary compile > ? Silent means that: Core infrastructure is not updated properly (i.e. RPackage) and tools (Browsers) can end desynchronised with the methods. > - compile for tests > Probably the one... But I wonder if this is a good idea anyway. I'd believe most tests using silently are using it wrongly and shouldn't be using it in the first place. > - compile autogenerated methods. > This one may not be silent. If the auto-generated method will be visible (saved in a package, can be browsed, etc...) then it shouldn't be silent. Thierry > > > > > nicolai > >

May 28, 2015

About "compileSilently"

by Nicolai Hess

How silent should "compileSilently" be? no trace in the system : 15314 <https://pharo.fogbugz.com/default.asp?15314> compileSilently and method history / changes file not half silenlty 13023 <https://pharo.fogbugz.com/default.asp?13023> Test Cases should not do things half silently not "SystemAnnouncer-silent" 10560 <https://pharo.fogbugz.com/default.asp?10560> SystemAnnouncer and compileSilently ? What do you think, what granularity of "silent" do we need. I see at least three different use cases: - just an ordinary compile - compile for tests - compile autogenerated methods. nicolai

May 28, 2015

Re: [Pharo-dev] Is there an official JSON parser/writer?

by Esteban A. Maringolo

2015-05-28 3:41 GMT-03:00 stepharo <stepharo(a)free.fr>: >> The problem is no JSON parser is bundled by default, so adding the >> dependency to either class is arbitrary. > Why declaring a dependency would be a bad idea. > You use then declare it! I didn't say "bad", I said "arbitrary". :) Otherwise I'm establishing a personal preference of a particular library, that isn't directly replaceable by other of the user preference. I like to provide a reasonable default, but keep options open. :) Regards! Esteban A. Maringolo

May 28, 2015

Re: [Pharo-dev] Beyond RPackages: RPackageTag and DynamicGroup

by Ben Coman

On Thu, May 28, 2015 at 5:48 PM, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: > (Personally I have no idea of Work criteria to list classes, and have no > idea of the details of the other two) Neither do I. Never used them. Now I wonder if when you define a new group, you might also define a filter and the existing groups use that facility, such that you could inspect and existing group to see its definition. cheers -ben

May 28, 2015

Re: [Pharo-dev] HudsonBuildTools repository?

by Johan Brichau

Ok, I will merge the code changes. Our package actually was already renamed JenkinsBuildTools [1] :) [1] https://github.com/jbrichau/JenkinsBuildTools <https://github.com/jbrichau/JenkinsBuildTools> > On 28 May 2015, at 13:02, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > ahhhhh :) > thatâs integrated in image (not that Iâm happy with that, butâ¦ ) so it has to be handled (for now) with SLICEs. > I would be super happy if you create a configuration of it and extract it to a subproject (like sthub Pharo/HudsonBuildToolsâ¦ or even better Pharo/JenkinsBuildTools). > then we can manage it through configurations, a much much better approach :) > > Esteban > >> On 28 May 2015, at 12:55, Johan Brichau <johan(a)inceptive.be <mailto:johan@inceptive.be>> wrote: >> >> Esteban, >> >> I mean the HudsonBuildTools Smalltalk package containing classes such as HDTestReport >> >> itâs still in your Pharo4 image btw :) >> >> Johan >> >>> On 28 May 2015, at 11:43, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>> >>> HI, >>> >>> Hudson tools are obsolete sinceâ¦ well, since before hudson was renamed as jenkins :) >>> I donât know why you maintain them or what changes you did, but is not needed and we are not using them since years (I donât even remember last time I checked at them). >>> Instead, we use zeroconf and command line (check at our configurations in ci.pharo.org <http://ci.pharo.org/> and pharo-contribution to have an ideaâ¦ >>> >>> Now, what we still use is the scripts to build distributions (formerly one-click, now platform dependent). You can check them at: https://github.com/pharo-project/pharo-ci <https://github.com/pharo-project/pharo-ci> >>> >>> Esteban >>> >>>> On 28 May 2015, at 10:49, Johan Brichau <johan(a)inceptive.be <mailto:johan@inceptive.be>> wrote: >>>> >>>> Hi all, >>>> >>>> Over the past few years we have maintained our own fork of Lukasâ HudsonBuildTools package, but I noticed there are updates flowing in with newer version of Pharo. >>>> >>>> So, I would like to merge our version with Pharoâs (and vice-versa) but I am unable to find where the main repository for this package is. >>>> >>>> Can anyone point me to that? >>>> >>>> thanks >>>> Johan >>> >> >

May 28, 2015

[pharo-project/pharo-core]

by GitHub

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

May 28, 2015

[pharo-project/pharo-core] eb08f8: 50071

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: eb08f8ddd1f60e951235d46481199f4e7d8bb684 https://github.com/pharo-project/pharo-core/commit/eb08f8ddd1f60e951235d464… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-28 (Thu, 28 May 2015) Changed paths: M Refactoring-Tests-Core.package/RBRefactoringTest.class/instance/set up/setUp.st M Refactoring-Tests-Core.package/RBRefactoringTest.class/instance/set up/tearDown.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50070.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50071.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50070.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50071.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Spec-Tests.package/TestAutoFractionComputation.class/instance/as yet unclassified/initializeWidgets.st A Spec-Tests.package/TestAutoFractionComputation.class/instance/initialization/initializeWidgets.st A Spec-Tests.package/TestingComposableModel.class/instance/accessing/list.st R Spec-Tests.package/TestingComposableModel.class/instance/as yet unclassified/initializeWidgets.st R Spec-Tests.package/TestingComposableModel.class/instance/as yet unclassified/list.st A Spec-Tests.package/TestingComposableModel.class/instance/initialization/initializeWidgets.st R Tool-Base.package/PharoShortcuts.class/instance/kaymaps - Tools/openKomitterShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - Tools/openKomitterShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - Tools/openMonticielloShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - Tools/openPlaygroundShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - Tools/openSettingsShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - Tools/openSystemBrowserShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - Tools/openTestRunnerShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - Tools/openTranscriptShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - Tools/saveImageShortcut.st M Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openMonticelloPackageBrowser.st M Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openSettings.st M Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openSystemBrowser.st M Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openTranscript.st M Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openUnitTestRunner.st M Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openWorkspace.st M Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/saveImage.st Log Message: ----------- 50071 15623 regenerate package information for TClass classTrait methods https://pharo.fogbugz.com/f/cases/15623 15620 RBRefactoringTest has strange code to access class variables https://pharo.fogbugz.com/f/cases/15620 15612 ToolShortcutsCategory has hard code shortcut. https://pharo.fogbugz.com/f/cases/15612 15618 Remove ComposableModel>>#instantiateModels:s senders in Spec-Tests https://pharo.fogbugz.com/f/cases/15618 http://files.pharo.org/image/50/50071.zip

May 28, 2015

does recent changes broke playground with dark theme?

by Esteban Lorenzano

Iâm having some forced black fonts there. Can you confirm it? Esteban

May 28, 2015

Re: [Pharo-dev] HudsonBuildTools repository?

by Esteban Lorenzano

ahhhhh :) thatâs integrated in image (not that Iâm happy with that, butâ¦ ) so it has to be handled (for now) with SLICEs. I would be super happy if you create a configuration of it and extract it to a subproject (like sthub Pharo/HudsonBuildToolsâ¦ or even better Pharo/JenkinsBuildTools). then we can manage it through configurations, a much much better approach :) Esteban > On 28 May 2015, at 12:55, Johan Brichau <johan(a)inceptive.be> wrote: > > Esteban, > > I mean the HudsonBuildTools Smalltalk package containing classes such as HDTestReport > > itâs still in your Pharo4 image btw :) > > Johan > >> On 28 May 2015, at 11:43, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> HI, >> >> Hudson tools are obsolete sinceâ¦ well, since before hudson was renamed as jenkins :) >> I donât know why you maintain them or what changes you did, but is not needed and we are not using them since years (I donât even remember last time I checked at them). >> Instead, we use zeroconf and command line (check at our configurations in ci.pharo.org <http://ci.pharo.org/> and pharo-contribution to have an ideaâ¦ >> >> Now, what we still use is the scripts to build distributions (formerly one-click, now platform dependent). You can check them at: https://github.com/pharo-project/pharo-ci <https://github.com/pharo-project/pharo-ci> >> >> Esteban >> >>> On 28 May 2015, at 10:49, Johan Brichau <johan(a)inceptive.be <mailto:johan@inceptive.be>> wrote: >>> >>> Hi all, >>> >>> Over the past few years we have maintained our own fork of Lukasâ HudsonBuildTools package, but I noticed there are updates flowing in with newer version of Pharo. >>> >>> So, I would like to merge our version with Pharoâs (and vice-versa) but I am unable to find where the main repository for this package is. >>> >>> Can anyone point me to that? >>> >>> thanks >>> Johan >> >

May 28, 2015

Re: [Pharo-dev] HudsonBuildTools repository?

by Johan Brichau

Esteban, I mean the HudsonBuildTools Smalltalk package containing classes such as HDTestReport itâs still in your Pharo4 image btw :) Johan > On 28 May 2015, at 11:43, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > HI, > > Hudson tools are obsolete sinceâ¦ well, since before hudson was renamed as jenkins :) > I donât know why you maintain them or what changes you did, but is not needed and we are not using them since years (I donât even remember last time I checked at them). > Instead, we use zeroconf and command line (check at our configurations in ci.pharo.org <http://ci.pharo.org/> and pharo-contribution to have an ideaâ¦ > > Now, what we still use is the scripts to build distributions (formerly one-click, now platform dependent). You can check them at: https://github.com/pharo-project/pharo-ci <https://github.com/pharo-project/pharo-ci> > > Esteban > >> On 28 May 2015, at 10:49, Johan Brichau <johan(a)inceptive.be <mailto:johan@inceptive.be>> wrote: >> >> Hi all, >> >> Over the past few years we have maintained our own fork of Lukasâ HudsonBuildTools package, but I noticed there are updates flowing in with newer version of Pharo. >> >> So, I would like to merge our version with Pharoâs (and vice-versa) but I am unable to find where the main repository for this package is. >> >> Can anyone point me to that? >> >> thanks >> Johan >

May 28, 2015