|
Enhancements requests from the issue tracker Tell us your ideas about labyrinth and we will add them here or add them yourself. - Speech bubble
Show extended info as a speech bubble that can be opened and closed.
- Fly by presentation
Start a presentation by zooming out and show the complete mindmap. Select a thought zoom in smoothly and show the extended content beside the thought if the user is near enough the thought. After selecting the thought again zoom out again smoothly to see the complete map.
- Tomboy Applet Style
Add Labyrinth to the applet panel and manage maps like Tomboy does with notes. See Issue 77 for some mockups provided by frandavid100.
- Gnome integration
Theme, Drag and Drop, ...
- Grouping of thoughts into "meta-thoughts". This would basically colour a region behind the thoughts to it was clear the thoughts are in related areas. Moving the big coloured area would move all associated thoughts. Moving a single thought in the backgrounded area would only move that thought.
- A11y. My initial idea was to make thoughts visible to a11y tools. But this is (very) difficult and doesn't really aid in a11y for some circumstances. To compliment this / replace this, I thought about having a treeview of thoughts, with the children being sub-members. This would get us free a11y through the GTK treeview implementation and still preserves some of the information in the map. Thoughts which are children of multiple nodes could be italicised or marked in some way. It's not a great solution, but what I came up with. ( Issue 97 )
- Exporting. For images, exporting of extended buffers is never going to happen. However, for pdf / ps / printing, it'd be nice to have an option to include the extended buffers somehow. I'm not sure of the mechanism for doing this. Maybe have each thought with an extended buffer assigned a small number, which is put in the top right, followed by the extended thought below, with the relevant number. This doesn't sound clear at all. I'll do a mock up at some point.
- Speed. I know Matthias has implemented some speedups, but there are more available. The biggest problem is when moving the canvas around, as all thoughts visible must be redrawn every movement. Maybe we could get around this be keeping a cache of the current view and blatting 1 that at the correct offset and only redrawing everything once movement has stopped.
- Speed (2). Another slow-down is moving thoughts around. One solution to this is to track which thought caused the redraw and pass this to every link we request drawing. The link would then know if it's associated with that thought and draw itself. Maybe it'd be enough to only draw the thought and all links. There's also an issue here with dragging thoughts over other thoughts. Guess we'd need to keep the original and new coords and redraw that area.
- More keyboard navigation possibilities.
- Import from (at least) kdissert and freemind
- Printing support for maps
LinksImage Thoughts- Abbility to change images
Drawing Thoughts
|
Sign in to add a comment
What about having a straight line option to join thoughts with a handles to allow right angles at a minimum? Doing so would allow for very easy/fast creation of Work Breakdown Structures (which are pretty much mind maps if you think about it!)
Also the ability to number thoughts hierachically ie from top node which would be the map name the next level of thoughts would be 1,2,3... and then child nodes of 1 would be 1.1,1.2 etc.
The ability to assign direction to links would be handy.
Hyperlinking between maps would be extremely cool (or alternatively zooming into and out of embedded maps).
For version 0.4 most of the interface is mouse-driven, yet adding (or removing) a link means you either have to use what would be a right-handed key combination on a QWERTY keyboard (Ctrl-L) or click twice through the edit menu. At the least a corresponding toolbar item for the Ctrl-L functionality would be an improvement; a "Linking Mode" would be even better as you avoid having to multi-select nodes in the first place.
Keyboard Shortcuts
Insert to add child Return to add sibling
I'd like you look at this software MyMind? (MacOS). Its interface is so simple and efficient. I'd like that you provide the same feature (texte and map combined). http://www.sebastian-krauss.de/software/mymindscreenshots.html
This software has real potential to become the simplest mind-mapping tool available. To keep it that way, the simple interface shouldn't be bothered with tens of extra cool edit tools with hundreds of options. If there will be more options, those should be very well planned ones.
Simple programs usually means fast editing. That part of the program could be improved considerably. Simple and well-known keyboard shortcuts can speed up the editing by lot and I mean LOT. There don't have to be thousands of them, just some basics like CTRL+B for bold text, INSERT for adding childnode, CTRL+ARROWS for moving nodes.. just some basic things like those.
I really like how the program feels right now. There are plenty of mind-mapping programs with huge set of tools and options. Lets them keep their complexity, this software doesn't need that.
Additionally I will add some commentary about the name Labyrinth. Yeah, it's really describable name for mind-mapping but it isn't very unique as a word. I talk about visibility. There are so many other projects and things named Labyrinth which can make reaching the software somewhat hard. For example when ranked with Google Search, the placement is 23, which is pretty good in this situation. Of course "labyrinth mind mapping" returns placement 1, but that isn't enough in my point of view. That's quite minor thing but good to make note for, expecially in new projects. Keep it up!
I have been toying with some mind mapping ideas, and now stumbled across this project. It seems like it wants a lot of the same things that I have been thinking about, but I have some ideas I don't see here (at least not immediately):
Somewhat bigger than todays aim, yes. But it could become a real killer app. The great thing is it could start small as long as the foundation is right. Get the base libraries defined and just implement what is needed for the current level of functionality. Borrow plugin architectures for both libraries and the application. Keep the actual application as clean and lean as possible.