{"action":"created","issue":{"url":"https://api.github.com/repos/shroffk/phoebus/issues/22","repository_url":"https://api.github.com/repos/shroffk/phoebus","labels_url":"https://api.github.com/repos/shroffk/phoebus/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/shroffk/phoebus/issues/22/comments","events_url":"https://api.github.com/repos/shroffk/phoebus/issues/22/events","html_url":"https://github.com/shroffk/phoebus/issues/22","id":255608939,"number":22,"title":"Managing the migration from cs-studio to phoebus","user":{"login":"shroffk","id":2111304,"avatar_url":"https://avatars0.githubusercontent.com/u/2111304?v=4","gravatar_id":"","url":"https://api.github.com/users/shroffk","html_url":"https://github.com/shroffk","followers_url":"https://api.github.com/users/shroffk/followers","following_url":"https://api.github.com/users/shroffk/following{/other_user}","gists_url":"https://api.github.com/users/shroffk/gists{/gist_id}","starred_url":"https://api.github.com/users/shroffk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shroffk/subscriptions","organizations_url":"https://api.github.com/users/shroffk/orgs","repos_url":"https://api.github.com/users/shroffk/repos","events_url":"https://api.github.com/users/shroffk/events{/privacy}","received_events_url":"https://api.github.com/users/shroffk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-09-06T13:44:17Z","updated_at":"2017-09-07T14:13:22Z","closed_at":null,"author_association":"OWNER","body":"Create a list of requirements for the transition from cs-studio to phoebus.\r\n\r\nTechnical Issues\r\n\r\n - [ ] the reusing of the same application con figuration files\r\n - [ ] transition from BOY to Display Builder (more below)\r\n - [ ] handling of saved layouts in Phoebus (more below)\r\n\r\nUser Experience/Branding issues\r\n\r\n\r\n@willrogers @kasemir @claudio-rosati \r\n"},"comment":{"url":"https://api.github.com/repos/shroffk/phoebus/issues/comments/327812153","html_url":"https://github.com/shroffk/phoebus/issues/22#issuecomment-327812153","issue_url":"https://api.github.com/repos/shroffk/phoebus/issues/22","id":327812153,"user":{"login":"kasemir","id":1932421,"avatar_url":"https://avatars1.githubusercontent.com/u/1932421?v=4","gravatar_id":"","url":"https://api.github.com/users/kasemir","html_url":"https://github.com/kasemir","followers_url":"https://api.github.com/users/kasemir/followers","following_url":"https://api.github.com/users/kasemir/following{/other_user}","gists_url":"https://api.github.com/users/kasemir/gists{/gist_id}","starred_url":"https://api.github.com/users/kasemir/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kasemir/subscriptions","organizations_url":"https://api.github.com/users/kasemir/orgs","repos_url":"https://api.github.com/users/kasemir/repos","events_url":"https://api.github.com/users/kasemir/events{/privacy}","received_events_url":"https://api.github.com/users/kasemir/received_events","type":"User","site_admin":false},"created_at":"2017-09-07T14:13:22Z","updated_at":"2017-09-07T14:13:22Z","author_association":"COLLABORATOR","body":"Regarding configuration files:\r\n\r\nApplication files for Display Builder, PV Table, ... are exactly the same.\r\n\r\nPreferences are different: plugin_customization.ini and external, maybe auto-created diirt config files are replaced by, for now, the XML format used by java.util.prefs.Preferences's `exportSubtree`. We might eventually use our own PreferencesFactory, see #4.\r\n\r\nLayouts: We thought about a 'memento' type mechanism to persist and restore state. The framework would handle persisting and restoring the windows, tabs, inputs-to-tabs, and each application can then store additional information (like PV Tree could store the PV). This would allow the original Eclipse restart-as-you-left-it behavior as well as start-in-a-known-layout behavior (by basically making the desired state read-only, so it's not overwritten on shutdown).\r\nThere have been no discussions about switching layouts at runtime similar to perspectives.\r\nThat would be a new issue for discussion: Does anybody need to switch between layouts? Do the hidden panels remain in memory, as in Eclipse, or should they close down and then restart when re-opened?\r\n"}}
{"actor":{"display_login":"kasemir"}}