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, 2013, at 11:19 PM, Stéphane Ducasse <stephane.duca...@inria.fr> > 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 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 the track, a feature useful for newcomers might >>> be a tooltip when hovering over items on the category list, or >>> alternatively, hover showing a list of the ten most common methods >>> appearing in that category. >> >> could be really neat :) >> >>> >>> cheers -ben >>> >>> Stéphane Ducasse wrote: >>>> 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 - change me' >>>> >>>> >>>> Stef >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> >
