libreoffice-online/loolwsd/Util.hpp

/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4; fill-column: 100 -*- */
/*
 * This file is part of the LibreOffice project.
 *
 * This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/.
 */

#ifndef INCLUDED_UTIL_HPP
#define INCLUDED_UTIL_HPP

#include <string>

#include <Poco/Net/WebSocket.h>

namespace Util
{
    std::string logPrefix();

    bool windowingAvailable();

    // Sadly, older libpng headers don't use const for the pixmap pointer parameter to
    // png_write_row(), so can't use const here for pixmap.
    bool encodePNGAndAppendToBuffer(unsigned char *pixmap, int width, int height, std::vector<char>& output);

    // Call WebSocket::shutdown() ignoring Poco::IOException
    void shutdownWebSocket(Poco::Net::WebSocket& ws);

    std::string signalName(int signo);
};

#endif

/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
Bump Emacs fill-column to 100 The default 70 is so last century. 2015-04-13 04:09:02 -05:00			`/* -- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4; fill-column: 100 -- */`
Use separate child processes for LibreOfficeKit For now, each LOOL client has a separate child process (or none at all, if it has accessed only information found in the cache). This will obviously have to chnage to handle collaboration. Etc. The parent process talks the same Websocket protocol with the child processes. When there is a child process for a client, traffic from the client is forwarded as such to the child process and vice versa. 2015-03-17 18:56:15 -05:00			`/*`
			`* This file is part of the LibreOffice project.`
			`*`
			`* This Source Code Form is subject to the terms of the Mozilla Public`
			`* License, v. 2.0. If a copy of the MPL was not distributed with this`
			`* file, You can obtain one at http://mozilla.org/MPL/2.0/.`
			`*/`

			`#ifndef INCLUDED_UTIL_HPP`
			`#define INCLUDED_UTIL_HPP`

Add Util::signalName() 2015-04-24 04:49:19 -05:00			`#include <string>`

Factor out WebSocket::shutdown() ignoring IOException 2015-04-22 03:14:11 -05:00			`#include <Poco/Net/WebSocket.h>`

Make Util a namespace instead of a class with just static member functions This is not Java or C#. 2015-03-26 10:07:52 -05:00			`namespace Util`
Use separate child processes for LibreOfficeKit For now, each LOOL client has a separate child process (or none at all, if it has accessed only information found in the cache). This will obviously have to chnage to handle collaboration. Etc. The parent process talks the same Websocket protocol with the child processes. When there is a child process for a client, traffic from the client is forwarded as such to the child process and vice versa. 2015-03-17 18:56:15 -05:00			`{`
Make Util a namespace instead of a class with just static member functions This is not Java or C#. 2015-03-26 10:07:52 -05:00			`std::string logPrefix();`
Cosmetics 2015-04-24 04:49:47 -05:00
Have lokitclient display tiles using ImageMagick's 'display' if available Refactor the PNG encoding of a pixmap out to Util. 2015-03-28 06:53:44 -05:00			`bool windowingAvailable();`
Cosmetics 2015-04-24 04:49:47 -05:00
Adapt for older libpng 2015-04-10 04:39:12 -05:00			`// Sadly, older libpng headers don't use const for the pixmap pointer parameter to`
			`// png_write_row(), so can't use const here for pixmap.`
			`bool encodePNGAndAppendToBuffer(unsigned char *pixmap, int width, int height, std::vector<char>& output);`
Factor out WebSocket::shutdown() ignoring IOException 2015-04-22 03:14:11 -05:00
			`// Call WebSocket::shutdown() ignoring Poco::IOException`
			`void shutdownWebSocket(Poco::Net::WebSocket& ws);`
Add Util::signalName() 2015-04-24 04:49:19 -05:00
			`std::string signalName(int signo);`
Use separate child processes for LibreOfficeKit For now, each LOOL client has a separate child process (or none at all, if it has accessed only information found in the cache). This will obviously have to chnage to handle collaboration. Etc. The parent process talks the same Websocket protocol with the child processes. When there is a child process for a client, traffic from the client is forwarded as such to the child process and vice versa. 2015-03-17 18:56:15 -05:00			`};`

			`#endif`

			`/* vim:set shiftwidth=4 softtabstop=4 expandtab: */`