| OLD | NEW |
|---|
| 1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> | 1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> |
| 2 <html> | 2 <html> |
| 3 <head> | 3 <head> |
| 4 <title>WebRTC PeerConnection Manual Test</title> | 4 <title>WebRTC PeerConnection Manual Test</title> |
| 5 <script type="text/javascript" src="../test_functions.js"></script> | 5 <script type="text/javascript" src="../test_functions.js"></script> |
| 6 <script type="text/javascript" src="../message_handling.js"></script> | 6 <script type="text/javascript" src="../message_handling.js"></script> |
| 7 <script type="text/javascript" src="../getusermedia.js"></script> | 7 <script type="text/javascript" src="../getusermedia.js"></script> |
| 8 <script type="text/javascript" src="../jsep01_call.js"></script> | 8 <script type="text/javascript" src="../jsep01_call.js"></script> |
| 9 <script type="text/javascript" src="peerconnection.js"></script> | 9 <script type="text/javascript" src="peerconnection.js"></script> |
| 10 <meta charset="utf-8"> | 10 <meta charset="utf-8"> |
| (...skipping 77 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 88 <td> | 88 <td> |
| 89 <h1>Messages</h1> | 89 <h1>Messages</h1> |
| 90 <button onclick="clearLog();">Clear Logs</button> | 90 <button onclick="clearLog();">Clear Logs</button> |
| 91 </td> | 91 </td> |
| 92 <td><h1>Debug</h1></td> | 92 <td><h1>Debug</h1></td> |
| 93 </tr> | 93 </tr> |
| 94 <tr> | 94 <tr> |
| 95 <td valign="top"><pre id="messages"></pre></td> | 95 <td valign="top"><pre id="messages"></pre></td> |
| 96 <td valign="top"><pre id="debug"></pre></td> | 96 <td valign="top"><pre id="debug"></pre></td> |
| 97 </tr> | 97 </tr> |
| 98 <tr> |
| 99 <td><button onclick="toggleHelp();">Toggle Help</button></td> |
| 100 </tr> |
| 101 <tr> |
| 102 <td id="help" style="display: none" colspan="2"> |
| 103 <h1>How This Page Works</h1> |
| 104 <p> |
| 105 This page is intended for testing WebRTC calls. |
| 106 |
| 107 This is how you set up a normal call: |
| 108 </p> |
| 109 <ol> |
| 110 <li>Open this page in two tabs.</li> |
| 111 <li>Start the peerconnection server. Click on the question mark next |
| 112 to the 'server' field for instruction on how to do that. The easiest |
| 113 thing is to start it on localhost, but you can start it on any |
| 114 machine you like and connect to hostname:8888.</li> |
| 115 <li>Click the Connect button in both tabs.</li> |
| 116 <li>Click the Call button in one of the tabs. You should see a bunch |
| 117 of printouts when this happens. Note that no streams are sent to |
| 118 begin with.</li> |
| 119 <li>Grant media access using the checkboxes and Request button.</li> |
| 120 <li>Send the local stream by clicking the "Send" button, in both tabs. |
| 121 </li> |
| 122 <li>You should now have a call up and both sides should be receiving |
| 123 media data (depending on what access you granted on the respective |
| 124 pages)</li> |
| 125 <li>You can now choose to stop, re-request, re-send or disable streams |
| 126 in any way you like, or hang up and re-start the call. You don't |
| 127 need to disconnect: that's done automatically when you close the |
| 128 page. Hanging up is NOT done automatically though.</li> |
| 129 </ol> |
| 130 <p>Detailed descriptions:</p> |
| 131 <ul> |
| 132 <li>Connect - once a connection is established, you generally won't |
| 133 need to click this button again. Connecting really isn't something |
| 134 related to WebRTC as such, it's just the signalling solution.</li> |
| 135 <li>Note that if more than two users/machines have established a |
| 136 connection to the same PC server, you will get an error when |
| 137 pressing this button. The test is hard-coded to only allow 2 peers |
| 138 on the server at the same time.</li> |
| 139 <li>Pressing the Send button for local streams will in effect add |
| 140 the current local stream, such as it is, to the current |
| 141 peerconnection and re-negotiate the call (e.g it will send SDP |
| 142 offers back and forth).</li> |
| 143 <li>If you request user media again, it will overwrite the current |
| 144 local stream with the new one. This means that pressing Send will |
| 145 add the stream you just got from the request. The code will not |
| 146 attempt to stop or remove the previous stream from the |
| 147 peerconnection, so depending on peerconnection's semantics the old |
| 148 stream will remain with the peerconnection (perhaps the streams will |
| 149 be sent simultaneously?)</li> |
| 150 <li>Hang Up will clear away peer connections on both sides, and a new |
| 151 call can be started if desired. The peers remain connected to the |
| 152 peerconnection server.</li> |
| 153 <li>The Toggle buttons will set the .enabled properties on the first |
| 154 video and audio track for the local or remote stream, respectively. |
| 155 This is effectively a temporary "mute" for the streams.</li> |
| 156 <li>Stop terminates a stream, which means it will no longer send any |
| 157 more data.</li> |
| 158 <li>Remove will remove the current local stream from the current |
| 159 peerconnection. For instance, you should be able to send a stream, |
| 160 remove it, re-request a new stream and send that within the same |
| 161 call. Note that re-requesting user media overwrites the current |
| 162 media stream, so the reverse is not possible.</li> |
| 163 <li>The Constraints field can pass in arbitrary constraints. The code |
| 164 will attempt to eval the code you write in and pass it whenever the |
| 165 code asks for constraints. [experimental]</li> |
| 166 </ul> |
| 167 </td> |
| 168 </tr> |
| 98 </table> | 169 </table> |
| 99 | 170 |
| 100 </body> | 171 </body> |
| 101 </html> | 172 </html> |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 11192013:
Added help text to PeerConnection test page. (Closed)
Base URL: svn://svn.chromium.org/chrome/trunk/src