You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Chris Smith 4991209d9d Add info about how to display text... преди 8 години
etc 2015! преди 9 години
gradle Bump gradle version. преди 9 години
res/com/dmdirc Improve formatting of whois events. преди 8 години
src Disable numeric formatting, remove dead code. преди 8 години
test/com/dmdirc Disable numeric formatting, remove dead code. преди 8 години
test-res/com/dmdirc Add basic test for PluginFileHandler. преди 9 години
.gitignore Stop ClientInfo being static. преди 9 години
AUTHORS Add Google to the AUTHORS file. преди 10 години
LICENCE 2015! преди 9 години
README.md Add info about how to display text... преди 8 години
UpdateCopyright.sh We're missing a file! преди 10 години
build-installer.xml Build process improvements. преди 10 години
build.gradle Bump gradle version. преди 9 години
circle.yml Set the working directory... преди 9 години
gradle.properties Add a bit more info to version.config. преди 9 години
gradlew Add gradle wrapper преди 9 години
gradlew.bat Add gradle wrapper преди 9 години
settings.gradle Don't force project names any more. преди 9 години

README.md

DMDirc

DMDirc is an IRC client written in Java. It’s cross-platform, hugely configurable, and is easily extensible with a robust plugins system.

This repository contains the ‘core’ of the client. If you’re interested in developing DMDirc or building it from scratch, you’d be much better off cloning the meta repository, which contains the core, plugins, IRC library, etc. Detailed setup instructions are available there as well.

Development information

Displaying text

Text shown in windows (channels, servers, etc) is generated automatically from certain types of events passed on the DMDirc event bus. Any event that subclasses DisplayableEvent can potentially be formatted.

DisplayableEvents are listened for by each window’s BackBuffer instance. A format is then applied to the event to transform it into one or more strings. Formats are specified in a YAML file included in the DMDirc jar, and can be overridden by the user by putting a format.yml file in their DMDirc config directory.

A couple of typical formatting entries looks like this:

ChannelMessageEvent:
  format: "<{{client.modePrefixedNickname}}> {{message}}"
ChannelModeNoticeEvent:
  format: "-{{client.modePrefixedNickname}}:{{prefix}}{{channel.name}}- {{message}}"
  colour: 5

The {{..}} templates retrieve properties from the event itself. {{client.modePrefixedNickname}} is the equivalent of calling getClient().getModePrefixedNickname().toString() on the event object.

Error handling

DMDirc has a user interface for displaying details of errors to users. It also supports uploading of errors to the DMDirc sentry instance if the user allows it (or manually clicks on send).

Errors should be logged using a Slf4j logger, and marked with one markers defined in LogUtils. These markers allow developers to specify whether an error is an “Application” error (which will get reported and should ultimately be fixed), or a “User” error (which is due to a problem with the user’s config, environment, etc), and also whether the error is fatal or not.

A typical class that reports errors will look something like the following:

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import static com.dmdirc.util.LogUtils.APP_ERROR;

public class MyClass {

    private static final Logger LOG = LoggerFactory.getLogger(MyClass.class);

    public void doSomething() {
        try {
            // Do something
        } catch (SomeException ex) {
            LOG.error(APP_ERROR, "Couldn't do something!", ex);
        }
    }

}