Details

      Description

      We should improve the layout of the "controls" widget. Right now it contains three controls (ManageDsaIT, Subentries, and PagedSearch). If we add more controls this widget could become too big.

      It is also implemented twice, once in the BrowserParameterPage and once in the SearchPageWrapper. It would be better to create a reusable widget.

      We also need a generic way to save controls and its options to the connections.xml and browserconnections.xml.

        Activity

        Hide
        Kasun Lakpriya added a comment -

        I would like to work on this issue. Can anyone, please, elaborate bit more on this so that I can start working on this.

        Show
        Kasun Lakpriya added a comment - I would like to work on this issue. Can anyone, please, elaborate bit more on this so that I can start working on this.
        Hide
        Stefan Seelmann added a comment -

        The controls I speak from are used for LDAP searches ([0] contains a list of controls supported by ApacheDS and/or Studio with links to RFC, just fyi). They can be defined at two levels:

        1st: At connection level in the connection properties [1] and wizard [2]. The controls that are set here are sent with each search request to the server while browsing the DIT. And (as far as I remember) they are used as default when creating a new search.

        2nd: At search level in the search dialog[3] and properties [4]. In that case the controls are sent only for the particular search.

        As you see the controls group looks very similar, but is implemented twice. I think a first step is to create a reusable widget that can be used in all four dialogs. In BrowserParameterPage and SearchPageWrapper we already use some custom widgets (LimitWidget, AliasesDereferencingWidget or ReferralsHandlingWidget), you can use them as templates.

        A special requirement is that the labels and tooltips are different in BrowserParameterPage and SearchPageWrapper. That is required because the controls may be used differently at connection or search level. For example the "subentries" control: If set only subentries are returned by a search, but no normal entries. When the checkbox is set at connection level we then do two searches, one without the control to get normal entries and one with the contol to get subentries. But when the checkbox is set at search level only one search request is performed and you either get normal entries only or subentries only.

        [0] http://directory.apache.org/apacheds/1.5/supported-ldap-controls-extended-operations-and-features.html

        [1]
        http://directory.apache.org/studio/static/users_guide/ldap_browser/tools_connection_properties.html
        http://directory.apache.org/studio/static/users_guide/ldap_browser/images/tools_connection_properties_3.png

        [2]
        http://directory.apache.org/studio/static/users_guide/ldap_browser/tools_newconnection_wizard.html
        http://directory.apache.org/studio/static/users_guide/ldap_browser/images/tools_newconnection_wizard_3.png

        [3]
        http://directory.apache.org/studio/static/users_guide/ldap_browser/tools_search_dialog.html
        http://directory.apache.org/studio/static/users_guide/ldap_browser/images/tools_search_dialog_1.png

        [4]
        http://directory.apache.org/studio/static/users_guide/ldap_browser/tools_search_properties.html

        Show
        Stefan Seelmann added a comment - The controls I speak from are used for LDAP searches ( [0] contains a list of controls supported by ApacheDS and/or Studio with links to RFC, just fyi). They can be defined at two levels: 1st: At connection level in the connection properties [1] and wizard [2] . The controls that are set here are sent with each search request to the server while browsing the DIT. And (as far as I remember) they are used as default when creating a new search. 2nd: At search level in the search dialog [3] and properties [4] . In that case the controls are sent only for the particular search. As you see the controls group looks very similar, but is implemented twice. I think a first step is to create a reusable widget that can be used in all four dialogs. In BrowserParameterPage and SearchPageWrapper we already use some custom widgets (LimitWidget, AliasesDereferencingWidget or ReferralsHandlingWidget), you can use them as templates. A special requirement is that the labels and tooltips are different in BrowserParameterPage and SearchPageWrapper. That is required because the controls may be used differently at connection or search level. For example the "subentries" control: If set only subentries are returned by a search, but no normal entries. When the checkbox is set at connection level we then do two searches, one without the control to get normal entries and one with the contol to get subentries. But when the checkbox is set at search level only one search request is performed and you either get normal entries only or subentries only. [0] http://directory.apache.org/apacheds/1.5/supported-ldap-controls-extended-operations-and-features.html [1] http://directory.apache.org/studio/static/users_guide/ldap_browser/tools_connection_properties.html http://directory.apache.org/studio/static/users_guide/ldap_browser/images/tools_connection_properties_3.png [2] http://directory.apache.org/studio/static/users_guide/ldap_browser/tools_newconnection_wizard.html http://directory.apache.org/studio/static/users_guide/ldap_browser/images/tools_newconnection_wizard_3.png [3] http://directory.apache.org/studio/static/users_guide/ldap_browser/tools_search_dialog.html http://directory.apache.org/studio/static/users_guide/ldap_browser/images/tools_search_dialog_1.png [4] http://directory.apache.org/studio/static/users_guide/ldap_browser/tools_search_properties.html

          People

          • Assignee:
            Unassigned
            Reporter:
            Stefan Seelmann
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development