{"action":"created","issue":{"url":"https://api.github.com/repos/vurtun/nuklear/issues/117","repository_url":"https://api.github.com/repos/vurtun/nuklear","labels_url":"https://api.github.com/repos/vurtun/nuklear/issues/117/labels{/name}","comments_url":"https://api.github.com/repos/vurtun/nuklear/issues/117/comments","events_url":"https://api.github.com/repos/vurtun/nuklear/issues/117/events","html_url":"https://github.com/vurtun/nuklear/issues/117","id":152020318,"number":117,"title":"Split to multiple headers for development","user":{"login":"jimon","id":1333661,"avatar_url":"https://avatars.githubusercontent.com/u/1333661?v=3","gravatar_id":"","url":"https://api.github.com/users/jimon","html_url":"https://github.com/jimon","followers_url":"https://api.github.com/users/jimon/followers","following_url":"https://api.github.com/users/jimon/following{/other_user}","gists_url":"https://api.github.com/users/jimon/gists{/gist_id}","starred_url":"https://api.github.com/users/jimon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jimon/subscriptions","organizations_url":"https://api.github.com/users/jimon/orgs","repos_url":"https://api.github.com/users/jimon/repos","events_url":"https://api.github.com/users/jimon/events{/privacy}","received_events_url":"https://api.github.com/users/jimon/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/vurtun/nuklear/labels/discussion","name":"discussion","color":"0052cc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-04-30T09:38:11Z","updated_at":"2016-05-02T08:54:33Z","closed_at":null,"body":"I think that having one header deployment is the best way to ship C/C++ libraries (aka [stb](https://github.com/nothings/stb) way), but it makes development a bit clumsy in a way. In my case I would like to contribute to the library, but having 15kloc file is just too bulky to work on and takes time to figure out the mental model behind the code. In some other projects like [tigr](https://bitbucket.org/rmitton/tigr/src) and [buildfox](https://github.com/beardsvibe/buildfox) they have source as separate files which gets amalgamated into final files in the end.\r\n\r\nWould be nice to have nuklear source divided across multiple files just for sake of making development a bit easier."},"comment":{"url":"https://api.github.com/repos/vurtun/nuklear/issues/comments/216154047","html_url":"https://github.com/vurtun/nuklear/issues/117#issuecomment-216154047","issue_url":"https://api.github.com/repos/vurtun/nuklear/issues/117","id":216154047,"user":{"login":"jimon","id":1333661,"avatar_url":"https://avatars.githubusercontent.com/u/1333661?v=3","gravatar_id":"","url":"https://api.github.com/users/jimon","html_url":"https://github.com/jimon","followers_url":"https://api.github.com/users/jimon/followers","following_url":"https://api.github.com/users/jimon/following{/other_user}","gists_url":"https://api.github.com/users/jimon/gists{/gist_id}","starred_url":"https://api.github.com/users/jimon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jimon/subscriptions","organizations_url":"https://api.github.com/users/jimon/orgs","repos_url":"https://api.github.com/users/jimon/repos","events_url":"https://api.github.com/users/jimon/events{/privacy}","received_events_url":"https://api.github.com/users/jimon/received_events","type":"User","site_admin":false},"created_at":"2016-05-02T08:54:33Z","updated_at":"2016-05-02T08:54:33Z","body":"@vurtun I think as a library user I really appreciate having one header, and as a library developer, well, not really. The point is not recompilation experience or anything, but actual library development experience. In current form the library is not so easy to contribute/modify.\r\n\r\nMaybe the problem I'm facing is not one/2+ files, but contribution/improvement itselfююю To understand current code layout I need to use editors with aggressive code folding, and it still takes time to build mental model.\r\n\r\nProbably this could be improved if we make some sort of more generic code overview (diagrams or something) about library internals?"}}