From FreeMind

Revision as of 12:19, 1 May 2007 by Ewl (Talk | contribs)
Jump to: navigation, search

The development of FreeMind is coordinated using FreeMind's project page at SourceForge, and also using this wiki. At wiki, we have requests for enhancements page; there is also requests for enhancements (RFEs) page at SourceForge (not preferred). You can browse CVS repository.

We also use SourceForge for bugs, and open discussion forum. We do not use the documentation part there as we use this wiki instead.


Getting started as a developer or tester

To get the latest beta version of FreeMind

You can get the beta version from the CVS. Look under branches. Observe, that these versions are not official releases and may admit serious errors. Please, use them only if you urgently need a feature included in such a version or to give us feedback to our development which is highly appreciated.

To compile FreeMind on your own

If you are a developer, just download the sources, unpack them, find the folder with the file build.xml, and execute the command ant in that folder. For more detail description see the Quick guide to compiling Freemind on an XP system using Eclipse prepared for you by Bob Alexander.

Broken down into simple steps, a simple way for a developer of compiling FreeMind is perhaps the following.

  1. install Java SDK — standard development kit
  2. install Ant — a tool for building code using complicated make files)
  3. download FreeMind's source code as published in the Files section
  4. unpack the source code package with the extension tar.gz
  5. change directory to the one where built.xml file resides — the build file for Ant, similar to make files for the C language
  6. type ant in the command shell

To set up a FreeMind project under Eclipse

You download FreeMind to ~/src/freemind say. Then, you have to compile FreeMind on command line using "ant dist". After that you open a new project with working directory ~/src you should find the following settings:

  • The binaries are stored into ~/src/bin/classes.
  • You have two source folders.
  • All jars you find in ~/src/freemind are added to the project.

Then finish the project settings and there should be no errors in the project. You can run FreeMind starting the class freemind.main.FreeMind.

Further development wiki pages

Further reading (still under construction):

To use concurrent version repository (CVS) with Eclipse

See Using CVS from within Eclipse guide by Bob Alexander.

When working with CVS, remember that it is difficult to change directory and file names under CVS. Moreover, it not easy to remove files completely. Therefore, pay attention when checking files in.

Contributing to the FreeMind

There are different possible ways of taking part in the FreeMind development: the project needs people for developing, testing and documenting of the program, and translating its interface and documentation in foreign languages.

New developer starts by sending his contributions for example as patches. Later on, he may get access to CVS repository. The process is approximately as follows.

  • Create a user account at SourceForge.
  • Discuss your contribution (the change, feature, bug fix, documentation or test plan) in our open discussion forum.
  • If the topic is accepted, start to change the actual CVS code. Be careful to use the right CVS branch. Currently we use the branch with a strange name "fm_060405_integration".
  • For later merging of the code it could be better if you start from code state already labeled by a tag, e.g. "fm_0_9_0_beta9".
  • If you have any questions during the implementing feel free to ask them in the "Open Discussion" forum. It is read by the other developers who possible can help you.
  • Post your contribution in the patch section of SourceForge or send it by email to the current project manager. We do not respond immediately, as FreeMind team consists of volunteers.
  • After having successfully developed and integrated some items, you get access to FreeMind's CVS repository at SourceForge.

Development resources

Getting the latest CVS branch

The latest integration branch is fm_060405_integration. The last release has tag FM-0-8-0.

How the FreeMind development is organized

Initially every active developer works on his own branch. Our intermediate results are published as our "alpha versions". We use forum Open Discussion and section Experimental_versions on this wiki page to communicate them.

Only after this partial developments are finished, they can me merged together. The resulting version is expected to work with all maps created by all versions, which are merged into it, but we can not assure it in any particular case.

The merged versions are published as Release Candidates and are released.

An alternative to this development scheme would be not to publish the intermediate versions, and I think the current method is probably a better one.

Experimental versions

Currently, there are the following experimental versions available. They are not meant for productive use; use at your own risk!

FreeMind with Node Attributes and Map Filters

Attaching of named attributes to every node, filtering of the displayed map content based on node text, node icons and node attributes

FreeMind with WYSIWYG rich text node editor

FreeMind Browser Applet for FreeMind 0.8

Alpha, Beta and Release Candidate

