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 50219 - Specify Root Methods UI not intuitive
Summary: Specify Root Methods UI not intuitive
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: iformanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-11 12:49 UTC by Jiri Skrivanek
Modified: 2006-03-24 12:49 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2004-10-11 12:49:19 UTC
UI to specify root methods is not very intuitive.
There is a three level dialog chain and it is not
clear what to do to add method to the list.
Additionally you don't know which methods were
already added to the list. Edit button is probably
redundant. I think it does the same as new button.

My idea is to have three lists: recent classes,
methods, root methods.

Recent Classes: list of classes previously used
Methods: when you select a class, only methods not
included in root methods are supplied
Root Methods: list of all root methods
Comment 1 iformanek 2004-10-11 16:48:57 UTC
Agreed, the UI needs to be simplified and streamlined
Comment 2 iformanek 2004-10-25 12:05:34 UTC
Postponed to M4
Comment 3 iformanek 2005-01-13 13:42:01 UTC
Postponing to M5, will redo as part of tighter 4.0 integration, 
probably similarly to how Open Class works in 4.0
Comment 4 iformanek 2005-02-03 02:32:07 UTC
Not much more to do here.
I cannot think of any better way to simplify the following sequence:
  
Select Task Panel
  -> click Part of App, Select...
Selected Root Methods
  -> click Add...
Specify Methods
  -> click Select...
Select Class from list of opened project
Comment 5 mishadmitriev 2005-02-03 02:43:28 UTC
Agreed. I think with projects class selection became more convenient,
plus our current GUI, improved more or less according to the initial
recommendations, is now intuitive enough for most users.
Comment 6 Jiri Skrivanek 2005-03-01 11:13:06 UTC
Better a UI enginneer should check correctness of the UI. For me it is
still not perfect but I accept it. Anyway 'Edit...' button is
definitely useless.