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

Re: [Pharo-dev] about diff paths

by Stephane Ducasse

'/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/Chapters/Scheme.pillar' asFileReference path relativeToPath: '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/Chapters/' asFileReference path In fact / should split or raise an exception. Stef On Fri, Feb 2, 2018 at 12:51 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > I want to know the path from a given point in a path > for example > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/Chapters/Scheme.pillar' > asFileReference path > relativeToPath: (Path / > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/') > > should give me 'Chapters/Scheme.pillar' > > as in the example in the method > > (Path / 'griffle' / 'plonk' / 'nurp') > relativeToPath: (Path / 'griffle') > returns plonk/nurp > > But I got > > Path * '..' / 'Users' / 'ducasse' / 'Workspace' / 'FirstCircle' / > 'MyBooks' / 'Bk-Writing' / 'PharoBooks' / 'Booklet-AMiniSchemeInPharo' > / 'Chapters' / 'Scheme.pillar' > > and I do not understand. I can do it doing string manipulation but it defeats > the purpose to have a nice library. > > Any hints? > > Stef

Feb. 2, 2018

Disabling a MenuGroupModel

by HernÃ¡n Morales Durand

Hi guys, If you develop an application window with multiple grouped menu items, you will certainly be able to enable/disable menu groups at once. Currently it is not possible with MenuGroupModel (Morphic). - A menu (item or group) model manages its state using enabledHolder instance variable (the enabledHolder is configured in its superclass' initialize) -- Being a value holder, one might think there is a propagation of state (enabled/disabled) changes to subwidgets, but it does not happen currently. --- Longer explanation: On static menu building, MenuGroupModel does not propagate #enable: state changes to its widget because "widget" i.v. is nil. The reason is a MenuGroupModel #enabled: is evaluated BEFORE its widget is built. How to reproduce: | mm | mm := MenuModel new addGroup: [ :group | group addItem: [ :item | item name: 'File'; icon: #openIcon asIcon; subMenu: (MenuModel new addGroup: [ : gp | gp disable; " <------ HERE we disable the group " addItem: [ : it | it name: 'Open'; icon: #openIcon asIcon; shortcut: $o meta; action: [ self inform: 'Open' ] ]; addItem: [ : it | it name: 'Save'; icon: #smallSaveIcon asIcon; shortcut: $s meta; action: [ self inform: 'Save' ] ] ]) ] ]; yourself. mm extent: 200 @ 100. mm openWithSpec. mm inspect. (it doesn't matter if #disable is sent after the #addItem: block evaluation) - Even after all MenuGroupModel widgets were built, if you try to disable a menu group dinamically: mm menuGroups anyOne menuItems anyOne subMenu menuGroups anyOne disable. you would get "Instance of OrderedCollection did not understand #enabled:" (the widget of a MenuGroupModel is an OrderedCollection!!). - However disabling/enabling MenuItemModel works: mm menuGroups anyOne menuItems anyOne subMenu menuGroups anyOne menuItems first disable. - MenuItemModel gets actually disabled in the ToggleMenuItemMorph/UpdatingMenuMorph (#isEnabled:) when the Canvas draws it. - Incredibly, all disabled groups are re-enabled from several places in the image. -- When the menu is clicked, a ToolDockingBarMorph triggers re-enablement of the MenuMorph in #removeMatchString/#displayFiltered:. This is presumably the code triggered when a menu is displayed and you type to filter the menu items. Something like this: "As initially there is no matchString in the activeSubMenu, then enable all menu items". Obviously it cleans disabled items. The message flow is: DockingBarMorph>>activeSubmenu: -> MenuMorph>>removeMatchString -> MenuMorph>>displayFiltered: --> m isEnabled: isMatch - Another place where menu items are automatically disabled is this flow: FormCanvas>>draw: -> ToggleMenuItemMorph>>drawOn: --> ToggleMenuItemMorph>>isEnabled --> ToggleMenuItemMorph>>isEnabled: !!! --> MorphicMenuItemAdapter>>enabled (This actually CHANGES the enabled state on the Model, disconnecting enabled state between the morph and the model adapter) This seem to have multiple paths of resolution. I'm going to propose a fix that I tested in Pharo 6.1 and Pharo 7. I don't know yet how to fix the menu search auto-enable on key-press but would be glad to read a solution to distinguish between both uses. My idea for now is to have a Morphic property which sets #doNotAutoReEnableItems. However I will open an issue and let people check. You can test it with " Disable the group " mm menuGroups anyOne menuItems anyOne subMenu menuGroups anyOne disable. " Enable the group " mm menuGroups anyOne menuItems anyOne subMenu menuGroups anyOne enable. Cheers, HernÃ¡n

Feb. 2, 2018

Re: [Pharo-dev] [ANN] Updating Consultants Listing

by Marcus Denker

> On 17 Jan 2018, at 17:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We have http://consultants.pharo.org <http://consultants.pharo.org/> > > I want to change it to > - not be a forward to files.pharo.org <http://files.pharo.org/> DONE: http://consultants.pharo.org <http://consultants.pharo.org/> TBD: > - be auto-generated from the https://association.pharo.org <https://association.pharo.org/> > Marcus

Feb. 2, 2018

[Pharo 7.0-dev] Build #493: 21230-revert-tearDown-order-in-OmSessionStoreTesttearDown

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #493 was: SUCCESS. The Pull Request #791 was integrated: "21230-revert-tearDown-order-in-OmSessionStoreTesttearDown" Pull request url: https://github.com/pharo-project/pharo/pull/791 Issue Url: https://pharo.fogbugz.com/f/cases/21230 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 2, 2018

about diff paths

by Stephane Ducasse

Hi I want to know the path from a given point in a path for example '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/Chapters/Scheme.pillar' asFileReference path relativeToPath: (Path / '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/') should give me 'Chapters/Scheme.pillar' as in the example in the method (Path / 'griffle' / 'plonk' / 'nurp') relativeToPath: (Path / 'griffle') returns plonk/nurp But I got Path * '..' / 'Users' / 'ducasse' / 'Workspace' / 'FirstCircle' / 'MyBooks' / 'Bk-Writing' / 'PharoBooks' / 'Booklet-AMiniSchemeInPharo' / 'Chapters' / 'Scheme.pillar' and I do not understand. I can do it doing string manipulation but it defeats the purpose to have a nice library. Any hints? Stef

Feb. 2, 2018

[Pharo 7.0-dev] Build #492: 20953-Gitlab-Private-Project-Support-via-Iceberg

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #492 was: FAILURE. The Pull Request #790 was integrated: "20953-Gitlab-Private-Project-Support-via-Iceberg" Pull request url: https://github.com/pharo-project/pharo/pull/790 Issue Url: https://pharo.fogbugz.com/f/cases/20953 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 2, 2018

[Pharo 7.0-dev] Build #491: 21229-Enhance-file-attribute-tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #491 was: SUCCESS. The Pull Request #789 was integrated: "21229-Enhance-file-attribute-tests" Pull request url: https://github.com/pharo-project/pharo/pull/789 Issue Url: https://pharo.fogbugz.com/f/cases/21229 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 2, 2018

[Pharo 7.0-dev] Build #490: 21161-Epicea-do-not-create-directory-on-startUp-if-EpMonitor-is-not-logging

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #490 was: SUCCESS. The Pull Request #751 was integrated: "21161-Epicea-do-not-create-directory-on-startUp-if-EpMonitor-is-not-logging" Pull request url: https://github.com/pharo-project/pharo/pull/751 Issue Url: https://pharo.fogbugz.com/f/cases/21161 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 2, 2018

Re: [Pharo-dev] MCGitlabRepository Missing

by Pavel Krivanek

The PR was against a wrong branch. The fixed one is being validated. -- Pavel 2018-02-02 8:17 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hi, > > The PR was this: > > https://github.com/pharo-project/pharo/pull/700/files > > It might be that the baseline is not used somehow? > > >> On 2 Feb 2018, at 04:36, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> Realized this should've been on dev list, not users. Sorry for the cross >> postâ¦ >> >> An image with build 454 seems still not to have MCGitlabRepository present. >> What am I missing? >> Same for build 462 with sha 3641442f3ba0613cd9a6428181487ea29e62418c, which >> has the package in its source: >> https://github.com/pharo-project/pharo/tree/3641442f3ba0613cd9a6428181487ea… >> >> Ditto for build 487.sha.58ee23aadcd15e0a969ed675e8141c0cfd95594a >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> > >

Feb. 2, 2018

[Pharo 7.0-dev] Build #489: 21094 Super tearDown need to be called as last message in tearDown of Metacello

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #489 was: SUCCESS. The Pull Request #767 was integrated: "21094 Super tearDown need to be called as last message in tearDown of Metacello" Pull request url: https://github.com/pharo-project/pharo/pull/767 Issue Url: https://pharo.fogbugz.com/f/cases/21094 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 2, 2018