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.
Greg Holmes dcaf58b0e4 Merge pull request #619 from csmith/tidying пре 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 a README. пре 9 година
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

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

}