libreoffice-online/loolwsd
2015-03-09 13:40:39 +02:00
..
.gitignore Autofooize 2015-03-09 11:19:00 +02:00
AUTHORS Autofooize 2015-03-09 11:19:00 +02:00
ChangeLog Autofooize 2015-03-09 11:19:00 +02:00
config.h.in Autofooize 2015-03-09 11:19:00 +02:00
configure.ac Portabillity improvements 2015-03-09 13:40:39 +02:00
COPYING Autofooize 2015-03-09 11:19:00 +02:00
INSTALL Autofooize 2015-03-09 11:19:00 +02:00
LOOLSession.cpp Rename LOOLConnectionServer to LOOLSession 2015-03-09 10:02:47 +02:00
LOOLSession.hpp Rename LOOLConnectionServer to LOOLSession 2015-03-09 10:02:47 +02:00
LOOLWS.cpp Rename LOOLConnectionServer to LOOLSession 2015-03-09 10:02:47 +02:00
Makefile.am Autofooize 2015-03-09 11:19:00 +02:00
NEWS Autofooize 2015-03-09 11:19:00 +02:00
protocol.txt Add the callbacks 2015-03-05 15:57:03 +02:00
README We have a "proper" autofooized Unix build now 2015-03-09 11:30:56 +02:00

LibreOffice On-Line WebSocket server

See protocol.txt for a description of the protocol to be used over the
websocket.

Uses libpng and the Poco library, from
http://pocoproject.org/index.html. Build it with ./configure
--prefix=/opt/poco && make install. Probably is available packaged in
some distros

At least I like the Poco library. But if it is not acceptable for some
reason, please scream quickly, before too much code that uses Poco has
been written... I found Poco while looking for code to do the
WebSocket handshake and marshalling. But that functionality is just a
small part of what Poco does.

This uses autofoo now: autoreconf, run ./configure with appropriate
--with-lokit-path, --with-poco-includes and --with-poco-libs options,
make.

For Windows, a proper VS2013 project is needed.

For now this is intentionally just serving one client once. (This is
what the SOW says we should do first. See SOW for the directions of
further work.)

Also there is unconditional debugging output etc.

Run loolwsd for instance like this to test:

(echo load foo.odt; echo tile width=500 height=500 tileposx=0 tileposy=0 tilewidth=10000 tileheight=10000) | ./loolwsd --lopath=<path-to-lo-builddir>/instdir/program --test

The handling of termination is a bit fragile, occasionally it dumps
core somewhere in LO code when quitting. Don't be scared.

Set the DUMPPNG env var and the code dumps PNGs sent for each tile requests to a FOO<n>.png.