aboutsummaryrefslogtreecommitdiffstats
path: root/teleterm-web/src/lib.rs
Commit message (Collapse)AuthorAgeFilesLines
* bump seedJesse Luehrs2019-12-071-4/+9
|
* add a logout buttonJesse Luehrs2019-11-261-0/+2
|
* move value extraction logic into the viewJesse Luehrs2019-11-251-1/+1
| | | | since it depends more on the structure of the rendered page
* make logins persistentJesse Luehrs2019-11-251-4/+7
| | | | so if the server knows we're logged in, don't show the login page
* add a basic login screenJesse Luehrs2019-11-241-2/+1
|
* simplify the update logic a bitJesse Luehrs2019-11-241-3/+3
|
* start working on the login flowJesse Luehrs2019-11-231-1/+3
|
* pass configuration from the web server to the web appJesse Luehrs2019-11-231-1/+2
|
* restrict the api a bit moreJesse Luehrs2019-11-231-3/+2
|
* move some things aroundJesse Luehrs2019-11-231-53/+2
|
* resize the browser terminal if the streamer terminal is resizedJesse Luehrs2019-11-221-0/+3
|
* add a button to stop watching the current streamJesse Luehrs2019-11-221-0/+5
|
* more information on the list pageJesse Luehrs2019-11-221-1/+1
|
* handle streamer disconnectsJesse Luehrs2019-11-221-0/+4
|
* move views out into separate modulesJesse Luehrs2019-11-221-13/+2
|
* use vt100 to render the terminal data in the browser(!)Jesse Luehrs2019-11-221-5/+2
|
* parse the websocket message in the browserJesse Luehrs2019-11-221-0/+13
|
* improve some loggingJesse Luehrs2019-11-221-4/+4
|
* switch to the log crateJesse Luehrs2019-11-221-17/+13
|
* don't manually disconnect on disconnect eventsJesse Luehrs2019-11-221-1/+0
| | | | | | | | we only get the disconnect events after the disconnect happens, and in this particular case it's happening because we dropped the old connection to replace it with a new connection, and so manually clearing the current connection on a disconnect event will usually end up clearing the new connection
* thread through the id to the actual message eventsJesse Luehrs2019-11-221-12/+4
| | | | | this is more accurate, since managing the lifetime of the websocket connection is a bit tricky
* refactorJesse Luehrs2019-11-221-45/+15
|
* implement listing and watching on the web sideJesse Luehrs2019-11-221-21/+78
| | | | | watching doesn't do anything yet, because the server side doesn't yet know how to send messages to a watch client
* refactor a bitJesse Luehrs2019-11-221-30/+28
|
* start using seed on the web sideJesse Luehrs2019-11-221-38/+61
|
* rename some stuffJesse Luehrs2019-11-211-1/+1
|
* shorter namesJesse Luehrs2019-11-161-3/+4
|
* add basic websocket clientJesse Luehrs2019-11-151-0/+49