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 140356 - [65cat][j2me] Resolving Reference Dialog for mobility doesn't resolve the references.
Summary: [65cat][j2me] Resolving Reference Dialog for mobility doesn't resolve the ref...
Status: RESOLVED WORKSFORME
Alias: None
Product: javame
Classification: Unclassified
Component: Build System (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Petr Suchomel
URL:
Keywords:
: 141234 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-07-16 16:55 UTC by esmithbss
Modified: 2008-07-24 09:10 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 esmithbss 2008-07-16 16:55:49 UTC
[ BUILD # : 200807101204 ]
[ JDK VERSION : 1.6.0_07 ]

I opened a project with a reference issue on the JavaME platform
name.  Once the project was opened, I brought up the Pop-Up menu and
selected "Resolve Reference Problems."

In the subsequent dialog it identified the problem as a bad reference
to the WTK.  So I clicked the Resolve button to bring up the Java
Platform Manager.

Double clicking on the proper platform (Sun Java(TM) Wireless Toolkit
2.5.2 for CLDC) did nothing so I clicked the close button.  

When I returned, the reference problem still exists.
Comment 1 Milos Kleint 2008-07-16 18:59:21 UTC
please file j2me related issue under mobility component. thanks.
Comment 2 Petr Suchomel 2008-07-22 17:01:33 UTC
I am not able to reproduce this issue: Could you better describe where you double clicked, possible attach
project.properties and also the version of WTK you are using.
Comment 3 Lukas Hasik 2008-07-23 08:21:26 UTC
*** Issue 141234 has been marked as a duplicate of this issue. ***
Comment 4 esmithbss 2008-07-23 08:33:00 UTC
Try this.

1) Download the LWUIT Gui Framework from lwuit.dev.java.net.  There is a project within the download that is configured
for the 2.5.1 WTK.

2) Within the NB Dev Build, open the LWUIT Demo project.  You will get a project with a reference problem.

3) Open the project pull down menu and Click on the "Resolve Reference Problems" item.

4) Select the proper WTK.

5) Close the WTK Dialog.

At this point, the reference problem has not been resolved.  To fix the problem, you need to open up the project
properties and fix it there.
Comment 5 esmithbss 2008-07-23 08:34:45 UTC
This issue is not limited to Windows XP, it also affects Linux platforms (issue located on XP also located on Ubuntu 8.04)
Comment 6 Lukas Hasik 2008-07-23 08:35:37 UTC
it seems as "misunderstanding" or more "usability problem" to me.

If the user clicks the  Resolve reference then we expect him to provide/install the missing platform to the IDE. If you
want to change the project platform you have to open project properties and change it (for all configurations that point
to the wrong/missing platform(s))

If I'm right then please close this issue as INVALID or re-phrase it to enhancement. Thank you. 
Comment 7 sunbiz 2008-07-23 10:31:19 UTC
This is a usability issue actually. We should be able to Resolve the Missing Platform by selecting a new platform that 
is already installed, instead of going to Properties and selecting the platform.
Comment 8 Lukas Hasik 2008-07-23 11:34:42 UTC
as I said before the purpose of the Resolve reference dialog is to add the missing reference platform/jar/library to the
IDE.
If you want to change (not resolve reference) the settings of project then you have to go to project properties.

I'm closing this as WORKSFORME now. BUT feel free to fill new enhancement for project/ui with exact description what you
don't like and how it could be improved. I agree that current behavior can confuse users.

thank you for report
Comment 9 esmithbss 2008-07-24 06:56:28 UTC
What you're saying is that the "Resolve References" capability within the IDE has multiple meanings based on the type of
item being resolved.

When I get a "Resolve References" issue and the item is a Library that cannot be found, I am presented with a dialog
that allows me to resolve the library reference.  This resolution is saved immediately.

But you are saying that "Resolve References" for a platform behaves in a contrary way and doesn't allow us to "Resolve"
anything.

Requiring the "Resolve References" item to be consistent, in fact any dialog or subcomponent within a system to behave
in a single, coherent manner is at the core of basic Human Interface Development Guidelines.

By your description, one or both of the groups (platforms/mobility and libraries/references) that designed an interface
to the "Resolve References" did not follow a consistent HIG and we have a component within the IDE that is effectively
unusable for it's named purpose (the resolution of reference problems).

It may have been a design/implementation decision, but any possible HIG violation or confusion based on an operation
like this not doing what its name identifies is a DEFECT and should be fixed.  It should not require an RFE to get the
operations to follow a consistent HIG for the IDE.
Comment 10 Lukas Hasik 2008-07-24 08:23:18 UTC
|What you're saying is that the "Resolve References" capability within the IDE has multiple meanings based on the type
|of item being resolved.

NO

|When I get a "Resolve References" issue and the item is a Library that cannot be found, I am presented with a dialog
|that allows me to resolve the library reference.  This resolution is saved immediately.

but you are required to add the library with the same name. Example: If the missing lib is "MyLib" then you have to
create new library with the same name to resolve the missing reference. The same is true for platform - if platform A is
missing then you have to add platform A to IDE. (and not just select platform B in the resolve reference dialog.

|But you are saying that "Resolve References" for a platform behaves in a contrary way and doesn't allow us to "Resolve"
|anything.

NO, see my previous comment.

|Requiring the "Resolve References" item to be consistent, in fact any dialog or subcomponent within a system to behave
|in a single, coherent manner is at the core of basic Human Interface Development Guidelines.
|By your description, one or both of the groups (platforms/mobility and libraries/references) that designed an interface
|to the "Resolve References" did not follow a consistent HIG and we have a component within the IDE that is effectively
|unusable for it's named purpose (the resolution of reference problems).

Please, try it. Resolve reference dialog let you find and add the missing reference - jar/library/platform to IDE.

|It may have been a design/implementation decision, but any possible HIG violation or confusion based on an operation
|like this not doing what its name identifies is a DEFECT and should be fixed.  It should not require an RFE to get the
|operations to follow a consistent HIG for the IDE.

Convince me that I'm wrong with all my previous comments. And please use simple/straightforward examples. I'm not
interested in esey about HIE and HIG. This is off-topic. If you want to discuss UI and IDE behavior sign to nbui mailing
list and start a discussion there. 

It seems to me that I'll rather record a screencast to show you how it works with the Resolve Reference dialog. 
Comment 11 esmithbss 2008-07-24 09:10:24 UTC
So by definition, "Resolve References" doesn't allow you to fully resolve invalid references.  Instead, it identifies
the missing references, but you have to go to two separate places to resolve the references completely.  

The first, if you want to add new stuff to the IDE with the old names, which may actually duplicate already installed
items but give them new names

And the second is actually updating the project references by going into the project properties and updating the
references there.

That being the case, and since both capabilities are necessary to completely resolve references when moving to an
updated IDE (with new library/platform/etc... lists) I can agree that this requires an RFE requesting these two
capabilies be combined into one comprehensive "resolve references" capability.

A request to combine both capabilities necessary for full reference resolution in a single location accessed from the
"Resolve References" hint dialog has been added as http://www.netbeans.org/issues/show_bug.cgi?id=141489