aboutsummaryrefslogtreecommitdiffstats
path: root/teleterm
Commit message (Collapse)AuthorAgeFilesLines
* use the correct username to log in on the server sideJesse Luehrs2019-11-252-10/+11
| | | | now that we're persisting it properly
* also build the wasm with -OzJesse Luehrs2019-11-252-1/+1
|
* remove a format! callJesse Luehrs2019-11-252-1/+1
| | | | apparently they are expensive (in code size)
* move value extraction logic into the viewJesse Luehrs2019-11-252-1/+1
| | | | since it depends more on the structure of the rendered page
* make logins persistentJesse Luehrs2019-11-254-4/+38
| | | | so if the server knows we're logged in, don't show the login page
* autofocus the username text boxJesse Luehrs2019-11-252-1/+1
|
* a bit more refactoringJesse Luehrs2019-11-252-1/+1
|
* add a basic login screenJesse Luehrs2019-11-242-1/+1
|
* simplify the update logic a bitJesse Luehrs2019-11-242-1/+1
|
* refactorJesse Luehrs2019-11-242-1/+1
|
* start working on the login flowJesse Luehrs2019-11-237-1/+171
|
* declare a character encodingJesse Luehrs2019-11-231-0/+1
|
* minify the wasm-bindgen generated jsJesse Luehrs2019-11-231-1068/+1
|
* strip out most logging in release buildsJesse Luehrs2019-11-232-29/+29
|
* remove unicode-normalization from the wasm buildJesse Luehrs2019-11-233-25/+24
| | | | | this cuts about 30% off of the binary size, and should have almost no impact
* stop hardcoding the list and watch urlsJesse Luehrs2019-11-235-67/+97
|
* 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-235-197/+217
|
* precompile the templatesJesse Luehrs2019-11-231-8/+17
|
* add basic template rendering abilityJesse Luehrs2019-11-235-167/+205
|
* remove some flickeringJesse Luehrs2019-11-232-21/+21
|
* enable lto for release buildsJesse Luehrs2019-11-232-397/+396
|
* i don't think rlib is necessary?Jesse Luehrs2019-11-232-40/+41
| | | | | 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-232-44/+43
|
* restrict the api a bit moreJesse Luehrs2019-11-232-32/+33
|
* move some things aroundJesse Luehrs2019-11-232-31/+31
|
* also draw the cursorJesse Luehrs2019-11-222-24/+24
|
* resize the browser terminal if the streamer terminal is resizedJesse Luehrs2019-11-225-46/+55
|
* 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-222-31/+31
|
* implement colors and text attributesJesse Luehrs2019-11-223-40/+39
|
* remove annoying log lineJesse Luehrs2019-11-221-2/+0
| | | | this is quite large for terminal output messages
* more web display improvementsJesse Luehrs2019-11-225-44/+75
|
* start working on watch displayJesse Luehrs2019-11-222-42/+41
|
* more information on the list pageJesse Luehrs2019-11-222-38/+39
|
* handle streamer disconnectsJesse Luehrs2019-11-223-34/+39
|
* move views out into separate modulesJesse Luehrs2019-11-222-32/+32
|
* use vt100 to render the terminal data in the browser(!)Jesse Luehrs2019-11-222-39/+39
|
* parse the websocket message in the browserJesse Luehrs2019-11-222-35/+38
|
* improve some loggingJesse Luehrs2019-11-222-23/+24
|
* switch to the log crateJesse Luehrs2019-11-222-52/+61
|
* 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-222-19/+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-222-30/+36
|
* thread through the id to the actual message eventsJesse Luehrs2019-11-222-22/+23
| | | | | 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
|
generated by cgit v1.2.3-54-g00ecf (git 2.45.1) at 2024-06-01 15:23:13 +0000