Implement next_step for web session about webgamelauncher HOT 8 OPEN

A quick look at a few plugins it appears that the Amazon one has a pretty simple next_setup but should be really looked into.

from webgamelauncher.

A new connection to the Amazon plugin from galaxy.
plugin-amazon-c2cd2e29-8b02-35a9-86fc-3faf90255857.log

from webgamelauncher.

Comparing with the amazon plugin, the launcher would need to watch requested urls and if they match end_uri_regex "end_uri_regex": ".*splash_continue.*" then it should return with that matching url in the next command, #33 . So this will also need to be parsed.

from webgamelauncher.

Any file paths, as in the examples above, would need to be served via the server for the client to have access to links from the current design. Not all work this way and directly pull from remote web pages. Another option is to have a local file that users open that loads up everything via javascript from the server endpoint.

from webgamelauncher.

Getting the final url will be a challenge since it will be considered cross site scripting by browsers. It may require a custom browser for this function and may not be super helpful for integration tests. In the short term getting the values for the next function would probably be easiest to get from galaxy's databases. C:\ProgramData\GOG.com\Galaxy\storage\plugins The data appears to be just base64 encoded.

from webgamelauncher.

May want to look into using selenium for this functionality to allow for plugin developers to create automated tests for validating these.

from webgamelauncher.

For opening the test code in development you can use the fo0llowing command to start it up.
java -cp target/webGameLauncher-0.0.1-SNAPSHOT-jar-with-dependencies.jar LocalClient.MainLocalClient

from webgamelauncher.

Currently not parsing all options passed in just what appear to be the minimum ones required.

from webgamelauncher.