I propose the following definitions of labels alpha, beta, and release candidate.

  • Alpha is a purely test version. Absolutely no guarantee is made on how it's going to work, keep data format of FreeMind mind maps, and the like. One alpha version may have other features and file format than another one, as each developer with source access may create his/her own Alpha version. Users of alpha are people who want to help in the development process of FreeMind by reporting bugs in early unstable versions, or who want to influence in which direction the alpha will be finetuned.
  • Beta is a version with known old and newly introduced bugs, with many fixes pending and possibly smaller enhancements. Maps saved from betas should ideally be readable by later versions. Thus, allocating label beta requires considerable attention.
  • Release Candidate is a version in which there are neither errors nor changes pending that the developers would know of at the date of publishing. After RC1, packagers and translators are called to do their work for the final release. Only changes required to fix critical bugs are acceptable; those fixes should avoid changes impacting translation or packaging efforts.

--Danielpolansky 04:49, 29 Apr 2006 (PDT)
-- Ewl 05:19, 1 May 2007 (PDT)

Conceptual remarks

Modular model - view design

The architecture of FreeMind makes it possible that FreeMind becomes general tool for editing tree-structured data, that is mind maps, XML/HTML documents, folder trees etc. in future.

All these kinds of data would be presented to the user as a mind map. Model-View-Controller design makes it possible for you only to write so called model of the data structure, without caring for the visual representation. Currently, mind map mode and file mode are implemented.

Original vision of Joerg Mueller

Joerg Muller is the original author of FreeMind, developing it up to the version 0.4.0. Here follows what he's got to say on his original vision:

What I had in mind when I began to write FreeMind, was creating a collaborative mind where people can intuitively share their ideas, knowledge and thoughts with each other. Of course FreeMind is only a first step into this direction, but I did this first step. Now a Mode must be implemented that makes collaboration over the Internet possible, maybe using the Topic-Map standard. I think linear text is a very poor way of representing knowledge, and by using trees and networks, visual representation, internet collaboration and open source we should be able to create some kind of a collaborative mind.
FreeMind now has evolved from a specific Mind Map Editor to a generic editor for tree structured data. I want FreeMind to become for tree structured data what emacs is for linear data (ie. text).

One may think of extending FreeMind to work with networks as opposed to trees only, an example of this being Topic Maps (ISO).

Daniel Polansky: Joerg's vision of FreeMind becoming Emacs for tree data is intriguing, but rather far fetched at the time. You would need to provide scripting facility and at least many basic operations, like upcase, downcase, replace and many others. It is even not evident that this goal valuable compared to other goals - there many quite obvious and still missing features.

Why not use OPML for storage instead of FreeMind's native XML format

The current version of OPML is not suited for our purposes. It should be easy to create conversion XSLT between FreeMind and OPML. First, if we decided to use OPML, we would have to wait until the owner of OPML changes his standard to fit our needs. Thus, we would be dependent, not being able to act dynamically. Second, already the current version of OPML is insufficient. It does not contain most of what FreeMind already uses: colors, fonts, folded tag, edges and icons. It is not a superset of FreeMind's XML format, even not in a vague sense. Even if I renamed the elements names properly, OPML would still be a subset and not superset of FreeMind's XML. As a result, we have no benefit from using OPML right now.

Summary: 1) we would run into dependence, and 2) OPML is insufficient, loosely speaking it is a subset.

Why may FreeMind be more relevant than some other open source applications

There are many efforts to create new text editors, text processor and the like. While this activity is not without value, it does not fill that big value gap as mind mapping application.

Take, for instance, text editors like JEdit. There are already well estabilished text editors like Emacs or Vim, and there are many others. It's not that these editors would be perfect, far from that, but they're still pretty useful and with some training users can become very efficient with them.

With text processors, the thing is that most users in companies have already Microsoft Office for free. What does that mean? That means that the individual users do not have to pay for the MS Office, and they cannot effectively decide to use other Office platform either because of the value of easy sharing. Furthermore, there are competing free Office platforms like KOffice, OpenOffice or AbiWord.

In mind mapping, the situation is quite different. You do not get commercial alternative granted in companies, unlike office applications. The point here is that most of MS Windows users, the mainstream, do not have a mind mapping application yet. For them, starting to use FreeMind is not a switch from Microsoft product to alternative product. It is a switch from scattered documents in incomparable and hard-to-overview formats to one document with unprecedented order and transparency - FreeMind's mind map.

Therefore, I am expecting a growth of interest of free developers in developing and using this application.

Furthermore, even though Java is quite slow and memory hungry, it solves the neverending quarrel between religious die-hard fans of different computing platforms, which I have first experienced with Atari 800 XL versus Commodore 64 battle, later IBM compatible versus Commodore Amiga battle, and nowadays Windows versus Linux battles.


