aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* minify the wasm-bindgen generated jsJesse Luehrs2019-11-232-1069/+5
|
* strip out most logging in release buildsJesse Luehrs2019-11-233-30/+30
|
* remove unicode-normalization from the wasm buildJesse Luehrs2019-11-235-28/+27
| | | | | this cuts about 30% off of the binary size, and should have almost no impact
* stop hardcoding the list and watch urlsJesse Luehrs2019-11-237-78/+104
|
* refactor a bitJesse Luehrs2019-11-233-409/+409
|
* also rely on the middleware for template renderingJesse Luehrs2019-11-231-18/+12
|
* use middleware insteadJesse Luehrs2019-11-231-22/+13
|
* move server address to configurationJesse Luehrs2019-11-235-27/+74
|
* pass configuration from the web server to the web appJesse Luehrs2019-11-239-201/+256
|
* precompile the templatesJesse Luehrs2019-11-231-8/+17
|
* add basic template rendering abilityJesse Luehrs2019-11-237-173/+282
|
* remove some flickeringJesse Luehrs2019-11-234-23/+40
|
* enable lto for release buildsJesse Luehrs2019-11-233-397/+399
|
* i don't think rlib is necessary?Jesse Luehrs2019-11-233-41/+42
| | | | | i thiiiiink that's just if the crate is supposed to be for both native code and wasm
* shuffle some of the view structure aroundJesse Luehrs2019-11-237-100/+106
|
* rename a variableJesse Luehrs2019-11-231-4/+4
|
* commentJesse Luehrs2019-11-231-0/+7
|
* restrict the api a bit moreJesse Luehrs2019-11-237-76/+66
|
* move some things aroundJesse Luehrs2019-11-234-84/+92
|
* also draw the cursorJesse Luehrs2019-11-223-27/+39
|
* changelogJesse Luehrs2019-11-221-0/+13
|
* resize the browser terminal if the streamer terminal is resizedJesse Luehrs2019-11-228-47/+66
|
* make sure our terminal size is updated correctlyJesse Luehrs2019-11-222-1/+3
| | | | a couple of our in-memory terminal parsers were being stuck at 80x24
* add a button to stop watching the current streamJesse Luehrs2019-11-227-358/+372
|
* implement colors and text attributesJesse Luehrs2019-11-224-40/+338
|
* remove annoying log lineJesse Luehrs2019-11-221-2/+0
| | | | this is quite large for terminal output messages
* more web display improvementsJesse Luehrs2019-11-229-54/+93
|
* start working on watch displayJesse Luehrs2019-11-224-49/+61
|
* more information on the list pageJesse Luehrs2019-11-226-57/+112
|
* also rebuild when a view changesJesse Luehrs2019-11-221-1/+1
|
* handle streamer disconnectsJesse Luehrs2019-11-226-34/+48
|
* move views out into separate modulesJesse Luehrs2019-11-229-46/+78
|
* remove no longer necessary directiveJesse Luehrs2019-11-221-1/+0
|
* use vt100 to render the terminal data in the browser(!)Jesse Luehrs2019-11-226-45/+60
|
* parse the websocket message in the browserJesse Luehrs2019-11-224-35/+58
|
* improve some loggingJesse Luehrs2019-11-223-27/+28
|
* switch to the log crateJesse Luehrs2019-11-225-69/+88
|
* simplifyJesse Luehrs2019-11-221-20/+8
|
* send terminal output messages back to the web pageJesse Luehrs2019-11-223-21/+130
|
* don't manually disconnect on disconnect eventsJesse Luehrs2019-11-224-24/+19
| | | | | | | | 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
* make sure we close old websocket connectionsJesse Luehrs2019-11-223-30/+42
|
* thread through the id to the actual message eventsJesse Luehrs2019-11-225-50/+39
| | | | | this is more accurate, since managing the lifetime of the websocket connection is a bit tricky
* hyper knows about these headers tooJesse Luehrs2019-11-221-4/+5
|
* connect to the teleterm server on watch requestsJesse Luehrs2019-11-226-36/+119
|
* wasm should be rebuilt if any .rs files changeJesse Luehrs2019-11-221-1/+1
|
* refactorJesse Luehrs2019-11-224-99/+131
|
* implement listing and watching on the web sideJesse Luehrs2019-11-225-57/+227
| | | | | watching doesn't do anything yet, because the server side doesn't yet know how to send messages to a watch client
* this variant should take an ErrorEventJesse Luehrs2019-11-221-1/+1
|
* refactor a bitJesse Luehrs2019-11-224-45/+57
|
* start using seed on the web sideJesse Luehrs2019-11-228-68/+837
|