Writing plugins

See FAQ: Plugins

Contributing

Angry IP Scanner's project is hosted by the Sourceforge.net – a free hosting site for open-source projects. The source code is in the Git repository provided by the service.

In order to get the source code, the following command must be run (make sure you have git-core installed):

git clone git://ipscan.git.sourceforge.net/gitroot/ipscan

This command will fetch the current source code of the program with full history into local directory named 'ipscan'. If the source of particular release is required, then you can later switch to particular tag using:

git checkout tag-name

where tag-name is the released version number (eg 3.0-beta4), for full list of available tags use:

git tag

Then, in order to build the binaries, you need only to run 'ant' in the 'ipscan' directory. Ant will use the standard build.xml script there and compile, test, and package the program for all platforms. Note: some packaging features were tested only on Linux.

The source code tree also includes the preconfigured Eclipse project for convenience. With Eclipse, you may use the 3rd-party Git plugin in addition to command-line git client. After opening the project from Eclipse, make sure you add to the build path the appropriate directory from src-platform according to the OS you are currently using as well as the correct swt jar file from ext/swt. Then, it can be run using the net.azib.ipscan.Main class.

After you have made you changes, you can send patches by email generated using the appropriate git command:

git format-patch origin/master 

or publish your own git repository, sending its URL and the branch name to pull the changes from.

Translations

If you know some language other than English well, then please help translating Angry IP Scanner into that language.

For that, you need to take the latest resources/messages.properties file, copy it with the ISO 2-letter language suffix (eg messages_et.properties), translate all the messages and send to me by email (or through the git).

To test your translations, run Angry IP Scanner from the command-line (assuming that the translated file is in the same directory as the original jar or exe):

java -cp . -jar ipscan-xxx.jar

Source structure

Directories

• src - the main subdirectory of the project tree, which contains the Java package structure of the source (net.azib.ipscan and its sub packages). All the source code, needed for running the program is stored there.

• src-platform - platform-specific source code. Use the appropriate subdirectory for your OS (linux, linux64, mac or win32) when compiling/running.

• test - contains exactly the same Java package structure as src does, but is intended for unit tests and other classes, which are not needed for running Angry IP Scanner itself. Each test case Java class should have the same name as the original class under test, but with the Test suffix, for example, Feeder and FeederTest.

• ext - for external libraries. The contents of each library's directory will depend on the original structure of that library, however, not all the original files may be included.

• resources - textual and graphical resources to be packaged with the program.

Java packages

Angry IP Scanner source code is in the net.azib.ipscan Java package.

• net.azib.ipscan.config - classes, related to configuration
• net.azib.ipscan.core - core scanner classes
• net.azib.ipscan.core.state - scanner's state machine implementation
• net.azib.ipscan.feeders - all feeder implementations
• net.azib.ipscan.fetchers - all fetcher implementations
• net.azib.ipscan.exporters - all exporter implementations
• net.azib.ipscan.gui - for GUI packages and classes (which are separate from the core functionality)
• net.azib.ipscan.gui.actions - most GUI listeners, such as menu item and button handlers

Dependency injection

Angry IP Scanner uses dependency injection pattern in its design, provided by the PicoContainer library, which was chosen for its lightweightness (adds about 60 kb).

PicoContainer encourages constructor injection, i.e. classes declare all required dependencies in their constrcutors, and container then resolves these dependencies (mostly) automatically, so that the classes themselves don't have to worry where these dependencies come from. This eases both development and unit testing of the code. Components are registered in the ComponentRegistry class.