floating
Ability to have more than one master node on the same map - i.e. a floating nodes. I see that other tools such as mindomo offer this feature.
you can now add multiple roots, disconnect nodes and float them, and manage multiple maps in the same file on mindmup 2.0.
If you use google drive, use https://drive.mindmup.com
if you use free storage or Gold storage, use https://app.mindmup.com
-
X-Raym commented
Floating nodes will be awesome and allow us to do more complex mapping, such as concept mapping (which is less hierarchical than mind mapping, and require such things)
-
Martin Jackson commented
In terms of the heatmap idea the provision of a floating toolbar for the progress colour palette get around the need for a multi-root map in this instance - originally I had to add another child node to show the colour keys. I am looking forward to giving this a run in the next couple of days. Thanks for all your efforts so far - it looks good!
-
>> I don't understand where this fits with "ability to have more than one master node on the same map"
The original request for for more than one master node in order to show a legend. we solved that problem I think a lot better. I still have to be convinced of the usefulness of multi-master maps. Conceptually, I don't really see how this is different from a single map where would-be roots are effectively first level nodes. If anyone can explain why multi-master maps are useful, we might do that as well.
-
Anonymous commented
I don't understand where this fits with "ability to have more than one master node on the same map"
-
michael commented
I would like multiple roots as well, not just for comments, but because I want to create a map as I'm learning about something, before I know its structure, so I may start with a forest of trees. it may turn out that I eventually can make them into a single tree, but it may not.
-
Martin Jackson commented
I have just thought - the concept of the "key" node with colours rolling up the hierarchy is somewhat similar to what other people have written about with numbers rolling up - such as planning estimates - value points - etc. maybe there is a higher domain concept here that could be worth exploring.
-
Martin Jackson commented
If anyone likes the "heatmup" concept - then should we start up another topic to vote on it? Anyone else have any other multi-root ideas that might help us to an even better generic concept?
-
Martin Jackson commented
I suppose I am thinking of both types. I like the concept of "multi-root maps" as it is a better description of what I meant by floating nodes - it feels more generic and would probably get more votes. I see the comment node as a special type of root node. I can see that annotating sections of the map with a comment box would be good - but you would need a way of anchoring it to the objects around it so that it moved around with the block - invisible lines maybe?. it would also have to be a different shape/border etc to indicate that it isn't a live node. Another example is a heatmap (or heatmup !) in which I am using colours to indicate the current status of the node in the tree (i.e. Red-Yellow-Green etc). What you could do then is have a "colour-key" node in which you place the colours in preference order. So if a leaf node is RED then all its parents up to the root node go RED. i.e. RED is the highest order. GREEN is the lowest order - ie. all leaf nodes under a parent node have to be GREEN before it turns GREEN. The colour key is on the "heatmup" and the order they appear controls the precedence order. I am doing this on my diagram by hand at the moment. I find it an awesome way to track progress on my current project. As an when branches go GREEN I simply collapse them down to hide all the detail. It really shows if the team is doing too much across too many areas. If you could actually make a node a reference to the root of another heatmup then I would be heaven !
-
Anonymous commented
Another example might be a comment relating to a set of sibling nodes that are the members of a list. You don't want the comment to be mistaken as another member of the list . Another example might be a Node expressing a relationship between 2 nodes that are on different branches of the hierarchy.
-
Martin Jackson commented
I am trying out using a mindmap as a quick and easy way to track the QA work for a release. Being able to colour code stuff makes it really easy for people to see what is going on. The problem with having to link everything to a central node is you lose control over the positioning of other nodes. For example take a look at my evolving diagram http://goo.gl/G3VEV Here I wanted to add a colour key but I had to add it as child of the master topic. It would be much better if it floated. In addition there are other streams that are in progress that I want to represent on the diagram that are not related to the central node directly. Another way to think of floating maps is that they are maps with invisible lines connecting them. The floating idea could also be useful when thinking about showing non parent-sibling relationships. i.e. the two maps are separate and then you connect two nodes together with a different (maybe directional, maybe labelled) between the two maps. At the moment you can only impose a parent-sibling relationship.