You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Nubsis <nu...@gm...> - 2011-04-21 12:31:49
|
Hey guys, If we were to implement custom protocol links like described in http://www.openlierox.net/forum/index.php/topic,13282.msg226448.html#msg226448 what in detail would we need to check off? I'm currently studying the code and trying to think of where to start coding. Here are some things from the top of my head: * Create a protocol handler (Design might depend on other components) * Register the protocol handler for different systems ** Various Linux variants ** Windows (Requires rights) ** Mac ** ... Others? * Keep track of which OLX instance should be adressed. * Enable message sending to OLX client (d-bus style?) ** Specifically - tell client to join server or initiate a download. * Possibly pass parameters to OLX. If OLX is instantiated, the message is passed to the active instance. ** Pre-load state determines whether or not to start a new instance of OLX or to send message to an existing one. * Make sure the message is sent to the correct instance (possibly limit instances to one) ** Limiting could for instance be done by attempting to bind a socket to a specific port. While this may be a cross platform solution, it still has some problems and there surely are cleaner solutions for that, which may be platform specific. ** Other solutions that may be platform specific. * Possibly separate some application components ** When a client receives the "join game" message, the user should be prompted whether or not he wants to join it. Once the user chooses profile and chooses to proceed, the "connect to game" process should start regardless of the state of the application. In any menu, in game or even if the client is not yet instantiated. Depending on the state, different resources may need to be loaded. If the application is not instantiated, naturally more (all) resources would need to be loaded, but the user should not need to navigate through any menus to start the game. Once the user leaves the server, he is returned to the network menu and is then free to continue playing or shutting the client down. ** When a client receives the "download content" link, the user will be prompted whether or not he wants to download and install it. Once the user chooses to do so, the content will be downloaded by the downloader that is already implemented. It should also be separated so that it can be invoked if OLX is not already running. In that case, OLX won't need to be instantiated, but the content is silently installed. Nubsis |