The use of separate descendants for attendees is usually because it is a larger, more formal meeting where many new people are being introduced and the tree structure gives me more room to capture relevant information about each as they are introduced. Sometimes I'll put attendees in a meeting in detail under the main node for the meeting sometimes I'll use a separate child node labeled "Attendees" with children appended there for each person at the meeting. Notes are usually reserved (in my use case) for after the meeting when I'm trying to make sense of what was said or to add my own reactions or ideas post meeting-I can go in there and ramble to my heart's content without changing the key points made in the meeting, opening up huge areas of thought when/if desired, still a part of the map, but out of the way.īut, truthfully, the whole division between details and the creation of a separate child node that does the same thing is much more art than it is science. The presence of this detail information is discretely indicated by the little triangle so I can quickly "windowshade" it in or out of the visual space of the map. Nodes and their children capture the flow of the meeting and the key information points details are used to capture enhancing information that is easily "toggled" off and on when desired to avoid cluttering up the map with incidental information. Of course, I COULD have put the extra information in a child node, but that information isn't really related to the agenda of the meeting. The main point is preserved, but the details provide some additional information that might be helpful when reviewing notes at some point later. The node might contain information like "Meeting to discuss new product rollout" but I'll use details to put "Where: Manila Time: 10:30am". ![]() Details work best for those things that may help to define the node without cluttering up the map with paragraph-style entries.Ĭonsider one simple example: Say I'm using FP as the very best notetaking tool out there (IMNSHO), a very frequent application for me. In my own case, I find notes to be the very thing for extended "word processing" (such as drafting a paragraph for use in a separate paper, based on the basic idea captured in the node container). Which you choose depends on what you want to do.Īs far as which tool to use for which use, additional experimentation, coupled with your own way of working will dictate. The first is quicker, the second offers some basic formatting options (bolding, italic, bullets, tables, etc). ![]() ![]() So, for example, you can edit nodes by simply double clicking in the interior of the node, or, you can open a Simply HTML editor window. With the exception of Notes which is restricted to editing in a separate window, all of the others can be edited by means of either their own discrete "window" or via an "inline" mode (activated by double clicking on the content), where you are editing the container directly without the use of a separate editor window. There are many information containers within Freeplane, e.g.:Īll of these have distinct properties that make them ideal for various tasks. Playing with the features is the best way to decide how each best suits what you're trying to do, even if the process of discovery isn't always "pretty". ![]() The sometimes staggering breadth of features in FP can make for some (momentary) confusion about how best to use the product for YOUR use. Well, I think you've just discovered the power of FreePlane!
0 Comments
Leave a Reply. |