Reduces unread status changes to publish to the eventbus
at most once every 200ms per window. These events are
handled synchronously on the EDT so cause massive
performance issues.

When connecting to several bouncers with huge backbuffers
this makes the client usable in seconds rather than tens of minutes.

Internally this uses RX to handle the throttling, because it's
super easy. We might eventually want to expose that externally
instead of using an event bus, but I'm not sure.

Needed for java 9 support.

Issue #750

Issue #750

Issue #750

This won't affect normal use of the client, other than it having
a few extra unused classes and some additional lines in the
manifest.

Issue #750

This is for the interfaces/trivial implementation classes that
DMDirc plugins can interact with. Eventually plugins will build
against the API instead of the DMDirc client itself, which will
allow for remote/detachable clients (amongst other things).

Stop swimming against the tide and accept what most of the rest of
the world does.

While it adds an annoying depth to the actual source code, it makes
the root directory nicer (no more 'test-res' dirs), means we don't
have to override the gradle config, and makes it nicer to work in
IDEA 2016.1.

DMDirc/Parser#23

Update DMDirc repo to HTTPS.

This enables release tracking in sentry.

This release contains some performance improvements compared
to the version we were using.

Error handlers are now passed in at construction time, so
there was a small bit of refactoring required.

No major changes, just a version bump for the Sentry protocol
(for Sentry 7) and removal of UDP connections which we never
used.

This doesn't seem to actually mark them as generated, but they're
marked as source/test dirs which stops the annoying errors every
time you sync.

Makes it a bit less messy, and easier to find the right bits.

This replaces the default source directories (src/main/java, etc)
with our own, instead of just appending ours to the list.

Don't include the version.config from build as well as the one we're
generating.

Don't include dependencies etc twice in fat jars.

Apparently this is useful in some cases. I have my doubts.

Building client:fatjar will bundle all plugins in the 'plugin'
configuration in gradle (currently IRC parser, Swing UI, two
tab completers) into a client jar.

Fixes #100

Fix incorrect plugin names.

Move task configuration into the task, rather than referencing it
oddly afterwards.