Re: [Pharo-project] I hate 'as yet unclassified'

Auto categorization in the old browser: " Categorize all uncategorized " had simple rules especially overridden methods / known methods in their known categories.. That would help greatly for most developers, more so the beginners to get a good feel of recommended categorization. But can auto ca

Re: [Pharo-project] I hate 'as yet unclassified'

On 2013-01-31, at 03:53, Ben Coman wrote: > > Camillo Bruni wrote: >> I was just waiting for the google issue tracker to come back to life... >> >> https://code.google.com/p/pharo/issues/detail?id=7373 >> >> => Slice in Inbox >> >> the major problem I have now, is that wrong categorizations

Re: [Pharo-project] I hate 'as yet unclassified'

On 30 January 2013 22:36, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > > 2013/1/30 Frank Shearar > >> On 30 January 2013 22:20, Nicolas Cellier < >> nicolas.cellier.aka.n...@gmail.com> wrote: >> >>> In st-80 these were protocols and the name make you think of it >>> differently.

Re: [Pharo-project] I hate 'as yet unclassified'

Camillo Bruni wrote: I was just waiting for the google issue tracker to come back to life... https://code.google.com/p/pharo/issues/detail?id=7373 => Slice in Inbox the major problem I have now, is that wrong categorizations might easily spread :P, the sepll-fleu and the space - vi rus, are

Re: [Pharo-project] I hate 'as yet unclassified'

Stephan Eggermont wrote > By author > > gvc 1307 > GaryChambers 195 > 186 > AlainPlantec 123 > CamilloBruni 89 > stephaneducasse 78 > SeanDeNigris 72 Sweet, I moved up in the rankings :) I'm so proud... -- View this message in context: http://forum.world.st/I-hate-as-yet-unc

Re: [Pharo-project] I hate 'as yet unclassified'

On Wed, Jan 30, 2013 at 12:53 PM, Chris Muller wrote: > On Wed, Jan 30, 2013 at 2:40 PM, Camillo Bruni > wrote: > > I just wrote a simple classifier which is going to be used in Nautilus. > > Basically it is an extensions of the existing code. > > > [snip] > > 3. know protocols of super impleme

Re: [Pharo-project] I hate 'as yet unclassified'

2013/1/31 Stéphane Ducasse : > > On Jan 30, 2013, at 7:20 PM, Nicolas Cellier wrote: > >> In st-80 these were protocols and the name make you think of it differently. > > nicolas normally in the book we use protocols and I normally picky about it. > I do not like categories even for classes :) > So

Re: [Pharo-project] I hate 'as yet unclassified'

I was just waiting for the google issue tracker to come back to life... https://code.google.com/p/pharo/issues/detail?id=7373 => Slice in Inbox the major problem I have now, is that wrong categorizations might easily spread :P, the sepll-fleu and the space - vi rus, are very common... On 2013

Re: [Pharo-project] I hate 'as yet unclassified'

On Jan 30, 2013, at 7:20 PM, Nicolas Cellier wrote: > In st-80 these were protocols and the name make you think of it differently. nicolas normally in the book we use protocols and I normally picky about it. I do not like categories even for classes :) So I will check. Stef > If you want to co

Re: [Pharo-project] I hate 'as yet unclassified'

> First, these are not categories. categories are for classes. > These are protocols. Yes :) > > A protocol is like an interface, or you can view it as services > offered by the instances of this class... > For example take a look at Number you have > 'comparing', is a very generic service, so t

Re: [Pharo-project] I hate 'as yet unclassified'

