plugin API

[karolherbst]

It would be nice to have a plugin API for desurium.

There are two ways we could use them

1. make calls from games to desurium

• getting account information (accountname, avatar, email)
• using the desurium chat (see #156)
• implement drm stuff needed for some windows game
• steam like gameoverlay

  2. extend desurium

• platform specific autoupdater/update checker
• populate stuff into the gameoverlay (media player, browser, social media, ...)

I've created a little flowchart to demonstrate the drm mechanism + adding some license information (see also #509) about the specific parts here: https://dl.dropboxusercontent.com/u/19446730/plugin.png

little explanation: all stuff we don't want to protect (some basic code snippets) or stuff that have to be used through prop. binaries should be licensed under LGPL, everything else have to stay GPL. I was thinking about moving util, util_fs, util_thread, ipc_pipe and managers LGPL (they have to be ported to shared libs then).

EDIT: I know that some might be worried about privacy. There should be a mechanism to allow access to specific data and should be disallowed by default.

[karolherbst]

@Cheeseness mentioned we should avoid relicense at all and do everything over IPC.

That would mean (as long as everything stays GPL) we have to develop everything on the game side from scratch. That would include IPC connection handling (done in ipc_pipe), GUI components (done in wx_controls), thread handling (done in threads), fs access (done in util_fs) and path fetching and some other stuff (done in util).

We don't need to write most of this new. It could be enough to just relicense ipc_pipe under LGPL and do everything over IPC.

[karolherbst]

The problem with a overlay library is, that we would need a 32bit version on 64bit systems. Because I don't want to build dependencies for both architectures, I am thinking about to write the overlay against low level APIs directly like xcb and pthread.