To create a new release

To succesfully complete a new release, do the following

  • upload the release files into /incoming at , use the user anonymous and your e-mail address as a password
  • create new release. The files you have uploaded with ftp will be offered to you. Releases have names like "0.6.1", "0.6.5".
  • update the home page so that it points to the new version of installation files
  • post news, listing the most important changes of the new version
  • repost the news to the Announce forum, with basically the same text
  • repost the news the mailing list

Notice that the news cannot be monitored unlike forum, and forum has no RSS feed unlike news.

To create proper copyright notice

A source file may be viewed as a sum b + d1 + d2 + ... + dk, where b is the basis, di are deltas (or patches), and the plus operator is the operator of applying a patch. The basis and each delta have their own copyright holder and the year of copyright.

If there is only one autor and one year, then the copyright notice is simple.

If there is only one autor and more years, then the copyright notice may look like

Copyright © 2003-2005 Big Author

which is to be understood as

Some parts of the sum are copyrighted in 2003, some perhaps in 2004, and some certainly in 2005.

If there are more authors, then the copyright notice consists of more lines, like

Copyright © 2003-2005 Big Author,
Copyright © 2005 Captain,

Not all changes are eligible for copyright. If a change is small, then it does not make sense to add a line to the copyright notice for it.

Copyright notice is not required for copyright to hold. It makes claiming your right at court easier.

The correctness of these instructions is not granted. They are subject to improvement as we see fit.

--Danielpolansky 11:29, 3 Jun 2005 (PDT)

All on keyboard mappings

Currently, each function has at most one key assigned. But, it should be the other way around; the keys should have functions assigned, rather than functions key. For instance, it would be valuable to have both insert and tab assigned to new node function. (Actually on MS Windows it is right now not possible at all to bind anything to tab.)

To translate FreeMind into your language

Look for a translation into your language present in the development branch. If such a translation isn't present, take the latest revision of Translate the labels in the text at the right side from = to your language.

You can directly create and edit any java property file in any language using propedit.

This editor can directly edit property files written in Unicode reference characters, and saves the time and effort of converting into Unicode through native2ascii. In addition to the usual functions of an editor, the plugin is integrated with Eclipse and JBuilder. Files can be opened in the IDE and saved in Unicode. It can use by intuitive and simple operation. For details, see Propedit.

Another interesting tool to manage language property files is popeye. Popeye can deal with several language property files at the same time so you can contrast the original property file data with their translations. Also, the program can highlight all properties that do not have a translation set in one of the selected languages.

Alternatively you can save your property file in UTF-8 encoding; this is possible e.g. using Microsoft Notepad. After that convert the file into \uXXXX Unicode escape notation, using native2ascii tool included with the Java SDK. Example of use ( is before conversion):

cd C:\j2sdk1.4.2\bin>
native2ascii.exe -encoding UTF8

Ideally, your file's name will be, where xx is the code of the language (e.g. en, de, dk etc.). Send your translation as a patch afterwards.

To convert \uXXXX Unicode encoded file back to UTF-8, use a command similar to the following.

cd C:\j2sdk1.4.2\bin>
native2ascii.exe -reverse -encoding UTF8

Currently, we have the following languages translated.

Already Translated Languages
Language Language Short If released Translator Reviewer Capitalized Titles
Czech Česky cs not released Radek Švarz Daniel Polansky No
Chinese trad.chinese zh released william chen    
Chinese simp.chinese zh_CN not released william chen    
Danish Dansk dk released
Dutch Nederlands nl released Koen Roggemans No
English English en released N/A Yes
Finnish Suomi fi not released Matti Lassila
French Francais fr released
German Deutsch de released Christian Foltin
Hungarian  ? not released documan
Italian Italiano it released Bob Alexander
Japanese Nihongo ja released Kohichi Aoki
Korean Hangeul kr released(rc5) Kim Jong Woo
Polish Polski pl not released Rafal Kraik No
Portuguese Português pt not released Luis Ferreira
Russian Pусский ru not released Prokudin Alexander
Slovenian sl released Martin Srebotnjak - filmsi No?
Spanish Espanol es released Hugo Gayosso Yes
Turkish Türkçe tr not released Uğur Çetin Yes

To activate a new translation, follow the following steps:

  • write or download the file;
  • unpack the freemind.jar file with 7-Zip or similar into a temp folder;
  • replace or add the with the new one;
  • repack the freemind.jar with the modified content of the temp folder.

