- Pharo-dev - lists.pharo.org

I need reviewer of https://pharo.fogbugz.com/default.asp?15646

by stepharo

Hi I continued to clean that classes have categories and method protocols because it was not finished. This entry is just adding protocol in the classes that were missing it, adding comments, and fixing some local senders It does not remove the category API but puts it in a accessing-backward protocol and in a second step I will fix all the senders I can (ie not Metacello for example). Category is really overloaded and we get lost when trying to understand code. I want to rename RBRule 'category' into 'kind' for this reason. Stef

May 31, 2015

Re: [Pharo-dev] monticello problems

by stepharo

When I merge a slice I get broken information = different from the merge of the slice elements merge. Stef Le 30/5/15 12:07, Esteban Lorenzano a Ã©crit : > Hi, > > Iâm having a lot of problems with monticello lately. > And it is not just the change of MCLazyVersionInfo (that affects just > the history). > > Now, looks like packages are keeping their own private list of > repositories. Look at the example: > > > > > Notice the âAllâ selection. Now see with âPackageâ selected: > > > And it is breaking not just my nerves, but a lot of tools, etc. > > So, I donât know it this was on purpose to avoid repositories > pollutionâ¦ but this is a bug or a bad change :) > > Can you confirm the problem? > > Esteban

May 31, 2015

Re: [Pharo-dev] DebugAction >> category

by stepharo

