MinDcard v2.0 is now available for purchase at the Apple app store. This version is primarily a refinement (both internal and user visible), but it also includes several notable feature enhancements. These changes include; Supports Freeplane 1.2.18 (in addition to FreeMind 0.9.0) During the initial development of MinDcard, Freeplane was updated from 1.1.3 to 1.2.18. This update catches up with the latest stable version of Freeplane. MinDcard will support FreeMind 1.
MinDgo v5.0 is now available at the iTunes App Store. This upgrade includes support for Freeplane’s 1.2.18 file format changes and includes additional icons. Note that MinDgo discards features that it doesn’t directly support when importing files. This means that some features may be lost when a mind map is (for example) created in Freeplane, imported into MinDgo and then exported back into Freeplane. Although MinDgo will support more features over time, the diverging file format and features between FreeMind and Freeplane will make full feature compatibility unlikely.
MinDgo v4.1 is now available as a FREE download from the Apple App Store. What’s New in Version 4.1.0 (since v3.1) Added support for iTunes File Sharing (requires iTunes 9.1+ and iOS 4+). Enhanced file imports; importing mind maps is 10x faster, uses less memory, improved error handling. Improved error handling when editing rich-text nodes. Minimized analytics tracking. Bug Fix: Empty nodes caused the back button to disappear.
There are several compatibility issues between MinDgo v4.1 and Freeplane 1.1.3 that make this version of MinDgo inappropriate for use by Freeplane users. The most serious of these issues concerns the format of the FONT element in the Freeplane data file. Freeplane appears to be more flexible regarding the structure of this data element than FreeMind. MinDgo can’t handle this difference and may fail to import the file. A fix will involve an update to the apps data mode and is in the works.
Dropbox has deprecated the v0 API, used by MinDgo, and will completely drop support on December 1, 2012. In order to continue supporting Dropbox, MinDgo will need to use the v1 SDK which requires iOS 4.0 or higher. So in the near future MinDgo will need to make a decision to either (1) drop support for pre-iOS 4 devices or (2) drop support for Dropbox.
A minor update to MinDgo is in the works that will help identify parsing problems when importing mind maps. As you know, MinDgo imports and exports FreeMind compatible data files. The problem occurs when these files contain badly formatted XML which can easily happen as a result of bad HTML markup in rich-text nodes or notes. When MinDgo encounters such errors, it simply stops processing the file, resulting in a truncated mind map and no error or warning is displayed to the user.
MinDgo v3 is now available in the Apple App Store. What’s new in MinDgo v3 Functional Changes: New support for Rich Format and Plain Text nodes. Node Styles (added in v2) have been replaced by Rich Format support. Support for iOS 5 Visual Improvements: Cell Shading: Mind map nodes are now shaded, providing greater visual separation. Child Counts: The display of node children has been visually enhanced.
The next chapter of MinDgo is being written. This version will include support for Rich Format (as well as Plain Text) nodes. There’s some visual refinement including text and child node count shading. This version will of course support iOS 5 while retaining support for iOS 3.1.3. The first screenshots on the right illustrates some simple text formatting made possible with the new Rich Format nodes. The second screenshot shows some of the visual enhancements made to increase productivity.
MinDgo v2.1.1 is now available for download from the Apple App Store. This version fixes a few bugs discovered shortly after the release of v2 and does not contain any new features. MinDgo v2 bugs fixed in v2.1.1: Swipe deletion of nodes no longer works. Nodes can still be deleted using Edit mode. Export of local mind maps causes the app to crash. Dropbox backed maps are still exportable.