To translate the wiki pages itself

See [1] for a description of how to do that. We don't have such a page yet, so, please, be careful.

FreeMind's xml data format (.mm)

FreeMind stores his data in own XML flavor. Up to FreeMind 0.6.5, the xml format has been unchanged. The list of elements and their attributes as of FreeMind 0.7.1 follows.

  • map (root element)
    • version (0.7.1)
  • node (parent element: node, map)
    • id (0.7.1)
    • text
    • link
    • folded
    • color
    • position (left or right, only for children of the root) (0.7.1)
  • edge (parent element: node)
    • style
    • color
    • width
  • font (parent element: node)
    • name
    • size
    • bold
    • italic
  • icon (parent element: node) (0.6.7)
    • builtin
  • cloud (parent element: node) (0.7.1)
    • color
  • arrowlink (parent element: node) (0.7.1)
    • color
    • destination (id of the target node)
    • startarrow (arrow style)
    • endarrow (arrow style)

The actual W3C schema can be found under [[2]].

Libraries and tools used in FreeMind

Sources of free icons

FreeMind uses (a) tool icons used in the toolbars, and (b) icons used in nodes. Especially for the icons used in nodes, a good comprehensive source of free icons is needed. FreeMind uses PNG icons, in the size of 16 x 16. Nowadays many icons are drawn in SVG vector format first, and converted to 16 x 16 bitmap images afterwards.

Ideally, it would not be the task of FreeMind team to draw icons; this task should be outsourced instead. Whether this is a realistic assumption remains to be seen.

Some links on the sources of free icons follow.

More relevant links


Menu Label Checklist

Menu Label Checklist Poor Good
In English, use capitalized labels Move to root Move to Root
Menu items leading to a dialog should end with ... . Open
Close ...
Do not repeat the verb already used in the menu heading Export > Export to PNG
Insert > Insert Hyperlink
Export > As PNG
Insert > Hyperlink

To implement embedded images

To implement embedded images, one would store binary data in a node, like <node TYPE="image" BINARY="x4543edvc...45ert"/> Upon opening the node for viewing, temporary file would be created and HTML viewer would point to that file. Upon editing, external image editor would be opened to edit the temporary file, like Gimp.

Improved HTML editing

FreeMind's long node may contain HTML. However, it needs to be edited in its source text form. We can improve upon that by

  • providing WYSIWYG HTML editor embedded in FreeMind, like Java based eKIT (project page LGPL licence).
  • enabling using external WYISWYG editor for editing HTML, like Microsoft FrontPage. This editor would be automatically opened upon clicking an HTML node, displaying it in WYSIWYG way. It is not clear how to get the changed node back to FreeMind. One option is to generate a temporary file, passing it to the external editor upon calling. However, how does the external editor tell FreeMind that the editing has ended? Futhermore, should such editing be modal? How to ensure such a modality and not get locked in it when the external editor crashes?
There is already some work done on integration of the WYSIWYG HTML editor Kafenio into FreeMind. --Danielpolansky 10:51, 6 Mar 2005 (PST)

Open Source WYSIWYG HTML editors in Java

There are the following open source WYSIWYG HTML editors written in Java.

  • eKit — LGPL licenced
  • Kafenio — LGPL licenced, developed as a fork of eKit
  • SimplyHTML — GPL licenced

Using HTML versus XHTML in rich text nodes

What follows is a preliminary analysis of the issues concerning HTML versus XHTML used for rich text in FreeMind.

AFAIK there are two separate questions: (1) should we store (a) HTML or (b) XHTML in nodes, and (2) should we (a) store only one thing or (b) store plain text in one attribute, and store HTML/XHTML in another attribute where HTML is available, modelling on email systems.

As for the first question, using HTML has the advantage of being straightforward: it is supported by JLabel, it is supported by Java HTML editing component, and it is the format now mostly used in web pages. An advantage of XHTML is that it is a flavor of XML and thus easily amenable to XSLT processing.

As for the second question, as soon as we would store also plain text, it would be automatically available to all XSLT processing, which would make the first question less decisive. However, it would considerably increase the size of mind maps stored on the disk, by my estimation by factor 1.5 as soon as a lot of rich text would be used.

Performing transformations of HTML to XHTML on the fly before performing preprocessing from FreeMind would not really save the day, as XHTML would still need to be stored in mind maps on the disk; if we would use HTML internally, we would have to convert XHTML to HTML upon loading a new map for all nodes, instead of doing that only upon nodes being shown for the purpose of JLabel.

