Closed tranek closed 9 years ago
I think stuff like chat should go into some sort of plugin framework and/or we leverage a third party. We don't want to have to maintain a chat client as well as a drawing client
Etherpad's chat isn't a plugin that we could reuse is it?
It could/should be, I guess..
LOL. More work? XD
I will ponder this and take a look to see how difficult it will be to do.. I think the main issue is going to be accessing the socket and dealing with auth.
Okay! Chat isn't a major thing right now. Our main concern is crashing the server! Ugh. But I'm glad that it'll be in the back of your mind :)
An outcome of doing it by making chat a plugin would be that currently etherpad wouldn't put through it's minification process so it would adversely affect performance ;\ This is a bad thing..
We could potentially do chat as an npm module still but afaik all client side code would still be replicated, heh, kinda pointless right as nearly all of the code is client side code...
So yea, I suggest we wait on this :)
I'm fine with waiting for now!
I'm not going to work on this, Etherpad already has chat and that is what should be used :)
Add a showChat = false query to the EtherDraw url so that we can add a chatbox to EtherDraw and not have two chat boxes for the Etherpad ep_draw plugin.
https://github.com/JohnMcLear/draw/issues/22