2015-05-08, 17:14
(2015-05-08, 17:11)ironic_monkey Wrote: it's just gonna be a hassle on your end (having to rebase the pr's now and then) i'll be lenient and cherry-pick whenever possible.
yes, merging becomes a real hassle. i need my stuff on top, if not every conflict ends up in a merge commit and not the original commit.
i'll gladly carry logging stuff as well - it will be a great improvement. i'm not very interested in headless as i don't think i like the approach rather i think kodi should be split into modules/libraries, then those are reused in a separate binary.
i saw some fixes on the vis api in your branch, those i am very interested in, that thing is a mess.
Cool, I'll try to do a logging pr/branch and the vis api too. In my current approach with the vis api I just put locking (and moved start to audio thread), but I'm contemplating moving it so that all calls are on main thread, then fishbmc wouldn't need changes
EDIT: Yeah I'm not overly fond of the approach either with headless, It was a minimal effort to get it working I'd much prefer it as you say