If you find the other options more attractive, an important question is: is it really possible to process XHTML from within an XML attribute? Can someone demonstrate that? If yes, that would make XHTML rather attractive. But if not really, then using HTML would be as good as using XHTML.

Converting HTML from node attribute TEXT to plain text within XSLT

Converting HTML from node attribute TEXT to plain text within XSLT is virtually impossible. XSLT does not feature regular replaces, and it does not even feature simple text replaces (simple text replaces can be sort of implemented within XSLT though). My old view on this option follows.

I estimate that the most straightforward way of solving the related problems is to find out how to convert HTML into plain text within XSLT script. I currently do not have a sufficient knowledge of XSLT to judge on that; it should be possible using several regular expression replacements, modelled on what we already have in FreeMind in Java. As soon as we would be able to do that, there might even be a regular expression way to covert boldface and italics to open document format of OpenOffice. Admittedly, instead of having one conversion routine from HTML to plain text in FreeMind, it would have to be replicated in every XSLT script dealing with FreeMind mind maps.

Storing XHTML on par with FreeMind XML

The option of storing XHTML elements on par with FreeMind XML elements like <node> would require a considerable effort. The benefits of the effort would include

  • + better support for XSLT transformations
  • + more readable XML of FreeMind mind maps

The costs would include

  • - switching away from NanoXML/Lite to a more bloated technology for reading and saving of mind maps, meaning considerable slowing down upon loading and saving of mind maps. (That is not true; I was wrong. We would only have to adjust NanoXML so that it stops parsing XML within certain elements and reads everything within them as uninterpreted string instead. --Danielpolansky 06:34, 13 May 2006 (PDT))

By storing on par, I mean the following.

        <body>Hello </br> Dolly.</body>

I recommend to avoid this option. Out current option is

    <node TEXT="& lt ; HTML & gt ; Hello & lt ; br & gt ; Dolly."/>

A discussion shows the following possibilities of storing on par.

  1. Storing HTML directly like < node >< html ></ html ></ node >
  2. Storing HTML within content element like < node >< content >< html >< /html ></ content ></ node > and
  3. Storing plain text within TEXT attribute of node element
  4. Storing plain text as < node >< text >Plain</ text ></ node >
  5. Storing plain text as < node >< content >Plain</ text ></ node >

Converting HTML to XHTML in Java

I find a conversion of HTML to XHTML possible with reasonable effort. I think there are not many more subtleties apart from those already addressed: closed tags < td >, < tr > and the like, closed tags < /br >, < /hr >, < img/ > and several others. We would be able to discover all the subtleties by reading XHTML standard and by empirical testing. (For reference, html2xhtml at, thanks to Dimitri)

However, W3C points out that converting HTML to XHTML is a tricky business.

The main problem of developing your own converter is that either you are sure your HTML is correct (and so you only need to fix cases, quotes in attributes, entitities and close the few HTML empty tags) or you will go crazy trying to cope with all the possible errors that the "official" web browsers accept but that would kill any simple parser.

See also Convert HTML content to PDF format at JavaWorld using JTidy.

Converting XHTML to HTML in Java

Searching the web using the expressions

  • "XHTML to HTML" java
  • XHTML2HTML java

I have found very little about already existing code for converting XHTML to HTML in Java, with GNU GPL licenced code. Thus, my recommendation is to create a new method for that, in the class Tools. The method would be created with the use of [1] as a checklist. The method would use regular expression replaces, unless we see that this is too slow, which I do not think will be the case. (We already use regular expression replaces in method update() of NodeView.)

