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

Issue validation seems really strange

by stepharo

Hi this is strange because the last issue validation (ilke adding class comments) got such validation output. The errors looks totally strange. Stef

Sept. 10, 2016

[pharo-project/pharo-core] 3963a8: 60211

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 3963a85c894d64bca7c4eaede7386a24feadee3f https://github.com/pharo-project/pharo-core/commit/3963a85c894d64bca7c4eaed… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-10 (Sat, 10 Sep 2016) Changed paths: M Morphic-Examples.package/PluggableButtonMorphExample.class/definition.st M Morphic-Examples.package/PluggableButtonMorphExample.class/instance/initialization/initialize.st M Morphic-Examples.package/TabExample.class/definition.st M Morphic-Examples.package/TabExample.class/instance/tabs creation/blueMorphTab.st M Morphic-Examples.package/TabExample.class/instance/tabs creation/freshListTab.st M Morphic-Examples.package/TabExample.class/instance/tabs creation/redMorphTab.st M Morphic-Examples.package/TabExample.class/instance/tabs creation/storedListTab.st A Nautilus-GroupManagerUI.package/DialogGroupManagerUI.class/instance/icon/iconNamed_.st M Nautilus-GroupManagerUI.package/DialogGroupManagerUI.class/instance/item creation/buildAddButton.st M Nautilus-GroupManagerUI.package/DialogGroupManagerUI.class/instance/item creation/buildAddSelectedPackageInSelectedGroupButton.st M Nautilus-GroupManagerUI.package/DialogGroupManagerUI.class/instance/item creation/buildEmptyGroupButton.st M Nautilus-GroupManagerUI.package/DialogGroupManagerUI.class/instance/item creation/buildRemoveButton.st M Nautilus-GroupManagerUI.package/DialogGroupManagerUI.class/instance/item creation/buildRemoveSelectedPackageFromSelectedGroupButton.st M Nautilus-GroupManagerUI.package/DialogGroupManagerUI.class/instance/item creation/buildRenameButton.st A NautilusCommon.package/NautilusPluginManager.class/instance/icons/iconNamed_.st M NautilusCommon.package/NautilusPluginManager.class/instance/items creation/buildDownButton.st M NautilusCommon.package/NautilusPluginManager.class/instance/items creation/buildFullDownButton.st M NautilusCommon.package/NautilusPluginManager.class/instance/items creation/buildFullUpButton.st M NautilusCommon.package/NautilusPluginManager.class/instance/items creation/buildUpButton.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60210.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60211.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60210.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60211.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Settings.package/PragmaSetting.class/instance/user interface/defaultIcon.st M System-Settings.package/SettingBrowser.class/instance/icons/taskbarIcon.st M System-Settings.package/SettingDeclaration.class/instance/user interface/defaultIcon.st M System-Settings.package/SettingDeclaration.class/instance/user interface/inputWidgetForFileOrDirectoryWithAction_.st M System-Settings.package/SettingTree.class/definition.st M System-Settings.package/SettingTree.class/instance/checking/checkForUnknownParent.st M System-Settings.package/SystemSettingLauncher.class/instance/accessing/defaultIcon.st M System-Settings.package/SystemSettingLauncher.class/instance/accessing/inputWidget.st R Tool-CriticBrowser.package/SingleCodeCriticResultList.class/instance/initialization/setTextModelForTransformationRule_.st M Tool-Diff.package/PSMCChangeWrapper.class/instance/accessing/icon.st M Tool-Diff.package/PSMCClassChangeWrapper.class/instance/accessing/icon.st M Tool-Diff.package/PSMCPatchOperationWrapper.class/instance/accessing/icon.st M Versionner-Commit.package/VSCommitAction.class/definition.st M Versionner-Commit.package/VSCommitBrowser.class/definition.st M Versionner-Commit.package/VSCommitBrowser.class/instance/building/buildBrowser.st Log Message: ----------- 60211 19055 More iconNamed: cleaning https://pharo.fogbugz.com/f/cases/19055 http://files.pharo.org/image/60/60211.zip

Sept. 10, 2016

[pharo-project/pharo-core]

