Great day to everyone.
I'm trying to design an application that is basically a to-do list, which of course provides some level of master-detail: a list of tasks and the detail for each task.
Now, the extra feature that this application will provide will be a graph that displays dependencies between all tasks. And here's the challenge: since this generated graph is useful as a master view of the general list, it should be displayed as well.
So, I have two sections: a master overview, a master list (with add / remove capabilities) and a detail view.
How can these be designed so that it flows a naturally usable way?
This is what I have so far, which is not close to something that makes real sense to me.
What is the proper approach to this master-master-detail need? Or maybe there's no such thing as master-master-detail?
Update: After Izhaki's feedback I put together a second iteration where the upper panel is what actually gets displayed all the time: the list and the graph overview. The details panel gets hidden or shown if necessary to edit detail, so thanks to that it has become a more common master-details approach.