Fallout from beb59a43.

We need a larger range to handle the temporary overflow caused by
the Floyd-Steinberg dithering.

The debug builds do extra check, so chose that mode for Travis so we
get early warnings for problems.

because it is not only platform independent
but also allows to override the build date
This helps to make tigervnc builds reproducible

See https://reproducible-builds.org/ for why this is good

Also adds UTC flag, to be independent of timezone.
Also changes JAVA_DATE format to ISO-8601 date format.

Requires cmake-2.8.11+ from 2013

Logging revealed that a few empty damage regions are emitted on startup. Those don't need to be rendered to the Surface pixmap.

The Pixmap is filled in as updates from the server arrive. Before the first full update, it would contain undefined contents, which would be rendered onto the ViewPort.
Clearing the Pixmap is only done on startup and when changing the server resolution, so it's not performance critical.

It doesn't belong on each socket server object as timers are global.
Force implementations to call the Timer system directly instead,
avoiding any middle men.

Get this timeout in to the timer system as well to make things
simpler and more robust.

Do a proper cleanup when one of the termination timeouts trigger
rather than just exiting on the spot. This makes sure we don't leave
stray stuff around, e.g. unix socket files.

This makes them more consistent with everything else, which makes
things clearer and also allows them to handle some corner cases
(e.g. only firing once).

Add missing comments and clearly separate methods from attributes.

It is an internal function so it has no business being public.
Compare with CConnection where it is already private.

It is static and only used from a single place, so let's inline it.

It isn't true so remove those comments.

Windows tries to do a copy of it, and it is too complex to survive
that. Just reference the object directly as we know the source of
the message here.

It is functionality specific to WinVNC, so move the code there
to make things more clear.

These are not allowed in C++, and have been made optional in C11.
So let's just get rid of them and any issues they may cause.

We need to test this always in order to catch Ctrl+AltGr, and to
handle release of the key properly. Hopefully there isn't any other
case where VK_MENU is sent without a scan code.

We might have an offset in the area of the screen we're tracking,
so make sure that offset is included in the changes we report.

ServerParams should contain the server state and not information about
client settings or capabilities. Move those things up a level to the
CConnection object.

No need to have one setting for each extension. All the client code
needs to indicate is if it supports resize. The common code can then
map this to relevant extensions.

It needs to be validated and take effect in the server first.

These were either completely unused, or always true.

Tight is the default preferred encoding, so we don't really need
special handling for it to be first in the list.

This is a lot safer and cleaner. The old code had a fixed size that
we didn't properly keep track of.

Make sure all methods only write what is given as arguments, and
avoid side effects by getting data from parameter objects. This keeps
things readable in the calling code.

It's a generic client thing, so abstract it in to the common library.
Makes it easier to integrate with other common code.

Avoid using the callbacks used for runtime changes for the initial
setup. They weren't really useful anyway as you could not allocate
a framebuffer without also knowing the pixel format. So make things
more clear by letting serverInit() get the initial settings.

Add an explicit callback for subclasses to do their startup in. This
makes it easier to do proper ordering, and avoids mistakes.

This method was only really useful when continuous updates was active,
so let's rely on a single extension rather than two.

Better to check the actual list of supported encodings directly.
Makes parts more readable, and no risk of getting out of sync.

No need to spread things out. Keep all of the handling in a single
place to make things clearer.

Now that we've split out server state to ServerParams, ConnParams
only contains state for a client. Rename the class and variables
to reflect this.

We need to track different things in the server and client, so
separate things to two independent structures to keep things more
clear.

Avoid direct access to the screen dimensions and layout so that we
can make sure it stays sane. This also makes sure the layout is
properly updated when we only get the screen dimensions from the
server.

We might only be using part of the X server's screen, so make sure
the layout we calculate is contained within this part.

That object is just a container for the current state. Move the I/O
to the classes already doing such stuff.

We should not be including server headers from client code. It was
not even needed, so simply remove it.

This makes VNCServer a sufficiently complete interface that callers
don't need to know about the specific implementation (VNCServerST
currently). And assuming that all servers will use sockets is not
that outrageous.