A preliminary code is as follows.

   public String xhtmlToHtml(String xhtmlText) {
      //Remove '/' from <.../> of elements that do not have '/' there in HTML
      return xhtmlText.

See also

  1. Discussion on converting XHTML to HTML using XSLT (can be checked against when developing conversion in Java)
  2. XHTML2HTML in Java, albeit needing some Perl package which is difficult to understand. As old as of year 2000.

Requirements on file format of FreeMind

We have identified the following requirements on the format of FreeMind. These have different priority; people may disagree about what the priority of their requirements are.

  1. guarantee file format integrity, i.e. XML conformance.
  2. be flexible for new features like (x)html, svg, mathml,...
  3. stay reasonably backwards compatible, so that all existing generators of FreeMind mind maps work with later versions of FreeMind too. Put differently, create new format only as an extension of the old format, that is by adding new elements and attributes only
  4. new format should allow for import of all old format features (from stable versions).
  5. limit redundancy of information.
  6. keep it easy to do XSLT transformations.
  7. keep the format as simple as possible.
  8. make it easy to create and edit mm files manually in an editor like Vim, Emacs or Notepad.
  9. make it easy to create mm files programmatically.
  10. the solution should be fast.
  11. the solution should be safe.
  12. the file format of both notes and nodes should be XHTML (a further specification of the first requirement)

For Danielpolansky, the requirement on staying reasonably backwards compatible is important; the requirement on the solution to be fast too; the requirement on XSLT transformations is completely unimportant in view of the possibility of replacing XSLT transformations with small Java functions doing the same with less footprint; the requirement on keeping the format simple is important; the requirement on making it easy to create mind maps programatically is important.

Sources of HTML coming to mind maps

Rich text in the form of HTML will be coming into FreeMind from the following sources:

  • directly entered in FreeMind using WYSIWYG editor
  • pasted from web pages
  • pasted from Microsoft Word documents, and other applications exposing HTML to the clipboard

To my experience, the pasting is much more usual and of higher volume than direct editing.

See also

--Danielpolansky 03:29, 29 Apr 2006 (PDT)

Rendering of HTML nodes is slow

Rendering of quite long HTML nodes is slow. If you have a HTML page corresponding to ten paper pages, then the rendering of the node upon unfolding takes several seconds. The related code is in the method update of the class NodeView. What takes so long is the statement


in the section

       if (nodeText.startsWith("<html>")) {
          // Make it possible to use relative img references in HTML using tag <base>.
          if (nodeText.indexOf("<img")>=0 && nodeText.indexOf("<base ") < 0 ) {
             try {
                nodeText = "<html><base href=\""+
                   map.getModel().getURL()+"\">"+nodeText.substring(6); }
             catch (MalformedURLException e) {} }

This result does not give us much hope of improving the speed easily, as the command just tells Java's JLabel to render the page. A solution would be to find a different HTML rendering Java component. We can also wait until Sun's Java virtual machine improves the speed of JLabel's HTML rendering.

-- What about pre-loading nodes which are likely to be expanded, using threading? Keep some relatively small cache of nodes in proximity to the last expanded node, and swap in the expanded node when the unexpanded one is clicked. No?

To obtain focus for selected node in reliable manner

Requesting focus for NodeView using requestFocus() method is unreliable. A reliable way of doing that has been implemented in the method obtainFocusForSelected() of Controller. A typical call in is


Requesting focus using


where newSelected is a NodeView is unreliable, though most often works.

To set the class load path in in jar

In the source folder tree of FreeMind, there's a file MANIFEST.MF. This file tells what should happen with the freemind.jar when java tries to run the jar archive. The file may look like

Manifest-Version: 1.0
Main-Class: freemind.main.FreeMind
Class-Path:                  silk.jar nanoxml.jar ekit.jar kafenio.jar
            kafenio-config.jar kafenio-icons.jar gnu-regexp-1.1.4.jar
Created-By: Joerg Mueller

A tricky thing about the file is that the length of the lines can be at most 72 characters. That creates difficulties when specifying Class-Path. In the exaple above, the first line of Class-Path is set in such a way that it has 70 chacters. That has been achieved by putting spaces before the actual list of classes. In the freemind.jar, the file can be found in the folder META-INF. Here you can check if the manifest has been created correctly.

Deleting nodes and branches in FreeMind

Since version 0.8.0, it is possible to delete a whole branch of nodes by pressing DELETE. When a user accidentally presses DELETE and does not notice that, they may loose considerable amount of data. For users using FreeMind as a knowledge base or a semi-structured database, being able to delete whole branch at one keystroke is problematic and unusual; in filesystem browsers, users are asked for confirmation before the file is deleted by the system.

However, some users use FreeMind as a mind mapper and are glad to be able to delete nodes just by pressing DELETE.

There are several solutions to this problem.

  • Add user option to enable or disable confirmation before deleting of nodes and branches (depending on model type)
  • Store all deleted nodes and branches in a kind of trashcan associated with every mind map
  • Ask for confirmation only for nodes with children
  • Ask for confirmation only for nodes with more than p children

The confirmation would be requested both for keystrokes DELETE and CONTROL + X, that is the actions Delete and Cut.

More development pages

Documentation efforts

See documentation efforts. Also, internals documentation at Under the covers.

Short patches

See short patches.

Community development

Personal tools