« get me outta code hell

mtui - Music Text User Interface - user-friendly command line music player
about summary refs log tree commit diff
path: root/socket.js
AgeCommit message (Collapse)Author
2024-05-16WIP socket shenanigans [!!!](quasar) nebula
this commit is mostly trash lol [!!!] Editor's note: Okay, after rebasing this commit is *super* spooky! It's interacting with a bunch of stuff that was previously handled in a merge commit and the revised changes may or may not be totally broken. If in doubt, assume this commit is the root of all evil (probably).
2024-05-16synchronize shared sources on join + other stuff(quasar) nebula
2024-05-16naughty hack for context menu in playlist sources(quasar) nebula
...plus a todo detailing what should be better
2024-05-16playlist sources = only what's shared with party(quasar) nebula
2024-05-16implement basic share-with-party command(quasar) nebula
2024-05-16actually set hasAnnouncedJoin on server lol(quasar) nebula
2024-05-16basic party sources creation for other sockets(quasar) nebula
2024-05-16announce joining party(quasar) nebula
2024-05-16identifier per socket connection(quasar) nebula
2024-05-16"party sources" ui (no socket functionality yet)(quasar) nebula
2024-05-16restore queued tracks from playlist sources(quasar) nebula
not sure why i didnt do this before but it Seems To Work Now! dog champ
2024-05-16add todo for remote/VPN mtui server hosting!(quasar) nebula
2024-05-16combining log messages (currently only seek!)(quasar) nebula
2024-05-16simplify log message text construction(quasar) nebula
2024-05-16log 'status' commands as new "verbose" (dim) lines(quasar) nebula
2024-05-16resume canonical player when all sockets are ready(quasar) nebula
this fixes an issue where a sync-playback received immediately during the resume would receive the paused status! in general, the canonical backend should always stay in line with the messages that the server sends out.
2024-05-16old "wait when done playing" code(quasar) nebula
I haven't tested this since writing it in July so I have no idea what it does! :D
2024-05-16socket log messages & misc npm updatesFlorrie
2024-05-16basic command log implementationFlorrie
2024-05-16support stop-playing over client socketsFlorrie
2024-05-16allow lines spread across multiple data chunksFlorrie
Wrapper functions 4 lyfe.
2024-05-16move data-handling code inside connection handlerFlorrie
This should make it easier to add state for individual sockets, which will be needed in coding better data handling. (Update: Actually, that wasn't necessary, because I wrote it as a more general wrapper function which contains its own state. Still, this could come in useful in the future, and it arguably reduces the code complexity anyway.)
2024-05-16synchronize playing new tracks across socketsFlorrie
2024-05-16support queue controls over socket clientsFlorrie
2024-05-16basic command relay across socket clientsFlorrie
2024-05-16basic working backend save/restore & socket serverFlorrie
Backend save/restore code (living in serialized-backend.js) has been well tested and shouldn't need much change going forward. Now we get to begin working on the actual synchronized-over-socket-server commands!