Different modes are equipped with mode controllers implementing interface ModeController. The mode controllers are responsible for registering of Actions, Menu Items, Hot Keys and Mouse Listeners which are available for the user. The mode controller of the edit mode MindMapMode takes the required menu structure from file mindmap_menus.xml. It can also include classes registered as Plug-Ins and loaded at the run-time using reflection.

It makes possible to create a relatively compact freemindbrowser.jar that can be used in the applet viewer with a subset of the classes that makeup the whole FreeMind program.

Model

MindMap

MindMapNode

Filtering

Edge Models

Links

Clouds

Atributes

Attribute Registry

Model Events

View

MapView

NodeView

Edges

Filtered Nodes

Attribute Table

Clouds

Link Views

Layout Managers

Controller

The Controller and mode controller classes set up all the Actions that are used to respond to user input and make changes to the model.

The main Controller class needs a FreeMindFrame for it's constructor. FreeMindFrame is an Interface. This gives Controller the ability to call back into the FreeMind class which implements FreeMindMain.

Modes

Actions

Undo Implementation

XML-Serialization

Listeners

Controller Events

Filter Controller

Configuration (Preferences)

Plug-Ins

The plug-ins allows adding of new operations capsuled in their own components without changing code of controller for registering and managing them. Such plug-ins are saved in directory "accessories". Even the note is implemented as a plug-in.

The plug-ins also provide additional functions that aren't needed by everyone. For instance, the SVG plug-in gives you the capability of exporting your Mind Maps to SVG format. These modules are left out of the minimum download configurations in order to save space.

Startup

Freemind is started by invoking a script:

Starting Scripts

Windows

freemind.bat

Linux

freemind.sh

The main class invoked by the script is: freemind.main.FreeMindStarter

FreeMindStarter checks the Java version and then invokes Freemind.main.

The Freemind takes care of initialization, setting the look and feel, loads maps and makes the GUI visible.

It might make some sense to refactor this class, it's very large and complicated. - Rben13

Currently the tabs and tab management are implemented as FreeMindStarterinner classes. Is it good? - DimitriPolivaev

As soon as the frame is created (or the applet is displayed), its event loop takes control over. The starter threads ends at this point

GUI Design Principles

The purpose of FreeMind is to provide an easy-to-use Mind Mapping application. It is important to make the users experience with the program as easy, natural, and intuitive as possible. The interface should be uncluttered and easy to navigate.