[Pharo-dev] New Critic Rule: Nobody should directly send #methodDict
Hi I'm really happy because "New Critic Rule: Nobody should directly send #methodDict" is the way to go. We should document the system design using automatic rules! Excellent! Stef
[Pharo-dev] full version of a Lint Chapter for Entreprise Pharo forthcoming book :)
Hi Pharoers since we believe in quality and automation, here is a new chapter on Lint rule support in Pharo :) https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Lint/Lint.pier.pdf Stef
[Pharo-dev] Starting image gives FileWriteError: File stdout is closed - huh?
Now, when starting my image: FileWriteError: File stdout is closed MultiByteFileStream(StandardFileStream)>>primWrite:from:startingAt:count: MultiByteFileStream(StandardFileStream)>>next:putAll:startingAt: MultiByteFileStream>>basicNext:putAll:startingAt: UTF8TextConverter(TextConverter)>>nextPutByteString:toStream: UTF8TextConverter(TextConverter)>>nextPutAll:toStream: MultiByteFileStream>>nextPutAll: I was a link while Googling but not resolution. What to do? -- Phil
Re: [Pharo-dev] What is WeakActionSequence?
El 04/10/2013 14:27, Camillo Bruni escribió: What is that class? No comments, two single methods on Object that refer to it? A WeakActionSequence is used as container for MessageSend's. It looks like is not even really weak, there is no weakSubclass: definition... You probably don't see users because it was (tipically) only used in OmniBrowser in Pharo <= 1.4. Users of the SASE (a.k.a triggerEvent) mechanism also are (or were) users. The question is, why every object should be able to register events? Think of magnitudes registering events. Object subclasses could include all the observer pattern implementations you like. Hernán
[Pharo-dev] External Semaphores leaking in Socket
I took some time to analyze my current problem with external semaphores. I was just reluctant to raise the limit in my image because I want the problem solved. I logged the management of external semaphores and discovered that the table fills if a connection times out. The problem turns out to be in Socket>>#connectTo: hostAddress port: port waitForConnectionFor: timeout "Initiate a connection to the given port at the given host address. Waits until the connection is established or time outs." self connectNonBlockingTo: hostAddress port: port. self waitForConnectionFor: timeout ifTimedOut: [ConnectionTimedOut signal: 'Cannot connect to ' , (NetNameResolver stringFromAddress: hostAddress) , ':' , port asString] When a socket is created three external semaphores are registered in the ExternalSemaphoreTable. If a connection times out the exception is thrown but the Socket still has his resources attached. So e.g. in SocketStream class>>#openConnectionToHost: hostIP port: portNumber timeout: timeout | socket | socket := Socket new. socket connectTo: hostIP port: portNumber waitForConnectionFor: timeout. ^self on: socket it holds locally a socket (with semaphores registered) but on exception time the reference to the socket gets lost and the semaphores stay registered. The only way to unregister is on finalization time but I think it should work better. So I would add a destroy before the exception is raised. Socket>>#connectTo: hostAddress port: port waitForConnectionFor: timeout "Initiate a connection to the given port at the given host address. Waits until the connection is established or time outs." self connectNonBlockingTo: hostAddress port: port. self waitForConnectionFor: timeout ifTimedOut: [ self destroy. ConnectionTimedOut signal: 'Cannot connect to ' , (NetNameResolver stringFromAddress: hostAddress) , ':' , port asString] I opened a ticket at https://pharo.fogbugz.com/f/cases/11797 but I'm not sure how I am supposed to provide fixes made against a pharo2.0 image. Probably I should fix this againt 3.0 but then I'm still a 2.0 user :) Norbert
Re: [Pharo-dev] [update 3.0] #30455
On Oct 6, 2013, at 12:38 AM, Camillo Bruni wrote: > > On 2013-10-06, at 00:06, Marcus Denker wrote: > >> 11792 First simplistic file system tree inspector >> https://pharo.fogbugz.com/f/cases/11792 >> >> >> actually a FileReference tree inspector... lots of improvments possible >> inspect >> >> FileSystem workingDirectory >> >> and select the FileReference Tree Inspector > > ha! nice :) actually we could reuse the file list here, no? Yes… that would be best. Marcus signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] New Critic Rule: Nobody should directly send #methodDict
Stéphane Ducasse wrote: Hi I'm really happy because "New Critic Rule: Nobody should directly send #methodDict" is the way to go. We should document the system design using automatic rules! Excellent! Stef So you could also have "Critic Rule: Should not implement system method." Like PharoLauncher got stuck having implemented class-side method #layout [1] btw, apart from having a separate critics browser, are the any plans to integrate it further into the system, perhaps as: * a Critics Panel in Nautilus in the same position as the Comments Panel, or perhaps appended to the Comment. * contextual highlighting cheers -ben [1] https://pharo.fogbugz.com/default.asp?11783
Re: [Pharo-dev] Starting image gives FileWriteError: File stdout is closed - huh?
On 6 October 2013 11:21, p...@highoctane.be wrote: > Now, when starting my image: > > FileWriteError: File stdout is closed > MultiByteFileStream(StandardFileStream)>>primWrite:from:startingAt:count: > MultiByteFileStream(StandardFileStream)>>next:putAll:startingAt: > MultiByteFileStream>>basicNext:putAll:startingAt: > UTF8TextConverter(TextConverter)>>nextPutByteString:toStream: > UTF8TextConverter(TextConverter)>>nextPutAll:toStream: > MultiByteFileStream>>nextPutAll: > > I was a link while Googling but not resolution. > > What to do? What operating system? Windows? frank > -- > Phil
Re: [Pharo-dev] New Critic Rule: Nobody should directly send #methodDict
ben this is not that we do not have plan and vision. Just that we have lot of consumers and not enough people thinking that Pharo is theirs :) Stef On Oct 6, 2013, at 2:19 PM, b...@openinworld.com wrote: > Stéphane Ducasse wrote: >> Hi >> I'm really happy because >> "New Critic Rule: Nobody should directly send #methodDict" is the way >> to go. We should document the system design using automatic rules! >> Excellent! >> >> Stef >> >> > So you could also have "Critic Rule: Should not implement system method." > Like PharoLauncher got stuck having implemented class-side method #layout [1] > > btw, apart from having a separate critics browser, are the any plans to > integrate it further into the system, perhaps as: > * a Critics Panel in Nautilus in the same position as the Comments Panel, or > perhaps appended to the Comment. * contextual highlighting > > cheers -ben > > [1] https://pharo.fogbugz.com/default.asp?11783 > > >
Re: [Pharo-dev] additional Milestone label for applications
seems like it works, so by default the pharo-internal projects will have the Area "1. Pharo Image" set. Why the "1."? Well I cannot order the Areas, and the first one is selected by default :P The filter "review" and "integration" now only look at issues that have the proper Area set. On 2013-10-06, at 08:08, Stéphane Ducasse wrote: > thanks! > This is a good idea. > > On Oct 6, 2013, at 1:57 AM, Camillo Bruni wrote: > I think it should just be fine if we define a different workflow (and thus different labels) for external projects... >>> The 'Area' field looks unused, having only a single option 'Misc'. Perhaps >>> that could be 'Image' and 'External Project' or similar. Most of an >>> external project's issues would also have an area of 'External 'Project', >>> but sometimes it might be 'Image' if a change there is required to fix an >>> issue reported on a project.Or maybe for external projects you have >>> only a single option 'External Project' for Area. >> >> So we need to have 2 things >> 1. a separate project for each external project that wants to report >> 2. a separate Area for these external projects >> >> For instance, NativeBoost has both a stable version in the image and a >> development >> version aside. So if a bug appears in the image we can set the Area to >> "Pharo Image" (the default). >> However, if the bug concerns the development version we set the Area to >> something project >> specific. >> >> I will try to update the tracker and the filters to reflect that... > > signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] Starting image gives FileWriteError: File stdout is closed - huh?
OSX Lion On Sun, Oct 6, 2013 at 2:22 PM, Frank Shearar wrote: > On 6 October 2013 11:21, p...@highoctane.be wrote: > > Now, when starting my image: > > > > FileWriteError: File stdout is closed > > MultiByteFileStream(StandardFileStream)>>primWrite:from:startingAt:count: > > MultiByteFileStream(StandardFileStream)>>next:putAll:startingAt: > > MultiByteFileStream>>basicNext:putAll:startingAt: > > UTF8TextConverter(TextConverter)>>nextPutByteString:toStream: > > UTF8TextConverter(TextConverter)>>nextPutAll:toStream: > > MultiByteFileStream>>nextPutAll: > > > > I was a link while Googling but not resolution. > > > > What to do? > > What operating system? Windows? > > frank > > > -- > > Phil > >
Re: [Pharo-dev] New Critic Rule: Nobody should directly send #methodDict
What I would like (and will probably give a try soon) is to run some critics automatically before committing a MC package :) That's how it's done in WebStorm by example, and I love this feature Ben On Oct 6, 2013, at 2:19 PM, b...@openinworld.com wrote: > Stéphane Ducasse wrote: >> Hi >> I'm really happy because >> "New Critic Rule: Nobody should directly send #methodDict" is the way >> to go. We should document the system design using automatic rules! >> Excellent! >> >> Stef >> >> > So you could also have "Critic Rule: Should not implement system method." > Like PharoLauncher got stuck having implemented class-side method #layout [1] > > btw, apart from having a separate critics browser, are the any plans to > integrate it further into the system, perhaps as: > * a Critics Panel in Nautilus in the same position as the Comments Panel, or > perhaps appended to the Comment. * contextual highlighting > > cheers -ben > > [1] https://pharo.fogbugz.com/default.asp?11783 > > >
Re: [Pharo-dev] New Critic Rule: Nobody should directly send #methodDict
> What I would like (and will probably give a try soon) is to run some critics > automatically before committing a MC package :) > That's how it's done in WebStorm by example, and I love this feature Yes this is a good practice. > Ben
Re: [Pharo-dev] New Critic Rule: Nobody should directly send #methodDict
Benjamin wrote: What I would like (and will probably give a try soon) is to run some critics automatically before committing a MC package :) That's how it's done in WebStorm by example, and I love this feature Ben That sounds cool. Without having used Code Critics yet (I've just discovered the menu option the Nautilus package pane), I am interested if your idea would that include a diff with the critics from the previous commit? While it a full list of critic-isms is be good prompt to reduce the list to zero, also useful would be knowing if any new critic-isms had been introduced in this commit. This might help at least maintain the status-quo without having to solve all existing critic-isms at once, to avoid new ones being lost amongst a potentially large existing list. cheers -ben On Oct 6, 2013, at 2:19 PM, b...@openinworld.com wrote: Stéphane Ducasse wrote: Hi I'm really happy because "New Critic Rule: Nobody should directly send #methodDict" is the way to go. We should document the system design using automatic rules! Excellent! Stef So you could also have "Critic Rule: Should not implement system method." Like PharoLauncher got stuck having implemented class-side method #layout [1] btw, apart from having a separate critics browser, are the any plans to integrate it further into the system, perhaps as: * a Critics Panel in Nautilus in the same position as the Comments Panel, or perhaps appended to the Comment. * contextual highlighting cheers -ben [1] https://pharo.fogbugz.com/default.asp?11783
Re: [Pharo-dev] External Semaphores leaking in Socket
On Oct 6, 2013, at 12:51 PM, Norbert Hartl wrote: > > I opened a ticket at https://pharo.fogbugz.com/f/cases/11797 but I'm not sure > how I am supposed to provide fixes made against a pharo2.0 image. Probably I > should fix this againt 3.0 but then I'm still a 2.0 user :) The best is to have two issues: one for 2.0 and one for 3.0. Then we can first commit it to Pharo3, test some days and then do the pharo2 version (you need to do two slices, one for 2.0 in the 2.0 inbox and one for 3.0) Marcus signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] pharo-vm reattached history + new branches
I reattached a clean version of the old history to the pharo-vm repository https://github.com/pharo-project/pharo-vm/network As a result all the SHA hashes of the commits changed :/ AFAIK you should be fine with your local copies by pulling the latest changes from pharo-vm and merge. Additionally we have now 2 branches following according to git-flow: - master: containing the stable version - develop: containing the latest dev version signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] New Critic Rule: Nobody should directly send #methodDict
I would first experiment to run the critics only on the modified code, not the full package :) Then you can have a pretty accurate feedback Ben On Oct 6, 2013, at 4:26 PM, b...@openinworld.com wrote: > Benjamin wrote: >> >> What I would like (and will probably give a try soon) is to run some critics >> automatically before committing a MC package :) >> That's how it's done in WebStorm by example, and I love this feature >> >> Ben >> > That sounds cool. Without having used Code Critics yet (I've just discovered > the menu option the Nautilus package pane), I am interested if your idea > would that include a diff with the critics from the previous commit? While > it a full list of critic-isms is be good prompt to reduce the list to zero, > also useful would be knowing if any new critic-isms had been introduced in > this commit. This might help at least maintain the status-quo without having > to solve all existing critic-isms at once, to avoid new ones being lost > amongst a potentially large existing list. > > cheers -ben >> On Oct 6, 2013, at 2:19 PM, b...@openinworld.com wrote: >> >> >>> Stéphane Ducasse wrote: >>> Hi I'm really happy because "New Critic Rule: Nobody should directly send #methodDict" is the way to go. We should document the system design using automatic rules! Excellent! Stef >>> So you could also have "Critic Rule: Should not implement system method." >>> Like PharoLauncher got stuck having implemented class-side method #layout >>> [1] >>> >>> btw, apart from having a separate critics browser, are the any plans to >>> integrate it further into the system, perhaps as: >>> * a Critics Panel in Nautilus in the same position as the Comments Panel, >>> or perhaps appended to the Comment. * contextual highlighting >>> >>> cheers -ben >>> >>> [1] https://pharo.fogbugz.com/default.asp?11783 >>> >>> >>> >>> >> >> >> >
Re: [Pharo-dev] additional Milestone label for applications
Camillo Bruni wrote: seems like it works, so by default the pharo-internal projects will have the Area "1. Pharo Image" set. Why the "1."? Well I cannot order the Areas, and the first one is selected by default :P The filter "review" and "integration" now only look at issues that have the proper Area set. Looks good. The "1." looks fine, but in case it is useful I happened to find a Fogbugz script "Set Hard Default for Project and Area in New Cases" at [1] that seems related. I'm curious now whether 'External' projects are then free to use Milestone=Pharo3.0 if they want to target certain issues of their own to align with that release date? cheers -ben [1] http://help.fogcreek.com/8534/bugmonkey-script-archive On 2013-10-06, at 08:08, Stéphane Ducasse wrote: thanks! This is a good idea. On Oct 6, 2013, at 1:57 AM, Camillo Bruni wrote: I think it should just be fine if we define a different workflow (and thus different labels) for external projects... The 'Area' field looks unused, having only a single option 'Misc'. Perhaps that could be 'Image' and 'External Project' or similar. Most of an external project's issues would also have an area of 'External 'Project', but sometimes it might be 'Image' if a change there is required to fix an issue reported on a project.Or maybe for external projects you have only a single option 'External Project' for Area. So we need to have 2 things 1. a separate project for each external project that wants to report 2. a separate Area for these external projects For instance, NativeBoost has both a stable version in the image and a development version aside. So if a bug appears in the image we can set the Area to "Pharo Image" (the default). However, if the bug concerns the development version we set the Area to something project specific. I will try to update the tracker and the filters to reflect that...
[Pharo-dev] FogBugz customizations
Just browsing around FogBugz docs a bit, I came across this... "Users can input any arbitrary javascript and css that you want to run on any FogBugz page." [1] I wonder if Amber could be loaded on top Fogbugz to do something-awesome(TM) with SmalltalkHub integration? Actually back to reality... the "13. Notification for Updates to Case You’re Working On" script [2] looks but I don't have a Customization> button [3]. Would it be possible to get either the facility to add that script myself, or someone to add that particular script to the Available Customizations. cheers -ben [1] http://www.fogcreek.com/fogbugz/plugins/plugin.aspx?ixPlugin=16 [2] http://help.fogcreek.com/8534/bugmonkey-script-archive [3] http://help.fogcreek.com/7585/customizing-your-fogbugz-site-with-bugmonkey
[Pharo-dev] [update 3.0] #30456
30456 - 11789 Trivial Critic clean in *Completion https://pharo.fogbugz.com/f/cases/11789 11796 New Critic Rule: Nobody should directly send #methodDict https://pharo.fogbugz.com/f/cases/11796 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1294.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-MarcusDenker.84.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/NOCompletion-MarcusDenker.43.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/NECompletion-MarcusDenker.137.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-Core-MarcusDenker.166.diff signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] StackVM on RaspberryPi
On Thu, Oct 3, 2013 at 5:37 PM, Jean Baptiste Arnaud wrote: > Using Nick's process for compiling the vm I reintroduce a process to compile > StackVM on Rasp. > So we have a StackVM compiling process on Rasp, with a simple > CMakeConfiguration class and a simple install script for Rasp. > Next step is to recompile from Rasp. Great ! where is the documentation to do that available ? Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=linux-stable-worker/577/ 4 regressions found. NECompletion.Tests.NECInstVarTypeGuesserTest.testTypeSuggestingParameter NECompletion.Tests.NECUntypedModelTest.testCaseSensitive NECompletion.Tests.NECUntypedModelTest.testCaseSensitivity NECompletion.Tests.NECUntypedModelTest.testForClassInstVars
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=mac/577/ 4 regressions found. NECompletion.Tests.NECInstVarTypeGuesserTest.testTypeSuggestingParameter NECompletion.Tests.NECUntypedModelTest.testCaseSensitive NECompletion.Tests.NECUntypedModelTest.testCaseSensitivity NECompletion.Tests.NECUntypedModelTest.testForClassInstVars
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=win/577/ 4 regressions found. NECompletion.Tests.NECInstVarTypeGuesserTest.testTypeSuggestingParameter NECompletion.Tests.NECUntypedModelTest.testCaseSensitive NECompletion.Tests.NECUntypedModelTest.testCaseSensitivity NECompletion.Tests.NECUntypedModelTest.testForClassInstVars
Re: [Pharo-dev] additional Milestone label for applications
On 2013-10-06, at 17:36, b...@openinworld.com wrote: > Camillo Bruni wrote: >> seems like it works, >> >> so by default the pharo-internal projects will have the Area "1. Pharo >> Image" set. >> >> Why the "1."? Well I cannot order the Areas, and the first one is selected >> by default :P >> >> The filter "review" and "integration" now only look at issues that have the >> proper Area set. >> >> > > Looks good. The "1." looks fine, but in case it is useful I happened to find > a Fogbugz script "Set Hard Default for Project and Area in New Cases" at [1] > that seems related. ah ok, I didn't see the script and went for the silly solution fogbugz proposed already for other things (wiki names ...). > I'm curious now whether 'External' projects are then free to use > Milestone=Pharo3.0 if they want to target certain issues of their own to > align with that release date? Yes, this is possible now, as long as the Area is not "1. Pharo Image" everything can be used freely. signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] I wanted to understand new list
And NewListExample new withNewList; openInWindow. does not work. separatorAfter: item at: index ^ separatorSelector ifNotNil: [ self model perform: separatorSelector with: item with: index ] separatorSelector is a valueHolder and not a symbol but I do not get it because separatorSelector ^ separatorSelector contents separatorSelector: anObject separatorSelector contents: anObject really looks like a valueHolder. Stef
Re: [Pharo-dev] [update 3.0] #30456
Is it me or recently there was many more updates on Pharo than it used to be ? Last week I saw 9 to 15 updates per day instead of the usual 3. Do we have even more contributors ? 2013/10/6 Marcus Denker > 30456 > - > > 11789 Trivial Critic clean in *Completion > https://pharo.fogbugz.com/f/cases/11789 > > 11796 New Critic Rule: Nobody should directly send #methodDict > https://pharo.fogbugz.com/f/cases/11796 > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1294.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-MarcusDenker.84.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NOCompletion-MarcusDenker.43.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NECompletion-MarcusDenker.137.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-Core-MarcusDenker.166.diff > >
Re: [Pharo-dev] [update 3.0] #30456
Otherwise, Marcus should undergo some drug tests, his performances are suspicious... 2013/10/6 Clément Bera > Is it me or recently there was many more updates on Pharo than it used to > be ? Last week I saw 9 to 15 updates per day instead of the usual 3. Do we > have even more contributors ? > > > 2013/10/6 Marcus Denker > >> 30456 >> - >> >> 11789 Trivial Critic clean in *Completion >> https://pharo.fogbugz.com/f/cases/11789 >> >> 11796 New Critic Rule: Nobody should directly send #methodDict >> https://pharo.fogbugz.com/f/cases/11796 >> >> Diff information: >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1294.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-MarcusDenker.84.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/NOCompletion-MarcusDenker.43.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/NECompletion-MarcusDenker.137.diff >> >> http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-Core-MarcusDenker.166.diff >> >> >
[Pharo-dev] about creating Morphic-Widgets
Hi guys I started to play with sorting a bit Morphic :) So I would like to create a new Package Morphics-Widgets with the following contents. Morphic-Widgets-Basic SimpleSwitchMorph MulticolumnLazyListMorph SimpleButtonMorph LazyListMorph IconicButton ThreePhaseButtonMorph CalendarMorph Morphic-Widgets-Pluggable PluggableTabButtonMorph PluggableButtonMorph PluggableTextMorph PluggableMultiColumnListMorph PluggableTextMorphWithLimits PluggableTabBarMorph PluggableListMorph Morphic-Widgets-NewList NewList NewListRenderer NewListAdapter Morphic-Widgets-Tab Morphic-Widget-MorphTreeWidget Morphic-Widget-MorphTreeWidget-Pagination I would promote Morphic-Base-ProgressBar -> Morphic-ProgressBar So what do you think?
Re: [Pharo-dev] [update 3.0] #30456
> Otherwise, Marcus should undergo some drug tests, his performances are > suspicious… indeed :) It compensates my lack of time :) > > > 2013/10/6 Clément Bera > Is it me or recently there was many more updates on Pharo than it used to be > ? Last week I saw 9 to 15 updates per day instead of the usual 3. Do we have > even more contributors ? > > > 2013/10/6 Marcus Denker > 30456 > - > > 11789 Trivial Critic clean in *Completion > https://pharo.fogbugz.com/f/cases/11789 > > 11796 New Critic Rule: Nobody should directly send #methodDict > https://pharo.fogbugz.com/f/cases/11796 > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1294.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-MarcusDenker.84.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NOCompletion-MarcusDenker.43.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NECompletion-MarcusDenker.137.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-Core-MarcusDenker.166.diff > > >
[Pharo-dev] is there a new inspector version for dictionary
Hi the old inspector defined a hierarchy of specialized inspector and I was giving a lecture to serious programmers :) and I noticed that they were confused by the inspector when opening dictionary because we see the dictionary state. Stef
Re: [Pharo-dev] is there a new inspector version for dictionary
I do not fully understand what you mean, but I assume the difference between a basic inspector on the real fields of an object and a specialized dictionary inspector which shows the elements in the inspector? We added the custom dictionary inspector a while ago, plus there was the right-click menu with the basic-inspect entry. With the new inspector views you can switch between the basic inspectors and custom inspectors. Just do: Smalltalk globals inspect. and you have 3 choices now ⌘+1 Collection Inspector (the original dictionary inspector) ⌘+0 Basic Inspector (here alternatively ⌘+1) ⌘+3 Tree Inspector For other objects there are even more choices: World inspect. ⌘+1 Basic Inspector ⌘+2 Tree Inspector ⌘+3 View Hierarchy Inspector ⌘+4 Morphic Viewer (currently broken due to spec changes) On 2013-10-06, at 20:58, Stéphane Ducasse wrote: > Hi > > the old inspector defined a hierarchy of specialized inspector and I was > giving a lecture to serious programmers :) > and I noticed that they were confused by the inspector when opening > dictionary because we see the dictionary state. > > Stef signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] is there a new inspector version for dictionary
On Oct 6, 2013, at 8:58 PM, Stéphane Ducasse wrote: > Hi > > the old inspector defined a hierarchy of specialized inspector and I was > giving a lecture to serious programmers :) > and I noticed that they were confused by the inspector when opening > dictionary because we see the dictionary state. > The new ones make this explicit: the menu on the top always lets you select the inspector. There always -> basic -> tree (explorer) and more if there is one. Now a class can define the default to be a different one that the basic. An example for that are collections. e.g. inspect Smalltalk globals World 1 FileSystem workingDirectory So for a Dictionary, you see key->value by default, but you can always jump to the basic inspector if needed. the only thing that is a bit confusing is that it show "class" and "self" in the basic inspector, but that very useful to have. (and technically class is a field in the object via the object header ;-) Marcus signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] is there a new inspector version for dictionary
> the only thing that is a bit confusing is that it show "class" and "self" in > the basic inspector, but > that very useful to have. (and technically class is a field in the object via > the object header ;-) it would be nice to distinguish the calculated/virtual values by using a different font or icon... signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] is there a new inspector version for dictionary
Ok I see I was using Moose for the lecture so probably still in 2.0 Stef On Oct 6, 2013, at 9:26 PM, Camillo Bruni wrote: >> the only thing that is a bit confusing is that it show "class" and "self" in >> the basic inspector, but >> that very useful to have. (and technically class is a field in the object >> via the object header ;-) > > > it would be nice to distinguish the calculated/virtual values by using a > different font or icon...
Re: [Pharo-dev] about creating Morphic-Widgets
I am in for splitting Morphic in more that one package. It makes things really boring to have every thing in one MC Package :( Ben On Oct 6, 2013, at 8:54 PM, Stéphane Ducasse wrote: > Hi guys > > I started to play with sorting a bit Morphic :) > So I would like to create a new Package Morphics-Widgets with the following > contents. > > > Morphic-Widgets-Basic > SimpleSwitchMorph > MulticolumnLazyListMorph > SimpleButtonMorph > LazyListMorph > IconicButton > ThreePhaseButtonMorph > CalendarMorph > Morphic-Widgets-Pluggable > PluggableTabButtonMorph > PluggableButtonMorph > PluggableTextMorph > PluggableMultiColumnListMorph > PluggableTextMorphWithLimits > PluggableTabBarMorph > PluggableListMorph > Morphic-Widgets-NewList > NewList > NewListRenderer > NewListAdapter > Morphic-Widgets-Tab > > Morphic-Widget-MorphTreeWidget > Morphic-Widget-MorphTreeWidget-Pagination > > I would promote Morphic-Base-ProgressBar -> Morphic-ProgressBar > > So what do you think? > >
Re: [Pharo-dev] I wanted to understand new list
On Oct 6, 2013, at 8:16 PM, Stéphane Ducasse wrote: > And > > NewListExample new > withNewList; > openInWindow. > > does not work. > > separatorAfter: item at: index > > ^ separatorSelector > ifNotNil: [ self model perform: separatorSelector with: item > with: index ] Should probably be ifNotNil: [ self model perform: self separatorSelector with: item with: index ] > > separatorSelector > is a valueHolder and not a symbol > > but I do not get it because > > > separatorSelector > ^ separatorSelector contents > > separatorSelector: anObject > separatorSelector contents: anObject > > really looks like a valueHolder. > > Stef > It is a value holder for sure :) I will have a look tomorrow to make the example works :) Ben
Re: [Pharo-dev] about creating Morphic-Widgets
+1 Doru On Sun, Oct 6, 2013 at 10:28 PM, Benjamin < benjamin.vanryseghem.ph...@gmail.com> wrote: > I am in for splitting Morphic in more that one package. > > It makes things really boring to have every thing in one MC Package :( > > Ben > > On Oct 6, 2013, at 8:54 PM, Stéphane Ducasse > wrote: > > Hi guys > > I started to play with sorting a bit Morphic :) > So I would like to create a new Package Morphics-Widgets with the > following contents. > > > Morphic-Widgets-Basic > SimpleSwitchMorph > MulticolumnLazyListMorph > SimpleButtonMorph > LazyListMorph > IconicButton > ThreePhaseButtonMorph > CalendarMorph > Morphic-Widgets-Pluggable > PluggableTabButtonMorph > PluggableButtonMorph > PluggableTextMorph > PluggableMultiColumnListMorph > PluggableTextMorphWithLimits > PluggableTabBarMorph > PluggableListMorph > Morphic-Widgets-NewList > NewList > NewListRenderer > NewListAdapter > Morphic-Widgets-Tab > > Morphic-Widget-MorphTreeWidget > Morphic-Widget-MorphTreeWidget-Pagination > > I would promote Morphic-Base-ProgressBar -> Morphic-ProgressBar > > So what do you think? > > > > -- www.tudorgirba.com "Every thing has its own flow"
[Pharo-dev] WhatsUp from: 2013-10-07 until: 2013-10-20
Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2013-10-20 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)
[Pharo-dev] [update 3.0] #30457
30457 - 11791 trivial critic cleanup in ClassOrganizer https://pharo.fogbugz.com/f/cases/11791 11802 Fix failing tests Ecompletion https://pharo.fogbugz.com/f/cases/11802 11765 whichSelectorsReallyRead: --> fix whichSelectorsRead: instead https://pharo.fogbugz.com/f/cases/11765 Thanks to Tommaso Dal Sasso for the last one! Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-MarcusDenker.576.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Tests-Core-MarcusDenker.84.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Environment-MarcusDenker.38.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-MarcusDenker.85.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Core-MarcusDenker.225.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/NECompletion-MarcusDenker.139.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/ClassOrganizer-Core-MarcusDenker.12.diff signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=win/578/ 1 regressions found. Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion
[Pharo-dev] [pharo-project/pharo-core]
Branch: refs/tags/30457 Home: https://github.com/pharo-project/pharo-core
[Pharo-dev] [pharo-project/pharo-core] 24acce: 30457
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 24accedbcb9668d8c38a530829a0d4cf221ee35e https://github.com/pharo-project/pharo-core/commit/24accedbcb9668d8c38a530829a0d4cf221ee35e Author: Jenkins Build Server Date: 2013-10-06 (Sun, 06 Oct 2013) Changed paths: M ClassOrganizer-Core.package/ClassOrganization.class/instance/accessing/comment_.st M ClassOrganizer-Core.package/ClassOrganization.class/instance/backward compatibility/classify_under_suppressIfDefault_.st R ClassOrganizer-Core.package/ClassOrganization.class/instance/notifications/notifyOfChangedSelectorsOldDict_newDict_.st M ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/private/existsProtocolNamed_.st M NECompletion-Tests.package/NECTestClass.class/definition.st M NECompletion-Tests.package/NECTestClass.class/instance/initialization/initialize_.st M NECompletion-Tests.package/NECTestClass.class/instance/utils/lowPriorityOverrides_.st R Refactoring-Core.package/extension/TClassDescription/instance/whichSelectorsReallyRead_.st M Refactoring-Critics-BlockRules.package/RBOnlyReadOrWrittenVariableRule.class/instance/running/checkClass_.st M Refactoring-Environment.package/RBVariableEnvironment.class/class/instance creation/on_readersOfInstanceVariable_in_.st M Refactoring-Environment.package/RBVariableEnvironment.class/class/instance creation/on_referencesToInstanceVariable_in_.st M Refactoring-Environment.package/RBVariableEnvironment.class/instance/accessing/environmentForInstanceVariable_in_.st M Refactoring-Environment.package/RBVariableEnvironment.class/instance/private/instanceVariableSelectorsFor_.st M Refactoring-Tests-Core-Data.package/RBBasicLintRuleTest.class/class/unnecessary code/onlyReadOrWritten.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script112.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30457.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits-Kernel-Traits.package/TBehavior.class/instance/queries/whichSelectorsRead_.st Log Message: --- 30457 11765 whichSelectorsReallyRead: --> fix whichSelectorsRead: instead https://pharo.fogbugz.com/f/cases/11765 11791 trivial critic cleanup in ClassOrganizer https://pharo.fogbugz.com/f/cases/11791 11802 Fix failing tests Ecompletion https://pharo.fogbugz.com/f/cases/11802
