{"action":"opened","issue":{"url":"https://api.github.com/repos/chloridite/OpenBoardView/issues/11","repository_url":"https://api.github.com/repos/chloridite/OpenBoardView","labels_url":"https://api.github.com/repos/chloridite/OpenBoardView/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/chloridite/OpenBoardView/issues/11/comments","events_url":"https://api.github.com/repos/chloridite/OpenBoardView/issues/11/events","html_url":"https://github.com/chloridite/OpenBoardView/issues/11","id":157661704,"number":11,"title":"Custom file format / wrapper.","user":{"login":"pafmaf","id":1395650,"avatar_url":"https://avatars.githubusercontent.com/u/1395650?v=3","gravatar_id":"","url":"https://api.github.com/users/pafmaf","html_url":"https://github.com/pafmaf","followers_url":"https://api.github.com/users/pafmaf/followers","following_url":"https://api.github.com/users/pafmaf/following{/other_user}","gists_url":"https://api.github.com/users/pafmaf/gists{/gist_id}","starred_url":"https://api.github.com/users/pafmaf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pafmaf/subscriptions","organizations_url":"https://api.github.com/users/pafmaf/orgs","repos_url":"https://api.github.com/users/pafmaf/repos","events_url":"https://api.github.com/users/pafmaf/events{/privacy}","received_events_url":"https://api.github.com/users/pafmaf/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-31T12:40:51Z","updated_at":"2016-05-31T12:40:51Z","closed_at":null,"body":"This is a suggestion / RFC thing.\r\n\r\nMost files I work with come as two distinct, weirdly named files, i.e. `<weird_name>.brd` layout and `<weird_name>.pdf` schematic.\r\n\r\nWhile working on the code I noticed I have no good way of storing annotations (e.g. component aliases) and when you want to find files quickly, it'd be cool to have more context/details on those files, like what product they possibly apply to.\r\n\r\nAnother thing is having background images for both sides, that's two more files for just one thing (unless you merge them etc.), so instead of having those simply in one folder I plan on implementing a 'custom file format' based on a zipped folder, something like: \r\n\r\n```\r\n<weird_name>.zip>\r\n| - ! board_info.json  # friendly name, model name, zip structure, other stuff\r\n| - thumbnail.jpg  # thumbnail for some explorer thing?\r\n| - annotations.json  # containing alias component names, highlights, text annotations\r\n| - favourites.json  # possibly a list of favourite nets, components?\r\n| - ! <weird_name>.(*.brd, *.bla)  # original board view file\r\n| - <weird_name>.pdf  # schematics PDF for possible integration later on (MuPDF?)\r\n| - hires_img/  \r\n  | - top.jpg\r\n  | - bottom.jpg\r\n``` \r\n\r\n(Elements with a `!` have to be present, the rest is optional.)\r\n\r\nSo it's a singe file containing all info, that may be hand-edited, customized and shared with collegues.\r\n\r\nAny ideas on this?"}}
{"actor":{"display_login":"pafmaf"}}