I provided an example in the Birthday Party situation where the memo could be linked to a Datebook event. However, dropping ToDo list as a stand alone application completely should be considered. Instead, ToDo check lists would be much more useful if they were only embedded within memos.
By memos, I mean not only those that are linked to Datebook events but also the unlinked memos within the Memo sub application. If designed similar to Tuxcards as previously discussed, this allows us to sort memos according to our thought process and then embed within some memos, any relevent ToDo check lists. This, I would think may actually get me to use the ToDo checklist feature again for the first time in seven years! :^) --Selva --- selva r <[EMAIL PROTECTED]> wrote: > Hi Manuel, > > As a Palm os handheld user since the original Palm > came out in 1998, I have found all of it's apps > useful > except the To Do app which as you describe is not > useful in practical life due to the very reasons you > describe. > > I would fully agree with your line of thinking here. > > Furthermore, I would go on to suggest that > Checklists > should be able to be embedded within Memos using a > simple protocol similar to adding bullet lists. In > the Palm the bullet list for example is added by > doing > a diagonal stroke from top left to bottom right and > then tapping a dot. A check list item might be > added > in some similar fashon on handhelds and keyboard > shortcut within individual memos. This would allow > us > to say attach a memo to a calendar event such as > "Wife's Birthday Party". Within the memo, we could > then form a check lists as needed in free form style > as you describe. I would find this type of approach > to To Do lists rather than a generic To Do list app > which over the past seven years of Palm usage has > been > utterly useless to me. > > Regards, > Selva > > --- Manuel Renz <[EMAIL PROTECTED]> wrote: > > Hi, > > I want to write a bit about the sub task thingy > > which is still marked as > > "Debatable Feature" on > > > http://wiki.osafoundation.org/bin/view/Chandler/TasksFeatureList > > I did a quick search on this topic and here are > some > > links that may be > > interesting, too. > > > http://archive.neotonic.com/archive/osaf-design/msg/893 > > > http://archive.neotonic.com/archive/osaf-design/msg/457 > > - this link > > mostly talks about higher features > > > > So first of all you can call this feature > > "Checklist" and this is IMHO a > > better description of what we are talking about. > > Imagine you have to prepare a little party in a > few > > weeks. What sense does > > it make to have 10 different tasks which all deal > > with this party, mixed > > up wiht all other tasks? Isn't it better to have > a > > checklist? Furthermore > > I do not want to set up a project with all its > > complicated settings. > > > > Example: > > > > [ ] invitations for party > > [ ] Party - buy drinks > > [ ] buy ink for printer > > [ ] select music for party > > [ ] get tickets for cornerstone fest > > [ ] ask John for help preparing the food (party) > > > > vs. > > -[ ] buy ink for printer > > -[ ] Prepare party > > -[ ] invitations (needs ink) > > -[ ] buy drinks > > -[ ] select music > > -[ ] ask John for help preparing the food > > -[ ] get tickets for cornerstone fest > > > > and vs. > > -[ ] buy ink for printer > > +[ ] Prepare party > > -[ ] get tickets for cornerstone fest > > > > > > I know that this may be a intersection with > project > > management, but life > > consists of hundreds of little projects. > > But those everyday life projects do not need a > gant > > graph and a detailed > > costs coverage. > > > > An dependencie in the example above would be, that > > before the inviatations > > can be checked as "Done!" the "Buy ink" task has > to > > be finished. But the > > "Buy ink" task has nothing in common with the > party > > invitation, itself. > > > > The next point is, if we do not have sub-tasks, or > > better call it > > checklists, you have to mention the buzzword in > > every task title to get a > > quick overview. Or you have to set up categories, > > which in this case is > > not a practicable way to get it done, till you get > > an obsolet categorie > > when the party is over. > > > > I think a "checklist" is a more everyday life > > approach. When implementing > > this feature of course it is a sub task. > > But it is possible to provide a different UI view > > for the same feature. > > You can do it the classical way with a tree view > > and the "Sub taks" > > terminology or you do it with a "Checklist" that > > contain tasks and of > > course other "Checklists". > > Despite that it's really the same feature as it's > > available in todays > > software, the new named feature offers an easy way > > to manage your > > day-to-day projects. > > > > Okay I hope you understand what I mean. And sorry > > for my bad English. > > > > greetz & blessings > > Manuel Renz > > -- > > > ======================================================================= > > | teleware-ITS Ziegler & Renz GbR Tel: > 07144 > > - 831298 | > > | Schillerstra�e 11/1 Fax: > 07144 > > - 831250 | > > | Kirchberg / Murr eMail: > > [EMAIL PROTECTED] | > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > > > Open Source Applications Foundation "Design" > mailing > > list > > > http://lists.osafoundation.org/mailman/listinfo/design > > > > ______________________________________________________________________ > > Post your free ad now! http://personals.yahoo.ca > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > Open Source Applications Foundation "Design" mailing > list > http://lists.osafoundation.org/mailman/listinfo/design > ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
