@savantier, You are expertly focusing in on the point that’s bugging many people here!
Nevertheless I would like to add my perspective to this- and Your pictures are putting out the reasons nicely as well.
- To have the checkboxes in a non- indented row and having the status coded in this element greatly facilitates quickly checking what is important.
- the “empty indenting rectangles” in Your pictures greatly support getting an idea of the underlying project structure / tasks and subtasks hierarchies
- data density: the first picture so very much captures why I eventually got overwhelmed by OF, making me search for easier alternatives- only to find that complicated project structures are only to be simplified to a certain level, before losing oversight again… I am more than happy that Omni is trying to find a middle ground for 2.0, while keeping adaptability in the back hand.
So basically for processing a long list of projects I first look right for task status, then mark the row of choice and look for the hierarchy involving this specific task. Adapting to this method was instant for me.
With the density update a couple of days ago Omni for me have hit the sweet spot between oversight and loss of screen estate. It will be nice to have the option to actually adapt this varying requirements, but as of now I am really happy with what I am working here.
Happy easter holidays to all!