Hector the file Inspector
Hector (AKA the little man with the hat) is just a wonderful UI
improvement. The human face has a lot of potential for conveying the
kinds of information developers need about the inspection status. Good
work.
Does Hector have any other "behaviors" than just turning around when you
turn inspections off?
My first reaction is that you should have a third behavior for when syntax
checking is on (when partial checking is being performed).
You need to make Hector your company mascot. That and perhap's get his
mustache trimmed.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Please sign in to leave a comment.
haha. Hector the inspector. He could also be Hector the code molestor. :D
"charles eubanks" <charles.eubanks@sbcglobal.net> wrote in message
news:op.ss4v3tqxwqdfgv@ceubanksxp.svl.ibm.com...
>
>
>
charles eubanks wrote:
(semi-seriously) What about a blindfold (perhaps just over one eye) when inspections are
turned off but syntax check is still on?
Sascha
Or Hector, the bug detector.
Tobin
Make him drink coffee :)
R
Don't touch his mustache, that's his main charm :)
OK, I like Hector, but why isn't he centered in his box?
Also, how about configurable characters, like Einstein, a paper clip or
Paris Hilton? OK, OK, just kidding here...
Amnon
charles eubanks wrote:
In article <d9ubvt$d15$1@is.intellij.net>,
"Amnon I. Govrin" <nomail@jetbrains.com> wrote:
I also filed a request to be able to change the inspection profiles from
that popup. Makes sense, tell Hector what the heck to inspect.
R
>
That would be for the idle mode, when he's doing nothing valuable, I guess.
:)
Alain
Hector can also selectively turn off syntax/inspection checking for HTML, JSP, or Java when
working on a JSP file.
Awesome! This is a cool implementation of this request:
http://www.jetbrains.net/jira/browse/IDEA-2267
Indeed. For a little icon, it sure does a lot.
>
But it's not visible enough. You could easily miss the fact that Hector
is sleeping for the current editor, and think that your code is perfect.
My eyes rarely go down there, but they often check the 'Inspection
Results' coloured square.
We need to find a move visible way to convey that info, like turning the
little coloured square into a coloured circle, or making it flash, or
whatever is better.
Alain
Or just like you got used to the gutter marks, get used to checking on
Hector.
Agreed. The green square when Hector has his back turned is a little UI lie. I'd suggest a different color, rather than a different icon. White possibly? I've submitted a request.
http://jetbrains.net/jira/browse/IDEA-3153
--Dave Griffith
Robert S. Sfeir wrote:
>>My first reaction is that you should have a third behavior for when syntax
>>checking is on (when partial checking is being performed).
Or eat donuts? ;)
N.
Robert S. Sfeir wrote:
Actually, I think that the colored square should be disabled (not colored) if syntax
checking is off.
It is deceptive to show a green square when nothing was analyzed.
Robert
>Or just like you got used to the gutter marks, get used to checking on
>Hector.
>
I don't have to check the gutter marks, I just have to see them. No
brain activity is required: it's a stripe or it's nothing, in a well
located area.
OTOH, Hector has to be actively located, looked at, and analysed - am I
seeing the moustache, or am I seeing the back of his head?
He's grayish, in a grayish overcrowded. area, next to a grayish bin
icon, ...
Alain
In article <d9ueea$rtj$1@is.intellij.net>,
Tim Haley <ymaraner@yahoo.com> wrote:
But that square also tells you if you have syntax issues too, so
disabling it makes no sense. While makes no sense as well. I think the
behavior is right.
R
Sascha Weinreuter wrote:
>>Does Hector have any other "behaviors" than just turning around when
>>you turn inspections off?
>>My first reaction is that you should have a third behavior for when
>>syntax checking is on (when partial checking is being performed).
Maybe rose-colored glasses.
Robert S. Sfeir wrote:
It doesn't if syntax checking is off, which is when I would disable it. Or am I missing
something?
For totally disabled I could see the square having a red x on it or
something, I agree with that. The problem is that it seems people want
all sorts of morse code going on in that little red square to tell them
what's up.
Nathan Brown wrote:
>>> My first reaction is that you should have a third behavior for when
>>> syntax checking is on (when partial checking is being performed).
>>
>>
>>
>> Make him drink coffee :)
>>
>> R
No, that's when he's not inspecting at all....
--
Rob Harwood
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
When Hector is looking our way, how about face state to represent the inspection result like a smile if all is good and a frown if not?
Jon Steelman wrote:
Nope, that's the job of the green/yellow/red square in the top-right
corner of the editor.
Hector's nice and all but I think people are reading more into his
visual appearance than was intended. He represents the state of
inspection configuration, not the result of inspection.
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://www.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: (416) 933-5046 | Fax: (416) 933-5001
Gosh, you don't even want his moustache to wiggle when he's inspecting?
:)
Speaking of syntax checking, would it be possible to clarify (now that the
inspector offers the setting) what's syntax and what's inspection validation?
I remember the built-in-vs-inspection-gadgets-inspections historical reasons
behind this, but having the syntax validator complain about unused imports
and unused local variables seems a bit odd to me.
Apart from that, the functionality is great, now I can safely open those
huge, "don't even think about it" files I kept avoiding. :)
Andrei
Andrei,
If you look at the error config, they've added 2 buttons so you can
filter out inspections from other error types. That would help I think.
R
Hello Robert,
Not sure I understand your suggestion.
I would expect IDEA to show me only the syntax problems (the code would not
compile) when set on syntax checking, and count the built-in IDEA inspections
(unused import, deprecated symbol warnings, unused local variable and the
few other) with the other inspections, and show them only if the setting
is on inspection level.
How would the two mentioned buttons help with that? I haven't been able to
figure if they do anything apart from changing what I see in the errors setup
pane.
Thx,
Andrei
Hecter doesn't seem to completely listen.
If I set JSP, HTML and Java highlighting to none, I still get some error highlights including:
- Unhandled Exception
- Magic Number
I also see the colored square at the top of the error bar and the tooltip says that analysis
was done. Isn't that what I am turning off?
Yep, you're right Andrei. What we've done now is not quite fair game since
those levels were taken on internal implementation basis. Specifically, we
just switch off some highlighting passes. I'm affraid we won't be able to
perform full correct separation until 5.0 release. A simple workaround will
probably rule though: if 'syntax highlighting' level choosen we can remove
warning-level annotations from the editor but analysis code that produces
them would still be executed.
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
>> If you look at the error config, they've added 2 buttons so you can
>> filter out inspections from other error types. That would help I
>> think. R
>>
>>My first reaction is that you should have a third behavior for when
>>syntax checking is on (when partial checking is being performed).
Yeah, like in the ads of the ZDF (German public TV station);
see http://www.zdf.de/ZDFde/img/77/0,1886,2294861,00.jpg for
an example.
Regards,
Jens