You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2023. It is now read-only.
There are many mindmapping programs out there - mindmeister, Xmind, MindManager etc. commonly mind mapping programs are bloated with features.
Also other lightweight mindmapping software are out there. I reckon user needs vary so much that it is impossible to strike any great balance without allowing users to explicitly enable functionality.
There are many features I would like that others would be put off by, and I imagine many features others would want that would put me off.
Have you considered a plugin system?
Possible related considerations:
Whether there is a fixed set of plugins
1.1 Plugin interoperability? probably easier with a fixed set
1.2 Awareness of other plugins' concerns could become very difficult as the set expands - becoming potentially even more messy than if the plugins were just always available
Granularity of concern for plugins - on a "node type" basis? larger?
What steps / common interfaces may be necessary to prevent plugins from stepping over each other's toes?
The text was updated successfully, but these errors were encountered:
this is a very interesting question! I had already thought of implementing a plugin management in the mmp library. But I had not yet asked myself these questions.
I was initially thinking of a dynamic set of completely independent plugins. But we could think of a solution that includes dependencies. If you want to discuss more in depth, contact me on slack in the public Mindmapp channel!
There are many mindmapping programs out there - mindmeister, Xmind, MindManager etc. commonly mind mapping programs are bloated with features.
Also other lightweight mindmapping software are out there. I reckon user needs vary so much that it is impossible to strike any great balance without allowing users to explicitly enable functionality.
There are many features I would like that others would be put off by, and I imagine many features others would want that would put me off.
Have you considered a plugin system?
Possible related considerations:
1.1 Plugin interoperability? probably easier with a fixed set
1.2 Awareness of other plugins' concerns could become very difficult as the set expands - becoming potentially even more messy than if the plugins were just always available
The text was updated successfully, but these errors were encountered: