{"action":"opened","issue":{"url":"https://api.github.com/repos/ISISComputingGroup/IBEX/issues/1347","repository_url":"https://api.github.com/repos/ISISComputingGroup/IBEX","labels_url":"https://api.github.com/repos/ISISComputingGroup/IBEX/issues/1347/labels{/name}","comments_url":"https://api.github.com/repos/ISISComputingGroup/IBEX/issues/1347/comments","events_url":"https://api.github.com/repos/ISISComputingGroup/IBEX/issues/1347/events","html_url":"https://github.com/ISISComputingGroup/IBEX/issues/1347","id":163115410,"number":1347,"title":"IBEX: \"Edit/New Configuration\" window enhancements ","user":{"login":"ThomasLohnert","id":18398579,"avatar_url":"https://avatars.githubusercontent.com/u/18398579?v=3","gravatar_id":"","url":"https://api.github.com/users/ThomasLohnert","html_url":"https://github.com/ThomasLohnert","followers_url":"https://api.github.com/users/ThomasLohnert/followers","following_url":"https://api.github.com/users/ThomasLohnert/following{/other_user}","gists_url":"https://api.github.com/users/ThomasLohnert/gists{/gist_id}","starred_url":"https://api.github.com/users/ThomasLohnert/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ThomasLohnert/subscriptions","organizations_url":"https://api.github.com/users/ThomasLohnert/orgs","repos_url":"https://api.github.com/users/ThomasLohnert/repos","events_url":"https://api.github.com/users/ThomasLohnert/events{/privacy}","received_events_url":"https://api.github.com/users/ThomasLohnert/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ISISComputingGroup/IBEX/labels/question","name":"question","color":"cc317c"},{"url":"https://api.github.com/repos/ISISComputingGroup/IBEX/labels/story","name":"story","color":"4ddbff"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-06-30T08:59:22Z","updated_at":"2016-06-30T08:59:22Z","closed_at":null,"body":"Following feedback from one of the scientists during sprint review a while back, I have been looking at the \"edit configuration window\" and ways to make the process of creating/editing a new configuration more intuitive and user friendly. While looking into this I have also come up with some additional proposed changes to the window, which can be found at the bottom of this page.\r\n\r\nSpecifically, the scientist was confused as to how to actually create a new configuration, which stemmed from the \"Description\" and \"Name\" fields, which are required to save a config, being somewhat 'hidden away' in the summary tab.\r\n\r\nTo address this issue, I have created the following 3 mockups, ordered from less to more radical in the changes they introduce.\r\n\r\nV1\r\n![edit_config_mockup1_small](https://cloud.githubusercontent.com/assets/18398579/16481258/3aa5e418-3ea2-11e6-9656-5f03c1d1df5e.png)\r\nIn this variant, I address the issue by simply moving the summary tab to the front so it is the first thing the user sees when opening the window.\r\n\r\nV2\r\n![edit_config_mockup2_small](https://cloud.githubusercontent.com/assets/18398579/16481373/df71ce94-3ea2-11e6-8aab-b5d1f4a87240.png)\r\nIn this variant, the \"Summary\" tab is essentially separated out from the tabbed pane, which provides the user with a sort of reference point across all tabs. (E.g. in the current version it is not easy to see which config it is you are actually currently editing.)\r\n\r\nV3\r\n![edit_config_mockup3_small](https://cloud.githubusercontent.com/assets/18398579/16482029/fdbc5ca4-3ea5-11e6-8c31-abcd55e9a6bf.png)\r\nThis variant is following an idea John had, the part of note here is the tree structure on the left. This provides the user with a full map of the configuration and should eliminate a lot of tab switching.\r\n\r\nFurthermore, I propose the following additional design changes to the window:\r\n- I understand the tabs are in order of the steps one would typically take to create a configuration (almost like a wizard). As such, would it not make sense to add components first as this will already add some fixed IOCs, Blocks, Groups?\r\n- Currently, to edit IOC macros / PV values / PV sets one has to switch to the relevant tab and selecting the relevant IOC from a drop down menu, which seems slightly awkward. I propose that they instead can be edited directly from the list of blocks, see the screenshot of V2. I am not completely sure if that makes sense with the workflow of editing configs, so feel free to tell me if this idea is rubbish. In V3 this is taken care of by having those settings in each IOCs tree structure.\r\n- Messages of errors which prevent the user from saving changes are currently displayed on top of the window. I propose to move to them next to the save buttons at the bottom to make it easier for the user to establish a connection between the two. (See screenshot of V1)\r\n\r\nOpen to discussion!"}}
{"actor":{"display_login":"ThomasLohnert"}}