{"action":"created","issue":{"url":"https://api.github.com/repos/IMA-WorldHealth/bhima-2.X/issues/270","repository_url":"https://api.github.com/repos/IMA-WorldHealth/bhima-2.X","labels_url":"https://api.github.com/repos/IMA-WorldHealth/bhima-2.X/issues/270/labels{/name}","comments_url":"https://api.github.com/repos/IMA-WorldHealth/bhima-2.X/issues/270/comments","events_url":"https://api.github.com/repos/IMA-WorldHealth/bhima-2.X/issues/270/events","html_url":"https://github.com/IMA-WorldHealth/bhima-2.X/issues/270","id":145992054,"number":270,"title":"(Proposal) Configuration Page Structure","user":{"login":"sfount","id":2844572,"avatar_url":"https://avatars.githubusercontent.com/u/2844572?v=3","gravatar_id":"","url":"https://api.github.com/users/sfount","html_url":"https://github.com/sfount","followers_url":"https://api.github.com/users/sfount/followers","following_url":"https://api.github.com/users/sfount/following{/other_user}","gists_url":"https://api.github.com/users/sfount/gists{/gist_id}","starred_url":"https://api.github.com/users/sfount/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sfount/subscriptions","organizations_url":"https://api.github.com/users/sfount/orgs","repos_url":"https://api.github.com/users/sfount/repos","events_url":"https://api.github.com/users/sfount/events{/privacy}","received_events_url":"https://api.github.com/users/sfount/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/IMA-WorldHealth/bhima-2.X/labels/design","name":"design","color":"f7c6c7"},{"url":"https://api.github.com/repos/IMA-WorldHealth/bhima-2.X/labels/needs%20discussion","name":"needs discussion","color":"eb6420"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-04-05T13:38:50Z","updated_at":"2016-04-13T15:05:36Z","closed_at":null,"body":"This is a generic proposal for how we structure configuration (management) pages. Currently we use a mixture of UI Grids and HTML tables, using a 2 column structure listing the entity on the left and allowing CRUD operations on the right. \r\n\r\n![Configuration Page](http://i.imgur.com/NFtPNer.jpg)\r\n\r\nThis proposal aims to improve on this in the following ways: \r\n* Allow much richer information to be displayed along with each entity. Displaying the entity in a 'card' allows more information than a single line a row of a table - management pages should never contain thousands of entries so this should not become overwhelming. \r\n* List structure can be sorted by various attributes \r\n* Pagination allows the page to never become overly large - this is something that hasn't been implemented in any of the current pages\r\n* Makes use of the latest state based routing as introduced https://github.com/IMA-WorldHealth/bhima-2.X/pull/225\r\n\r\n![Edit/ Create Page](http://i.imgur.com/Yqgemqu.jpg)\r\nThis is the modules create/update state, it provides a link back to the main list and allows the user to change the entities value - it could also provide additional information about the entity (when and where it is being used, how often, etc.)\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/IMA-WorldHealth/bhima-2.X/issues/comments/209497254","html_url":"https://github.com/IMA-WorldHealth/bhima-2.X/issues/270#issuecomment-209497254","issue_url":"https://api.github.com/repos/IMA-WorldHealth/bhima-2.X/issues/270","id":209497254,"user":{"login":"sfount","id":2844572,"avatar_url":"https://avatars.githubusercontent.com/u/2844572?v=3","gravatar_id":"","url":"https://api.github.com/users/sfount","html_url":"https://github.com/sfount","followers_url":"https://api.github.com/users/sfount/followers","following_url":"https://api.github.com/users/sfount/following{/other_user}","gists_url":"https://api.github.com/users/sfount/gists{/gist_id}","starred_url":"https://api.github.com/users/sfount/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sfount/subscriptions","organizations_url":"https://api.github.com/users/sfount/orgs","repos_url":"https://api.github.com/users/sfount/repos","events_url":"https://api.github.com/users/sfount/events{/privacy}","received_events_url":"https://api.github.com/users/sfount/received_events","type":"User","site_admin":false},"created_at":"2016-04-13T15:05:36Z","updated_at":"2016-04-13T15:05:36Z","body":"I agree - I think because each entity would be so different for now it will be sufficient to just use a template, each module will define it's own template for how the card will look which will just be regular Angular markup. \r\n\r\nDo you know of anything the card component would do specifically? If not I would just have each module specify a template for the list component to use when doing  `ng-repeat` on the data."}}