(09-16-2016, 08:41 PM)Durandle Wrote: "If you are going to make a GUI especially for Dolphin, then embedding it inside Dolphin itself is the way to go."
This seems the opposite of best-practice design/programming. Making it easy for 3rd party UIs to hook into Dolphin, then writing a default big-picture UI that uses it, seems like the best bet.
Not inside Dolphin's source code, but the GUI code need to be embedded into the same processes as Dolphin, somehow. Some kind of scripting interface, or dll loading.
There are basically two options:
A) Dolphin is built as a dll and embedded into a program that does the GUI. This is how RetroArch and friends work, but dolphin is currently incompatible with this technique.
B) The GUI is built as a dll (or a script) and embedded into dolphin. This is how things like the steam overlay are usually implemented.
Personally, I'm in favor of a scripting interface that is powerful enough to partially or fully replace the default Dolphin GUI.