Preview releases

Preview releases offer you a possibility to try and test new features. I still have to add additional customisations and exception handling, but you should be able use the basic feature. The feature has also not been tested thoroughly, so do not use your regular GTD mind map and todo.txt file or make at least a proper copy of them. Any feedback is welcome in the related thread on the forum or in the comments of the ticket describing the Feature. I hope to use your comments to improve the final release of the feature.

Installation

https://sourceforge.net/p/gtdsync/wiki/Installation/

Quick start

Press Ctrl+F1 after installation.

V0.7.7-pre01: Preview enhancement, bug fix and refactoring

• Feature #8: Archive completed actions to another mind map (preview)
• Bug #25: Cancelled GTD Sync on wrong mind map leaves language attribute in root node
• Task #29: Regroup language keys for better recognition

The Archive function is built and can be tried and tested. In the final release the ability to choose the archive mind map and some file checks will be added, see scenarios not tagged @preview and @done in Feature #8. Many thanks to Evereasy for providing the basic script.

In the meantime Bug #25 is released in v0.7.7 together with some other bugs. Feature #8 and Task #29 will be released in v0.8.0.

Description Archive function

The Archive function archives a selected completed action or all completed actions in the child tree of the selected node to a specified archive mind map. The Archive function moves every completed action, i.e. selected directly or by selecting a node in its parent tree, to the end of an identical branch in the archive mind map. If the path between the root node and the completed action does not exist or partly exists in the archive mind map, the Archive function will recreate the missing nodes.

Preparation:

If you already have a mind map to archive your completed action, rename it to "Completed Actions.mm" and place it in the same folder as you GTD mind map. If you do not have a mind map for archiving, you do not have to do anything: "Completed Actions.mm" will be created automatically in the same folder as your GTD mind map. Probably needless to say: you need a GTD mind map containing completed actions imported from todo.txt or marked as completed with the function of the same name. You should have synchronised your GTD mind map with todo.txt at least once.

Usage:

• Select a single completed action and press F4 - the completed action will be archived
• Select a single node that has several completed actions in the child tree and press F4 - all completed actions in the child tree will be archived.
• Select the root node of the GTD mind map and press F4 - all completed actions in the GTD mind map will be archived.

Exceptions:

• If you start the Archive function from a mind map that is not a GTD mind map or a GTD mind map that has not yet been synchronised with todo.txt, it will abort and inform you that you should use a synchronised GTD mind map.
• If the archive mind map already contains a node with the same name and position as the completed action to be archived, this completed action will not be archived and you will be informed that there is already a duplicate of the completed task in the archive.
• If the path for the completed action to be archived branches into two or more nodes with the same name as the node in the original path, the completed action will not be archived and you will be informed that there are duplicates in the archive path.

Notes:

• The function only works on one single node. If you select more than one node, Freeplane randomly chooses one of the selected nodes for further processing.
• Whether a node already exists in a path in the archive map is evaluated by its name. So if you have siblings in your GTD mind map with duplicate names, those nodes will never be duplicated in the archive mind map but appear as one node.
• The order of sibling branches under a parent node might differ between the GTD mind map and the archive mind map.
• The function does not support movement of projects or nodes that will change their paths to the root node. So you can reorder nodes or projects in relation to their siblings, because that will not change that path. But if you, for example, archive a completed action for a project, then move that project up or down its branch or to another branch and then archive another completed action, the project will be recreated in its new position, leading to a duplicate. So if you would like to use the Archive function and avoid duplicate nodes in the archive file, do not move nodes in a way that changes the branch of underlying next actions. Note that this kind of movement is also not necessary for GTD Sync to do its job. Of course you need to change the basic structure of your GTD mind map now and then. Then you should change the structure of the archive mind map accordingly. If for some reason you need to move projects around in your GTD mind map often, you could prevent duplicates by archiving completed action once per project, at the end of its life cycle.