601
edits
FGCom-mumble: Difference between revisions
Jump to navigation
Jump to search
m
→Idea to integrate into FGFS
| Line 155: | Line 155: | ||
== Idea to integrate into FGFS == | == Idea to integrate into FGFS == | ||
{{progressbar|10|10}} {{pending}} | {{progressbar|10|10}} {{pending}} | ||
ML Discussion: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1919A28D-44D8-46F0-8A65-A5633A8AB743%40hallinger.org/#msg58717212 | |||
Using [https://github.com/mumble-voip/libmumble libmumble], a standalone mumble c++17 library, we could integrate FGCom-mumble directly into FlightGear. This way, FGFS would talk "mumble" to a mumble server and the plugins functions would be integrated into the core. For pilots, a simple "click" to connect in the multiplayer would be enough to participate, while having all the advanced features of fgcom-mumble available (like custom NDBs, radio stations; as well as the possibility for other clients (ATC!) to participate easily on the radio spectrum). | Using [https://github.com/mumble-voip/libmumble libmumble], a standalone mumble c++17 library, we could integrate FGCom-mumble directly into FlightGear. This way, FGFS would talk "mumble" to a mumble server and the plugins functions would be integrated into the core. For pilots, a simple "click" to connect in the multiplayer would be enough to participate, while having all the advanced features of fgcom-mumble available (like custom NDBs, radio stations; as well as the possibility for other clients (ATC!) to participate easily on the radio spectrum). | ||
A main idea is also to use the existing fgcom-mumble code to avoid double work. But otoh maybe a direct rewrite of the core stuff may be cleaner; most of the magic is in the fgcom-mumble radio model code anyway, so we might just use some bits, if that is possible? | |||
libmubmble is not yet API-stable, but there was already a [https://github.com/mumble-voip/libmumble/issues/18 first dicussion] about feasability and basic mechanics: | libmubmble is not yet API-stable, but there was already a [https://github.com/mumble-voip/libmumble/issues/18 first dicussion] about feasability and basic mechanics: | ||
| Line 174: | Line 178: | ||
*** {{tick}} And what about libmubmles dependencies, like OpenSSL? | *** {{tick}} And what about libmubmles dependencies, like OpenSSL? | ||
*** technically, how to include that all into the existing build system? | *** technically, how to include that all into the existing build system? | ||