hi doru could you the same for GTSpotterAllCandidatesAdded, CandidateAdded, CandidataedAmountChanged, CatgeorySelected DiveInCategory category "It has nothing to do with class category or the old method category now method protocol." ^ category It would be nice to have a common superclass and move the duplication there. stef Le 31/5/15 07:35, Tudor Girba a Ã©crit : > Hi, > > This is not dead code, only the default Pharo debugger does not make > use of it. > > It is used in the GTDebugger for helping group actions by their > category. The terminology is taken from Glamour (GLMAction>>#category). > > Cheers, > Doru > > On Sun, May 31, 2015 at 7:24 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi andrei and others > > we have > > DebugAction>>category > > ^ category ifNil: [ self defaultCategory ] > > DebugAction>>defaultCategory > > ^ nil > > And I tried to browse the senders by scoping the search to the > Debugger* packages > and I got no sender. > > I have no direct user either. > So do you know if this is deadcode? > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

May 31, 2015

Re: [Pharo-dev] DebugAction >> category

by stepharo

Doru can you change the comment of this method to the GLM GLMAction>>category "The name of the category that should be used when this action is displayed in a context menu. It has nothing to do with class category or the old method category now method protocol." ^ category Yes it is the hell to do changes that touch several package managed with configurations and I will not publish other configurations. Stef Le 31/5/15 07:35, Tudor Girba a Ã©crit : > Hi, > > This is not dead code, only the default Pharo debugger does not make > use of it. > > It is used in the GTDebugger for helping group actions by their > category. The terminology is taken from Glamour (GLMAction>>#category). > > Cheers, > Doru > > On Sun, May 31, 2015 at 7:24 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi andrei and others > > we have > > DebugAction>>category > > ^ category ifNil: [ self defaultCategory ] > > DebugAction>>defaultCategory > > ^ nil > > And I tried to browse the senders by scoping the search to the > Debugger* packages > and I got no sender. > > I have no direct user either. > So do you know if this is deadcode? > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

May 31, 2015

SyntaxErrorNotification api question

by stepharo

Hi marcus we SyntaxErrorNotification>>setClass: aClass category: aCategory code: codeString doitFlag: aBoolean errorMessage: errorString location: anInteger inClass := aClass. category := aCategory. code := codeString. doitFlag := aBoolean. messageText := errorString. location := anInteger and I wonder what is the category? I imagine that this is a method protocol more than a class category? I would like to add setClass: aClass protocol: aProtocol code: codeString doitFlag: aBoolean errorMessage: errorString location: anInteger inClass := aClass. category := aCategory. code := codeString. doitFlag := aBoolean. messageText := errorString. location := anInteger and keep the other as backward compatibility. Stef

May 31, 2015

Re: [Pharo-dev] DebugAction >> category

by stepharo

I wrote category "Return the kind of debugger action. It has nothing to do with class category or the old method category now method protocol." ^ category ifNil: [ self defaultCategory ] Stef Le 31/5/15 07:35, Tudor Girba a Ã©crit : > Hi, > > This is not dead code, only the default Pharo debugger does not make > use of it. > > It is used in the GTDebugger for helping group actions by their > category. The terminology is taken from Glamour (GLMAction>>#category). > > Cheers, > Doru > > On Sun, May 31, 2015 at 7:24 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi andrei and others > > we have > > DebugAction>>category > > ^ category ifNil: [ self defaultCategory ] > > DebugAction>>defaultCategory > > ^ nil > > And I tried to browse the senders by scoping the search to the > Debugger* packages > and I got no sender. > > I have no direct user either. > So do you know if this is deadcode? > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

May 31, 2015

Re: [Pharo-dev] DebugAction >> category

by stepharo

Oki You see when you browse the code you wonder if you should pass a class tag or a method protocol. So I will update the comment. To me category is a bit too much overloaded. Stef Le 31/5/15 07:35, Tudor Girba a Ã©crit : > Hi, > > This is not dead code, only the default Pharo debugger does not make > use of it. > > It is used in the GTDebugger for helping group actions by their > category. The terminology is taken from Glamour (GLMAction>>#category). > > Cheers, > Doru > > On Sun, May 31, 2015 at 7:24 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi andrei and others > > we have > > DebugAction>>category > > ^ category ifNil: [ self defaultCategory ] > > DebugAction>>defaultCategory > > ^ nil > > And I tried to browse the senders by scoping the search to the > Debugger* packages > and I got no sender. > > I have no direct user either. > So do you know if this is deadcode? > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

May 31, 2015

Re: [Pharo-dev] DebugAction >> category

by Tudor Girba

Hi, This is not dead code, only the default Pharo debugger does not make use of it. It is used in the GTDebugger for helping group actions by their category. The terminology is taken from Glamour (GLMAction>>#category). Cheers, Doru On Sun, May 31, 2015 at 7:24 AM, stepharo <stepharo(a)free.fr> wrote: > Hi andrei and others > > we have > > DebugAction>>category > > ^ category ifNil: [ self defaultCategory ] > > DebugAction>>defaultCategory > > ^ nil > > And I tried to browse the senders by scoping the search to the Debugger* > packages > and I got no sender. > > I have no direct user either. > So do you know if this is deadcode? > > Stef > > -- www.tudorgirba.com "Every thing has its own flow"

May 31, 2015

DebugAction >> category

by stepharo

Hi andrei and others we have DebugAction>>category ^ category ifNil: [ self defaultCategory ] DebugAction>>defaultCategory ^ nil And I tried to browse the senders by scoping the search to the Debugger* packages and I got no sender. I have no direct user either. So do you know if this is deadcode? Stef

May 31, 2015

Re: [Pharo-dev] About category

by stepharo

thanks thierry (just getting up and I realised that too). Stef Le 30/5/15 22:13, Thierry Goubier a Ã©crit : > Le 30/05/2015 21:44, stepharo a Ã©crit : >> Hi guys >> >> We introduced protocol for sorting methods and package for categories >> but we left many users of categories. >> I think that it would be good to finish the clean this. >> I'm cleaning some of the method level one. >> Now I have a question what is a class category? Because it does not look >> like a package name >> >> Point category -> 'Kernel-basicObject" >> Point package name -> 'Kernel' > > (Point package classTagNamed: (Point package toTagName: Point > category)) name -> #BasicObjects > > i.e. class category = package name + tag name > > Thierry > >> Stef >> >> >> >> > > > >

May 31, 2015