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 66539

Summary: [50cat] module display mapping to code name base
Product: apisupport Reporter: rrochat <rrochat>
Component: ProjectAssignee: Martin Kozeny <mkozeny>
Status: NEW ---    
Severity: blocker Keywords: UI
Priority: P4    
Version: 5.x   
Hardware: PC   
OS: Windows XP   
Issue Type: ENHANCEMENT Exception Reporter:

Description rrochat 2005-10-11 23:36:12 UTC
[ BUILD # : 200509261930 ]
[ JDK VERSION : 1.5.0_05 ]

Being able to specify a "display name" for a module is nice, but it's really 
tough to map between the display name and the package name.
I could name quite a number of cases where I've wasted a lot of time trying
to track down the corresponding item, but I'll just say that I'd
rather just have all the NetBeans modules be named with their
package names.  They'd sort nicely together in the project list and I wouldn't
have to play guessing games trying to figure out where and how 
a newly opened project got displayed when I started with something like

Or maybe even an option to use the code name base instead of the display name for all Projects?

Failing that, we need better support for mapping
in both directions (the module dependency wizard is 
great at mapping from the package TO the display name, 
but not backwards after you've made a selection).
Maybe the tooltip could include the package name whenever
a display name was used in a list?
Perhaps the most important thing is to have one place where
ALL the display and package names could easily be searched.
The main API Javadoc page
would be a great place to do this, but it needs some work.
(Try to find the display name for org.openide.awt.
Why are there 2 "Settings" links in the upper left hand module list?
Why do the things under Content look so different?)
Comment 1 Jesse Glick 2005-10-12 01:56:55 UTC
There are already several places where both the code name and display name are
shown, e.g.

- in the add module dep dialog for a module project

- in the platform modules list for a suite project

If you see places where this info is needed but missing, please remove the
INCOMPLETE keyword and enumerate the exact locations in the GUI.

Re. Javadoc etc. - please use nbdev. (Anyway the Javadoc page is not really
appropriate for this purpose since only modules with official APIs are
documented there, yet sometimes you need to deal with modules without APIs in
the module devel environment.)
Comment 2 rrochat 2005-10-12 03:37:20 UTC
Both the code name and display name are shown when you're adding a module 
dependency (Project Properties), but not when you come back and look at it 
after you've gotten a message like 
"module1 - The module named was needed and not found."
and want to know if you added the module.  Either you have
to delete likely candidates and add them back, or just give up and go
to the file.

Entries in the Projects window do have tooltips that give the complete 
pathname, but 80% of the time these tooltips don't pop up. (I click,
wait, one may pop up or not, I move the cursor to another, hover, it 
may pop up, but 2 in a row is the most I can get.)

The 3rd place I miss this information is in the Project Properties / Build /
Module List.  Under platform6, for example, I see "Actions APIs" and the tooltip
here is "Definition of common actions for NetBeans"
Again, how do I map "The module named was needed and not found."
to something in this list?

Yes, you can add more tooltips, but instead of bridging the gaps, I'd just
rather that the gaps didn't exist in the first place.

As to nbdev, I've already commented there about the inconsistencies on the
javadoc page. 
Comment 3 rrochat 2005-10-12 03:42:04 UTC
Sorry, you may have addressed the Module List issue.  I forgot you added that
note to 65924; I'm still looking at the 1st beta.
Comment 4 Jesse Glick 2006-10-28 17:19:37 UTC
*** Issue 88178 has been marked as a duplicate of this issue. ***