-
Notifications
You must be signed in to change notification settings - Fork 259
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some feedback on the customizing input options page
|
||
|
||
## Customising the Player Webpage | ||
The Pixel Streaming Signaling and Web Server provides a sample player page that is already set up to stream in media from your Unreal Engine application and to send mouse, keyboard, and touch events back to the application. You can use this default player page as-is, if it meets your needs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signaling
to
Signalling
not sure why, but convention throughout source and docs is two l's
For example, if you save a file to `Engine/Source/Programs/PixelStreaming/WebServers/SignallingWebServer/myfolder/myplayerpage.html`, and you set the `HomepageFile` parameter to `myfolder/myplayerpage.html`, the page would be accessible without needing to provide a file name in the URL: `http://127.0.0.1/`. | ||
* You can create a new implementation page and place it in [`/Frontend/implementations/EpicGames/src/`](/Frontend/implementations/EpicGames/src) alongside the sample implementations. This must consist of both a base `.html` page and the `.ts` source for your application's entrypoint. This will then be accessible by appending the name of the `html` file to IP address or hostname of the computer running the Signalling Server. | ||
For example, the sample `stresstest` page can be accessed on a locally-running infrastructure at `http:/127.0.0.1/stresstest.html`. | ||
* You can customize the `HomepageFile` parameter for the Signaling and Web Server, and set the path to the filename of your custom HTML player page relative to the [Frontend implementations source folder](/Frontend/implementations/src). It will then be accessible when you access the IP address or hostname of the computer running the Signaling and Web Server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signaling
to
Signalling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good docs writing. Made some minor suggestions.
Signed-off-by: Luke Bermingham <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made the small changes myself. Approved.
* Downgrade ts-jest and jest to support older Node version (#168) * Downgrade ts-jest and jest to support older Node version * bumbed ts-jest to 27.1.5 (latest 27.x.y) * Bump lib-pixelstreamingfrontend to 0.3.0 Signed-off-by: Luke Bermingham <[email protected]> * Bump lib-pixelstreamingfrontend-ui to 0.2.0 update dep versions Signed-off-by: Luke Bermingham <[email protected]> * Bump versions in package-lock.json for ui-library * Bump ui-library to 0.2.0 and force NPM publish * Update UE version printed when Cirrus starts Signed-off-by: Luke Bermingham <[email protected]> * Bump Github release of 5.2 infra to 0.4.0 Signed-off-by: Luke Bermingham <[email protected]> * Fix: sfu player would try subscribing when sfu disconnected * Updating the Frontend Docs (#152) --------- Signed-off-by: Luke Bermingham <[email protected]> Co-authored-by: hmuurine <[email protected]> Co-authored-by: William Belcher <[email protected]> Co-authored-by: Michael Stopa <[email protected]>
Not ready for merging yet (not for a little while yet). Preliminary pull request made so there's somewhere for review feedback to live.
Resolves #98