Single tree root serves no purpose and prevents multiple projects
In the tree view it should be possible to have several items at the top level.
Examples:
If 'Book' is the top tree node, and Chapter-1, Chapter-2 and Chapter-3 are in the level below, it is not possible to have multiple books.
If a 'single' Book is being worked on, then it is needed to have Chapter-1, Chapter-2 and Chapter-3 at the very top level.
The current top level item does not serve any purpose!
(This is a low effort Item. See link to successful example.)
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- ianp5a
Related branches
Related bugs
Sprints
Whiteboard
This is a chicken-and-egg problem. Basically it is: do you want to see the root node or not? You can rename the nodes any way you'd like, so the problem you've described is easily solveable by renaming the root node to "Series" and moving it's children to "Book 1" and then starting new Book nodes in the Series. From a programming point of view, its just easier to display the root node, although we do have to make functionality exceptions when the user has clicked on it.
"Do you want to see the root node?" No. It does not do anything. It takes up space and adds more lines to the tree that show no added information. You can't use it to navigate or anything. "Collapse it to hide chapters" has no purpose. We have a rule for GUIs "if it is not needed by the user, do not include it in the design (GUI). Keep it simple"
"IF" you could open multiple files at the same time, and show each tree separately in the list one above each other, then it would have a use. -Ianp5a
I know this isn't a forum, but I wanted to add a note, that I disagree with the poster.
To me, that "root node" is one of the most important features of Kabikaboo!
I can use it to View everything in the entire program file, in a nice, neat, clean and orderly fashion.
It also allows me to maintain the Backstory behind the series and keep each series as a separate child.
I feel perhaps the original poster has not used Kabikaboo enough to realize the importance of having an at-a-glance View All feature, that can allow the user to quickly find and copy the entire works into an editing program.
It only takes one line at the top of the hierarchy tree, not multiple lines as indicated in the original post.
It is a most valuable asset to the program! Please do not remove it! I NEED IT!
