Hi Jerad, Thanks for the feedback. Please find my responses inline. On Tue, Sep 6, 2016 at 10:28 AM, Jerad Rutnam <[email protected]> wrote:
> Hi Chamalee, > > Why do we have a checkbox in the beginning of the row? IMO I think having > 2 checkboxes in the same row in 2 different places will confuse the user. > In a table row, the first checkbox is to select the gateways where the API to be Published. And the checkbox that I have newly added (Use Defaults) is to select to get the Gateway URLs from the environment configuration. So they are for two different purposes. > And you can use bootstrap text input grouping [1] to have "http://"; & > "https://"; texts. > I will use this. It looks much better. > And is there any reason we are not giving enabling/disabling transport > type inline within the table? So user don't have to go back to > configuration section again if he/she wants to enable it. > What I understand from this comment is as following. Please correct me if I am Wrong. As an example in a situation where only *http* is enabled for Transports in the Configuration section of "Manage" page, - if a user unchecked the Use Defaults, both the *http* and *https* text boxes get enabled. - At that time the http and https checkboxes in the configuration section (transports) will be checked. - if that URL text boxes are enabled and if user save and Publish the API, the URLs for both http and https will be displayed in the store taking from the environment configuration or from the user input. But the problem here is, - In API Manager we are providing the facility to the user to restrict transports. - If a user want to restrict one transport (assume http), then since he want to add a custom URL with the other transport protocol (https), he will not get the chance to restrict the required transport. So we have to give the chance for the user to enable and disable transports independent from the selections of this table. > And if user adds an URL, we can validate and change the styling of the > text input using bootstrap input validation styling [2]. And along with the > input fields we can have the "Use Default" checkbox as it is now. And if > it's checked we can disable the input fields. > Great. I will use this. > > Also if we are forcing an URL when the text input field is blank, better > we indicate that to the user. Maybe we can use an icon with a tooltip to > indicate user that it will load the default url from API Manager > Configuration. > It is not a must to add the URL and the user can keep it blank so that the default URL will be added. Yes I wll try with adding a tooltip like what you mentioned without blocking the user to go further. > > [1] - http://getbootstrap.com/components/#input-groups-basic > [2] - http://getbootstrap.com/css/#forms-control-validation > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
