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 215843 - Be able to "sticky" navigator to one class
Summary: Be able to "sticky" navigator to one class
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Navigation (show other bugs)
Version: 7.3
Hardware: PC All
: P3 normal with 1 vote (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-23 17:27 UTC by ecerichter
Modified: 2013-09-04 13:46 UTC (History)
1 user (show)

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 ecerichter 2012-07-23 17:27:51 UTC
Navigator is one of the most important high level views of classes, specially the "Beans pattern" view. The problem is that the content is always synchronized to current context, whereas sometimes this is not desired.

Today (up to NB 7.2RC1) behavior:
1) Click on class, class structure is shown.
2) Click xhtml source code, page structure is shown. Class structure disappear, so if you forgot something, then you have to click again in the class.

Desired behavior is:
1) Click on class, class structure is shown.
2) Click on "stick to this" button.
3) Click xhtml source code: class structure keep visible

As future enhancement (RFE to be submitted) is the ability to "drang-n-drop" bean pattern on navigator over xhtml source code, giving as result the "<h:outputText value='#{someBean.someAttribute}'/>" code.

Regards,

Edson.
Comment 1 ecerichter 2012-10-25 21:29:44 UTC
Adjusting request to the new development version and OS = All, because it will benefit all users no matter wich OS.
Comment 2 Tomas Zezula 2012-10-26 05:55:04 UTC
Makes sense to me.
Reassigning to UI team to decide.
Comment 3 Petr Somol 2012-11-01 15:54:58 UTC
Just remarking that the idea is good. Before we can proceed, however, we need to go through a wider UI review that would unify this with "pinning" of other stuff as well, like sub-tabs in tabs etc. Also, in NB7.3 we changed the Inspect Members and Inspect Hierarchy actions so that now Inspect Members takes place in Navigator; the newly added history combo follows a slightly different logic from the idea proposed here - this will need to by adjusted as well..
Comment 4 ecerichter 2012-11-02 18:34:21 UTC
Won't hurt wait even for 7.4 if necessary.
NB UI is one of the most friendly, I'll not be rush to introduce something that would make it unstable.

Regards,

Edson