{"action":"created","issue":{"url":"https://api.github.com/repos/LWJGL/lwjgl3/issues/67","labels_url":"https://api.github.com/repos/LWJGL/lwjgl3/issues/67/labels{/name}","comments_url":"https://api.github.com/repos/LWJGL/lwjgl3/issues/67/comments","events_url":"https://api.github.com/repos/LWJGL/lwjgl3/issues/67/events","html_url":"https://github.com/LWJGL/lwjgl3/issues/67","id":88904112,"number":67,"title":"Support Logger rather for debug log messages","user":{"login":"dannypurcell","id":3235832,"avatar_url":"https://avatars.githubusercontent.com/u/3235832?v=3","gravatar_id":"","url":"https://api.github.com/users/dannypurcell","html_url":"https://github.com/dannypurcell","followers_url":"https://api.github.com/users/dannypurcell/followers","following_url":"https://api.github.com/users/dannypurcell/following{/other_user}","gists_url":"https://api.github.com/users/dannypurcell/gists{/gist_id}","starred_url":"https://api.github.com/users/dannypurcell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dannypurcell/subscriptions","organizations_url":"https://api.github.com/users/dannypurcell/orgs","repos_url":"https://api.github.com/users/dannypurcell/repos","events_url":"https://api.github.com/users/dannypurcell/events{/privacy}","received_events_url":"https://api.github.com/users/dannypurcell/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/LWJGL/lwjgl3/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-06-17T03:57:40Z","updated_at":"2015-06-21T20:18:03Z","closed_at":null,"body":"I love the support for debugging in GLContext. The setupDebugMessageCallback() method is super convenient.\r\nWhile building up the debugging support in my own project I thought of something that would make the logging support even better.\r\nPlease consider adding a method that sends debug messages to a java.util.logging.Logger rather than a PrintStream. This would help lwjgl users easily tie GL debug messages in to application logs and enable the output during runtime.\r\n\r\nTo take this idea a bit further, the holy grail would be swapping in [slf4j](http://www.slf4j.org/) loggers for log output throughout the lwjgl library. That might take a bit more time to implement though so feel free to consider slf4j a low priority nice to have. \r\njava.util Loggers are already on hand and slf4j can remap their output so that might be the best option if adding the slf4j dependency is undesirable.\r\n\r\nThanks again for all the great work! The new version is looking really good!"},"comment":{"url":"https://api.github.com/repos/LWJGL/lwjgl3/issues/comments/113951418","html_url":"https://github.com/LWJGL/lwjgl3/issues/67#issuecomment-113951418","issue_url":"https://api.github.com/repos/LWJGL/lwjgl3/issues/67","id":113951418,"user":{"login":"httpdigest","id":7488613,"avatar_url":"https://avatars.githubusercontent.com/u/7488613?v=3","gravatar_id":"","url":"https://api.github.com/users/httpdigest","html_url":"https://github.com/httpdigest","followers_url":"https://api.github.com/users/httpdigest/followers","following_url":"https://api.github.com/users/httpdigest/following{/other_user}","gists_url":"https://api.github.com/users/httpdigest/gists{/gist_id}","starred_url":"https://api.github.com/users/httpdigest/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/httpdigest/subscriptions","organizations_url":"https://api.github.com/users/httpdigest/orgs","repos_url":"https://api.github.com/users/httpdigest/repos","events_url":"https://api.github.com/users/httpdigest/events{/privacy}","received_events_url":"https://api.github.com/users/httpdigest/received_events","type":"User","site_admin":false},"created_at":"2015-06-21T20:18:03Z","updated_at":"2015-06-21T20:18:03Z","body":"Personally, I would like to have more control over the formatting of the generated messages.\r\nAnd this would usually be done with a common callback interface that the user can set.\r\nHaving had a look into the relevant code in LWJGL 3 the problem seems, though, that the callback interface and the actual formatting of the messages are intertwined because both depend on the underlying native extension/GL core function being used, which have differing signatures and provided information.\r\nThe only thing I can think of right now is a common interface which is the union of the information provided by all different underlying callbacks.\r\nThis way the user can adapt any logging library he/she wants to use, without introducing a dependency into LWJGL 3."}}