選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
Greg Holmes 21cbd44046
Publish to github packages (#815)
4年前
.github/workflows Publish to github packages (#815) 4年前
api Update autovalue to 1.6. 6年前
bundles Remove unnecessary asserts. 7年前
docs First pass at a style guide. 7年前
etc Rename PMD ruleset, update PMD. 7年前
gradle Publish to github packages (#815) 4年前
src Fix imports 6年前
.gitignore Ignore .nb-gradle folder 7年前
AUTHORS McCormack => Mc Cormack 5年前
LICENCE Update copyright for 2017 7年前
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 Throttle unread status changes. 6年前
circle.yml Add support for sending coverage to codacy. 7年前
gradle.properties Add a bit more info to version.config. 9年前
gradlew Update gradle to 3.1. 7年前
gradlew.bat Update gradle to 3.1. 7年前
settings.gradle Move Yaml utils to com.dmdirc.util.io.yaml bundle. 7年前

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);
        }
    }

}