The overhead the user has to incur to create subtasks. If folders are used to create the hierarchy, the user must first create a folder to hold the subtasks for "Pick up cleaning" and then enter the two subtasks. I'd rather just directly create a subtask because that eliminates the step to create a folder. Viewing will also be cleaner because you never the a folder obscuring the subtasks. Chris Withers wrote:
Greg Gehrich wrote:
I want to be able to create content and then attach sub-content to it. For example, if tasks were the content, it would look like the following:
go shopping get bananas get bread pick up cleaning get shirt get pants clean house clean kitchen clean mixer clean clean sink clean bedroom
I don't want to have the overhead of creating and sifting through folders as you navigate the hierarchy. In order to do this, I need the ability to have content that has folderish properties allowing sub content.
What overhead is this?
I'd do this as nested ordered folders and use the ZMI to manage it all, unless there are other hidden requirements here...
Chris