#1315 Allow various "profiles" for styles (and related settings) to be stored and loaded
Currently, when I create a custom node style, it's not stored in my .mm file, but apparently globally: When I create a new map document, my custom style is available there, as well.
This is often not desired, because styles are used for semantic distinction of nodes, which only makes sense in one use case, not in others. For example, I have defined some node styles for one of my tasks, "reading scientific publications". My custom node styles are "read paper", "irrelevant paper", "dead-end (not available paper)", "cited", "cited by", etc. I create a new map for that task with every new research question, and in each of these maps, I need these node styles, and only these node styles. When performing some other task, I might need a completely different set of node styles (possibly some of the pre-defined ones such as "Important", "Question", "Idea", etc. - which I actually dislike to see in the menu during my "reading scientific publications" task, but I cannot delete them because I fear they'll be gone globally rather than just for that one map).
Hence, it would be great if I could save various independent sets of node styles as a "profile". cf. general-purpose diagramming applications which usually offer various sets of symbols/connectors that are almost always used mutually exclusively.
On an additional side-node, I have assigned keyboard shortcuts to my node styles, so I just need to select a node, press a key and it gets the desired style. It would be great if those could be saved along with a profile - of course, this might create problems in case a shortcut defined in the application clashes with a shortcut defined in the profile. My personal stance on this would be to give the profile-defined shortcut prevalence because this would make the application-defined one the "default setting" unless temporarily overridden by the currently loaded node style profile.
---- additional_information ----
I'm using the latest available stable Freeplane version, 1.1.3.
I have added a new feature request #2361 for linked style.mm files which may affect this request too.