No description
7af1db615d
To use such enums would be a mistake. It is quite enough to just use the message tokens as strings. Duplicating them as enums will just lead to the enums getting out of synch (as they already were). We would also need functions to covert between the string and enum forms. It seems to be hard enough to keep the messages documented in protocol.txt. |
||
---|---|---|
loleaflet | ||
loolwsd | ||
scripts | ||
.gitreview | ||
README |
LibreOffice on-line. This project fundamentally has two pieces: loolwsd/ The server side component. loleaflet/ The client side component. First compile loolwsd, and then loleaflet. Since you need both of these to get things working, it is recommended to read the READMEs in both projects. Enjoy.