stepharo wrote:
if someone want to do a final pass on the recategorizer that I harvested and improved we could have a much better categorizer in the system
Because we can define the rules we want and it can take into account the root a hierarchy or other...
My code is at:
MCHttpRepository location: 'http://www.smalltalkhub.com/mc/StephaneDucasse/AutomaticMethodCategorizer/ma...'
user: ''
Thanks Steph. I am interested in having a look, just not for a while. I'll tag it for later. cheers -ben
On 22/6/14 14:30, Ben Coman wrote:
Just a random idea as I am working on the PharoLaserGame tutorial, and I see the need to repetitively tell the reader to create the same standard protocols on each new class, e.g. accessing, initialization, testing....
It might be useful for newly defined classes to pre-populate the System Browser Protocols List with a small set of the most common protocols...etc. These could be displayed in grey similar to extension methods until they actually contained anything. Obviously this would not suit everyone but might be very useful to novices. You might consider it a form of cultural training/normalism. Is is practical to have such a common subset of protocols? The danger of course is that the list grows to an unwieldy size. Now I am not such a novice, but personally I'd find this somewhat useful day to day.
Enough rambling, what are your thoughts? cheers -ben