Cool Camillo can I see the code? I was planning to look for the old autocategoriser. Stef > I just wrote a simple classifier which is going to be used in Nautilus. > Basically it is an extensions of the existing code. > > Methods are classified using the following rules: > > 1. known prefixes (

Re: [Pharo-project] I hate 'as yet unclassified'

> To be honest I have problems understanding why method categorization is so > important. Because I do not like to live in an environment where there are papers on the floor. Did you read the pragmatic programmer book? I dislike these guys personally but the first book is excellent. "No broken

Re: [Pharo-project] I hate 'as yet unclassified'

I'm not blaming, blaming is not interesting. I want to fix them. - automatically as much as possible - with social pressure ie CATEGORISE ME PLEASE > But blaming people who contribute (a lot) might not be the best strategy. > Often the author is the one who last changed a method,

Re: [Pharo-project] I hate 'as yet unclassified'

such queries do not mean much because people change code. Anyway. I spent time on categorizing methods when I do not have my brain on to do something useful. Stef > In Pharo 20498, sorted by author in the method timestamp: > > gvc 1550 > AlainPlantec 320 > 216 > GaryChambers 215 > C

Re: [Pharo-project] I hate 'as yet unclassified'

Ah, here is a good link, http://www.cs.virginia.edu/~evans/cs655/readings/smalltalk.html Let's read what those people naming things had in mind. Nicolas 2013/1/30 Nicolas Cellier > > 2013/1/30 Frank Shearar > >> On 30 January 2013 22:20, Nicolas Cellier < >> nicolas.cellier.aka.n...@gmail.com>

Re: [Pharo-project] I hate 'as yet unclassified'

2013/1/30 Frank Shearar > On 30 January 2013 22:20, Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com> wrote: > >> In st-80 these were protocols and the name make you think of it >> differently. >> If you want to continue thinking of it in term of category, then I >> understand your miss-con

Re: [Pharo-project] I hate 'as yet unclassified'

Of course, it's documentation only. The main value is when a general service is spreaded across class library Also 'testing' and 'accessing' would be questionnable from this POV. Querying and changing state are very wide band protocols ;) The classification is also somewhat arbitrary, but for stre

Re: [Pharo-project] I hate 'as yet unclassified'

On 30 January 2013 22:20, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > In st-80 these were protocols and the name make you think of it > differently. > If you want to continue thinking of it in term of category, then I > understand your miss-conception. > I'm curious to know when

Re: [Pharo-project] I hate 'as yet unclassified'

In st-80 these were protocols and the name make you think of it differently. If you want to continue thinking of it in term of category, then I understand your miss-conception. I'm curious to know when the term category was introduced... Maybe with Monticello where it means 'Package'? Clever hacks

Re: [Pharo-project] I hate 'as yet unclassified'

On 30 January 2013 21:03, Nicolas Cellier wrote: > First, these are not categories. categories are for classes. > These are protocols. > > A protocol is like an interface, Yes, only no. Think of the messages that make something like a Stream: you have accessing things (#next, ...), you have testi

Re: [Pharo-project] I hate 'as yet unclassified'

Am 30.01.2013 um 22:03 schrieb Nicolas Cellier :First, these are not categories. categories are for classes.These are protocols.Well, that's one reason I took the term "uncategorized". If I take the context menu in the category (!) pane I seeSo it looks to me tha

Re: [Pharo-project] I hate 'as yet unclassified'

On 2013-01-30, at 21:53, Chris Muller wrote: > On Wed, Jan 30, 2013 at 2:40 PM, Camillo Bruni wrote: >> I just wrote a simple classifier which is going to be used in Nautilus. >> Basically it is an extensions of the existing code. >> >> Methods are classified using the following rules: >> >>

Re: [Pharo-project] I hate 'as yet unclassified'

First, these are not categories. categories are for classes. These are protocols. A protocol is like an interface, or you can view it as services offered by the instances of this class... For example take a look at Number you have 'comparing', is a very generic service, so that any object can be i

Re: [Pharo-project] I hate 'as yet unclassified'

On 30 January 2013 21:40, Camillo Bruni wrote: > I just wrote a simple classifier which is going to be used in Nautilus. > Basically it is an extensions of the existing code. > > Methods are classified using the following rules: > > 1. known prefixes (initialize.* => initialize-reseleas, test.* ->

Re: [Pharo-project] I hate 'as yet unclassified'

On Wed, Jan 30, 2013 at 2:40 PM, Camillo Bruni wrote: > I just wrote a simple classifier which is going to be used in Nautilus. > Basically it is an extensions of the existing code. > > Methods are classified using the following rules: > > 1. known prefixes (initialize.* => initialize-reseleas, te

Re: [Pharo-project] I hate 'as yet unclassified'

I just wrote a simple classifier which is going to be used in Nautilus. Basically it is an extensions of the existing code. Methods are classified using the following rules: 1. known prefixes (initialize.* => initialize-reseleas, test.* -> testing..) 2. getters and setters of instance variables 3

Re: [Pharo-project] I hate 'as yet unclassified'

> To be honest I have problems understanding why method categorization is so > important. It provides a look into the mind of the author. > Often I don't care a single bit about categories because I don't understand > them. I often categorize just to make lint happy :) Ha! I remember when I u

Re: [Pharo-project] I hate 'as yet unclassified'

Sorry! Mostly me... Regards, Gary - Original Message - From: "Esteban Lorenzano" To: Sent: Wednesday, January 30, 2013 1:07 PM Subject: Re: [Pharo-project] I hate 'as yet unclassified' holy s**t , 35! and I'm more or less a maniac of classification :P

Re: [Pharo-project] I hate 'as yet unclassified'

On 30 Jan 2013, at 15:08, Sven Van Caekenberghe wrote: > Can it be done in plain Smalltalk ? Something crude like this: OrderedCollection streamContents: [ :stream | Object withAllSubclassesDo: [ :eachClass | stream nextPutAll: (eachClass methods

Re: [Pharo-project] I hate 'as yet unclassified'

Norbert wrote: >To be honest I have problems understanding why method categorization is so >important. Often I don't care a single bit about categories because I don't >understand them. I often categorize just to >make lint happy :) >What is the use? Declaring usage patterns? Declaring visibilit

Re: [Pharo-project] I hate 'as yet unclassified'

2013/1/30 Norbert Hartl : > (SNIP) > I would make the none categorized term weaker by naming it "uncategorizied" > so at least I have the change to deliberately not categorizing my methods > without being annoyed by someones opinion about what is essential. I agree with this, I'd fine if the met

Re: [Pharo-project] I hate 'as yet unclassified'

Hernan Wilkinson wrote: I think that classification is a matter of time and maturity of what you are doing. When I'm programming, using TDD or in the debugger, I don't care about categorization, I don't want to be stopped or slowed down by that. But before I commit the code, I run SmallLint and s

[Pharo-project] I hate 'as yet unclassified'

>in the 4.3 one-click too >... >#unclassified methods by author >... >stephaneducasse145 Interesting ;) As I wrote in http://markmail.org/message/oo4gsiyasoinkmol: "Removing packages or classes that are not documented is too hard ... but we should use Lint rules to check the "completen

Re: [Pharo-project] I hate 'as yet unclassified'

Am 29.01.2013 um 16:57 schrieb Stéphane Ducasse : > Hi guys > > I spend my time recategorizing methods. > > I would like the change the intention of 'as yet unclassified' because this > is a PLAGUE. > It is like throwing papers on the floor. > So we should have a different name to indicate th

Re: [Pharo-project] I hate 'as yet unclassified'

Sven wrote: >Euh, I want to fix some of them ! Good, that was the idea :) I was inspired by Doru's humane assessment primer. >Could you express this query in executable code ? >I am guessing you did this with Moose ? >Can it be done in plain Smalltalk ? I opened a Moose to take a look at the Mon

Re: [Pharo-project] I hate 'as yet unclassified'

As there was a discussion on the Pharo mailing list on the number of these methods, I thought to check in the 4.3 one-click too. Some synchronisation would be possible by adding a hash over the method source, compare one method in the other system to see if it was classified there. Stephan #

Re: [Pharo-project] I hate 'as yet unclassified'

Euh, I want to fix some of them ! Stephan, Could you express this query in executable code ? I am guessing you did this with Moose ? Can it be done in plain Smalltalk ? Sven On 30 Jan 2013, at 14:02, Stephan Eggermont wrote: > In Pharo 20498, sorted by author in the method timestamp: > > gvc

Re: [Pharo-project] I hate 'as yet unclassified'

I think that classification is a matter of time and maturity of what you are doing. When I'm programming, using TDD or in the debugger, I don't care about categorization, I don't want to be stopped or slowed down by that. But before I commit the code, I run SmallLint and solve all the uncategorized

Re: [Pharo-project] I hate 'as yet unclassified'

Ben On Jan 30, 2013, at 2:02 PM, Stephan Eggermont wrote: > In Pharo 20498, sorted by author in the method timestamp: > > gvc 1550 > AlainPlantec 320 > 216 > GaryChambers 215 > CamilloBruni 163 > IgorStasenko 159 > stephaneducasse 152 > avi 148 > Igor.Stasenko 128

Re: [Pharo-project] I hate 'as yet unclassified'

In Pharo 20498, sorted by package name Polymorph-Widgets 1116 Polymorph-Widgets-Windows 615 Polymorph-Tools-Diff260 Monticello-Repositories 240 Morphic-MorphTreeWidget-Examples192 Monticello-Versioning 144 NativeBoost-Core-Types 104 Monticello-Storing 66 NativeBoost

Re: [Pharo-project] I hate 'as yet unclassified'

holy s**t , 35! and I'm more or less a maniac of classification :P On Jan 30, 2013, at 2:02 PM, Stephan Eggermont wrote: > In Pharo 20498, sorted by author in the method timestamp: > > gvc 1550 > AlainPlantec 320 > 216 > GaryChambers 215 > CamilloBruni 163 > IgorStasenko 159 > step

Re: [Pharo-project] I hate 'as yet unclassified'

In Pharo 20498, sorted by author in the method timestamp: gvc 1550 AlainPlantec320 216 GaryChambers215 CamilloBruni163 IgorStasenko159 stephaneducasse 152 avi 148 Igor.Stasenko 128 StephaneDucasse 85 SeanDeNigris81 MarcusDenker78 ab 75

Re: [Pharo-project] I hate 'as yet unclassified'

Ok but in 3.0 We will kill that bad habit. We should investigate in an automatic categorizer. There was one I should have a look one of these days (since I do not know what to do :)). Stef > Code with "as yet unclassified" methods should be rejected by the monkey ! > > Ben > > On Jan 29, 201

Re: [Pharo-project] I hate 'as yet unclassified'

On 29 janv. 2013, at 23:21, Benjamin wrote: > Code with "as yet unclassified" methods should be rejected by the monkey ! +1

Re: [Pharo-project] I hate 'as yet unclassified'

Code with "as yet unclassified" methods should be rejected by the monkey ! Ben On Jan 29, 2013, at 11:19 PM, Stéphane Ducasse wrote: > > On Jan 29, 2013, at 2:03 PM, Ben Coman wrote: > >> While on the topic, some of the category chooser dialogs are sorted so that >> the extensions are liste

Re: [Pharo-project] I hate 'as yet unclassified'

On Jan 29, 2013, at 2:03 PM, Ben Coman wrote: > While on the topic, some of the category chooser dialogs are sorted so that > the extensions are listed first - which I find annoying (in 1.4). In 2.0 > can the standard categories be shown first ? > > Also, I still struggle to really be confid

Re: [Pharo-project] I hate 'as yet unclassified'

On Jan 29, 2013, at 1:06 PM, wam wrote: > 'CATEGORIZE ME' > Because smalltalkers hate upper cased letters, so everyone will categorize > them quickly ;) :) may be should add 'ASs' I really hate hate hate all this easy sloppiness. Stef > > On 29 janv. 2013, at 16:57, Stéphane Ducasse

Re: [Pharo-project] I hate 'as yet unclassified'

While on the topic, some of the category chooser dialogs are sorted so that the extensions are listed first - which I find annoying (in 1.4). In 2.0 can the standard categories be shown first ? Also, I still struggle to really be confident I am choosing the right categories. Perhaps down th

Re: [Pharo-project] I hate 'as yet unclassified'

+1 :) Ben On Jan 29, 2013, at 5:06 PM, wam wrote: > 'CATEGORIZE ME' > Because smalltalkers hate upper cased letters, so everyone will categorize > them quickly ;) > > On 29 janv. 2013, at 16:57, Stéphane Ducasse wrote: > >> >> I would like the change the intention of 'as yet unclassified'

Re: [Pharo-project] I hate 'as yet unclassified'

'CATEGORIZE ME' Because smalltalkers hate upper cased letters, so everyone will categorize them quickly ;) On 29 janv. 2013, at 16:57, Stéphane Ducasse wrote: > > I would like the change the intention of 'as yet unclassified' because this > is a PLAGUE. > It is like throwing papers on the fl

Re: [Pharo-project] I hate 'as yet unclassified'

2013/1/29 Stéphane Ducasse : > Hi guys > > I spend my time recategorizing methods. > > I would like the change the intention of 'as yet unclassified' because this > is a PLAGUE. > It is like throwing papers on the floor. > So we should have a different name to indicate that it should be fixed. >

[Pharo-project] I hate 'as yet unclassified'

Hi guys I spend my time recategorizing methods. I would like the change the intention of 'as yet unclassified' because this is a PLAGUE. It is like throwing papers on the floor. So we should have a different name to indicate that it should be fixed. Any ideas? 'you are a dirty programmer - c