xihesi / chartr

Automatically exported from code.google.com/p/chartr
0 stars 0 forks source link

automatic placement #73

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
I really want to ditch Freemind, but couldn't find mindmapping software
that did focus on actual contents like Freemind does, instead of focusing
on positioning/fancy colors/gimmicks.

Freemind's user interface is HORRIBLE, but, they got something nailed down
real good: 
1- you don't have to worry/think about placement of thoughts, visual
layouting, and generally wasting time moving things around ending up with a
messy mindmap
2- their entire app can be used with the keyboard only

So I would like a mode for chartr to create thoughts and they get
automatically positionned -- the user, in this mode, cannot change the
placement of thoughts (for technical reasons I would think).

This leads to much quicker and cleaner creation of mindmaps, with the only
drawback being that it somewhat limits freedom of designing the mindmap
(but I have not missed that part). I can create in a few minutes a mindmap
that would take me hours in chartr.

We could even change the way the user interacts with the gui completely in
this case. It could be designed like this:

- a sidebar on the left allows entering thoughts in hierarchical order,
maybe using a gtk treeview or sourceview
- a pane at the bottom allows editing the details of a particular thought
- a "preview" area on the right shows the result as a mind map in real-time

So, it could look like this:

_______________________________
|     |                        |
|     |   mindmap area         |
|     |                        |
|     |                        |
|     |                        |
|     |                        |
|------------------------------|
|  comments on a thought       |
|                              |
°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°

Where the user only interacts with the left and bottom panes, and then he
can export the mind map afterwards.

Original issue reported on code.google.com by nekoh...@gmail.com on 23 Nov 2008 at 6:42