This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Recently I've found very useful to highlight with a flashy colour the calls or invocations to methods in Java. So much that this mere fact has completely changed my mind about how to use the syntax highlighting feature (I was over-using it). I've always tried to avoid nesting more than 2 method calls because it may make that a call to an important method remains "buried" in a mess of code. However, sometimes you have to edit code from other developers and have no time to re-format everything. Or even worse: You are forced to follow that style and not to create "too many" temporary variables. In these cases, highlighting the method calls it's vital. I've done this in Java with some legacy code and it has made my life a lot easier. I can distinguish perfectly where there is each call. Would it be possible to have this feature in JavaScript too? Thank you!
Hi, I'm not sure whether I understand. For me what you described, it is highlighting occurrences. And this feature is in javascript as well. I can be wrong. Could you please attach an example?
Hello Petr: I guess that the term "highlighting" may be confusing here, because NetBeans IDE has syntax highlighting (Fonts & Colors → Syntax) and a more general highlighting (Fonts & Colors → Highlighting). So let's refer to the first one as "colouring", if you agree. I was referring to colouring all method and function calls or invocations, not one in particular or its occurrences. In the colouring section for Java (Fonts & Colors → Syntax → Java) there are the options "Method Declaration" and "Method Use", so you can choose the last one to colour only the calls or invocations. If this option existed in JavaScript, this piece of code: var score = normalizeScore (parseInt (document.getElementById ("score").value, 10)); Would have these words coloured in a different colour: normalizeScore parseInt getElementById This option, that sounds trivial, helps a lot not to miss the existence of a method call when there are several ones nested. One can prevent that by "dissecting" the calls, putting one by line. However when you've to read others' code, you can find lots of nested calls that are very complicated to be read :S . Right now, if I set a colour for the item "Method", it's only the method definition what is coloured: function normalizeScore (...) { ... } The calls to that method get the colour from the item "Identifier". Thank you!
Thanks for the explanation. Now it is clear.