Re: The screwdriver is back!

OK, screw the screwdriver.

Checking in implements.png;
/cvs/java/editor/src/org/netbeans/modules/java/editor/resources/implements.png,v 
  <--  implements.png
new revision: 1.5; previous revision: 1.4
done
Checking in overrides.png;
/cvs/java/editor/src/org/netbeans/modules/java/editor/resources/overrides.png,v 
  <--  overrides.png
new revision: 1.5; previous revision: 1.4
done

Is it better now?


H

Petr Hrebejk wrote:
> Just got another complaint about screwdriver. What's so bad about 
> screwdrivers? Interestingly the wrench for not yet built classes in 
> explorer seems to be OK. Am I missing something about tools connotations?
> 
> Thanks
> Hrebejk
> 
> Petr Hrebejk wrote:
> 
>> Cau,
>>
>> I don't know what is more ugly, screwdriver or the green ones. Maybe 
>> HIE will come up with something nicer.
>>
>> I agree with having the hint, but I disagree that it would help to get 
>> rid of the icons.
>>
>> 1) If there is not the @Override in the then there would a warning but 
>> the warning icon does not show what warning that is.
>>
>> 2) Clicking the icon gets you to the super method. Clicking a hint or 
>> @Overrides annotation obviously doesn't. Go To super implementation is 
>> less discoverable IMO.
>>
>> 3) Id the navigation does not work please file a bug.
>>
>> Hrebejk
>>
>> Jesse Glick wrote:
>>
>>> For a while we had overrides/implements icons which were green "O"s 
>>> and "I"s, which was easy enough to remember, if not very elegant. Now 
>>> we are back to a cleaned-up version of the 5.x icons.
>>>
>>> http://deadlock.nbextras.org/fisheye/changelog/netbeans/java/editor?cs=MAIN:phrebejk:20070221161628 
>>>
>>>
>>> Why the screwdriver, or whatever it is?
>>>
>>> For that matter, why do we need two different icons? IMHO we could 
>>> just use the "overrides" icon. All I usually care about is knowing 
>>> that this method's signature is constrained by some supertype, i.e. 
>>> that the @Override annotation could be used. The details are 
>>> available in the tooltip if you care anyway.
>>>
>>> More radical idea: get rid of the override/implements annotations 
>>> completely for 1.5+ sources. Instead, add an editor hint to add 
>>> @Override to any method which could use it but does not currently 
>>> have it. (Jackpot has a transformer like this too.) I would actually 
>>> find this more valuable - @Override helps prevent stupid mistakes 
>>> when editing supertypes (just as C#'s language keyword does), and 
>>> once your code is fully @Override-annotated, you won't need to see 
>>> the distracting editor glyph icons any more. "Go to Super 
>>> Implementation" would then take care of the navigation aspect of the 
>>> current annotations. (Assuming it actually worked - currently it 
>>> doesn't.)
>>
>>
>>
>>> -J.
>>>