[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842708#action_12842708
 ] 

Stefan Seelmann commented on DIRSTUDIO-625:
-------------------------------------------

When the Plugins are installed within Eclipse the title bar actually shows 
connection context information in the window title, it is updated whenever 
another entry is opened. The following format is used:
  Perspective - Entry DN - Connection Name - Eclipse

However in the RCP application we only have the static title "Apache Directory 
Studio".

I figures out that in Eclipse the WorkbenchWindowsAdvisor implementation sets 
up some listeners that updates the title, see 
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ui.ide.application/src/org/eclipse/ui/internal/ide/application/IDEWorkbenchWindowAdvisor.java?view=markup

So I tried to adapt this class to our ApplicationWorkbenchWindowAdvisor, see 
the result in the attached image.

Any thoughts before I commit the change?
Is the order of the information (Perspective Name - Entry DN - Connection Name 
- Product Name) ok? At least it is the same order than in Eclipse.
On Windows and Linux that should be ok. But how does it look like on MacOS (I 
think there is no window title)? 


> Add Connection Context in the LDAP Browser Window
> -------------------------------------------------
>
>                 Key: DIRSTUDIO-625
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-625
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-ldapbrowser
>    Affects Versions: 1.5.2
>         Environment: Windows 32
>            Reporter: Jean-Marc
>
> When we navigate between multiple connections, we have to keep the connection 
> window opened to see in which we currently are in the LDAP Browser window. It 
> would be easier if the connection name appeared in the title window of the 
> LDAP Browser or in the root node

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to