[davidamis]

The following is my understanding of the hierarchy for actions and containers for actions of the user interface. Do I have it correct? I'm asking for two reasons. First, I want to verify terminology and what can contain what, i.e. a project can't contain a folder. Second, I'm going to write Applescripts, and need to know the constraints the UI places on containers.

Thanks,
David

Inbox
Contains: actions, groups.
Shown in sidebar
Applescript name: inbox tasks (elements of document). In Applescript, contains 'inbox task'

Library
Contains: projects, folders, single-action lists
Shown in sidebar
Applescript name: sections (elements of document)

Section (Applescript only)
Section is an abstraction that can contain folders or projects
Contains:projects, folders, single-action lists
Applescript name: section

Folder
Contains:projects, folders, single-action lists, sections (Applescript only)
Shown in sidebar
Applescript name: folder

Single-Action List AKA Shoebox, SAL
Contains: actions, groups
Shown in sidebar
Applescript name: project, with 'singleton action holder' property set to true

Project
Contains: groups, actions
Shown in sidebar
Applescript name: project

Group AKA Action Group
Note: don't confuse group with grouping
Contains: actions, groups
Not shown in sidebar
Applescript name: task, inbox task (if in the inbox). The tasks element is not empty, i.e. it has subtasks.

Action
Contains: nothing
Not shown in sidebar
Applescript name:task, inbox task (if in the inbox). The tasks element is empty.