by GitHub

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

Sept. 10, 2016

Re: [Pharo-dev] class deprecation notices

by stepharo

yes NB is really specific with its metadata description Le 10/9/16 Ã 10:03, Ben Coman a Ã©crit : > In Pharo 5.0 I see deprecated classes stripped of all methods and > variables defined in a package like... > > Object subclass: #NBExternalStructure > instanceVariableNames: '' > classVariableNames: '' > package: 'Deprecated50' > > It was was useful having these remain to facilitate loading Pharo > 4.0's TalkFFI for a first look at porting it to Pharo 5.0. Somewhat > expectedly, the class initialization fails with... > MessageNotUnderstood: CXIdxDeclInfoStruct class>>rebuildFieldAccessors > > (since that method used to be in NBExternalStructure > due to "NBExternalStructure subclass: #CXIdxDeclInfoStruct) > > But it would be nicer to get a Deprecated message rather than a MNU, > initially something simple like this... > > Deprecated subclass: #NBExternalStructure > > Deprecated class >> doesNotUnderstand: > DeprecatedError signal. > > but maybe later something like... > > Deprecated class >> doesNotUnderstand: > Transcript crShow: self deprecationNotes. > DeprecatedError signal. > > NBExternalStructure class >> deprecationNotes > ^ 'Blah-d-blah. Use UFFIXxxxxx instead'. > > cheers -ben

Sept. 10, 2016

class deprecation notices

by Ben Coman

In Pharo 5.0 I see deprecated classes stripped of all methods and variables defined in a package like... Object subclass: #NBExternalStructure instanceVariableNames: '' classVariableNames: '' package: 'Deprecated50' It was was useful having these remain to facilitate loading Pharo 4.0's TalkFFI for a first look at porting it to Pharo 5.0. Somewhat expectedly, the class initialization fails with... MessageNotUnderstood: CXIdxDeclInfoStruct class>>rebuildFieldAccessors (since that method used to be in NBExternalStructure due to "NBExternalStructure subclass: #CXIdxDeclInfoStruct) But it would be nicer to get a Deprecated message rather than a MNU, initially something simple like this... Deprecated subclass: #NBExternalStructure Deprecated class >> doesNotUnderstand: DeprecatedError signal. but maybe later something like... Deprecated class >> doesNotUnderstand: Transcript crShow: self deprecationNotes. DeprecatedError signal. NBExternalStructure class >> deprecationNotes ^ 'Blah-d-blah. Use UFFIXxxxxx instead'. cheers -ben

Sept. 10, 2016

Re: [Pharo-dev] Rubric set text without undorecord

by stepharo

Oops. I will ask Alain (if he survives to the restart of the year). Stef Le 9/9/16 Ã 19:49, Nicolai Hess a Ã©crit : > Anyone knows how to set the text in a rub text model without > generating an undorecord? > > Right now, opening a message browser and scrolling through the lists > of entries > updates the text on the code pane and every update will create a new > undorecord. > I would prefer if the undorecord is only generated when *editing* a > method. > > nicolai

Sept. 9, 2016

Re: [Pharo-dev] About file printOn: method

by Udo Schneider

