As plugin developer your job is to write new and/or maintain existing plugins.
To implement a plugin you need to create a property file: plugin.properties.
You should define the following properties:
If your plugin has menus you should create an XML file describing the menu structure.
Here is the format of the menu structure:
<menus> <menu text="The name of the main menu item, typically the name of the plugin"> <menuitem actionclass="The fully quailified name of the action (which must implement org.qfirst.batavia.plugin.AbstractPluginAction)"/> </menu> <menus>
The submenu item name come from the Action class. (see swing documentation for details).
The plugin class should implement the start() (invoked when the plugin is started) and the stop() method (invoked when the plugin is stopped).
If your plugin has options, it should be decribed in options.xml. The xml format is described here
You can also help maintaining old plugins.
The already existing plugins are:
As VFS developer you should create and/or maintain existing virtual file systems like sftp, ftp, jar, zip, tar, gz, bzip2, etc. To implement a new type of filesystem, you should subclass the org.qfirst.vfs.AbstractFile and the org.qfirst.vfs.AbstractFileSystem class.
In your AbstractFile subclass you should implement methods which deletes, renames the file, queries its attributes (name, path, size, etc.) In your AbstractFileSystem subclass you should implement three methods:
Your job would be to improve the UI of Batavia. Although the UI is written in Java (using Swing) you do not really need to be familiar with programming, it is enough to send me prototypes and/or suggestions.