![]() a few tags for different priorities, a few tags for different contexts, a few tags for different "statuses" like Next, Waiting etc - then your grouping and sorting ("group by Tag" ) obviously will not work Grouping and sorting: Since it has no other parameters than the "tags", and if you then use tags for absolutely everything you want parameters for - e.g.no priority, no energy, no duration, no nothing built in). In fact it has no other task "parameters" than tags and the "due date" (e.g. I would have to use tags (aka contexts) to implement workarounds for separating Next, Waiting, Someday, Calendar, Tickler etc. I would also need to devise my own workaround for "real" due dates (aka "deadline" dates), if I were to decide not to manage those manually by simply writing the deadline date, if any, in the task name. Dates: It has only one date, called "due date", which seems to be intended by the developer as a "do date" (aka calendar action date, e.g an appointment etc), which is not what I need most in my app, which means I would have to devise a workaround for using this date as what I really need most, which is a GTD tickler date (aka "start date", i.e. ![]() But there are a few things that I find it very hard to accept, perhaps mainly: It seems appealing and powerful in many, many ways.
0 Comments
Leave a Reply. |