{"action":"created","issue":{"url":"https://api.github.com/repos/jodersky/vfd/issues/8","labels_url":"https://api.github.com/repos/jodersky/vfd/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/jodersky/vfd/issues/8/comments","events_url":"https://api.github.com/repos/jodersky/vfd/issues/8/events","html_url":"https://github.com/jodersky/vfd/issues/8","id":64125193,"number":8,"title":"Redesign Cockpit Layout (RFC)","user":{"login":"jodersky","id":1007012,"avatar_url":"https://avatars.githubusercontent.com/u/1007012?v=3","gravatar_id":"","url":"https://api.github.com/users/jodersky","html_url":"https://github.com/jodersky","followers_url":"https://api.github.com/users/jodersky/followers","following_url":"https://api.github.com/users/jodersky/following{/other_user}","gists_url":"https://api.github.com/users/jodersky/gists{/gist_id}","starred_url":"https://api.github.com/users/jodersky/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jodersky/subscriptions","organizations_url":"https://api.github.com/users/jodersky/orgs","repos_url":"https://api.github.com/users/jodersky/repos","events_url":"https://api.github.com/users/jodersky/events{/privacy}","received_events_url":"https://api.github.com/users/jodersky/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jodersky/vfd/labels/ui","name":"ui","color":"006b75"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-24T23:19:10Z","updated_at":"2015-03-25T07:44:17Z","closed_at":null,"body":"## Problem\r\nThe current UI positioning is the result of a quick and dirty implementation. It would be great to implement a design that is both\r\n 1. well structured\r\n 2. keeps a certain degree of flexibility to accomodate user preferences\r\n\r\n## Idea\r\nMy initial idea addressing this issue is to reposition elements into a region-based layout according the following image:\r\n![design](https://cloud.githubusercontent.com/assets/1007012/6814551/e6c35cac-d27f-11e4-9800-6c18452cf66e.png)\r\nInitially, the \"Normal View\" is shown, i.e. the main cockpit with all instruments and video feed. A second layout, the \"Detailed View\" can be brought up to access some detailed settings or views. In this way the main panel is always visible to the user.\r\n\r\nFurthermore, to accomodate users' preferences, they should be able to reposition individual instruments into the different region. I.e. a user may chose to move the communication panel from the right to the left or to completely hide the video feed.\r\n\r\n## Implementation\r\nBeing no expert in web-design, two solutions come into my mind:\r\n 1. Using the standard bootstrap grid layout\r\n 2. Using flexboxes\r\nSince the cockpit differs from most webapps in that it has a height constraint of 100%, using the bootstrap grid system feels clunky. I find the second solution is the most modern and elegant way to handle such a layout.\r\n\r\n## Request For Comments\r\nThis is a just a first idea and in no way definite. Any comments on the design or implementation ideas? @lbarman?"},"comment":{"url":"https://api.github.com/repos/jodersky/vfd/issues/comments/85902594","html_url":"https://github.com/jodersky/vfd/issues/8#issuecomment-85902594","issue_url":"https://api.github.com/repos/jodersky/vfd/issues/8","id":85902594,"user":{"login":"chernetsov","id":917270,"avatar_url":"https://avatars.githubusercontent.com/u/917270?v=3","gravatar_id":"","url":"https://api.github.com/users/chernetsov","html_url":"https://github.com/chernetsov","followers_url":"https://api.github.com/users/chernetsov/followers","following_url":"https://api.github.com/users/chernetsov/following{/other_user}","gists_url":"https://api.github.com/users/chernetsov/gists{/gist_id}","starred_url":"https://api.github.com/users/chernetsov/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chernetsov/subscriptions","organizations_url":"https://api.github.com/users/chernetsov/orgs","repos_url":"https://api.github.com/users/chernetsov/repos","events_url":"https://api.github.com/users/chernetsov/events{/privacy}","received_events_url":"https://api.github.com/users/chernetsov/received_events","type":"User","site_admin":false},"created_at":"2015-03-25T07:44:17Z","updated_at":"2015-03-25T07:44:17Z","body":"Folks,\r\n\r\ngreat starting point!\r\n\r\nmy 50 cents:\r\n\r\nI've already had a chance to play with non-web tools like qgroundcontrol & apm planner and they all look like the tools that at some point got overwhelmed with features in uncontrolled way and hense started to look clunky and ugly.\r\n\r\nI suggest that now it's a good moment to figure out the top priority use cases we want to use the tool for and build UIs based on that. How do you plan to use the tool?\r\n\r\nYour thoughts."}}