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 84351 - The title of the properties window should be used consistently in format "$node.name [$node.kind] - Properties".
Summary: The title of the properties window should be used consistently in format "$no...
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Shivanand Kini
URL: http://xdesign-tools.czech.sun.com/us...
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-06 17:34 UTC by Chris Webster
Modified: 2006-09-22 06:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screen shot showing soap:operation [null] in properties pane. (2.93 MB, application/octet-stream)
2006-09-19 17:34 UTC, jlautz
Details
From Jirka's mail shows current and proposed changes (210.47 KB, image/png)
2006-09-19 23:00 UTC, Shivanand Kini
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Webster 2006-09-06 17:34:30 UTC
Also finding in WSDL editor:

http://xdesign-tools.czech.sun.com/usability/jse/jse9-coke-endToEnd/report.html#Finding_WSDLtreeTooComplex

split into two bugs.
Comment 1 Shivanand Kini 2006-09-15 00:29:50 UTC
Checked in fix for this.
Now shows {name} [{kind}} - Properties in the property sheet title bar.
Shows some relationship using grey text on the node name.
Comment 2 jlautz 2006-09-19 17:31:36 UTC
I LOVE THIS FEATURE!

However, on Windows XP with NB55 200609190000:

soap:operation has a [null] type. Screenshot attached.
Comment 3 jlautz 2006-09-19 17:34:18 UTC
Created attachment 34170 [details]
Screen shot showing soap:operation [null] in properties pane.
Comment 4 Shivanand Kini 2006-09-19 21:19:04 UTC
added a fix to not show [null], if the type name is not available.
Comment 5 Shivanand Kini 2006-09-19 22:58:39 UTC
Added missing type display name for some nodes.
Changed the node decoration as per Jirka's recommendations as follows:
(attached left and right images)
The current state is on the left, suggested state is on the right.

Truly, there are some consistency issues, some work still could be done on that
but - isn't that better? Less cluttered?

* Let's really follow the pattern used in BPEL and Java navigator for message
types definitions. I think that the fact whether the reference is made to a
complex/simple type or element is not that important (it can be in tooltip or -
in the end - it's in property sheet). Please correct me, if I'm wrong, if that
information is significant.

 

[SKINI] We hide the fact that it is an element or type in the property sheet
(because it’s a mutually exclusive selection, we show only attribute on the
property sheet). I think showing the type/element will help advanced users to
know whether it’s an element or type, instead of going into the source and
looking at it.

But I am ok with removing it if others see that its not required.


* Let's get rid of the parenthesis, they don't make it better.

[SKINI] I agree to this.


* I think there's no need for (Message Not Set) kind of labels.
[SKINI} I can do this too.


If you object, please do so - I'm always interested in other's opinion!
Comment 6 Shivanand Kini 2006-09-19 23:00:36 UTC
Created attachment 34184 [details]
From Jirka's mail shows current and proposed changes
Comment 7 pushpa 2006-09-22 06:40:01 UTC
Verified on: 060921 build