[jira] Commented: (DIRSTUDIO-180) Connection wizard and properties tabs are out of order

["Stefan Seelmann (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524324 ] 

Stefan Seelmann commented on DIRSTUDIO-180:
-------------------------------------------

Thanks Chris, for this catch.

With the new connection plugin I splitted the connection pages. The two pages "Network paramter" and "Authentication" were moved to the connection plugin, however the "Browser options" page is still located in the browser plugin. At runtime they are loaded using the Eclipse extension mechanism. 

I haven't added any order to these pages, because the browser plugin depens on the connection plugin, so the connection plugin is loaded first. I didn't run into that problem and I thought that the connection pages are loaded in the same order as the plugins.


> Connection wizard and properties tabs are out of order
> ------------------------------------------------------
>
>                 Key: DIRSTUDIO-180
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-180
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-connection
>    Affects Versions: 1.0.0
>         Environment: Fedora Core 6 Linux, JDK
>            Reporter: Chris Custine
>         Attachments: New LDAP Connection1.png, Screenshot-New LDAP Connection 2.png, Screenshot-New LDAP Connection 3.png, Screenshot-Properties.png
>
>
> When I installed Studio on my Linux system, it appears as if the connection wizard and properties editor tabs are out of order.  When you click on "New Connection..." the first thing you see is Browser Options and all buttons are disabled.  If you unselect "Get Base DN from root DSE" you can go then click the "next" button and configure the network parameters.  
> If you edit properties of an existing connection the editor tabs are in the same order.
> I will attach screenshots to demonstrate.  I also tried the same thing on Windows which appears to have normal behavior.

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