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.

Bug 54959 - Case insensitive filters
Summary: Case insensitive filters
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Sedlacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-14 18:24 UTC by Antonin Nebuzelsky
Modified: 2007-02-12 22:09 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2005-02-14 18:24:11 UTC
I think it would be better to have the filters in
Profiling Results' views case insensitive.
Comment 1 mishadmitriev 2005-02-14 18:44:06 UTC
I am sorry... the Java language is case-sensitive, so I don't think 
our filters should introduce inconsistency and confusion by being 
case-insensitive.
Comment 2 iformanek 2005-02-14 23:19:02 UTC
I'd disagree with Misha here. Whatever is the case sensitivity in Java
language spec has lower impact on what is going to be useful.

An example I'd use here is IntelliJ's "Open Class" dialog, which is
class insensitive by default, even accepting "Camel words" (i.e. "TAR"
would match to "TargetAppRunner" for instance).

Jirka and I have been thinking about whether to make the String
comparison case sensitive or insensitive, and have leaned towards case
sensitivity, but we are not completely sure about that, so this type
of feedback is quite useful.
Comment 3 mishadmitriev 2005-02-14 23:38:31 UTC
Well, opening a file and dealing with Java program identifiers are 
somewhat different issues. Consider a case when you have both package 
foo.bar and class foo.Bar. If you want to just load Bar.java, you can 
always point the tool at the right file, if not by typing its name 
then by clicking on it. But a user who just wants to filter out just 
methods of class foo.Bar (and maybe foo.Bar1,.. etc.) will be 
confused and dissatisfied if they receive the whole foo.bar package 
in addition to that. For this reason, I think we need to have case-
sensitivity as at least an option (and probably a default one). 
Comment 4 iformanek 2005-02-15 09:01:41 UTC
Thanks for your opinion Misha.
We'll play with the two options, possibly asking users at the 
usability study, and based on that will decide which is the better 
way to do this.
Comment 5 Antonin Nebuzelsky 2005-02-15 10:25:01 UTC
I vote for having this at least as an option. I find it quite useful
in OptimizeIt.
Comment 6 iformanek 2005-03-29 14:50:03 UTC
Assigning to Jirka to resolve
Comment 7 Jiri Sedlacek 2005-04-15 16:03:47 UTC
I agree that for instrumentation filters case sensitivity should follow Java 
language approach. On the other side, I think that usage of results filters is 
slightly different and case insensitivity could simplify using it.

I've changed results filters to be case insensitive from now and I'm closing 
this issue for now. We can reopen it if there will be any problems with this 
approach.
Comment 8 ehucka 2006-10-09 12:09:32 UTC
Verification of old issues.
Comment 9 Alexander Kouznetsov 2007-02-12 22:09:36 UTC
Closing old issues.