Hi Stef, once upon in time :-) I picked up the notion that #printString "should" return a string which (when executed) results in the printed object. Whereras #displayString is "nicer" for the user. Not quite sure if this still applies though. But in this regard what about something like fr1 := FileSystem disk root / 'folder' / 'file.txt'. fr2 := FileSystem memory root / 'folder' / 'file.txt'. fr1 printString. "FileSystem // 'file:///folder/file.txt'" fr2 printString. "FileSystem // 'memory:///folder/file.txt'" fr1 displayString. "'file:///folder/file.txt'" fr2 displayString. "'memory:///folder/file.txt'" For FileReferences which use a FileSystem with a configured Store those settings could be added to the URL as host/query. E.g. for a WebDav FileReference: #printString "FileSystem // 'webdav://uid:pwd@host/folder/file.txt&usePatch=false'" #displayString "'webdav://uid:pwd@host/folder/file.txt'" CU, Udo On 09/09/16 20:34, stepharo wrote: > Hi Udo > > Thanks for the suggestion. It means that the printOn: should really > involve the FieSystem and this is probably right. > Now the point of the printOn: vs the displayString is that we can get > back an object and right now we get a string :) > Your URI suggestion should be applied to the displayString or the > asFileReference should understand it. > I added your feedback to the entry. > > Stef > > Le 9/9/16 Ã 20:19, Udo Schneider a Ã©crit : >> I'm a bit biased on this. IMHO this simplification in the #printString >> (which I quite like BTW!) is only applicable to Files in DiskFileSystem. >> >> If you have a FileReference on a non disk filesystem (e.g. >> >> fr1 := FileSystem memory root / 'folder' / 'test.txt'. >> "memory:///folder/test.txt" >> >> on use this simplified #printString you'll end up with >> >> '/folder/test.txt' asFileReference. >> >> This might be confusing as this does not mention the filesystem. So >> you might end up creating a new instance via >> >> fr2 := '/folder/test.txt' asFileReference. >> >> which is not equal to the original fileRef: >> >> fr1 = fr2 "false" >> >> As I do like the #printString simplification ... why not simply adopt >> a URI style scheme for FileReferences. This would allow encoding the >> filesystem type (e.g. file://, memory://, zip://, s3://) including >> parameters like host if needed and of course the path. >> >> CU, >> >> Udo >> >> >> >> On 04/09/16 09:47, stepharo wrote: >>> It is raining and I will do it :) >>> >>> >>> stef >>> >>> >>> Le 4/9/16 Ã 02:38, monty a Ã©crit : >>>> +1 >>>> >>>>> Sent: Saturday, September 03, 2016 at 10:39 AM >>>>> From: stepharo <stepharo(a)free.fr> >>>>> To: "Pharo Development List" >>>>> <pharo-dev(a)lists.pharo.org> >>>>> Subject: [Pharo-dev] About file printOn: method >>>>> >>>>> Hi >>>>> >>>>> >>>>> I will implement the following because this is too annoying. >>>>> >>>>> currently >>>>> >>>>> 'tmp/foo.txt' asFileReference >>>>> > >>>>> File @ tmp/foo.txt >>>>> >>>>> and it would be much much better to get back >>>>> 'tmp/foo.txt' asFileReference >>>>> >>>>> So that we can get >>>>> { 'tmp/foo.txt' asFileReference } >>>>> > { 'tmp/foo.txt' asFileReference } >>>>> >>>>> and not >>>>> "an Array(File @ tmp/foo.txt)" >>>>> >>>>> >>>>> In addition we should turn the current printOn: method into a >>>>> displayString method so that >>>>> a list of fileReference can be well display with File @ tmp/foo.txt >>>>> for >>>>> example >>>>> >>>>> >>>>> https://pharo.fogbugz.com/f/cases/18956 >>>>> >>>>> >>>>> >>>> >>> >>> >>> >> >> >> >> > > >

Sept. 9, 2016

Re: [Pharo-dev] About file printOn: method

by stepharo

