Re: [Pharo-dev] printString of fileReference sucks!

Tx I will reread the threads! On Sat, Feb 3, 2018 at 4:07 AM, Sean P. DeNigris wrote: > Stephane Ducasse-3 wrote >> What do you think? > > If it helps, here is some background material… > > - The original issue where we (I) created this behavior, along with the >

Re: [Pharo-dev] printString of fileReference sucks!

Stephane Ducasse-3 wrote > What do you think? If it helps, here is some background material… - The original issue where we (I) created this behavior, along with the rationale: https://pharo.fogbugz.com/f/cases/7366/FileReferences-have-a-confusing-wrong-external-representation - A subsequent ML

Re: [Pharo-dev] MCGitlabRepository Missing

Pavel Krivanek-3 wrote > The PR was against a wrong branch. The fixed one is being validated. The class has appeared in the latest built image! The only thing left for this to work is to update Iceberg (dev-0.6 branch) where the other half of the patch lives :) - Cheers, Sean -- Sent from:

Re: [Pharo-dev] Disabling a MenuGroupModel

https://pharo.fogbugz.com/f/cases/21233/Disabling-a-MenuGroupModel-bug 2018-02-02 10:10 GMT-03:00 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

Re: [Pharo-dev] Weird ZnClient benchmarking result

https://pharo.fogbugz.com/f/cases/21232/BenchmarkResult-printFrequencyOn-can-be-confusing https://github.com/pharo-project/pharo/pull/794 > On 12 Dec 2017, at 07:22, Stephane Ducasse wrote: > > sven did you submit a fix to get a clearer printout? > > Stef > > > On

Re: [Pharo-dev] another file reference question

Hi Stef, On 2 February 2018 at 20:58, Stephane Ducasse wrote: > Then I do not get why / is expecting a string and cannot accept a path. > > Then I do not get why we have paths. > Stef Paths are intended to be internal, and not something you ever deal with directly. I'm

Re: [Pharo-dev] another file reference question

Hi Can you provide more simple example with shorter paths? I am lost in these long strings :). 2018-02-02 20:22 GMT+01:00 Stephane Ducasse : > HI > > I have the following scenario: > > '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- >

Re: [Pharo-dev] printString of fileReference sucks!

2018-02-02 20:39 GMT+01:00 Esteban A. Maringolo : > If for some reason the option chosen is to keep the current > printString then the printString should be: > >>> 'File @ ''/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk- >

Re: [Pharo-dev] printString of fileReference sucks!

Hi. I do not think that getting simple string as result is a good idea. It is important to easily distinguish class of object using printIt operation and as a field in raw inspector. During code migration to FileSystem it is classic way to check variables in debugger to see if they are already

Re: [Pharo-dev] Change Pharo window icon

Yes I did that when I was at University. So clearly dated. On Fri, Feb 2, 2018 at 8:40 PM, p...@highoctane.be wrote: > For Windows one can change it using a resource editor. > > http://www.angusj.com/resourcehacker/ > > Phil > > On Feb 2, 2018 20:33, "Stephane Ducasse"

[Pharo-dev] FileSystem copyToFolder: is missing :(

Hi copyTo: forces the user to manipulate full path while we could also have aFileReference copyToFolder: aFileReference Now I have to create the target. Stef

Re: [Pharo-dev] printString of fileReference sucks!

I saw that guillermo already needed it for pillar Path >> pillarPrintString self isEmpty ifTrue: [ ^ '' ]. ^ String streamContents: [ :str | str nextPutAll: (self at: 1) asString. 2 to: self size do: [:i | str

Re: [Pharo-dev] another file reference question

Then I do not get why / is expecting a string and cannot accept a path. Then I do not get why we have paths. Stef On Fri, Feb 2, 2018 at 8:22 PM, Stephane Ducasse wrote: > HI > > I have the following scenario: > >

Re: [Pharo-dev] printString of fileReference sucks!

Exactly, let us see what others think and we fix it. To me FileSystem deserves some love. On Fri, Feb 2, 2018 at 8:39 PM, Esteban A. Maringolo wrote: > Hi Stef, all, > > I've seen this "inconsistency" as well. The current printSting tries > to be descriptive but isn't

Re: [Pharo-dev] Change Pharo window icon

For Windows one can change it using a resource editor. http://www.angusj.com/resourcehacker/ Phil On Feb 2, 2018 20:33, "Stephane Ducasse" wrote: > Would it be possible to change the icon without having to compile a new VM? > To me the current setup looks so

Re: [Pharo-dev] printString of fileReference sucks!

Hi Stef, all, I've seen this "inconsistency" as well. The current printSting tries to be descriptive but isn't handy to work with. I would go one step further and have no #asFileReference suffix nor File @ prefix, it is:

Re: [Pharo-dev] Change Pharo window icon

Would it be possible to change the icon without having to compile a new VM? To me the current setup looks so monolithic and dated. I would expect that somebody can deploy a application with its own logo by just providing some new resources. Stef On Wed, Jan 31, 2018 at 11:17 PM, Eliot Miranda

[Pharo-dev] another file reference question

HI I have the following scenario: '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' asFileReference / 'book.pillar' >>> "File @

[Pharo-dev] printString of fileReference sucks!

Hi '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' asFileReference printString >>> "File @ >>> /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result" so either we add @ one File or we

Re: [Pharo-dev] about diff paths

'/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 /

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

> On 17 Jan 2018, at 17:27, Marcus Denker wrote: > > Hi, > > We have http://consultants.pharo.org > > I want to change it to > - not be a forward to files.pharo.org DONE:

[Pharo-dev] Disabling a MenuGroupModel

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

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

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:

[Pharo-dev] about diff paths

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 /

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

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

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

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:

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

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:

Re: [Pharo-dev] MCGitlabRepository Missing

The PR was against a wrong branch. The fixed one is being validated. -- Pavel 2018-02-02 8:17 GMT+01:00 Marcus Denker : > 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

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

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: