|
hace 8 años | |
---|---|---|
etc | hace 9 años | |
gradle | hace 8 años | |
res/com/dmdirc | hace 8 años | |
src | hace 8 años | |
test/com/dmdirc | hace 8 años | |
test-res/com/dmdirc | hace 9 años | |
.gitignore | hace 9 años | |
AUTHORS | hace 10 años | |
LICENCE | hace 9 años | |
README.md | hace 8 años | |
UpdateCopyright.sh | hace 10 años | |
build-installer.xml | hace 10 años | |
build.gradle | hace 8 años | |
circle.yml | hace 9 años | |
gradle.properties | hace 9 años | |
gradlew | hace 9 años | |
gradlew.bat | hace 9 años | |
settings.gradle | hace 9 años |
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.
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.
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);
}
}
}