Graham Perrin wrote:
> Owen-2 wrote:
>> As an example, in RTM I created a task-list and planned a tentative
>> project, task by task, without knowing when, I would actually be able to
>> do it. These were all effectively notes, which I turned into tasks when I
>> found a slot into which I could schedule the project.
>>
>
> For that type of activity: in Chandler I would probably create at least one
> collection per project.
Which begs a bit of question.
Would it be possible to work towards a situation where collections could
contain both tasks and more collections ?
Your WORK collection might then contain
Task: Annual Review
Task: See ICT about new laptop.
Collection: Water Source Heat Pump Project
Collection: City Energy Project Development
etc. It wouldn't be a bad thing if collections could be fully recursive.
Certainly having your 'Work' and 'Project' collections at the top level
seems to be limiting.
Cheers, J/.
--
John Beardmore, MSc EDM (Open), B.A. Chem (Oxon), CMIOSH, AIEMA, MEI
Managing Director, T4 Sustainability Limited. http://www.T4sLtd.co.uk/
Energy Audit, Carbon Management, Design Advice, Sustainable Energy
Consultancy and Installation, Carbon Trust Standard Registered Assessor
Phone: 0845 4561332 Mobile: 07785 563116 Skype: t4sustainability
_______________________________________________
[email protected] mailing list
unsubscribe here: http://lists.osafoundation.org/mailman/listinfo/chandler-users
Chandler wiki: http://chandlerproject.org/wikihome