Hi Udo Thanks for the suggestion. It means that the printOn: should really involve the FieSystem and this is probably right. Now the point of the printOn: vs the displayString is that we can get back an object and right now we get a string :) Your URI suggestion should be applied to the displayString or the asFileReference should understand it. I added your feedback to the entry. Stef Le 9/9/16 Ã 20:19, Udo Schneider a Ã©crit : > I'm a bit biased on this. IMHO this simplification in the #printString > (which I quite like BTW!) is only applicable to Files in DiskFileSystem. > > If you have a FileReference on a non disk filesystem (e.g. > > fr1 := FileSystem memory root / 'folder' / 'test.txt'. > "memory:///folder/test.txt" > > on use this simplified #printString you'll end up with > > '/folder/test.txt' asFileReference. > > This might be confusing as this does not mention the filesystem. So > you might end up creating a new instance via > > fr2 := '/folder/test.txt' asFileReference. > > which is not equal to the original fileRef: > > fr1 = fr2 "false" > > As I do like the #printString simplification ... why not simply adopt > a URI style scheme for FileReferences. This would allow encoding the > filesystem type (e.g. file://, memory://, zip://, s3://) including > parameters like host if needed and of course the path. > > CU, > > Udo > > > > On 04/09/16 09:47, stepharo wrote: >> It is raining and I will do it :) >> >> >> stef >> >> >> Le 4/9/16 Ã 02:38, monty a Ã©crit : >>> +1 >>> >>>> Sent: Saturday, September 03, 2016 at 10:39 AM >>>> From: stepharo <stepharo(a)free.fr> >>>> To: "Pharo Development List" >>>> <pharo-dev(a)lists.pharo.org> >>>> Subject: [Pharo-dev] About file printOn: method >>>> >>>> Hi >>>> >>>> >>>> I will implement the following because this is too annoying. >>>> >>>> currently >>>> >>>> 'tmp/foo.txt' asFileReference >>>> > >>>> File @ tmp/foo.txt >>>> >>>> and it would be much much better to get back >>>> 'tmp/foo.txt' asFileReference >>>> >>>> So that we can get >>>> { 'tmp/foo.txt' asFileReference } >>>> > { 'tmp/foo.txt' asFileReference } >>>> >>>> and not >>>> "an Array(File @ tmp/foo.txt)" >>>> >>>> >>>> In addition we should turn the current printOn: method into a >>>> displayString method so that >>>> a list of fileReference can be well display with File @ tmp/foo.txt >>>> for >>>> example >>>> >>>> >>>> https://pharo.fogbugz.com/f/cases/18956 >>>> >>>> >>>> >>> >> >> >> > > > >

Sept. 9, 2016

Re: [Pharo-dev] About file printOn: method

by Udo Schneider

I'm a bit biased on this. IMHO this simplification in the #printString (which I quite like BTW!) is only applicable to Files in DiskFileSystem. If you have a FileReference on a non disk filesystem (e.g. fr1 := FileSystem memory root / 'folder' / 'test.txt'. "memory:///folder/test.txt" on use this simplified #printString you'll end up with '/folder/test.txt' asFileReference. This might be confusing as this does not mention the filesystem. So you might end up creating a new instance via fr2 := '/folder/test.txt' asFileReference. which is not equal to the original fileRef: fr1 = fr2 "false" As I do like the #printString simplification ... why not simply adopt a URI style scheme for FileReferences. This would allow encoding the filesystem type (e.g. file://, memory://, zip://, s3://) including parameters like host if needed and of course the path. CU, Udo On 04/09/16 09:47, stepharo wrote: > It is raining and I will do it :) > > > stef > > > Le 4/9/16 Ã 02:38, monty a Ã©crit : >> +1 >> >>> Sent: Saturday, September 03, 2016 at 10:39 AM >>> From: stepharo <stepharo(a)free.fr> >>> To: "Pharo Development List" >>> <pharo-dev(a)lists.pharo.org> >>> Subject: [Pharo-dev] About file printOn: method >>> >>> Hi >>> >>> >>> I will implement the following because this is too annoying. >>> >>> currently >>> >>> 'tmp/foo.txt' asFileReference >>> > >>> File @ tmp/foo.txt >>> >>> and it would be much much better to get back >>> 'tmp/foo.txt' asFileReference >>> >>> So that we can get >>> { 'tmp/foo.txt' asFileReference } >>> > { 'tmp/foo.txt' asFileReference } >>> >>> and not >>> "an Array(File @ tmp/foo.txt)" >>> >>> >>> In addition we should turn the current printOn: method into a >>> displayString method so that >>> a list of fileReference can be well display with File @ tmp/foo.txt for >>> example >>> >>> >>> https://pharo.fogbugz.com/f/cases/18956 >>> >>> >>> >> > > >

Sept. 9, 2016

Rubric set text without undorecord

by Nicolai Hess

Anyone knows how to set the text in a rub text model without generating an undorecord? Right now, opening a message browser and scrolling through the lists of entries updates the text on the code pane and every update will create a new undorecord. I would prefer if the undorecord is only generated when *editing* a method. nicolai

Sept. 9, 2016