Exporting

The User Guide articles on Exporting are here: Exporting from Topicscape.

I exported to FreeMind, but the map just has one topic

Topicscape can import from FreeMind 0.8.0 and 0.9.0, but when you export to FreeMind, you must run FreeMind 0.9.0 or later to see the resulting 2D map. Topicscape needs to use elements that are not present in 0.8.0.

My large Topicscape exported to OPML is very slow in the browser

Topicscape can export an OPML file which can be viewed in a browser, and has collapsing branches.

A very large Topicscape will produce an OPML file that, depending on your computer's performance, may indeed be slow to render in the browser, and slow to collapse or expand branches. This is a browser limitation.

Difficulty opening the OPML file

"When I export a Topicscape or part of a Topicscape to OPML and click on the XML file, I get a message saying 'This file does not have a program associated with it for performing this action.' (or 'Windows cannot open this file'). What can I do?"

Generally users will be able to view OPML files made with "Export to OPML" in a browser window. This uses a small script that we include with the exported file, and allows you to collapse or expand branches to explore the Topicscape just exported.

To view the OPML in a browser you should check the xml box. In the folder that you define as the destination for the XML file, Topicscape will add another folder (called "opml"). This contains the files needed to display the OPML file with branches that collapse or expand in the browser window. The files will be opml.css, opml.js and opml.xslt.

For browser viewing to work properly, you must keep the .xml file in the same folder as the opml folder. If you only saved an opml file and you want to view it in a browser, just change the ".opml" extension to ".xml".

If you cannot open the file by double-clicking, please first ensure that the "opml" folder is in the same folder as the xml file. If it is in the right place, then this will be because you have another application that has changed the file association for .XML when it was installed.

This can be overcome by opening your web browser first and dragging the xml file to its window. Alternatively, you can right-click the xml file and choose "Open with..." and choose Internet Explorer from the list.